51. Legislative Materials: Attribution, Stage, and Source Form

51.1 Identify the legislative object before interpreting it

The same policy phrase can appear in a bill, amendment, committee report, prepared witness statement, floor speech, or enacted law. Those appearances have different authors and procedural settings. A reference that supplies only the policy title and a year can conceal the difference. Citation Code's house construction begins with the object: “bill, introduced version,” “committee report, minority views,” or “hearing testimony of named witness.” The writer then identifies the legislature, session, document number, version or event date, and pinpoint needed to retrieve that object.

Use a record with separate fields for document author, speaker, issuing institution, legislative stage, version date, publication date, and passage location. The committee that convened a hearing is not necessarily the author of a witness's views. The publisher of the hearing volume is not its legislative speaker. A bill's sponsor and a report's institutional author can likewise differ. These distinctions should be made before the prose attributes a purpose, recommendation, or criticism.

GovInfo's congressional bill guide distinguishes published bill versions and provides version-specific retrieval fields. Its congressional collections also provide separate routes for hearings, reports, and the Congressional Record. Those distinctions support the research architecture used here; they do not determine the interpretive weight of a particular statement. Congressional bills guide; congressional hearings guide; congressional reports guide; Congressional Record guide.

All six legislative packets below concern the fictional Training Assembly. TRAIN identifiers never denote an actual congressional bill, report, hearing, or enacted law. The completed references use Citation Code's teaching construction. The legal weight of legislative history in an actual tribunal requires the applicable law and a source-specific analysis beyond the citation itself.

51.2 Packet L1: Introduced and reported versions differ

Supplied packet. The Training Assembly's 14th Session considered the Records Access Bill, TRAIN-BILL-L1. The introduced version, February 2, 2026, § 6(a), allowed five days to acknowledge a request. The reported version, March 6, § 6(a), allowed seven days. A later enacted document, TRAIN-ACT-L1, adopted a different structure at § 9 and allowed eight days. The writer's task is to describe what the committee's reported bill proposed, not what ultimately became law.

Completed sentence and reference: “The reported bill proposed a seven-day acknowledgment period. Records Access Bill, TRAIN-BILL-L1, 14th Training Assembly Session, § 6(a) (reported version, Mar. 6, 2026).” The phrase “proposed” and the version label work together. They prevent the reference from making the reported language look operative merely because an act bearing a similar title later existed.

For a comparison, write: “The introduced text used five days; the reported text used seven. TRAIN-BILL-L1 § 6(a) (introduced version, Feb. 2, 2026); TRAIN-BILL-L1 § 6(a) (reported version, Mar. 6, 2026).” Do not abbreviate both references to “Records Access Bill § 6” in the same comparison. The short reference must retain the version distinction doing the analytical work. The enacted § 9 belongs in a separate sentence if the argument also addresses the final text.

51.3 Packet L2: Committee explanation and minority views

Supplied packet. Report TRAIN-REPORT-L2 accompanies the reported Records Access Bill. It was issued by the Training Assembly Committee on Records on March 6, 2026. The committee explanation at pages 8–9 says the proposed acknowledgment period permits initial file identification. Minority views signed by Training Members Vale and Ives at pages 24–25 criticize the period as too short. The report's table of contents labels those portions distinctly. The draft says “The committee considered the period too short,” citing page 24.

Completed construction: “The report's minority views criticized the proposed period as too short. Vale & Ives, Minority Views, in Training Assembly Committee on Records, TRAIN-REPORT-L2, at 24–25 (Mar. 6, 2026).” A separate statement about the committee explanation should cite “Training Assembly Committee on Records, TRAIN-REPORT-L2, at 8–9 (Mar. 6, 2026).” The institutional report identity remains present in both forms, but the named authorial component changes.

If the subject of analysis is disagreement within the report, use both references and explain the disagreement in prose. Do not merge the two passages into an unattributed quotation. The report number retrieves the volume; the component title and author identify the perspective; the pages find the passage. This three-level construction also works for additional, dissenting, or supplemental views when those labels actually appear in the source.

51.4 Packet L3: Prepared statement and oral answer

Supplied packet. Hearing TRAIN-HEARING-L3 occurred before the Training Assembly Committee on Records on February 20, 2026. Witness Nia Mercer submitted a prepared statement printed at pages 30–35. Page 32 estimates an average retrieval time of four days. During questioning, printed pages 71–72, Mercer clarified that the estimate excluded off-site files. The hearing volume was published April 4. The draft quotes the four-day estimate while describing it as the committee's factual finding.

Completed construction: “Mercer's prepared statement estimated four days for the covered files, and her oral answer excluded off-site files from that estimate. Nia Mercer, Prepared Statement, TRAIN-HEARING-L3, at 32 (hearing Feb. 20, 2026); Nia Mercer, Testimony, TRAIN-HEARING-L3, at 71–72 (hearing Feb. 20, 2026).” The source record also retains the volume's April 4 publication date. The hearing date identifies the event; the publication date identifies a later publication fact.

The citation should not imply that a prepared statement was spoken verbatim at the hearing. If an audiovisual record is used instead, cite the recording and timestamp and verify the words there. A printed question-and-answer transcript, a submitted statement, and a recording can document related but nonidentical material. In the packet's final reference list, expand TRAIN-HEARING-L3 to its committee and full title once so repeated citations remain compact without concealing the convening body.

51.5 Packet L4: A floor statement with an inserted attachment

Supplied packet. The Training Assembly's Proceedings for March 18, 2026, volume TRAIN-PROC-14, records Member Rowan's remarks at pages P410–P411. At P412–P414, the publication reproduces a letter from the fictional Records Users Association submitted for inclusion. The letter says small offices lack scanning equipment. Rowan's remarks thank the association but do not repeat or expressly adopt every claim. The draft attributes the equipment statement directly to Rowan. The letter is dated March 15, 2026; its equipment statement appears on printed page P413.

Completed construction: “The association's inserted letter stated that small offices lacked scanning equipment. Records Users Association, Letter to Member Rowan (Mar. 15, 2026), reprinted in TRAIN-PROC-14, at P413 (Mar. 18, 2026).” If the proposition instead concerns Rowan's act of submitting the letter, cite Rowan's remarks at P411 and describe that event. The insertion date and the letter date perform different functions and both belong in the full reference.

The publication's chamber or section prefix is part of the locator. Retain P413 rather than reducing it to 413 when the prefix distinguishes this portion of the volume. If a later bound edition repaginates the proceedings, verify the corresponding page before changing editions. The source record can link the two manifestations, but a letter's presence in a legislative publication does not change the identity of its author.

51.6 Packet L5: Amendment proposal, vote, and resulting text

Supplied packet. Amendment TRAIN-AMEND-L5, offered March 19, 2026, proposed replacing the reported bill's seven days with ten days. The amendment sheet contains that proposal at line 4. The training journal at page J88 records that the amendment was not adopted. The next engrossed bill, dated March 20, retains seven days. The writer wants to show that ten days was proposed and rejected during the training process. The supplied journal entry is dated March 19, 2026.

Completed construction: “An amendment proposed ten days, but the recorded vote did not adopt it. TRAIN-AMEND-L5, line 4 (Mar. 19, 2026); Training Assembly Journal, 14th Session, at J88 (Mar. 19, 2026). The supplied engrossed bill retained seven days. TRAIN-BILL-L1 § 6(a) (engrossed version, Mar. 20, 2026).” Each proposition has the source that establishes that particular step.

A citation to the amendment sheet alone cannot establish the vote outcome. A citation to the journal alone may establish the outcome without exposing the proposed words. A citation to the engrossed text establishes its wording but does not necessarily explain why the proposal failed. The completed construction therefore uses three source objects. It does not infer the collective reasons of the voting members from the failure itself; any asserted reason would require additional support and careful attribution.

51.7 Packet L6: Explanatory statement versus adopted text

Supplied packet. A training conference committee issued Joint Explanatory Statement TRAIN-EXPL-L6, April 1, 2026. Page 12 describes an eight-day period intended to accommodate weekends. The enrolled training bill, TRAIN-BILL-L1-ENR, § 9, uses “eight calendar days.” The enacted TRAIN-ACT-L1 § 9 uses the same words. No source in the packet says that weekends are excluded. A draft reads “The act allows eight business days,” citing the explanation. The supplied enactment is dated April 9, 2026.

Completed construction: “The enacted packet text specifies eight calendar days. TRAIN-ACT-L1 § 9 (Apr. 9, 2026). The joint explanation discusses accommodating weekends but does not change the supplied statutory words. Joint Explanatory Statement TRAIN-EXPL-L6, at 12 (Apr. 1, 2026).” The construction identifies the operative text and separately attributes the explanation. It does not silently replace “calendar” with “business.”

When quoting the explanatory statement itself, use its document title and page rather than citing the act as though the quoted sentence appears there. When comparing enrolled and enacted text, preserve their distinct identifiers even if the relevant wording matches. That matching comparison can support a narrow statement about the supplied documents. It cannot by itself establish every procedural requirement of enactment or every rule governing interpretation in a real legislature.

51.8 Create a legislative source map

A useful source map has one row for each proposition, not merely one row for each downloaded PDF. For L3, “Mercer estimated four days” points to prepared statement page 32; “the estimate excluded off-site files” points to testimony pages 71–72. A single row called “hearing” would fail to preserve the distinction. For L5, the proposed text, vote result, and resulting bill wording require separate rows even though they concern one amendment.

Name the action in the prose before choosing an explanatory parenthetical. “Proposed,” “reported,” “testified,” “submitted,” “criticized,” and “enacted” communicate different events. A parenthetical should refine an already accurate statement, not rescue a sentence that assigns words to the wrong author. When a source contains no evidence of adoption, approval, or agreement, do not infer those events from inclusion in an official publication.

The final review should test date and role conflicts. A hearing date later than the cited prepared statement is possible; a publication date later than both is also possible. Those dates need labels, not forced uniformity. An explanatory report may refer to a bill section that moved before enactment. Keep the report's original section reference in a quotation while explaining the final location in the surrounding prose. The goal is a traceable account of the actual source sequence, not a retroactive rewriting of every historical source to match the final statute.