12Regulations and Administrative Materials

Your draft cites a proposed rule as though it were an operative regulation. Its Federal Register page contains an agency explanation, proposed text, and a comment deadline. The citation must distinguish those materials before it can accurately support the sentence.

Distinguish codified regulations, rulemaking publications, proposals, preambles, and agency decisions; collect title/section or volume/page information; identify dates and status; and avoid treating agency guidance as binding solely because it has an official URL.

The Code of Federal Regulations organizes federal regulatory text by title and section. A conventional citation identifies title number, C.F.R., section, and the applicable edition/year under Indigo. Subsections locate the precise command. An eCFR display is an electronic presentation with its own currency information; record what it says about the version rather than substituting retrieval date for legal effectiveness.

The Federal Register publishes rulemaking notices and other materials in volume/page/date form. It can contain proposed text, final text, effective dates, explanations, notices, and corrections. Identify which component supports your sentence. A preamble explanation is not the codified rule text, although it can be relevant to understanding the agency's action.

The chapter includes a verified historical federal-regulation model and a Federal Register publication model below. Its separate Harbor packets are fictional, allowing practice without confusing invented provisions with real law.

Fictional training example — not legal authority. Packet: fictional Harbor Administrative Code, title 4, section 12.3(b), edition 2025; text requires a signed application. Training citation: Harbor Admin. Code tit. 4, § 12.3(b) (2025).

For a real federal regulation, replace the fictional compilation with the actual title-number/C.F.R. pattern and inspect its text and version. For a state regulation, follow the state's actual code structure and local requirements. Do not present a training label as a real abbreviation.

Fictional training example — not legal authority. A Harbor agency notice dated March 1, 2025, proposes removing the signature requirement. Its status field says “proposed”; the packet contains no final adoption. The operative 2025 fictional code still requires a signature. A sentence saying “The agency has eliminated signatures” is unsupported by the proposal. A supported sentence says the agency proposed that change, with a citation identifying the proposal.

A final rule can have a later effective date. Publication is not necessarily the moment its commands govern. A correction can change text. A judicial order can affect implementation. Citation formatting cannot establish applicability without version and status research.

Indigo R19 supplies Federal Register patterns, including proposed-rule status and anticipated codification information where appropriate. R19 covers codified regulations. Do not omit a proposal label to make a draft look shorter; the status is central to the proposition.

Administrative decisions can appear in official reporters, services, databases, or agency documents. Their formats depend on the agency and publication. Collect the proceeding name, decision or release number, reporter/service information, page or paragraph locator, deciding body, and date as applicable. Indigo T2 is an agency-specific orientation, with historical publications and some legacy names. It is not a current directory of every agency publication.

An administrative law judge's decision is not necessarily the agency's final decision. Identify the deciding level and status. A staff no-action letter, interpretive release, commission order, and adjudication can have different functions. Their official origin does not make every statement a universally binding legal rule.

Indigo T2 contains at least one demonstrably mismatched access link: its Prime Roofing example links to an unrelated report. This project does not reuse that example as verified authority. When a link points to the wrong document, retain the error in the editorial record and find the actual source before relying on it.

An agency FAQ or guidance page is still an agency page, not automatically a regulation. Identify its title, issuing office, date/status, and URL under the appropriate electronic-source rule. If the sentence describes what the agency's guidance says, attribute it to the guidance. If it states an enforceable legal duty, research the statute, regulation, order, or other operative source establishing that duty.

Save a permissible copy or snapshot for mutable pages. Record the difference between publication, update, and retrieval dates. A last-modified label may describe the page rather than the underlying policy. Avoid guessing a legal effective date from website metadata.

Read the source title and status. Identify its publication system. Locate the exact text supporting the sentence. Record its version and effective-date information. Construct the citation. Then review the sentence's verb: proposed, adopted, requires, recommends, explained, or ordered. Each verb makes a different claim. Supply a local-rule check when the receiving document requires a specific source or format.

Codified text: title/code/section/version. Rulemaking publication: title or subject, volume/publication/page/date/status. Agency decision: agency-specific identifying fields and pinpoint. Guidance: its actual title/date/URL and attributed role.

Fictional training example — not legal authority. An invented agency issues a proposal on March 1, 2025, adopts a final rule on June 1, and sets an effective date of July 1. A supplied fictional codification displays the operative provision as Harbor Admin. Code § 30. The proposal would have required ten-day notice; the final rule instead requires fourteen days. The dates, documents, agency, and code are training materials only.

If your sentence describes the proposal, use the proposed document and identify it as proposed. If it describes the final adopted text, use the final rule or relevant codified provision. The proposed ten-day language cannot establish the final fourteen-day requirement. A word processor's ability to generate a regulation citation from either document does not solve the source-selection problem. Status belongs in the analysis and may also require descriptive citation information.

Separate adoption from effectiveness. The final rule exists on June 1 in this packet, but its operative requirement begins July 1. A dispute concerning June 15 may require the prior rule, transition provisions, or other supplied law. Do not assume that the publication date and effective date are interchangeable. Inspect the document's dates and applicability language before using its newest wording to describe an earlier event.

An administrative publication can contain several kinds of material on adjacent pages: proposed text, final text, preamble explanation, notice, correction, or agency interpretation. Identify which passage supports your sentence. A preamble's discussion of why the agency adopted a rule is not automatically the rule's operative text. If you describe that explanation, cite the passage as explanatory material. If you describe a command, point to the actual provision and preserve its qualifications.

For a Federal Register-style source, publication volume, page, full date, document title, and status may be relevant. For a codified regulation, the title and section locate text within the code, with appropriate version information. For an agency adjudication, the matter's name, decision identifier, issuing body, date, and locator may matter. An agency webpage can deliver any of these forms. It does not erase the differences by hosting them under one domain.

Agency decisions also require accurate characterization. A notice of investigation does not prove a violation. A party's submission does not establish the agency's finding. A final order may describe findings, remedies, or procedural steps with different legal consequences. Match the sentence's verb to the inspected material. When the source is only a docket entry announcing that a document was filed, obtain the document before representing its contents as verified.

At the final check, build a short document sequence: proposal, final adoption, effective provision, correction or amendment if supplied. Identify the version actually used and the proposition it supports. Keep unsupported stages out of the citation history. This method makes administrative citation manageable without pretending that a historical abbreviation table supplies a current regulatory survey or that every agency publication carries the same legal force.

The inspected 2024 edition directs a public entity to make necessary reasonable modifications to policies, practices, or procedures to avoid disability discrimination, subject to the stated fundamental-alteration exception. 28 C.F.R. § 35.130(b)(7)(i) (2024). This sentence describes that subdivision's text, not the outcome of a particular accommodation dispute. The adjacent subdivision supplies an additional limitation, illustrating why the exact pinpoint and surrounding context both matter.

The supporting paragraph appears on printed page 594, the second sheet of the saved section PDF. That printed page is useful in the verification record, but the citation's regulatory pinpoint is § 35.130(b)(7)(i). The page header on that sheet also names the next section, § 35.131. Read the continuation of § 35.130 above it; a running header is not a substitute for following the provision's actual text across the page break. The official file identifies a July 1, 2024 edition. Its later typesetting timestamp does not change that edition date. See EX-P12-01.

A real Federal Register item has several relevant dates

The Department of Justice published its web-accessibility final rule at Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities, 89 Fed. Reg. 31,320 (Apr. 24, 2024) (to be codified at 28 C.F.R. pt. 35). The first page labels the action a final rule and gives an effective date of June 24, 2024. It separately lists compliance dates. This model illustrates the information printed in the 2024 publication; it does not represent a later compliance-date update or a current application assessment. See EX-P12-02.

That citation demonstrates three numbers with different jobs. The 89 is the Register volume, 31,320 is the document's first page, and 35 is the intended C.F.R. part. None can replace the others. An explanation elsewhere in the document needs its actual Register page as a pinpoint. Because the demonstrated dates appear on the first page, the first-page locator already reaches the inspected passage. Do not use the PDF's sheet number as the published page.

When a rulemaking document contains codified text near its end and an extensive preamble before it, identify both the source and the component. “The agency explained” directs attention to the preamble; “the regulation provides” ordinarily directs attention to operative regulatory text. If the distinction matters to the argument, make it explicit in the sentence or explanatory parenthetical. The same volume and document title do not eliminate that distinction.

Fictional training example — not legal authority. A supplied Harbor rulemaking packet includes Notice 25-14, a public comment submitted by Harbor Access Association, an agency response, final text, and a later correction. The comment asks for a thirty-day period. The response explains the agency's selection of twenty days. The final text says twenty days. The correction changes a cross-reference but leaves that period untouched. All documents and identifying labels in this workshop are invented.

Begin by separating speakers. The association requested thirty days; the agency explained twenty days; the final text enacted the packet's twenty-day requirement. A sentence saying the agency required thirty days cannot rely on the comment merely because the agency docket hosts it. A docket collects material from different authors. Its government host does not convert every filed comment into the agency's own statement.

For the comment, collect the commenter's actual name, the proposal identified, the date submitted, the document or comment identifier if helpful, the supporting locator, and the direct access route. For an agency response, identify the response's own location. If the response reproduces the relevant comment and answers it, a citation can direct the reader to that combined location; explain whose words are being used. Indigo R19.5 treats comments and subsequent responses expressly, so these documents should not be squeezed into an anonymous generic-webpage citation.

For adjudications, Indigo R19.3 ordinarily uses the first-listed private party and omits procedural terms such as In re. Agency-specific publication conventions can add decision, release, docket, reporter, or service numbers. Keep those labels attached to their numbers. A docket number identifies the proceeding; a release number identifies an agency issuance; a reporter page identifies a publication location. One proceeding can generate several orders and releases, so the proceeding number alone may not identify the document relied on.

Distinguish the deciding body from the organization that hosts the file. An administrative law judge, a commission, an appellate board, and an agency staff office may issue different documents within one agency. Record the actual body on the document. If a published agency decision becomes available after you cited a website copy, compare the text and its new pinpoints before changing the citation. Do not carry an old PDF page number into a reporter without checking the corresponding passage.

For arbitration under Indigo's convention, identify whether the decision has adversary parties; that affects whether the citation resembles a case caption or an agency adjudication. Preserve the arbitrator's supplied name and the abbreviated role Arb. where the convention requires it. Do not infer the arbitrator's identity from the file's uploader, counsel's signature, or the name of the administering institution. Missing metadata is a research question, not an invitation to complete a plausible formula.

Finally, read the correction. A correction can concern typography, an instruction, a cross-reference, a date, or substantive text. Record what it actually changes. A history note saying “corrected” without explaining whether the relied-on passage changed may be insufficient for the proposition under review. Keep the original and corrected versions identifiable, and point the reader to the version your sentence describes.