52. Rulemaking Sources: From Proposal to Operative Paragraph

52.1 Separate the published notice from the codified text

A rulemaking file can contain a proposed text, explanatory discussion, public comments, a final publication, codified paragraphs, later corrections, and changes to effective or compliance dates. The same topic and docket label may appear on all of them. Citation Code's house record therefore identifies document type, issuing agency, docket, publication identifier, publication date, effective date, compliance date, and the particular component cited. Components include preamble discussion, amendatory instruction, regulatory paragraph, table, and appendix.

The Federal Register collection guide provides a route to the published issue and document. The eCFR reader aid describes its continuously updated regulatory presentation and relationship to official editions. These are complementary research routes; the writer must identify the source and temporal state actually used. GovInfo Federal Register guide; eCFR reader aid.

The six packets below use a fictional Training Water Office, TRAIN Register, and TRAIN Regulatory Code. They provide all relevant dates and expressly stated effects for the exercises. They do not purport to establish an actual agency's authority, judicial deference, procedural compliance, or a rule's validity. Their purpose is to make the source-construction decisions visible and reproducible.

52.2 Packet R1: Proposed language and final language

Supplied packet. Docket TRAIN-R1 contains a proposed rule published January 8, 2026, at 4 TRAIN Register 100. Proposed § 12.4(a), printed page 104, requires a weekly meter report. A final rule published April 8 at 4 TRAIN Register 500 adopts a monthly report at printed page 507, effective June 1. The packet's final code compilation prints the monthly text at TRAIN Regulatory Code § 12.4(a). A memorandum dated June 10 states that the rule requires weekly reporting and cites the proposal. The supplied code compilation is expressly labeled the June 1, 2026 version.

Completed construction: “The supplied final text requires a monthly report. TRAIN Regulatory Code § 12.4(a) (June 1, 2026 version).” To explain the development, add: “The proposal had used weekly reporting. Meter Reporting Proposal, 4 TRAIN Register 100, 104 (Jan. 8, 2026) (proposed § 12.4(a)); Meter Reporting Final Rule, 4 TRAIN Register 500, 507 (Apr. 8, 2026).” Both the sentence and the source identity now express the stage correctly.

The proposal remains a legitimate source for what was proposed. It is the wrong source for the asserted final obligation. The version ledger records proposed frequency=weekly, final frequency=monthly, and effective date=June 1. A title-only search result could retrieve either document; the docket alone is also insufficient because both share it. The citation must preserve the stage that makes the passage relevant.

52.3 Packet R2: Preamble explanation and operative paragraph

Supplied packet. The R1 final publication contains preamble section “Response to Comments” on printed pages 503–505 and regulatory text on pages 507–509. At 504, the Training Water Office says monthly reporting reduces duplicate submissions. Adopted § 12.4(a), at 507, states the monthly obligation. The writer wants one sentence describing the requirement and another describing the agency's explanation.

Completed construction: “The supplied paragraph requires monthly reporting. TRAIN Regulatory Code § 12.4(a) (June 1, 2026 version). The office explained that this frequency reduces duplicate submissions. Meter Reporting Final Rule, 4 TRAIN Register 500, 504 (Apr. 8, 2026) (response to comments).” The second citation does not imply that the explanation is itself the codified paragraph. The first does not attribute explanatory words to the regulatory text.

For a sentence combining both ideas, place each reference immediately after its corresponding clause or use a parenthetical that identifies which source supports which point. Avoid a broad citation to pages 500–509 when page 504 and § 12.4(a) locate the material precisely. If the issue concerns whether the explanation supports an interpretation, articulate that inference and research the applicable interpretive law. The publication architecture alone does not settle the legal force of preamble language.

52.4 Packet R3: A public comment quoted in the agency's response

Supplied packet. Comment TRAIN-R1-C17, submitted by the fictional Small Utilities Group on February 3, 2026, estimates that manual monthly compilation takes six staff hours. Its supporting spreadsheet is attachment A, cell D18. The agency quotes the estimate at final-publication page 503, then explains at page 504 that it used a different estimate for its analysis. The draft says, “The agency found that reporting takes six hours.” The six-hour estimate appears on page 3 of the comment.

Completed construction: “The Small Utilities Group estimated six staff hours for manual monthly compilation. Small Utilities Group, Comment TRAIN-R1-C17, at 3 & attachment A, cell D18 (Feb. 3, 2026). The agency recited that estimate while describing a different estimate used in its analysis. Meter Reporting Final Rule, 4 TRAIN Register 500, 503–504 (Apr. 8, 2026).” The construction names the original speaker and distinguishes quotation from adoption.

If only the agency's quotation is available, say that the estimate is quoted in the final publication and cite that page. Do not imply that the comment and spreadsheet were inspected. Here they are supplied, so the source card can identify the original comment and attachment directly. Preserve the spreadsheet version and cell label; a printed attachment page may be added when the receiving format requires a page locator, but it should not silently replace the meaningful cell coordinate.

52.5 Packet R4: Correction to a table entry

Supplied packet. TRAIN Regulatory Code § 12.8 contains Table A. The April 8 final publication prints the reporting threshold for Type B meters as “50.” Correction TRAIN-R1-COR, published April 18 at 4 TRAIN Register 620, identifies that entry and directs replacement with “500.” The supplied June 1 code version displays 500 and includes a source note for the correction. The packet stipulates that this is the corrected adopted text; it does not ask for a determination of the issuing body's correction power.

Completed construction: “The corrected table uses 500 for Type B meters. TRAIN Regulatory Code § 12.8, tbl. A (June 1, 2026 version); Meter Reporting Correction, 4 TRAIN Register 620 (Apr. 18, 2026) (Type B entry).” When explaining the discrepancy in an earlier draft, cite the original page and the correction separately. The original erroneous number may be historically relevant, but it must be identified as the earlier printing.

The source record should describe the precise unit of change: section 12.8 / table A / Type B / threshold column / 50 to 500. A general note that the rule was corrected would not permit a reviewer to determine whether the cited row was affected. If another table row is cited, compare that row rather than assuming every number changed. Table references need row and column identity when the page alone contains several similar values.

52.6 Packet R5: Effective date and compliance date diverge

Supplied packet. The R1 final rule states an effective date of June 1, 2026, and an initial compliance date of September 1. A later publication, TRAIN-R1-DATE, at 4 TRAIN Register 900 on August 10, changes only the initial compliance date to November 1. It expressly leaves the effective date unchanged. A draft says the rule “did not take effect until November” and cites the later publication. The final publication states its dates on printed page 501.

Completed construction: “The packet's rule became effective June 1, while its initial compliance date was later moved to November 1. Meter Reporting Final Rule, 4 TRAIN Register 500, 501 (Apr. 8, 2026) (dates); Meter Reporting Compliance-Date Change, 4 TRAIN Register 900 (Aug. 10, 2026).” The two date fields remain distinct in the source record. A subsequent reference to the November date should call it the compliance date.

For a question about conduct in October, identify exactly which provision and timing condition is relevant. The supplied date change does not authorize an inference about every possible consequence of effectiveness during that interval. The completed citation supports the publication's stated schedule. It does not substitute for substantive analysis of a real rule's obligations, enforcement, or transition treatment. In a chart, use separate columns rather than a single “starts” column that forces the two events into one misleading date.

52.7 Packet R6: Withdrawal of one proposal, survival of another source

Supplied packet. Docket TRAIN-R6 includes Proposed Sensor Certification, 5 TRAIN Register 40, published January 10, 2026. On March 10, Withdrawal TRAIN-R6-W, 5 TRAIN Register 180, withdraws that proposal in full. A separate existing paragraph, TRAIN Regulatory Code § 15.2, remains in the supplied code and is unaffected according to the withdrawal notice. An agency FAQ, version FAQ-3 dated March 15, discusses voluntary testing without purporting to amend § 15.2. The draft cites the withdrawn proposal as the current certification requirement. The code view is labeled March 15, 2026, and the FAQ passage appears in question 4.

Completed construction: “The certification proposal was withdrawn. Proposed Sensor Certification, 5 TRAIN Register 40 (Jan. 10, 2026), withdrawn by 5 TRAIN Register 180 (Mar. 10, 2026). The packet's existing requirement remains at TRAIN Regulatory Code § 15.2 (Mar. 15, 2026 version).” If discussing voluntary testing information, cite “Training Water Office, Sensor FAQ, version FAQ-3, question 4 (Mar. 15, 2026)” and describe it as the FAQ's statement.

The record links the withdrawal to the proposal it actually identifies. It does not attach the label “withdrawn” to every source in the docket or to the agency's entire subject area. The FAQ is kept as a separate document type. Its later date does not, by itself, make it a superseding regulatory text. A useful source map shows three branches: withdrawn proposed text, continuing supplied code paragraph, and later informational publication.

52.8 Audit a rulemaking chain by component

The final audit starts with the sentence being supported. An obligation points to the operative supplied paragraph; a statement of agency explanation points to the relevant preamble passage; a claim about a commenter's position points to the comment; a change in timing points to the date-change publication. The document's title does not override these component distinctions. A final-rule PDF can contain both explanatory and operative material, and the citation should tell the reader which is used.

For web presentations, store the publication locator and the codified locator separately even if one page offers both. An electronic section link can change to show a newer version while a saved publication page remains stable. Preserve the date-specific section view or a verified archived copy when the argument is historical. Record any unavailable attachment as a missing object, not as an inspected source inferred from its title.

For print, a concise source note can explain the chain once: “References to § 12 use the supplied June 1 version, including the April 18 correction; the initial compliance date is addressed separately.” Repeated citations then remain manageable. That note should be revisited when a later amendment changes the section or when the analysis moves to a different period. A single matter can require several temporal views, and a house convention should make those views visible rather than forcing every citation into the latest snapshot.