What it means
A pension plan is hundreds of pages of legal engineering, and the Summary Plan Description is the law's insistence that the people whose money it is get a readable version. ERISA requires it: the federal benefits statute makes plan administrators hand each participant a summary of the plan's key rules, in language calculated to be understood by the average participant.
The reporting and disclosure guide from the US labour department (the DOL) lists the required contents: eligibility, benefits, vesting, claims procedures, and the circumstances that could cost you benefits. The deadlines are legal: new participants get the SPD within 90 days of coverage, and an updated SPD is due every five years if the plan has been amended or every ten years if it has not.
The summary of material modifications is its running mate: when the plan changes, participants get the change summary on its own clock, generally within 210 days after the end of the plan year of the change, not whenever the next full SPD happens along. The digital era changed delivery, not duty: electronic distribution is permitted under conditions, but the obligation to inform, in writing and on time, is unchanged.
The document is a legal weapon in both directions: courts consult it in benefit disputes, and a sloppy SPD can expose the plan to claims based on promises the formal plan document never made. How far a court will hold the plan to the SPD's wording varies by case and jurisdiction, so the two documents should say the same thing.
Missing or late SPDs can draw penalties in DOL audits, and the failure is usually discovered only when a dispute sends everyone hunting for the file. The blackout notice is the cousin requirement: when a plan suspends trading rights, as during a recordkeeper change, participants must be warned in advance, typically at least 30 days ahead, another page of the same disclosure philosophy.
For a non-finance reader, the SPD is the owner's manual your retirement plan owes you by law: not the engine schematics, but the book that tells you what the buttons do.
In practice
Real-world examples.
Example
An acquirer audits six years of SPDs because the summary, not the plan document, is what employees were promised and relied on.
Example
A friendlier vesting schedule in the SPD than in the plan document exposes the plan to claims, so the employer reconciles the two and takes legal advice before correcting either.
Example
A delivery log with dates wins the claims dispute, because DOL deadlines bind the employer.
Case study
Seen in the real world.
This case study is fictional and illustrative. A made-up mid-sized employer acquires a company whose 401(k) plan it must merge, and its benefits counsel opens the project with a demand for the target's SPDs going back six years. The acquiring HR director learns why: the SPD, not the thousand-page plan document, is what employees were promised. The audit finds the classic trap: the acquired plan's SPD describes a vesting schedule friendlier than the plan document's, a drafting drift nobody caught, and the correction strategy must assume that employees could press claims based on the friendlier version in any dispute.
The merger communications become the compliance lesson written large: a new combined SPD, a summary of material modifications for every change, and a delivery log that can prove each participant was served, because the deadlines in the DOL guide are enforced against the employer, not the mail. Two years later a former employee's claim tests the paperwork: the dispute turns on the SPD's claims-procedure section, the dates in the delivery log close the question, and the case settles on the documents' terms rather than anyone's memory. The HR director's annual ritual is now fixed: read the SPD aloud to a new hire, and wherever the new hire frowns, that is where next year's redraft begins. The plan document stays in the vault; the SPD does the talking.
The HR director also adds a yearly checklist that compares the SPD, the plan document and any summaries of material modifications side by side, with a named owner and a date for each step. Counsel signs off on every change before it goes out to participants. The employer, the plan and the people in this story are invented for illustration.
Watch out
Common mistakes.
- Treating it as marketing; the SPD is a legal disclosure with content and deadline rules, and errors can expose the plan to claims.
- Letting it drift from the plan document; courts sometimes hold the plan to the SPD's friendlier wording, so the two must be reconciled continuously.
- Missing the modification clock; plan changes trigger summary deadlines independent of the five-year SPD cycle.
Questions
People also ask.
What is a Summary Plan Description?
The plain-language summary ERISA requires employee benefit plans to give participants, covering eligibility, benefits, vesting, and claims procedures.
When must it be delivered?
To new participants within 90 days of coverage, refreshed every five years if the plan has been amended or every ten if not, with separate summaries for material changes on their own deadlines.
Is it legally binding?
It is a disclosure document and not itself the plan, but courts can hold plans to its statements in some circumstances, so inconsistencies with the plan document are dangerous.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related