An ERISA 104(b) document request is the written letter, email or form a participant or beneficiary sends asking for plan documents, and it starts a statutory clock that many employers do not realize is running. The duty to respond falls on the plan administrator personally, not on the recordkeeper, and a missed response can expose the administrator to per-day penalties that a court may impose at its discretion. This post explains what sponsors must send, who owns the response, and how to build a process that proves you answered on time.
Why a Document Request Is a Fiduciary Event, Not an HR Errand
Most sponsors treat a participant’s request for plan paperwork as customer service. Under ERISA it is a formal disclosure obligation with a response deadline and a penalty provision attached. The administrator named in your plan document owns that duty, and delegating the mailing does not delegate the liability.
1. Who is the “plan administrator” for this purpose?
Your plan document designates the administrator. If it names the company, the company carries the duty. If it names a committee or an individual, that person or body carries it. Review your plan administrator designation and our guide to plan administrator vs. trustee so everyone knows who is accountable.
2. Why the recordkeeper’s help does not shift the duty
Recordkeepers often hold the documents and can mail them. But the statute looks to the administrator. If the recordkeeper is slow, misses a request, or sends the wrong version, the exposure stays with you. See our comparison of providers vs. administrators.
3. What counts as a valid written request
Generally a request must be in writing and directed to the administrator. Requests sent to a supervisor, a payroll contact or the wrong address are where sponsors get hurt, because the request may still count while nobody who owns the duty ever sees it.
How Document Requests Go Wrong
- The request lands in a general HR inbox and sits unread.
- Staff assume the recordkeeper will handle it and never confirm they did.
- The wrong plan year’s summary or an outdated plan document is sent.
- The administrator sends a summary when the participant asked for the full instrument.
- Nobody keeps proof of what was sent, to whom, and when.
- The request comes from a former employee or beneficiary and is treated as a courtesy rather than a legal obligation.
What You May Be Required to Provide
The statute lists specific documents. Confirm the current list and any recent changes with your ERISA counsel or document provider, since the exact scope depends on your plan type and facts.
1. The governing plan documents
This includes the plan instrument, any amendments, and the trust agreement or other instruments under which the plan is established and operated. Keep these current and organized; our plan document restatements guide explains why version control matters.
2. The summary plan description and modifications
The latest SPD and any summaries of material modifications are commonly requested. Your SPD and SMM process should let you pull the correct version for the requester quickly.
3. The latest annual report
The most recent Form 5500 is typically within scope. Know where your signed copy lives and who approved it; see who signs Form 5500.
4. Contracts and other instruments
Service agreements and similar instruments under which the plan operates may also be covered. Your 408(b)(2) fee disclosure review file is a good place to find them.
5. What is usually not required
Not every internal record is a plan document. Privileged legal advice, committee deliberations and an individual’s account data requests are often governed by other rules. Do not guess; route unclear requests to counsel before you decline anything in whole or in part.
The Clock and the Penalty, in General Terms
The statute sets a response period measured from the administrator’s receipt of the written request, and it allows a court to impose a per-day penalty when the administrator fails to comply. The period, the penalty amount and how courts apply them are matters to confirm with counsel for your situation and plan year. What matters operationally is simple: log the date of receipt, treat it as a deadline from day one, and never assume a late response will be forgiven.
1. When the clock starts
It generally runs from receipt by the administrator, which is why intake discipline matters. Create one designated address or contact for requests and publish it in your SPD.
2. Why courts get involved
Penalties are not automatic. A court weighs the circumstances, including whether the failure was in good faith and whether the participant was harmed. A documented process is your best evidence of good faith.
3. Requests that signal a bigger problem
A document request often precedes a benefit claim, a dispute or a lawyer’s involvement. Treat it as an early warning. Coordinate with your ERISA claims procedure so the response and any later claim are consistent.
An 8-Step Response Self-Check
- Stamp the date the administrator or its designee received the request.
- Confirm the requester is a participant or beneficiary, using the recordkeeper roster, including terminated participants with balances and alternate payees.
- Identify each document requested and match it to the statutory list.
- Pull the correct, current versions, including all amendments.
- Have the administrator or a counsel-reviewed delegate approve the package.
- Send by a method that produces proof, such as tracked mail or a logged secure portal delivery. See electronic disclosure safe harbors before relying on email alone.
- Save a copy of everything sent, with a cover letter listing the contents.
- Close the log entry with the send date and who completed it.
Where Sponsors Get Hurt
- Document gaps: the plan document, trust or an amendment cannot be located. Our document retention checklist helps prevent this.
- Practice differs from paper: the document says one thing and operations do another, and the request exposes it. See plan document and operations mismatch.
- No log: you cannot prove when the request arrived or when you answered.
- Charging improper fees: reasonable copying charges may be allowed, but excessive charges invite trouble. Confirm limits with counsel.
- Inconsistent answers across multiple requesters from the same dispute.
What You Can Delegate and What You Cannot
You can delegate assembling, copying and mailing the documents. A 3(16) plan administrator can take on the administrator duties, including tracking and answering requests, under a written agreement. You cannot delegate the settlor decisions: what the plan provides and whether to amend it remain your calls. Employer-only data, such as hire dates, compensation and employment status, must come from you, and a late or wrong answer on that data can undo a timely response. For a fuller map of who owns what, see 316, 321, 338 and 402(a) fiduciary roles.
Put a Named Fiduciary Behind the Process
A request process only works if someone owns it. Admin316 serves as 3(16) administrator and also accepts formal appointment as the plan’s ERISA 402(a) named fiduciary, which most providers decline. That means a documented, accountable fiduciary stands behind your disclosures, logs and responses rather than a vendor that disclaims the role. If a participant letter just landed on your desk, or you want a process in place before one does, book a time with Admin316 and we will walk through your plan’s current exposure.
