What Is a DOL Rulemaking Docket for a 401(k) Plan?

The docket is the folder. The rule is one document in the folder.

That distinction sounds almost too basic to matter.

It matters constantly.

A Regulations.gov record can contain:

• proposed rule
• supporting analysis
• comment submissions
• hearing notices
• hearing requests
• data
• agency memoranda
• comment-period extensions
• corrections
• final action.^[1][2]

Those materials do not all have the same author.

They do not all have the same legal weight.

And they do not all share the same identifier.

A reliable 401(k) regulatory memo therefore needs to answer two questions before quoting anything:

What kind of record is this?

Who created it?

What Is a Regulations.gov Docket?

GSA's Regulations.gov documentation defines a docket as an:

organizational folder containing multiple documents.^[1]

A docket can be classified as:

• rulemaking
• nonrulemaking.^[1]

For a DOL rulemaking, the folder gives the public one place to find records connected with the agency action.

The Federal eRulemaking Program's public guidance says a docket can contain materials such as:

• proposal
• studies
• supporting documents
• comment submissions
• hearing notices
• comment-period extensions
• eventually the final rule.^[2]

That makes the folder valuable.

It does not make the folder itself legal text.

The Folder, Item and RIN Identifiers Are Different

This is the identifier problem.

One regulatory project can generate several strings that look interchangeable.

They are not.

Folder identifier

The folder ID identifies the organizational folder.

Example Docket ID:

EBSA-2026-0166

for the 2026 designated-investment-alternatives proceeding.^[7][8]

Item identifier

The item ID identifies a specific item associated with the folder.

A document identifier often extends the folder identifier with a sequential suffix.

A single folder can therefore contain many separately identified items.

RIN

The Regulation Identifier Number tracks the regulatory action across systems such as:

• Unified Agenda
• OIRA
• Federal Register.^[6]

For the same 2026 project:

RIN 1210-AC38.^[5][6]

The RIN is the project tracker.

The folder identifier organizes the public record.

Those are different jobs.

Federal Register Identifiers Add Another Layer

The AC38 proposal also has:

FR Doc. 2026-06178^[5]

and the publication begins at:

91 FR 16088.^[5]

Those two identifiers are not interchangeable either.

FR Doc number

Identifies the Federal Register document.

Federal Register citation

Identifies volume and page location in the official daily publication.

The same regulatory action can therefore legitimately have:

• RIN
• folder ID
• item ID
• FR Doc number
• FR citation.

That is not redundant bureaucracy.

Each identifier points to a different layer of the record.

What Is a Comment Tracking Number?

A submitted comment creates another identifier.

Regulations.gov supports a:

Comment Tracking Number

for following a submission.^[1]

The API documentation also distinguishes:

• tracking number
• docket ID
• document ID
• comment-on document
• received date
• posted date.^[1]

A tracking number is not:

• the RIN
• the docket
• the Federal Register citation.

It belongs to the comment workflow.

This is why copying an unidentified alphanumeric string from a receipt into a regulatory citation can produce nonsense.

An Identifier Map Prevents Most Research Errors

The RIN answers:

Which rulemaking project?

The folder ID answers:

Which public record collection?

A document identifier answers:

Which item?

The comment number answers:

Which submission?

Keep those questions separate.

The 2026 Alternative-Investments Proposal Is a Clean Example

DOL published:

Fiduciary Duties in Selecting Designated Investment Alternatives

on March 31, 2026.^[5]

The Federal Register heading identifies:

RIN 1210-AC38.^[5]

The proposal directs comments through:

Regulations.gov.^[5]

Public filings on the proceeding identify the folder as:

EBSA-2026-0166.^[7][8]

The same rulemaking therefore has at least two prominent identifiers before even considering:

• FR Doc number
• FR citation
• individual comment records.

A researcher who knows only one identifier can still find useful material.

A researcher who knows what each identifier means can reconstruct the process.

Why Doesn't the Federal Register Need to Be the Same Thing as the Docket?

Because they serve different functions.

The Federal Register is the government's official daily publication for agency documents.

The Regulations.gov folder organizes the public rulemaking record.

For AC38, the March 31 NPRM establishes:

• proposal status
• proposed regulatory text
• comment deadline
• agency rationale
• legal authority.^[5]

The public folder can then accumulate:

• comments
• supporting material
• required summary
• later actions.

The proposal is a legal rulemaking document.

The folder is the container around the broader public record.

What Is the 100-Word Summary in the Docket?

Congress added a new transparency requirement in 2023.

Current:

5 U.S.C. 553(b)(4)

requires an NPRM to provide the internet address of a plain-language summary of the proposal that is no more than:

100 words

and is posted on Regulations.gov.^[3][4]

The AC38 Federal Register document expressly tells readers that its Regulations.gov record includes that statutory summary.^[5]

This is useful.

It is also easy to misuse.

The 100-Word Summary Is Not the Rule

A 57-page proposal cannot be legally reduced to 100 words.

The summary is designed to make the action easier to understand.

It cannot reproduce:

• definitions
• exceptions
• conditions
• safe-harbor elements
• economic assumptions
• proposed amendatory instructions.

A plan committee can use the summary to decide:

Is this worth reading?

It should not use the summary to decide:

What exactly would the regulation require?

That requires the actual NPRM.

Why Does a Docket Include Supporting Materials?

Because the agency's reasoning can depend on material outside the four corners of the proposed text.

Supporting records can include:

• regulatory impact analyses
• economic data
• technical appendices
• surveys
• research
• information-collection material.

DOL's AC38 proposal specifically encourages commenters to provide:

• supporting facts
• research
• evidence
• citations
• data sets
• detailed findings.^[5]

Those materials help build the record on which DOL evaluates the proposal.

They still require attribution.

A study filed by a trade association remains that association's study unless the agency separately adopts it.

Government Hosting Does Not Transfer Authorship

This is the most important source-reading habit after identifier control.

A PDF hosted at:

regulations.gov

may have been written by:

• DOL
• another federal agency
• trade association
• investment firm
• participant
• union
• academic
• anonymous commenter.

The host tells the reader where the material was filed.

It does not tell the reader who believes the claim.

Example:

A private submission estimates a proposal will cost plans $500 million.

The correct citation is:

"Commenter X estimated..."

Not:

"DOL estimated..."

unless DOL independently made the same estimate in its own analysis.

Public Comments Are Evidence, Not Agency Guidance

A strong comment can matter.

It can provide:

• data
• legal argument
• market evidence
• implementation experience
• proposed language
• criticism of agency assumptions.

That does not make it guidance.

INV-189 covers the broader public-comment problem.

The folder adds another trap:

because the submission is sitting inside an official government system, it can look more authoritative than a letter hosted on the commenter's own website.

Legal weight does not come from the URL.

Comment Count Is Not a Vote

Rulemaking is not a referendum.

DOL does not have to choose the position supported by the largest raw number of submissions.

The APA requires consideration of relevant comments.

The quality and relevance of the issues matter.

A technically supported comment identifying a statutory problem can matter more than thousands of form submissions repeating the same sentence.

That is why:

comment count

and:

substantive record

should be tracked separately.

EBSA's Own Posting Policy Makes Raw Counts Tricky

EBSA says that when submissions are duplicate or near-duplicate copies from a mass-mail campaign, it may post:

• a representative sample
• a tally of duplicate or near-duplicate copies.^[9]

That means one visible document can represent many submissions.

The opposite can happen too.

One commenter can file:

• main comment
• attachment
• supplemental comment
• hearing request.

Raw item counts therefore do not automatically equal:

• people
• organizations
• unique views.

A dashboard number needs context.

EBSA Accepts Anonymous Comments

EBSA encourages commenters to identify themselves.

It also says it accepts and posts:

anonymous comments.^[9]

That matters when analyzing the record.

An anonymous submission can still contain:

• useful evidence
• detailed legal analysis
• factual claims.

Its evidentiary value should be assessed on substance and support.

Identity alone is not a substitute for analysis.

Are All Comments Posted Exactly as Submitted?

Not always.

EBSA says comments are generally posted without redaction to preserve substance.

But its policy also allows actions involving:

• sensitive personally identifiable information
• threats
• hate speech
• profanity
• commercial promotion
• spam
• copyrighted material submitted without redistribution rights.^[9]

Some information can be redacted.

Some submissions can be rejected or removed.

So:

not visible

does not always mean:

never received.

Do Comments Appear Immediately?

Not necessarily.

Regulations.gov's API documentation says comments submitted through the API are not publicly available immediately because agencies must approve them before posting.^[1]

The API separately exposes:

• receive date
• posted date.^[1]

Those fields exist for a reason.

A comment can be received before it becomes publicly visible.

This matters around a deadline.

A researcher looking at the folder at midnight on the closing date should not assume every timely submission is already posted.

Submission Deadline and Posting Date Are Different

Suppose a comment is received:

June 1

and posted:

June 3.

The June 3 display does not prove the comment was late.

The relevant rulemaking instructions and agency record determine timeliness.

The public posting process can lag.

For historical research, preserve both dates where available.

Do not infer filing timeliness from the public display date alone.

Personal Information Can Become Public

The AC38 proposal warns commenters not to include personally identifiable or confidential business information they do not want publicly disclosed.^[5]

It says comments are public records posted online and can be retrieved by search engines.^[5]

EBSA's general policy reinforces that warning.^[9]

That is not boilerplate to ignore.

A comment should be drafted as a public document.

If a submission needs confidential treatment, the commenter should follow the exact agency instructions applicable to that proceeding rather than assuming the portal automatically protects it.

A Docket Can Cover a Coordinated Regulatory Package

The 2023 Retirement Security proceeding is a strong example.

The central rule carried:

RIN 1210-AC02.^[10][11]

Related proposed prohibited-transaction exemption amendments used separate identifiers.

The public hearing notice covered:

• fiduciary-definition proposal
• PTE 2020-02 amendment
• PTE 84-24 amendment
• amendments to several other PTEs.^[12]

Hearing requests were submitted through:

folder EBSA-2023-0014.^[12]

One public folder therefore supported a coordinated package involving multiple legal instruments.

Why Is That Important?

Because a folder boundary is not necessarily a legal-instrument boundary.

The Retirement Security package included:

• regulation
• class exemption amendments
• hearing materials.

Those instruments had different legal functions.

A researcher should not write:

"Everything in EBSA-2023-0014 is the fiduciary regulation."

Some items concern exemptions.

Some are stakeholder submissions.

Some are hearing records.

The folder groups related work.

It does not erase legal distinctions.

The Final Rule Can Point Back to the Same Record

DOL issued the Retirement Security final rule in April 2024.^[13]

The final stage followed:

• proposal
• comments
• hearing
• related PTE rulemaking.

The public record helps explain how DOL got from proposal to final action.

But the final rule's legal status came from:

• agency promulgation
• Federal Register publication
• applicable dates

and was later affected by litigation.

The folder preserved the history.

It did not immunize the outcome.

Docket vs OIRA Review

INV-197 covers OIRA.

The distinction:

OIRA record: Executive Branch review of a draft.

Public folder: materials available in the public rulemaking record.

OIRA can review a proposal before the NPRM is public.

After publication, the Regulations.gov record becomes central to public participation.

The two systems can be connected by a RIN.

They are not the same record.

Docket vs Unified Agenda

INV-196 covers the agenda.

Agenda: what DOL plans or tracks.

Docket: records associated with an actual public proceeding.

A RIN can exist in the Unified Agenda before any public folder is needed.

Once DOL opens an RFI, NPRM or other public process, a folder may organize the materials.

Planning and public record are different stages.

Docket vs Federal Register

The Federal Register answers:

What agency document was officially published?

The folder answers:

What public record has accumulated around the proceeding?

A Federal Register page may link into the folder.

A comment in the folder may cite the Federal Register page.

Neither source replaces the other.

Docket vs CFR

The CFR answers:

What codified regulation applies now?

That is a different question from:

What arguments did commenters make?

or:

What did DOL propose two years ago?

A folder can remain online long after:

• proposal changed
• rule finalized
• rule was stayed
• rule was vacated.

Historical completeness does not equal current legal force.

Worked Example: One Document Is Mistaken for the Whole Docket

Researcher sees:

EBSA-2026-0166-0001

and labels it:

"Docket EBSA-2026-0166-0001."

That can blur the distinction between:

• folder
• individual item.

The safer workflow is:

1. identify the base folder ID
2. identify the specific item
3. describe the item type.

For a citation, specificity is good.

For status, mislabeling the item as the entire record is not.

Worked Example: Private Comment Becomes "DOL Says"

Vendor white paper is filed in an EBSA folder.

Internal memo quotes it:

"DOL says the proposed rule will increase returns by 150 basis points."

The only source is the vendor's comment.

That is attribution failure.

Correct:

"Vendor X argued in its public comment that..."

If DOL later repeats or accepts the figure in a final regulatory impact analysis, that later agency source can be cited independently.

Worked Example: Comment Count Becomes a Vote

Rule receives:

• 2,000 form letters supporting
• 300 form letters opposing
• 12 technical comments.

Presentation says:

"87% of commenters support the rule."

That statistic may be mathematically tidy and analytically weak.

Questions remain:

• Are form letters duplicate?
• Does EBSA display samples plus tallies?
• Do some documents represent multiple signatories?
• Are organizations and individuals being counted identically?
• What legal issues did the technical submissions raise?

Notice-and-comment is deliberative input.

Not ballot counting.

Worked Example: The 100-Word Summary Replaces the NPRM

Committee chair reads the statutory plain-language summary.

Meeting minutes state:

"The proposal requires six mandatory investment tests."

The full NPRM may instead describe:

• proposed factors
• examples
• safe-harbor conditions
• optional pathways.

A 100-word summary cannot carry that nuance.

Use it as navigation.

Not as a substitute for legal text.

Worked Example: Posted Date Is Treated as Filing Date

Comment closes June 1.

A filing appears publicly June 4.

Analyst excludes it as late.

That conclusion is unsupported without the received-date information or agency record.

Regulations.gov distinguishes those dates.^[1]

The processing queue can create a gap.

Timing analysis should use the right field.

A Docket Research Workflow

Start with the RIN

This identifies the regulatory project.

Find the folder identifier

This opens the public record folder.

Identify the document type

Is it:

• proposed rule
• rule
• notice
• supporting material
• public submission?

Confirm authorship

Who wrote it?

Record identifiers

Keep:

• RIN
• folder ID
• document identifier
• FR citation
• FR Doc number.

Read attachments

The substantive analysis may be in an attachment rather than the comment text field.

Check dates

Separate:

• received
• posted
• publication
• deadline.

Check later agency action

Did DOL:

• extend comments
• hold hearing
• issue final rule
• withdraw
• correct?

Close with current law

Check the current CFR or exemption.

That turns a pile of documents into a usable administrative history.

A Practical Identifier Matrix

The identifiers work together.

They should not be collapsed into one generic "docket number."

A Practical Source-Weight Matrix

The same folder can contain evidence at very different levels of authority.

Docket Validation Checklist

Before citing a record from Regulations.gov, verify:

Folder

What is the folder identifier?

Project

What is the RIN?

Item

What is the specific item ID?

Type

Is it:

• rule
• proposed rule
• notice
• supporting material
• public submission?

Author

Who created it?

Dates

What are the:

• received
• posted
• published
• deadline dates?

Attachment

Is the substantive material in an uploaded file?

Agency treatment

Did DOL later respond, adopt, reject or modify the issue?

Current status

Did the final action:

• take effect
• change
• get stayed
• get vacated?

Current text

What does the CFR or current exemption say now?

Those checks prevent the most common docket errors without making research slow.

Fast Answers

What is a Regulations.gov docket?

An organizational folder containing multiple documents associated with a rulemaking or other agency process.^[1]

Is the docket itself a regulation?

No.

What is a folder identifier?

The identifier for the folder.

What identifies one item?

The identifier for a specific item within the Regulations.gov system.

What is a RIN?

A Regulation Identifier Number used to track the regulatory project across federal regulatory systems.

What is the AC38 RIN?

1210-AC38.^[5][6]

What is the AC38 Docket ID?

EBSA-2026-0166.^[7][8]

What is the AC38 Federal Register citation?

91 FR 16088, published March 31, 2026.^[5]

What is its FR Doc number?

2026-06178.^[5]

Is a public comment DOL guidance?

No.

Does government hosting make a private submission an agency statement?

No.

Is comment count a vote?

No.

Does EBSA accept anonymous comments?

Yes.^[9]

Can EBSA group duplicate mass-mail comments?

Yes. Its policy allows a representative sample plus a tally for duplicate or near-duplicate campaigns.^[9]

Can a comment appear after it was received?

Yes. Regulations.gov distinguishes receive and posted dates, and agency processing can delay public visibility.^[1]

What is the 100-word summary?

A plain-language NPRM summary required by 5 U.S.C. 553(b)(4) to be posted on Regulations.gov.^[3][4]

Does that summary replace the NPRM?

No.

What is the safest one-sentence rule?

Use the RIN to follow the regulatory project, the folder identifier to inspect the public record, and the actual agency legal documents to determine what DOL proposed or finalized.

Sources & References

1. General Services Administration — Open GSA: Regulations.gov API Documentation — https://open.gsa.gov/api/regulationsgov/
2. Federal eRulemaking Program / Regulations.gov: How You Can Effectively Participate in the Regulatory Process — https://www.regulations.gov/assets/files/Public-Comment-on-Federal-Regulations_Final.pdf
3. U.S. House of Representatives — Office of the Law Revision Counsel: 5 U.S.C. §553 — Rule Making — https://uscode.house.gov/view.xhtml?req=(title:5%20section:553%20edition:prelim)
4. U.S. Government Publishing Office: Providing Accountability Through Transparency Act of 2023, Pub. L. 118-9 — https://www.govinfo.gov/content/pkg/PLAW-118publ9/pdf/PLAW-118publ9.pdf
5. U.S. Department of Labor — Employee Benefits Security Administration / GovInfo: Fiduciary Duties in Selecting Designated Investment Alternatives — Proposed Rule, 91 FR 16088, March 31, 2026 — https://www.govinfo.gov/content/pkg/FR-2026-03-31/pdf/2026-06178.pdf
6. Reginfo.gov — DOL/EBSA: RIN 1210-AC38 — Fiduciary Duties in Selecting Designated Investment Alternatives — https://www.reginfo.gov/public/do/eAgendaViewRule?RIN=1210-AC38&pubId=202510
7. U.S. Small Business Administration — Office of Advocacy: EBSA Proposed Rule on Fiduciary Duties in Selecting Designated Investment Alternatives — https://advocacy.sba.gov/2026/04/01/ebsa-proposed-rule-on-fiduciary-duties-in-selecting-designated-investment-alternatives/
8. U.S. Small Business Administration — Office of Advocacy: Advocacy Supports EBSA Rule Clarifying Fiduciary Duties — Docket No. EBSA-2026-0166 — https://advocacy.sba.gov/2026/06/09/advocacy-supports-ebsa-rule-clarifying-fiduciary-duties/
9. U.S. Department of Labor — Employee Benefits Security Administration: Public Comments — Posting and Privacy Policies — https://www.dol.gov/agencies/ebsa/laws-and-regulations/rules-and-regulations/public-comments
10. U.S. Department of Labor — Employee Benefits Security Administration: Retirement Security Rule — Public Comments, RIN 1210-AC02 — https://www.dol.gov/agencies/ebsa/laws-and-regulations/rules-and-regulations/public-comments/1210-AC02
11. U.S. Department of Labor — Employee Benefits Security Administration / GovInfo: Retirement Security Rule — Proposed Rule, 88 FR 75890, November 3, 2023 — https://www.govinfo.gov/content/pkg/FR-2023-11-03/pdf/FR-2023-11-03.pdf
12. U.S. Department of Labor — Employee Benefits Security Administration / Federal Register: Hearing on Retirement Security Rule and Associated PTE Amendments — Docket ID EBSA-2023-0014 — https://public-inspection.federalregister.gov/2023-25522.pdf
13. U.S. Department of Labor — Employee Benefits Security Administration / Federal Register: Retirement Security Rule — Final Rule, 89 FR 32122, April 25, 2024 — https://www.federalregister.gov/documents/2024/04/25/2024-08065/retirement-security-rule-definition-of-an-investment-advice-fiduciary
14. U.S. Department of Labor — Employee Benefits Security Administration: Automatic Portability Transactions — Public Comments, RIN 1210-AC21 — https://www.dol.gov/agencies/ebsa/laws-and-regulations/rules-and-regulations/public-comments/1210-AC21
15. U.S. Department of Labor — Employee Benefits Security Administration: Selection of Annuity Providers — Safe Harbor for Individual Account Plans — Public Comments, RIN 1210-AC33 — https://www.dol.gov/agencies/ebsa/laws-and-regulations/rules-and-regulations/public-comments/1210-AC33
16. U.S. Department of Labor — Employee Benefits Security Administration: Rules & Regulations — https://www.dol.gov/agencies/ebsa/laws-and-regulations/rules-and-regulations

Educational Disclaimer

ROIStreet publishes educational content about 401(k) plans, ERISA, Department of Labor rulemaking, Regulations.gov, public comments, Federal Register documents and administrative records. This article is not legal, fiduciary, tax, investment, regulatory, litigation or plan-administration advice. A public rulemaking folder contains materials with different authors, purposes and legal weights. Current compliance should be verified against operative statutes, published agency actions, current CFR text, valid exemptions, current judicial decisions and applicable agency guidance. Public comments, supporting submissions, plain-language summaries and docket metadata should be attributed according to their actual source and should not be treated as current law merely because they appear on a government website.

The ROIStreet Reader Promise

We strive to explain before we evaluate, present evidence before opinions, discuss risks alongside potential benefits, distinguish facts from analysis, and correct material errors transparently.

Our purpose is to help readers better understand investing—not to tell them what to do.