What are you actually reading — the code or the session law?
Congress enacts session laws (public laws), which are compiled in the Statutes at Large and then arranged by subject into the United States Code. Those are not always the same text. Roughly half the titles of the U.S. Code have been enacted into positive law; for the rest, the Code is only prima facie evidence of the law, and the Statutes at Large is legal evidence that controls in a conflict. See 1 U.S.C. §§ 112, 204. In practice this matters rarely, but when a codification note flags an editorial change or a section was "transferred" or "omitted," go pull the public law on GovInfo.
Pick your source deliberately. The Office of Law Revision Counsel version at uscode.house.gov is the official text. U.S.C.A. (Westlaw) and U.S.C.S. (Lexis) reproduce the same text plus the two things you actually need: the credits line showing every amendment, and Notes of Decisions collecting cases construing the section. Read the credits line first. It tells you when the language you are reading arrived.
Then ask which version governs your facts. Statutes generally do not apply retroactively to conduct completed before enactment absent clear congressional intent, per Landgraf v. USI Film Products, 511 U.S. 244 (1994). If your client acted in 2019 and the section was amended in 2022, you need the 2019 text. Westlaw and Lexis both let you pull prior versions; use that feature rather than assuming.
How do you break a section into elements?
Find the single sentence that does the legal work — the one containing the operative verb ("shall be liable," "is guilty of," "may not," "is entitled to"). Everything else in the section is definition, exception, remedy, or enforcement mechanism.
Diagram that sentence into numbered elements, and write them out. For 42 U.S.C. § 1983 the elements are: (1) a person, (2) acting under color of state law, (3) subjects or causes to be subjected, (4) a citizen or other person within the jurisdiction, (5) to a deprivation of rights secured by the Constitution and laws. Each element is a separate research question. Most statutory arguments are fights about one element, and you cannot brief the fight until you know which one.
Then answer four structural questions about the section: Who is regulated? What conduct triggers liability or entitlement? What mental state, if any, is required? Who enforces it, and how? On that last question, note that a private right of action is not implied merely because a statute prohibits something — Alexander v. Sandoval, 532 U.S. 275 (2001), requires rights-creating text plus evidence of remedial intent.
What do the drafting conventions actually signal?
Statutes are drafted in a hierarchy: title, chapter, section, subsection (a), paragraph (1), subparagraph (A), clause (i), subclause (I). Use those names precisely. A brief that says "section 1(a)(2)(B)" when it means subparagraph (B) of paragraph (2) of subsection (a) is fine; a brief that misidentifies the level looks careless and can misstate the scope of a proviso.
Learn the vocabulary. "Shall" is mandatory and "may" is discretionary. "Means" introduces an exhaustive definition; "includes" is ordinarily non-exhaustive. "And" is conjunctive and "or" is disjunctive, though courts sometimes read one as the other to avoid absurdity — flag it rather than assume. "Notwithstanding any other provision of law" overrides conflicting statutes; "subject to" subordinates. The Dictionary Act, 1 U.S.C. § 1, supplies default federal rules: singular includes plural, "person" includes corporations and partnerships, and the masculine includes the feminine.
Modifier placement generates real litigation. Under the rule of the last antecedent, a limiting phrase ordinarily modifies only the noun immediately preceding it, as in Barnhart v. Thomas, 540 U.S. 20 (2003), and Lockhart v. United States, 577 U.S. 347 (2016). But when a modifier follows a parallel series and is separated by a comma, the series-qualifier canon applies it to the whole series — the approach the Court took in Facebook, Inc. v. Duguid, 592 U.S. 395 (2021). Read the punctuation as if the drafter meant it.
How far outside the sentence should you read?
Always substitute defined terms before you interpret. Definitions may sit in the same section, at the front of the chapter, or in a general definitions section for the whole title, and a chapter-specific definition displaces the ordinary meaning entirely. A statute that seems to say something surprising usually has a definition you have not found.
Then read the neighbors. Under the whole-act rule, identical words in the same act are presumed to carry the same meaning and different words to carry different meanings; see Gustafson v. Alloyd Co., 513 U.S. 561 (1995). Under the rule against surplusage, prefer a reading that gives every clause effect — a "cardinal principle" the Court restated in TRW Inc. v. Andrews, 534 U.S. 19 (2001). Structure can override an isolated phrase: in King v. Burwell, 576 U.S. 473 (2015), the Court read "Exchange established by the State" against the design of the entire statutory scheme.
Finally, check the surrounding apparatus that students routinely skip: the definitions section, exceptions and provisos, effective-date and applicability provisions, savings clauses, severability clauses, preemption provisions, statutes of limitations, and any express jurisdictional grant. These are where cases are won.
Which canons should you actually use?
Canons are tiebreakers, not starting points. Use them when the text is genuinely ambiguous after you have read the whole section in context, and use the ones a court has applied to a comparable statute. Karl Llewellyn's classic point — that canons come in opposing pairs — is still true, so never rest an argument on a canon alone.
The workhorses are few. Ejusdem generis limits a catchall to items of the same kind as the enumerated list. Noscitur a sociis reads an ambiguous word in light of its neighbors; both did the work in Yates v. United States, 574 U.S. 528 (2015), where "tangible object" in an evidence-destruction statute was read against "record" and "document" and held not to cover a fish. Expressio unius treats an enumeration as excluding omitted items. The rule of lenity resolves genuine ambiguity in criminal statutes for the defendant, and constitutional avoidance prefers a reading that does not raise serious constitutional doubt. In administrative cases, the major questions doctrine of West Virginia v. EPA, 597 U.S. 697 (2022), demands clear congressional authorization for agency action of vast economic and political significance.
Dictionaries help fix ordinary meaning at the time of enactment, and the Court uses them constantly — compare the majority and dissent in Muscarello v. United States, 524 U.S. 125 (1998), on what it means to "carry" a firearm. Use a dictionary contemporaneous with enactment, not the current edition.
Do legislative history and agency views still matter?
Yes, but with a hierarchy and a caveat. The most persuasive materials are conference committee reports, then committee reports on the enacted bill, then statements by the bill's sponsor or floor manager, then general floor debate, then hearings, then post-enactment statements (nearly worthless). Textualist judges — and much of the current Supreme Court — will discount all of it, so lead with text and structure and use history as corroboration. Bostock v. Clayton County, 590 U.S. 644 (2020), is the model: the majority resolved a major Title VII question on ordinary public meaning alone.
For agency interpretations, the ground has shifted. Loper Bright Enterprises v. Raimondo, 144 S. Ct. 2244 (2024), overruled Chevron deference; courts now exercise independent judgment on the best reading of a statute. Agency views can still persuade under Skidmore v. Swift & Co., 323 U.S. 134 (1944), in proportion to their thoroughness, consistency, and validity of reasoning. So read the implementing regulations in the C.F.R. and any agency guidance — they tell you how the statute operates in practice — but do not assume they bind a court.
State statutes work the same way with thinner materials. Many states have little usable legislative history; instead, look for official comments to uniform acts (the UCC comments are the paradigm) and for the state's own codified interpretation rules, which many legislatures enact.
How do you verify and cite what you found?
Before you rely on a section, run it through the citator. KeyCite or Shepardize the statute itself, not just the cases: that surfaces pending amendments, repeals, and — critically — holdings that the provision is unconstitutional, preempted, or has been narrowed as applied. A statute can remain on the books and be unenforceable.
Then read the Notes of Decisions for the specific subsection at issue, filtered to your jurisdiction. Circuit splits on statutory meaning are common and controlling in a way that a Supreme Court case on a different subsection is not.
For citation form, Bluebook Rule 12 governs. Federal code sections take the form 42 U.S.C. § 1983; state codes follow the Table 1 abbreviations for that jurisdiction, e.g., Cal. Civ. Code § 1542. Cite a session law as Pub. L. No. 111-148, 124 Stat. 119 (2010). The date-parenthetical convention for current code citations changed between recent Bluebook editions, so check the edition your journal or professor requires rather than copying an older brief.