How to Research a Statute: The Five-Step Workflow

Researching a statute runs in five steps, in order: find the current version (on an official source with a currency line, not the top Google result), read it in context (definitions, cross-references, effective dates), find the cases interpreting it (annotations, or their free equivalent), check the regulations implementing it, and pull legislative history only when the text leaves a real ambiguity. Each step exists because the one before it is not enough on its own.

This is a different discipline from researching case law, where the unit of work is an opinion and the question is precedent. With a statute, the text is the law — but the text you found may be superseded, defined out from under you, narrowed by a court, or fleshed out by a regulation you have not read. The five steps close those gaps one at a time. If you do not yet know which statute governs, spend twenty minutes in a treatise or practice guide first: a good secondary source hands you the section numbers and saves an hour of keyword guessing.

The five steps at a glance

Step 1 — Find the current version, not the Google version

Statutes are published in stages. A newly enacted law appears first as a slip law, then in the session laws — the chronological record of everything the legislature passed that session — and finally gets integrated by subject into the jurisdiction's code, per the Georgetown Law Library's statutes guide. You research in the code, because the code is the integrated, current arrangement. The problem is that the internet is full of copies of codes that are not current.

Search a section number and the top results are often aggregator sites carrying a snapshot of the code frozen at whatever year it was scraped, with no statement of currency and no notice of later amendments. The text looks authoritative because statutory text always looks authoritative. The fix is a habit, not a subscription: go to the official source and read its currency line before you read the section.

For federal statutes, the official source is the Office of the Law Revision Counsel at uscode.house.gov. Its currency page is one sentence long: the Code is current through a named public law, with the date that law was enacted. Read that sentence before you read your section, and copy it into your research notes — it is the version stamp on everything you are about to quote. Then look at the section itself: if any later-enacted law affects it, a Pending Updates list appears with the public law numbers, and the classification tables map each new law to the sections it touches. For state statutes, use the legislature's or revisor's own site, find its equivalent currency statement, and run your section through the current session's enacted bills, because a law passed two months ago may not be codified yet.

It is also the check a research tool should be doing for you. CaseRead fetches statutes and regulations at request time, from every US jurisdiction, so the version quoted in an answer is the current one, cited — not a training-data memory of the section.

Step 2 — Read it in context: definitions, cross-references, effective dates

A statutory section is a node in a structure, and three parts of that structure change meanings.

Definitions. Nearly every act or chapter opens with a definitions section ("As used in this chapter..."), and a defined term means what the definition says, not what the word usually means. Read your section, list every term that carries weight, and check each against the chapter and title definitions before you rely on plain meaning. The Boston College Law Library's research checklist puts it simply: read provisions carefully, including nearby definitions and exceptions.

Cross-references. "Except as provided in section 407" and "notwithstanding any other provision" are load-bearing. Open every cross-referenced section. Statutes on one topic cluster in the same chapter, so skim the table of contents around your section — the exception that swallows your rule is usually within a few section numbers.

Effective dates. The code tells you what the law says; the session law tells you when it started saying it. A federal statute takes effect on its date of enactment unless it provides otherwise, per the Congressional Research Service's guide to reading federal legislation, and acts routinely do provide otherwise. States set their own defaults: Minnesota gives most new laws an effective date of the August 1 after final enactment, with appropriations running from July 1, under Minn. Stat. § 645.02. The history note after your section lists each amending law. If your facts straddle an amendment, pull the session law and read its effective-date section before anything else — a limitations period that changed between accrual and filing is the classic trap, and it is why our Utah statute of limitations guide leads with dates rather than durations.

One federal wrinkle belongs in your notes: only some titles of the U.S. Code have been enacted into positive law. For those titles, the Code text is the law — legal evidence in every federal and state court. The rest are prima facie evidence of the law, and if the Code and the Statutes at Large ever disagree, the Statutes at Large control. It comes up rarely. When opposing counsel raises a text discrepancy, it is the rule in play.

Step 3 — How do you find cases interpreting a statute?

The words of a statute mean what the courts of that jurisdiction have held they mean. A term you read one way may have thirty years of contrary construction behind it, which is why no statutory read is finished until you have looked for the interpreting cases.

The traditional tool is the annotated code — West's U.S.C.A., Lexis's U.S.C.S., or a state equivalent — which appends editor-written summaries of the cases construing each section, sorted by issue (West calls them Notes of Decisions). If you have Westlaw or Lexis, start there.

If you do not, run a citation search. CourtListener, the nonprofit Free Law Project's search engine, holds more than nine million decisions, and the Library of Congress includes it in its guide to free case-law research. Search your section's citation as a quoted phrase. This is full-text search, not a curated annotation service: it surfaces opinions that quote the citation in a form you searched, so search the variants courts actually write — "§ 78B-2-307" and "78B-2-307," with and without the title number. Filter to your jurisdiction and read the highest court's cases first. It is slower than Notes of Decisions and it will not sort holdings by issue, but the opinions are there. From here the work becomes ordinary case-law research — our guide to that process picks up where this step ends, and sorting binding constructions from persuasive ones is the controlling-authority question. The rest of the no-subscription stack is in our roundup of free legal research tools.

Step 4 — Check the regulations implementing it

Statutes delegate. The legislature sets the rule; an agency fills in the deadlines, forms, thresholds, and procedures — and those details bind. If the statute mentions an agency, a permit, a filing, or "as the Secretary shall prescribe," there are regulations, and your research is not done until you have read them.

For federal law, read them on the eCFR, which the National Archives describes as an unofficial editorial compilation updated daily and generally current within two business days. It is not the official annual edition, but for knowing what the rule says today it is the right tool. To get from statute to regulation, work the authority trail: every CFR part cites the statute it implements in its authority note, so search your U.S. Code citation in the eCFR's full text to find the parts that rest on it. Then check the Federal Register for proposed or final rules not yet codified. States run the same two-layer system through their administrative codes, usually published by the secretary of state or the agency itself.

Step 5 — When does legislative history matter?

Less often than the hours spent on it suggest. If the text, read with its definitions and neighboring sections, answers the question, most courts will not care what a committee hoped it meant — and some judges give legislative history no weight at all. Reach for it when a genuine ambiguity survives steps one through four and decides your issue, or when you need to explain what problem an amendment was solving.

The mechanics are short. The history note after your section lists the public law (or state chapter) numbers for the original act and each amendment. Take the public law number to congress.gov for the bill, its committee reports — generally the most persuasive legislative-history materials — and the floor record; the Marquette Law Library's step-by-step guide walks the full compilation. The enacted text itself lives in the Statutes at Large on govinfo.gov. For state statutes, the trail runs through the legislature's bill-tracking site, though depth varies wildly by state.

The workflow, without the tab explosion

Five steps, four websites, zero subscriptions. What the workflow costs is attention: currency lines copied down, definitions cross-read, citations run through a second database, authority notes chased into the CFR. That attention is what CaseRead carries — it searches your firm's own files and the public law together, fetches statutes and regulations current at request time across every US jurisdiction, and cites only what it actually retrieved, with every citation linked to its text.

When the statute lands in a brief, verify it the way you would verify case citations: paste the draft into the free Hallucination Shield to confirm every cited authority is real and says what you claim, no signup required. If you want the current-version discipline built into the research rather than bolted on at the end, that is the rest of CaseRead — free tier included.

Frequently asked questions

What is an annotated statute? An annotated statute is a code section published with editorial additions: summaries of the cases that have interpreted it, its amendment history, cross-references, and pointers to secondary sources. West's U.S.C.A. and Lexis's U.S.C.S. are the federal annotated codes, and most states have an annotated version of their code. The statutory text is identical to the unannotated official code; the annotations are what you are paying for. The free substitute is searching the statute's citation in a case-law database like CourtListener.

How do I find the current version of a statute? Go to the official source and read its currency line. For federal statutes, uscode.house.gov states the exact public law the Code is current through and lists pending updates for sections affected by newer laws. For state statutes, use the legislature's or revisor's own site and find its equivalent currency statement, then check the current session's laws for amendments not yet codified. Avoid relying on a search engine result: aggregator copies of codes are often snapshots frozen at whatever year they were scraped.

What is the difference between a statute and a regulation? A statute is enacted by a legislature. A regulation is issued by an agency under authority a statute delegated to it, and it fills in the operative detail the statute left open — deadlines, forms, thresholds, procedures. A regulation cannot exceed its statutory authority, but within it, regulations bind. Federal regulations are codified in the CFR and are best read on the eCFR, which is updated daily; states publish their own administrative codes.

What is the difference between session laws and a code? Session laws are the laws of a legislative session published chronologically, each exactly as enacted. A code takes those same laws and arranges them by subject, integrating amendments into a single current text. You research in the code because it reflects the law as it stands, but the session law remains the authoritative record of what passed — it is where effective dates, transition rules, and uncodified provisions live. For titles of the U.S. Code enacted into positive law, the Code text is itself the law; for the rest, the Statutes at Large control if the two conflict.

When should I use legislative history? Only when the statutory text, read in context with its definitions and related sections, leaves a genuine ambiguity that decides your issue. Courts differ on how much weight it deserves, and committee reports are generally treated as the most persuasive materials. The mechanics: take the public law number from the statute's history note, pull the bill and its committee reports on congress.gov, and pull the enacted text from the Statutes at Large on govinfo.gov.