By the Digital Empire Regulatory Research Team (TariffWatch Analysis Team) · Reviewed by Andy Gaber, Founder, Digital Empire Holdings LLC · Published August 29, 2026 · Last updated August 29, 2026
The Federal Register is where every U.S. federal agency publishes proposed rules, final rules, notices, and Presidential documents. A single notice can carry an executive-order text, a two-line correction, or a 200-page rulemaking with technical appendices; the structure is the same across all of them. This tutorial walks a Federal Register notice section by section, names each header field and what to read from it, shows where the docket lives, and pins the running example to the current BIS Section 232 derivative-metals NPRM at Federal Register notice 2026-15961, published 2026-08-06 with the public-comment window closing 2026-08-27. The goal is that after reading this, an importer, an in-house compliance lead, or a non-lawyer can navigate any FR notice with the same confidence a trade attorney does.
The Federal Register is produced by the Office of the Federal Register (a component of the National Archives and Records Administration, NARA) and printed by the Government Publishing Office (GPO). Its authoritative electronic version is at federalregister.gov, which lets a reader search across every notice back to 1994, filter by agency and document type, subscribe to daily digests, and browse the daily Table of Contents. The archival PDF and XML for every notice back to 1994 lives at govinfo.gov/app/collection/FR, which is the GPO's bulk-access surface; anyone building a systematic Federal Register pipeline pulls from the govinfo XML feed rather than from the federalregister.gov HTML.
Every notice carries three cross-references. The FR citation is of the form "Volume FR Page" (for example, 91 FR 47823) — the volume increments once per year on January 1, and the page increments continuously through the volume. The FR document number is of the form "YYYY-NNNNN" (for example, 2026-15961) — a per-notice identifier the Office of the Federal Register assigns at publication. The federalregister.gov URL slug is of the form /documents/YYYY/MM/DD/YYYY-NNNNN/plain-language-slug — a stable permalink to the notice page.
Every notice opens with a header block that names the promulgating agency (and, where applicable, the sub-agency or bureau within it), the CFR title and part the notice touches, the RIN, and the document title. On a rulemaking notice the header also carries the ACTION line, which is a short label declaring the document type: Notice, Notice of Proposed Rulemaking, Direct Final Rule, Interim Final Rule, Final Rule, Correction, or Withdrawal. The ACTION line is the fastest way to know whether the notice opens a comment window (NPRM), codifies text in the CFR (Final Rule), or does neither (Notice).
The running example: FR 2026-15961 is titled "Section 232 National Security Investigation of Imports of Aluminum and Steel Derivative Articles," issued by the Bureau of Industry and Security (BIS) at the Department of Commerce, touching 15 CFR Part 705. The ACTION line reads Notice of Proposed Rulemaking (NPRM), which means it opens a public-comment window. The RIN is 0694-XC166. The header block sits at the top of the notice on federalregister.gov and on the govinfo PDF.
Every notice carries a SUMMARY paragraph — written in plain language by the promulgating agency — describing what the notice does and why. For an NPRM the SUMMARY typically names the statutory authority, describes the policy problem the rulemaking addresses, and states what the proposed text would do. Skimming the SUMMARY answers the question "do I need to keep reading" in under a minute; the SUMMARY is deliberately written for non-lawyer readers because federal agencies are required, under the Plain Writing Act of 2010 and OMB guidance, to write notices for a general audience.
For FR 2026-15961 the SUMMARY explains that BIS is proposing to add 14 new derivative-article definitions to the Section 232 national-security duty on aluminum and steel, to prevent circumvention of the existing Section 232 duty on primary and semi-fabricated aluminum and steel by importers who could otherwise re-classify aluminum-content or steel-content finished products outside the covered HTS codes. Anyone whose products contain aluminum or steel and whose HTS codes could plausibly fall within one of the 14 proposed definitions is a stakeholder in this rulemaking.
The DATES section carries two dates for an NPRM: the date the notice takes effect as a published notice (typically the publication date itself) and the comment-window closing date. For a Final Rule the DATES section carries the publication date and the effective date — the day the codified text actually starts binding regulated parties. The interval between publication and effective date is typically 30 days for a routine Final Rule (per the Administrative Procedure Act) and can be longer for a rule that carries significant compliance-implementation burden.
For FR 2026-15961 the DATES section states that comments must be received on or before 2026-08-27. That is a hard-coded date in the notice text and the same date BIS pins on the docket at regulations.gov. A comment received after that date is at the discretion of the agency to consider; agencies typically log late comments to the docket but are not required to weigh them in the final analysis. Anyone submitting a rebuttal or inclusion argument on the derivative-article proposal is filing against that deadline.
The ADDRESSES section names the electronic docket location and, for some agencies, the physical filing address if one still applies. Nearly every federal agency filing today accepts submissions through the standard federal docketing system at regulations.gov. The docket is where the original notice PDF sits, where any supporting analysis documents live, and where every public comment submitted through the electronic system is posted (typically within one business day, sometimes after PII redaction). The docket ID is of the form AGENCY-YYYY-NNNN.
For FR 2026-15961 the docket ID is BIS-2026-0331, and the full docket URL is regulations.gov/docket/BIS-2026-0331. That docket carries the original NPRM as filed by BIS, the technical appendices for each of the 14 proposed derivative-article definitions, the economic-analysis package, and (as the comment window remains open) the running list of public comments submitted through the docket. Anyone monitoring the rulemaking bookmarks the docket URL and refreshes to watch comments arrive.
Every notice names a specific agency-staff contact person with a phone number and (sometimes) an email address. This is a real person at the promulgating agency — typically the rule-writing analyst or the desk officer for the specific program. The contact is available to answer clarifying questions about the notice itself: what does a specific term mean, how does a specific provision interact with another regulatory framework, when is the next scheduled public meeting. The contact is not a substitute for filing a comment, and the contact does not have authority to bind the agency on the substance of a proposed rule. But for a technical question that is not obvious from the notice text, the contact is often the fastest path to an answer.
The SUPPLEMENTARY INFORMATION section carries the substantive text of the notice. On an NPRM this section typically walks through the statutory authority for the proposed rule, the background policy context, an analysis of alternatives considered, the specific proposed regulatory text, and any required companion analyses (regulatory-impact analysis, initial regulatory-flexibility analysis for small entities, unfunded-mandates analysis, Paperwork Reduction Act analysis, and so on). On a Final Rule this section carries the agency response to public comments received on the earlier NPRM, plus the specific final regulatory text.
SUPPLEMENTARY INFORMATION is where most of the pages of a long notice live. The section is organized with numbered or lettered sub-headings a reader can navigate by table of contents (federalregister.gov auto-generates a table of contents at the top of the notice page from these sub-headings). Anyone reading a long notice for the first time reads the SUMMARY, DATES, ADDRESSES, and then jumps directly to the specific SUPPLEMENTARY INFORMATION sub-heading that touches their interest. Reading a 100-page notice cover to cover is rarely necessary; reading the specific sub-sections that touch a specific product line or a specific policy question typically is.
For FR 2026-15961 the SUPPLEMENTARY INFORMATION section walks through the Section 232 statutory authority at 19 USC 1862, the history of Section 232 aluminum and steel actions since Proclamation 9704 in 2018, the specific 14 proposed derivative-article definitions (each with an accompanying HTS-code reference table), a discussion of the circumvention analysis that motivated the proposal, and the required companion analyses. Anyone whose products touch a specific HTS code within one of the 14 tables reads the sub-heading for that specific derivative article and reviews the HTS-code list.
Every notice closes with an authority citation naming the statutes and executive orders under which the agency is acting. The authority citation matters because it constrains what the agency can lawfully promulgate: an agency cannot issue a rule outside the scope of its statutory authority, and the authority citation is the first place a court reviewing the rule looks. Reading the authority citation tells the reader what the agency claims as its power for this specific action.
For FR 2026-15961 the authority citation names 19 USC 1862 (the Section 232 statute), Proclamation 9704 of March 8, 2018 (the original aluminum Section 232 action), Proclamation 9705 of March 8, 2018 (the original steel Section 232 action), and the subsequent proclamations that modified the Section 232 aluminum and steel regime. The BIS role in implementing Section 232 (including issuing derivative-article definitions and exclusion requests) is delegated from the President through the Secretary of Commerce.
Every rulemaking that appears in the semi-annual Unified Agenda receives a Regulation Identifier Number (RIN) of the form NNNN-XCNNN. The same RIN follows the rulemaking across every notice, from initial notice of inquiry, through NPRM, through Final Rule. The Unified Agenda entry for a given RIN is on reginfo.gov, published semi-annually by the Office of Information and Regulatory Affairs (OIRA) at OMB. The entry states the current stage of the rulemaking, the projected next action, and the projected next action date. Anyone tracking a rulemaking over months or years cross-references by RIN, not by individual FR document number.
For FR 2026-15961 the RIN is 0694-XC166, the standard BIS prefix for Export Administration Regulations and related Section 232 rulemakings. Anyone tracking BIS Section 232 activity over multiple years subscribes to the reginfo.gov Unified Agenda RSS feed for RIN 0694-XC166 and adjacent BIS RINs.
Filing a comment through regulations.gov is a self-serve web workflow. Navigate to the docket page (regulations.gov/docket/DOCKET-ID), click the "Comment" button on the notice, complete the identity block (name, organization, mailing address, email — anonymous comments are allowed but the docket typically weighs identified comments more heavily), upload the comment PDF or paste the comment text into the form, review, and submit. The system produces a tracking number the commenter should retain. Comments are typically posted to the public docket within one business day.
A well-formed comment names the specific docket ID and RIN in the first line, identifies the commenter and the commenter's stake in the rulemaking (importer, manufacturer, trade association, industry expert), states the specific position (support, oppose, request modification), and supports the position with specific citations to primary sources. Comments that are boilerplate or that do not engage with the specific proposed text are given less weight than comments that cite specific evidence, propose specific alternative text, or supply data the agency did not previously have. The comment-response section of the eventual Final Rule will name and address the substantive comments received; anonymous or boilerplate submissions are typically summarized in aggregate rather than addressed individually.
For an NPRM, the comment window closes on the DATES-section deadline. After the window closes the agency reviews the received comments (typically a multi-month process for a complex rulemaking), revises the proposed text as appropriate, prepares the required comment-response analysis, and issues a Final Rule in a subsequent Federal Register notice. The Final Rule carries its own effective date; on that date the regulatory text takes effect and the corresponding sections of the Code of Federal Regulations at ecfr.gov are updated to reflect the new codified text.
For a rulemaking that spans multiple years, the same RIN tracks the arc across notices, and the Unified Agenda entry for the RIN is the running status log. For FR 2026-15961, the comment window closes 2026-08-27; the BIS review-and-response phase typically runs weeks to months after the comment window closes; the Final Rule (with the specific final list of derivative-article definitions and the effective date) is expected in a subsequent Federal Register notice under the same RIN, timing at BIS discretion.
The Federal Register is the daily bulletin. The Code of Federal Regulations is the codified enforceable text. Once a Final Rule reaches its effective date, the corresponding CFR sections carry the new text; the Federal Register notice becomes a historical artifact that added, amended, or removed CFR text. Reading the current CFR text on ecfr.gov is how a compliance officer answers "what does the rule say today." Reading the underlying Federal Register notice is how the same officer answers "how did the rule get here, what were the agency's stated reasons, and what did the comment record look like."
Both sources cross-reference each other. Each ecfr.gov section carries an "as amended by" history that names the specific Federal Register notices that produced the current text. Each Federal Register notice states, in its authority citation and its regulatory text, the specific CFR sections it adds, amends, or removes. Working from either direction is fine; the workflow depends on whether the reader is starting from a compliance obligation (start at the CFR) or a rulemaking event (start at the Federal Register).
TariffWatch is not a general-purpose Federal Register reader. It is built specifically around FR 2026-15961, the BIS Section 232 derivative-metals NPRM. The tool ingests the specific 14 proposed derivative-article definitions from the notice, extracts the HTS-code references for each definition, and lets an importer paste a 10-digit HTS code at /tariffwatch/hts-checker and see whether the code plausibly falls within one of the 14 definitions. The comment-letter drafter at /tariffwatch/comment-letter generates the docket-formatted comment text; the inclusion-rebuttal templates at /tariffwatch/inclusion-rebuttal generate the substantive argument text. For any Federal Register notice outside the Section 232 derivative-metals scope, federalregister.gov itself is the primary reading surface.
TariffWatch is a data and workflow tool that estimates Section 232 tariff exposure from publicly available Federal Register, USITC, and CBP data. TariffWatch is NOT a licensed customs broker under 19 CFR 111, NOT a filer of record, and NOT a legal-advice service. This is not customs classification advice. Compliance decisions remain the responsibility of the importer and their customs broker or trade attorney. TariffWatch does not guarantee that any classification, exposure estimate, or comment letter will be accepted by CBP, BIS, or Commerce.
TariffWatch is not affiliated with the U.S. Department of Commerce, the Bureau of Industry and Security (BIS), U.S. Customs and Border Protection (CBP), or the U.S. International Trade Commission (USITC). This page is educational and is not customs classification advice, legal advice, or a substitute for reading the underlying notice.
The Federal Register is a daily publication of the U.S. federal government, produced by the Office of the Federal Register (a component of the National Archives and Records Administration) and printed by the Government Publishing Office. The authoritative electronic version lives at federalregister.gov, with the daily print PDF and bulk XML feed available at govinfo.gov under the FR collection. Every notice, proposed rule, final rule, and Presidential document has a stable citation of the form "Volume FR Page" (for example, 91 FR 47823) and a stable notice number of the form "YYYY-NNNNN" (for example, 2026-15961), plus a URL slug on federalregister.gov of the form /documents/YYYY/MM/DD/YYYY-NNNNN/slug.
A typical notice has, in order: (1) an agency-and-title header block; (2) an ACTION line naming the document type (Notice, Proposed Rule, Final Rule, Notice of Proposed Rulemaking, Interim Final Rule); (3) a SUMMARY paragraph in plain language; (4) DATES with the effective date and, for a proposed rule, the comment deadline; (5) ADDRESSES with the docket location (regulations.gov docket ID) and the physical filing address if one still applies; (6) FOR FURTHER INFORMATION CONTACT with an agency staff person and phone number; (7) SUPPLEMENTARY INFORMATION with the substantive text of the notice (typically the longest section); and (8) an authority citation at the end tying the notice to its statutory basis. The header also carries a RIN (Regulation Identifier Number) that ties the notice to the semi-annual Unified Agenda entry for the same rulemaking.
A RIN (Regulation Identifier Number) is an eight-character identifier of the form "NNNN-XCNNN" assigned by the Office of Information and Regulatory Affairs (OIRA) to every rulemaking that appears in the semi-annual Unified Agenda. The same RIN follows the rulemaking across notice-of-inquiry, notice of proposed rulemaking, interim final rule, and final rule stages, and across every Federal Register notice for the same rulemaking. Anyone tracking the same rulemaking through multiple notices uses the RIN, not the individual FR document number, as the persistent identifier. The Unified Agenda entry for a given RIN is on reginfo.gov.
Every Federal Register notice that accepts public comments cites a docket ID in the ADDRESSES section, of the form "AGENCY-YYYY-NNNN" (for example, BIS-2026-0331 for the FR 2026-15961 derivative-metals rulemaking). The docket lives at regulations.gov/docket/DOCKET-ID and typically holds the original notice, any supporting analysis documents (economic analysis, regulatory-impact analysis, technical appendices), and every public comment submitted through the docket. Comments are visible as they are posted; some agencies redact PII before posting, others post as submitted.
A Proposed Rule (typically labeled Notice of Proposed Rulemaking, or NPRM) states an agency intent to promulgate a rule and opens a public-comment window during which anyone can file comments in the docket. After the comment window closes, the agency reviews the comments, revises the text as appropriate, and issues a Final Rule that states the actual regulatory text going into the Code of Federal Regulations, with a stated effective date. A Direct Final Rule and an Interim Final Rule bypass or shorten the notice-and-comment cycle under specific statutory authorities and are less common. The current status of any rulemaking is visible in the Unified Agenda entry for its RIN on reginfo.gov.
The enforceable text is what appears in the Code of Federal Regulations (the CFR) after the Final Rule takes effect. The Federal Register notice is the vehicle that adds text to, amends, or removes text from the CFR; the CFR is the codification. The two are cross-referenced by title and section, and the electronic Code of Federal Regulations at ecfr.gov shows both the current text and, via the "as amended by" history, the specific Federal Register notices that produced it. A notice that has not yet reached its effective date, or that has been stayed, does not modify the CFR until the effective date arrives or the stay lifts.
TariffWatch is built specifically around Federal Register notice 2026-15961, the BIS Section 232 derivative-metals NPRM. It ingests the notice text, extracts the 14 proposed derivative-article definitions and the specific HTS references, and lets a user check a 10-digit HTS code against those definitions and draft a comment letter or inclusion rebuttal indexed to the notice. TariffWatch is not a general Federal Register reader; it does not summarize arbitrary notices. For general Federal Register browsing, federalregister.gov itself is the primary tool.
Or read the running example directly at federalregister.gov.