14. Work Across Law School and Practice

14.1 First-year research and writing

Use early assignments to learn the relationship between a sentence and its support. Keep a proposition list beside the draft. For each legal rule, identify the authority, the relevant passage, and the facts or procedural setting that limit its use. For each material factual statement, identify the source in the assignment record.

Follow the assignment's prescribed style and source limits. A closed-universe exercise tests work with a defined packet; adding outside authority can violate the assignment even if the authority is real. A research memorandum may ask for an objective assessment rather than an advocacy presentation. Citation choices should fit that task.

Before submission, explain one citation aloud: what each component identifies, where the reader will land, and why the source supports the sentence. If you cannot explain those points, the citation is not ready merely because its punctuation looks familiar.

14.2 Journal and seminar work

Long scholarly projects require version control. Assign each source a stable internal record and track the approved short form. Record whether the cited passage was checked against a scan, a final publication, or another version. When an editor changes the proposition, revisit the support rather than approving the old citation by habit.

A journal cite-check should separate retrieval, quotation verification, substantive support, and house-style review. The same editor may do several tasks, but the record should show which tasks were completed. A technically polished footnote may still depend on an unread source.

For a seminar paper, retain the search and selection method when making empirical claims. “Most courts” is a claim about a population, not a synonym for “the cases I happened to find.” A convenience sample needs to be described as such. A literature review should explain its scope without pretending to be exhaustive.

14.3 Moot court and clinics

Moot court records often supply artificial names, dates, and record pagination. Treat the packet as the assigned source and distinguish it from real-world authority. Do not allow a fictional citation from a problem to enter a reusable real-case database without a clear label.

In clinics, source handling intersects with client work. Use the authorized matter system for client documents, preserve confidentiality, and follow supervisory requirements. A citation exercise may be low stakes; a filed assertion about a client's record is not. Review the actual final submission, including attachments and redactions.

Build habits that transfer: record the governing instructions, identify the source, locate the passage, check the support, and verify the final form. The document changes; the method remains useful.

14.4 Practice teams and reusable work product

An old brief can be a starting point, but its citations belong to the time, forum, facts, and version of law for which it was written. Reusing the prose without rechecking those elements can carry old defects into a new matter.

Maintain reusable research notes with a “last substantively checked” date and a statement of scope. Distinguish a formatting update from a legal update. Fixing italicization does not justify changing the substantive review date.

When a team shares research, assign ownership of unresolved questions. A note saying “check this” becomes useful only when someone is responsible for the check and knows what would resolve it. Before filing, identify which unresolved issues affect the representations in the document.

14.5 Make feedback reusable

Classify corrections by cause: wrong source, wrong version, wrong locator, overstated support, ambiguous short form, or presentation mismatch. This makes feedback useful beyond the corrected line. A student who repeatedly confuses PDF pages with printed pages needs a locator habit, not another memorized punctuation rule.

Keep a brief personal correction log. Include the error, the reason, and the check that would have caught it. As the same pattern disappears from later work, retire it from the active checklist so the checklist remains manageable.