When a participant puts a complaint in writing, the ERISA claims procedure is what turns an HR conversation into a fiduciary process with rules, clocks and a record that a court may one day read. Sponsors who treat the letter as ordinary correspondence are the ones who end up defending a lawsuit without a defensible file.
Why a Benefit Claim Is a Fiduciary Event, Not an HR Ticket
ERISA requires every plan to maintain a reasonable written claims procedure and to give participants a full and fair review of any denied claim. That obligation sits with the plan’s fiduciaries, not with the recordkeeper’s call center and not with whoever happens to open the mail. A decision about who is entitled to what is an exercise of plan discretion, and it must follow the plan document.
Most of the claims we see are not dramatic. They look like a former employee who believes the match was calculated wrong, a terminated participant told a distribution is unavailable, a beneficiary disputing who gets the account, or a participant who says a loan or hardship request was mishandled. Each one can become a formal claim the moment it is made in writing. Our overview of 401(k) fiduciary responsibilities explains why process, not outcome, is what protects you.
How Claims Go Wrong
- The letter is treated as a complaint and answered informally, so no one issues a written decision.
- The person who made the original decision also decides the appeal.
- The denial does not cite the plan provision it relies on.
- Deadlines are missed because no one logged the date the claim was received.
- The decision follows what the recordkeeper’s system allowed, not what the plan document says.
- Employer-side facts (hours, hire dates, compensation, termination status) are never pulled, so the answer rests on incomplete data.
The last two are the same document-versus-practice gap we describe in when plan documents and operations do not match.
What the Claims Procedure Must Contain
1. A Written Procedure Participants Can Actually Find
The procedure should appear in the summary plan description and be reasonable in how a claim is filed. If your SPD is stale or silent, fix that first. See SPDs and summaries of material modifications for what to distribute and keep.
2. Defined Timing for Decisions and Appeals
ERISA’s regulations set the outer limits for deciding an initial claim and for deciding an appeal, and the limits differ depending on the type of claim and whether extensions apply. Do not memorize numbers from a blog. Confirm the timing that applies to your plan with your document provider and counsel, then put it in a calendar the committee can see.
3. A Denial Notice With Required Content
An adverse determination should state the specific reasons, cite the specific plan provisions, describe any additional information needed to perfect the claim and why, and explain the appeal steps and the participant’s right to sue after a final denial. A denial that says only “you are not eligible” invites trouble.
4. A Full and Fair Appeal
The participant must have a reasonable opportunity to appeal, to submit written comments and documents, and to receive, on request and free of charge, the records relevant to the claim. The appeal must be reviewed by someone who was not involved in the original decision and who is not that person’s subordinate, with fresh consideration of what was submitted.
5. A Named Decision-Maker
Someone must have authority to decide. Your plan document should say who the claims fiduciary and the appeals fiduciary are, and your committee charter should match. If you have not written that down, read retirement plan governance and benefit plan committee charter before the next claim lands.
6. Exhaustion of Administrative Remedies
Courts generally expect participants to use the plan’s internal process before suing, and they review what is in the claim file. The file you build during the process is often the evidence in the case.
Who Does What When a Claim Arrives
1. The Recordkeeper
The recordkeeper can supply account history, transaction detail and, often, intake of the claim. It generally does not make discretionary eligibility decisions unless the plan has delegated that in writing.
2. The Employer
Only the employer holds hire dates, hours, compensation, classification and termination facts. Many disputes turn entirely on that data, which is why participant data reconciliation matters long before a claim exists.
3. The Plan Administrator
The plan administrator under ERISA is responsible for running the process and issuing compliant notices. Where that role sits with a 3(16) provider, the claims workflow becomes a defined service rather than an improvised one. See 3(16) plan administration and ERISA plan administrator for the division of duties.
An 8-Step Self-Check When a Claim Arrives
- Log the date the writing was received and who received it.
- Decide whether the writing is a claim, an inquiry or an appeal, and treat doubtful cases as claims.
- Pull the plan document, adoption agreement and any amendments in effect for the relevant period.
- Collect employer data and recordkeeper history that bears on the question.
- Confirm the decision-maker named in the document and recuse anyone involved in the underlying action.
- Draft the decision with specific reasons, plan citations and appeal instructions.
- Deliver it in a way you can prove, using your electronic disclosure or mail practice, and keep the proof.
- Retain the entire file under your document retention policy, and note any operational fix the claim reveals.
Where Sponsors Get Hurt
- Beneficiary and death disputes: competing claimants and spousal rights need a documented process. See plan sponsor duties when a participant dies.
- Divorce-related claims: an alternate payee has rights a participant may not mention. Review QDRO plan sponsor duties.
- Operational errors: a valid claim often exposes a real mistake. Correcting it for one person while ignoring others similarly situated creates a bigger problem; start with administrative error correction.
- Hardship and loan denials: these turn on documentation. See hardship withdrawals and loans documentation.
- Retaliation or pressure: a claimant who is still an employee must not be treated differently for filing. Keep claim handling away from the employee’s manager.
What You Can Delegate and What You Cannot
You can delegate intake, data gathering, drafting, notice delivery, calendaring and recordkeeping of the claim file to a qualified administrator. You can also delegate the claims decision itself if the plan document and the delegation are written and the delegate accepts fiduciary status.
You cannot delegate the settlor decisions that sit behind many claims: what the plan’s eligibility terms say, whether to amend the document to resolve an ambiguity, or whether to adopt a corrective policy. You also cannot delegate your own facts. If the employer’s records are wrong or missing, no provider can decide the claim correctly for you.
The Cleaner Way to Run Claims: Appoint the Decision-Maker in Writing
The weakest claims files we see have an unclear decision-maker, an informal reply and no record of why. The strongest have a named fiduciary, a written procedure and a file that reads like a decision, not a reaction. Admin316 accepts formal appointment as the plan’s ERISA 402(a) named fiduciary, a role most providers decline, which puts authority over claims decisions where the document says it belongs. Pair that with a clear map of the 3(16), 3(21), 3(38) and 402(a) roles and an employer data feed you can trust, and a claim becomes a managed process rather than a threat. If you want to test your current procedure against this checklist, book a time with Admin316.
