Build a citation you can explain

Opening problem

A brief quotes a witness at a hearing and calls the statement Congress's command. Another cites a bill number without identifying the Congress or the bill version. The documents are real kinds of sources, but the draft's characterization and identification are incomplete.

Learning objectives

Distinguish enacted legislation from bills and legislative history; identify Congress/session and version; cite reports and hearings with pinpoints; recognize tax-source categories; and keep the legal significance of specialized material separate from its format.

Bills and enactments

A bill is proposed legislation. Its number recurs across different Congresses or sessions, and its text may change during consideration. Collect chamber, bill number, Congress/session, date or version, and relevant section. The version introduced, reported, passed by one chamber, or enrolled can differ. Cite the version inspected.

Once a federal bill is enacted, a proposition about the law ordinarily uses the statute or session-law source. A bill citation can still identify legislative history when that history is the subject. Do not make a proposal sound enacted by omitting its status. Do not assume a bill became law because a database page has a polished summary.

Read the legislative prefix

The chamber prefix identifies the type of measure. H.R. identifies a House bill; it is not the ordinary abbreviation for a House simple resolution. The following forms follow the distinctions in the U.S. Senate's official Key to Legislative Citations, with spacing normalized for this handbook's citation typography.

Keep the measure's actual type when recording its number. A joint-resolution number must not become a bill number during abbreviation cleanup. Likewise, a chamber's adoption of a resolution must be described by its actual status; do not infer an enacted statute from the word passed alone. The measure type, Congress, version, and actual status together identify what happened.

Annotated training model

Fictional training example — not legal authority. Supplied bill packet: Harbor Notice Bill, H.R. 9000, 119th Congress, introduced in 2025, section 3(b). The entire bill and its number are invented for training.

Harbor Notice Bill, H.R. 9000, 119th Cong. § 3(b) (2025).

A training citation can teach field order without claiming the fictional bill existed. For real research, Congress.gov, GovInfo, and the relevant legislature's official records can supply actual text and status. Access those records rather than guessing missing version history.

Session laws

Federal enacted legislation can be identified by public-law number and Statutes at Large volume/page information, with a section pinpoint when necessary. A public-law number contains Congress and sequential enactment information; it is not the same as a bill number. A code citation identifies a different organization of the law. When the provision is uncodified or the amendment as enacted matters, session laws may be the necessary source.

State session-law formats vary. The state reference table supplies edition-specific publication names and templates. A chapter number, session year, and page can each perform a different identifying function. Preserve the required fields and check local style. Never convert all session-law numbers into federal public-law syntax.

Reports and hearings

A committee report normally has chamber/report designation, Congress/report number, at-page pinpoint, and publication year. A conference report may need that status identified. A hearing normally identifies its title, relevant bill if any, committee/subcommittee, Congress or session, page, publication year, and speaker attribution where useful.

Fictional training example — not legal authority. Packet: fictional H.R. Rep. No. 119-500, page 12, 2025, states the committee's reason for a notice proposal. Training citation: H.R. Rep. No. 119-500, at 12 (2025). A sentence describing the report should attribute the explanation to the report or committee. It should not say the statute commands that result unless the enacted text supplies it.

At a hearing, speakers can disagree. A witness's statement is not necessarily the committee's view. A committee's view is not automatically the whole legislature's enacted command. Identify the source's author and status before using legislative history to interpret law. This handbook does not resolve all doctrinal controversies about legislative history's weight.

Tax-source orientation

Distinguish the Internal Revenue Code, Treasury regulations, revenue rulings, revenue procedures, Treasury decisions, and private letter rulings. The current Internal Revenue Code can be identified as I.R.C. or as title 26 of U.S.C. Historical versions require appropriate version information. Treasury regulations use their own Treas. Reg. pattern, with temporary regulations identified as temporary.

Revenue rulings and revenue procedures use document numbers and bulletin locators. A private letter ruling has a ruling number and precise date. These categories have different legal functions. A citation to one does not establish that it can be relied on by every taxpayer or for every transaction. Source-specific tax research must verify the document, its status, and the applicable reliance restrictions.

The tax section teaches source classification and citation fields, including a verified historical statutory limit on precedential use below. It does not decide a taxpayer's liability or the treatment of a particular transaction. The reference section labels its source conventions by edition; apply the publication and reliance rules relevant to the actual instrument and period being researched.

Short forms and document stability

Legislative and administrative materials permit source-specific shorter references where identification remains clear. Maintain the distinguishing report/bill/regulation information rather than using an unexplained number. Id. requires a single immediately preceding source. An eligible supra reference must meet source-specific conditions; it is not a universal primary-source shortcut.

Keep a stable record of legislative versions and the pages used. A webpage's latest version can replace the text you initially inspected. An archived official PDF with a version label is easier for a reviewer to compare against your sentence than an unrecorded mutable summary.

Common mistakes and repairs

Compact reference

Bill: chamber/number + Congress/session + provision + date/version. Report: chamber/report number + Congress + pinpoint + year/status. Hearing: title/committee/body + page + date + speaker where needed. Tax: classify the instrument before selecting its specialized locator.

Worked editing session: attribute legislative statements

Fictional training example — not legal authority. A packet contains four statements about notice: an introduced bill proposes ten days; a committee report recommends fourteen; a hearing witness favors thirty; and the enacted text requires fourteen. The witness's statement appears on hearing page 31. The report's recommendation appears on report page 12. No other publication identifiers are supplied.

The draft reads, “The legislature required thirty days because the hearing established that period.” Two claims are wrong. The enacted number is fourteen, and the hearing statement belongs to a witness. A useful correction begins: “The witness advocated thirty days, while the committee recommended—and the enacted text required—fourteen.” Attach the hearing locator to the witness clause, the report locator to the committee clause, and the enactment locator to the enacted requirement. A single hearing citation at the end would not support all three statements.

Now consider the explanation: “The legislature chose fourteen days because thirty would be costly.” The numerical sequence alone does not establish that reason. If the report gives the cost explanation, attribute it to the committee. If only the witness discusses cost, preserve that attribution. Agreement between a report's recommended number and the enacted number does not prove adoption of every reason in the report.

A hearing volume may contain prepared testimony, live testimony, exhibits, and later written responses. A witness can qualify a prepared position during questioning. Identify the particular contribution and page you use. To compare the positions, cite both locations and explain the qualification; do not select whichever passage gives the simplest account while presenting it as the witness's entire position.

Legislative history becomes more useful when each citation answers a defined question: what words were proposed, who recommended a change, what reason a speaker gave, or what text was enacted. Those questions may require adjacent documents, but they do not require merging the documents' voices.

A verified enactment: read the session law itself

The 1966 enactment commonly associated with the Freedom of Information Act is identified as Pub. L. No. 89-487, 80 Stat. 250 (1966). Its opening identifies the enactment as amending section 3 of the Administrative Procedure Act. Its closing provision says the amendment becomes effective one year after enactment, and the approval line gives July 4, 1966. The enactment's original effective-date language is on page 251. Pub. L. No. 89-487, 80 Stat. 250, 251 (1966).

This example deliberately omits an optional popular name from the citation. The public-law number and official session-law coordinates identify the inspected enactment without requiring an uninspected short-title section. The bill number printed with an enacted item is legislative history information; it is not a replacement for the public-law number. The original 1966 language is also not a substitute for the later codified law when a sentence concerns another period.

The source illustrates why an enactment date belongs in one research field and an effective date in another. A writer describing the original delayed effectiveness should cite the actual provision on page 251. A writer describing the currently operative disclosure regime needs the applicable current code and amendments. A precise historical citation can be entirely correct while being the wrong source for a present-tense claim.

Advanced workshop: compare legislative versions and speakers

Fictional training example — not legal authority. The Harbor Notice Bill packet supplies three labeled versions: introduced text dated February 4, 2025; committee-reported text dated April 9, 2025; and chamber-passed text dated June 12, 2025. The introduced notice provision is § 3(b). The reported version moves it to § 5 and changes the period. The passed version retains § 5 but adds an exception. There is no enactment in the supplied packet.

A reliable comparison follows the provision rather than the number. Build a row for the notice period, another for the exception, and another for any effective-date provision. Record the section and version that supplies each entry. A comparison of “section 3” in all three files would miss the renumbering and could describe unrelated text. Likewise, the newest bill page does not prove that an earlier quotation appeared in the introduced version.

When the sentence concerns the introduced text, identify that version in the citation or accompanying words. When it concerns the difference between introduced and passed text, supply access to both versions and their separate locators. “The bill changed” is incomplete unless the reader knows the two versions being compared. “Congress enacted the change” is unsupported when the packet stops at one chamber's passage. A citation must preserve the legislative event the evidence actually supplies.

Reports and hearings require different attribution

Fictional training example — not legal authority. A hearing packet has a witness's prepared statement at printed page 18 and questioning at page 31. The witness's statement favors ten-day notice; in questioning the witness accepts fourteen days for one category. A draft quotes the broad ten-day recommendation without mentioning the later qualification and says the committee rejected fourteen days. Neither the speaker nor the claimed committee action matches the source.

Begin the repair with attribution: identify the witness and whether the passage is the prepared statement or the answer given during questioning. Read the qualification before summarizing the witness's position. If the sentence concerns the committee's position, obtain the relevant report, vote, or other actual committee record. The hearing title does not make each witness's view the committee's view.

A full hearing citation must give enough information to recover the hearing: title, bill if relevant, committee or subcommittee, Congress or legislative session, publication year, and page. A speaker parenthetical can distinguish the cited contribution. Use the printed hearing page, which may differ substantially from the PDF sheet because of covers, front matter, and appendices. If the only available source is a separately posted witness statement, cite that actual document rather than pretending to have inspected a paginated hearing volume.

For committee reports, preserve the chamber and the Congress-report sequence. A conference-report parenthetical describes the report's status, not the preceding bill's passage. If the report is reprinted in another publication, record which version supplies the pinpoint; do not combine one publication's identifying number with another publication's pages without a clear parallel reference. These details let the reader recover the same text and assess whose explanation it contains.

A verified tax-source limitation

The inspected 2024 Code restricts the precedential use of written determinations unless the Secretary establishes otherwise by regulation, while preserving the stated treatment of determinations concerning subtitle D taxes. 26 U.S.C. § 6110(k)(3) (2024). This is an example of a restriction found in the statutory text itself. It is not a conclusion about the permissible use of any particular ruling in an actual dispute.

The subdivision shows why “an IRS document says so” is too broad. First classify the document. Then check the applicable reliance rules and the specific instrument's status. A revenue ruling, revenue procedure, private letter ruling, and Treasury decision require different identifying fields and can serve different functions. The fact that a document is publicly accessible does not answer how it may be used as authority.

The historical publication guidance includes the Cumulative Bulletin, Internal Revenue Bulletin, and older Treasury decision collections. Use that guidance to recognize existing citations. For a newly obtained instrument, inspect its actual official publication and identifiers rather than inventing a Cumulative Bulletin locator from an older model. Preserve a temporary regulation's Temp. Treas. Reg. designation where supplied, and distinguish the instrument's issuance date from the date of the statutory transaction being analyzed. The citation identifies the source; the relevant tax period and reliance question still have to be matched to it.

Source laboratory: follow the definition before describing the command

The title Plain Writing Act of 2010 suggests a broad subject. It does not tell you which documents the enacted command reaches. The three-page public law provides a complete source-reading exercise: a definition on the first page, an operative requirement on the second, and enforcement language spanning the second and third.

Start with the proposed sentence: “The Act requires every federal regulation to be written plainly.” Section 3(2)(C) expressly excludes a regulation from the defined term covered document. That exclusion defeats this sentence as a description of this Act's covered-document requirement. A citation to the Act's title or purpose cannot repair the overstatement. The reader must follow the defined term into the operative provision.

Section 4(b) directs agencies to use plain writing in covered documents they issue or substantially revise, beginning no later than one year after enactment. Section 3(2)(A)–(B) supplies the included categories and section 3(2)(C) supplies the exclusion. A carefully bounded historical model is: “As enacted, the Act directed plain writing in newly issued or substantially revised covered documents after its specified implementation period; its definition excluded regulations.” Plain Writing Act of 2010, Pub. L. No. 111-274, §§ 3(2), 4(b), 124 Stat. 2861, 2861–62.

The full citation begins with the Act's permitted short title and public-law number. Volume 124 and page 2861 identify its place in the Statutes at Large. The section locators distinguish the definition and operative provision, while the final page range tells the reader where those passages appear. The year already appears in the Act's name, so this model does not add a redundant year parenthetical. A model omitting the popular name would need the appropriate identifying year.

Now test a second sentence: “Anyone can sue to enforce that command.” Section 6 separately addresses judicial review and enforceability. Subsection (a) bars judicial review of compliance or noncompliance; subsection (b) states that the Act creates no administratively or judicially enforceable substantive or procedural right or benefit. Those provisions are essential context if the writer discusses enforcement. They do not need to be forced into a short sentence concerned only with the definition, but they cannot be ignored while claiming the Act supplies a private enforcement route.

The lesson is a method of reading enacted language, not a survey of every source that might govern federal drafting or litigation. Other authorities may address plain language or related obligations. This example establishes what the inspected 2010 enactment says. To make a present-tense claim about a particular agency and document, extend the research to the relevant current authorities and facts.

Test the claim chain. Mark the defined term, the command using it, the relevant timing provision, and any remedy or enforcement language necessary to your sentence. Give each proposition its own locator. A legislative title helps you find a subject; these linked provisions determine the reach of the sentence you can responsibly write.

Takeaway

Legislative and specialized sources need identification and status. Attribute the statement to the document that actually makes it.

Chapter source note

Citation conventions draw on The Indigo Book 2.0, R16, R20–R22, T1, and T4–T5. Legislative prefixes follow the official Senate Key to Legislative Citations, entries 1–8, checked October 8, 2026; it resolves inconsistent House-resolution forms in Indigo R21.1.

Historical examples use Pub. L. No. 89-487, 80 Stat. 250–51 (1966); 26 U.S.C. § 6110(k)(3) (2024), printed page 3491; and the Plain Writing Act of 2010, 124 Stat. 2861–63, especially §§ 3(2), 4(b), and 6. The examples concern those inspected texts, not a survey of later amendments. All Harbor legislative and tax packets are fictional.