FirstHR

What Is an SPD? Summary Plan Description Explained

In HR, SPD means Summary Plan Description. What it is, what ERISA requires it to contain, who must provide one, and the deadlines small employers miss.

Nick Anisimov

Nick Anisimov

FirstHR Founder

Benefits
17 min

What Is an SPD?

In HR it means Summary Plan Description: what the document is, what the law requires it to contain, and the deadlines small employers miss

SPD is one of those abbreviations that means four unrelated things, and search engines cannot tell which one you want. So before anything else: if you are here about voltage spikes, hospital instrument sterilization, or a sensory condition, this page will not help you and you should go back.

If you are an employer, SPD means Summary Plan Description, and it is the document you are federally required to hand every employee covered by your benefit plans. Most small business owners have never produced one. Many believe they have, because a carrier sent them a booklet, and the booklet is almost certainly not it.

This guide covers what a Summary Plan Description actually is, what the regulation requires it to contain, who is on the hook to produce it, the three deadlines that govern distribution, and what genuinely happens when you do not have one. That last part is the section where I disagree with most of what is written on this subject, because the penalty story is routinely told wrong in a way that makes it both scarier and less useful than the truth. I build FirstHR for businesses with five to fifty employees, which is exactly the size where this obligation is most often missed. This is general information rather than legal advice.

TL;DR
In HR, SPD stands for Summary Plan Description: the plain-language document explaining an employee benefit plan to the people covered by it, required under ERISA. The employer is the plan administrator and carries the obligation, not the insurance carrier. There is no small-employer exemption. Deadlines: 90 days after an employee becomes covered, 120 days after a new plan is established, 30 days after a written request. The carrier booklet on your desk is usually not an SPD, which is why wrap documents exist.

Which SPD Do You Mean?

SPD has at least four established meanings across unrelated fields, and no single one of them dominates. That is why this page opens by sorting them rather than assuming.

Summary Plan DescriptionHR and employee benefits
The plain-language document that explains an employee benefit plan to the people covered by it. Required by federal law for nearly every private employer that offers benefits. This is the meaning covered on this page.
Surge Protection DeviceElectrical engineering
Hardware that protects electrical systems from voltage spikes. If you arrived here after searching about wiring, panels, or lightning protection, this is the meaning you want and it has nothing to do with employment.
Sensory Processing DisorderHealthcare
A condition affecting how the nervous system handles sensory input. Sometimes appears in HR contexts only in the narrow sense of an accommodation request, which is a separate topic from anything on this page.
Sterile Processing DepartmentHospital operations
The hospital unit that cleans and sterilizes surgical instruments. Turns up in job listings for sterile processing technicians, which is why it competes with the benefits meaning in search results.

The rest of this page is about the first one. If you searched the abbreviation on its own and landed here, the fastest way to tell whether this is your meaning is context: if the question came up while dealing with health insurance, a retirement plan, an employee question about coverage, or anything a broker sent you, you want Summary Plan Description.

What Is a Summary Plan Description?

A Summary Plan Description is the document that explains an employee benefit plan to the employees covered by it, in language they can understand, and it is required by federal law rather than offered as a courtesy.

Definition
Summary Plan Description (SPD)
A Summary Plan Description is the written summary of an employee benefit plan that the Employee Retirement Income Security Act requires plan administrators to furnish to participants. It must accurately reflect the plan's governing document while being written in a manner calculated to be understood by the average participant, and it must cover eligibility, benefits, cost sharing, claims and appeals procedures, circumstances that can reduce or end benefits, and participants' rights under federal law. The employer is normally the plan administrator and therefore the party responsible for producing and distributing it.

Two phrases in the regulation do most of the work. The first is accurately reflect: the SPD summarizes the real plan document, and a summary that promises something the plan does not deliver creates a problem rather than solving one. The second is calculated to be understood by the average participant, which is a genuine legal standard rather than stylistic advice. A summary that technically contains everything but is impenetrable does not meet it.

The practical function is worth stating plainly, because it explains why the requirement exists. When an employee asks whether a procedure is covered, whether their spouse can be added, or why a claim was denied, the SPD is supposed to be the answer. It is the document that stops benefit questions from being answered by whoever happens to remember something. That makes it useful to you and not only to them.

SPD vs Plan Document vs SBC vs Carrier Booklet

Four documents circulate around any benefit plan and they are constantly confused with one another. The confusion is expensive because it leads employers to believe an obligation is satisfied when it is not. If you are still deciding what to offer in the first place, the small business employee benefits guide covers the plans that generate these documents.

DocumentWhat it isWho produces itGiven to employees?
Plan documentThe governing legal instrument setting out the plan's full terms and how it is administeredEmployer, usually via an attorney or a document providerNot routinely, but must be furnished on written request
Summary Plan DescriptionThe plain-language summary of that plan document, with content set by federal regulationEmployer as plan administratorYes, on a required schedule
Summary of Benefits and CoverageA short standardized comparison of a health plan's costs and coverage, required under the Affordable Care ActUsually the insurer or the planYes, and it does not replace the SPD
Certificate of insurance or benefit bookletThe carrier's description of the insured coverage, written to state insurance rulesInsurance carrierYes, but on its own it generally does not satisfy the SPD requirement

The last row is the one that catches small employers. A carrier booklet looks comprehensive, arrives unprompted, and describes the benefits in detail, so it feels like the document has been handled. It typically omits the ERISA-specific content entirely: the plan administrator identification, the agent for service of legal process, the plan number, the claims procedures in the required form, and the statement of ERISA rights.

The Wrap Document Exists Because of This Gap
The standard fix is a wrap document: a supplementary document that adds the ERISA-required content the carrier booklet leaves out, so that the wrap and the booklet together form the complete SPD. This is why benefits administrators talk about wrap SPDs so often. The important operational consequence: if you use a wrap, both pieces must be distributed to participants. Handing out the wrap alone is as incomplete as handing out the booklet alone.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
See How It Works

Who Must Provide an SPD

The plan administrator must provide it, and under ERISA the plan administrator is the employer unless the plan document specifically names someone else. That single sentence resolves most of the confusion on this topic.

Small business owners frequently assume the obligation belongs to whoever sold them the plan. It does not. Your broker advises and places coverage. Your carrier insures the risk and issues certificates. Your third-party administrator processes claims. None of them is your plan administrator for ERISA purposes, and none of them inherits your disclosure duty by virtue of being involved. Many will help you obtain the documents, and that help is worth using, but the responsibility remains yours.

The scope is broader than most employers expect. ERISA covers private-sector employee benefit plans generally, which includes group health, dental, vision, life, disability, and retirement plans, and it applies to corporations, partnerships, limited liability companies, sole proprietorships, and nonprofits alike. Governmental and church plans are the principal exclusions. The Department of Labor maintains a resource section for small business plan sponsors that is worth bookmarking if you offer a retirement plan.

No Headcount Threshold
There is no small-employer exemption from the SPD requirement. A six-person business offering group health coverage has the same obligation as a national employer. The persistent myth comes from a genuinely different rule: small plans with fewer than 100 participants are frequently excused from filing the Form 5500 annual report. That is a reporting exemption, not a disclosure exemption, and conflating the two is one of the most common compliance errors at this size.

What an SPD Must Contain

The required content is set by regulation and runs to roughly twenty categories. Here it is grouped into something you can actually check a document against, though the underlying rule is more detailed and pension plans carry additional requirements.

Identifying the plan
Plan name, plus any name employees actually use for it
Employer name and address
Employer identification number and the plan number you assigned
Type of plan and type of administration
The plan year end used for the plan's financial records
Who is responsible
Plan administrator: name, business address, business phone
Agent for service of legal process, with the address for service
A statement that process may also be served on a trustee or the administrator
Name, title, and principal business address of each trustee
Sources of contributions and how the amount is determined
The funding medium: the insurer, trust, or other entity holding the assets
What employees get
Eligibility requirements for participating and for receiving benefits
Description or summary of the benefits themselves
For group health plans: cost sharing, premiums, deductibles, coinsurance, copays
Network provisions, out-of-network coverage, and preauthorization requirements
Circumstances that cause loss, forfeiture, denial, or reduction of benefits
Any provision letting the sponsor amend or terminate the plan
Rights and procedures
Claims procedures, applicable time limits, and how denials are appealed
COBRA continuation rights for group health plans, including qualifying events
The statement of ERISA rights, presented as one consolidated statement
Written in a manner calculated to be understood by the average participant
Condensed from 29 CFR 2520.102-3, which sets out the full list in paragraphs (a) through (u). Pension plans carry additional requirements covering vesting, years of service, joint and survivor benefits, and PBGC coverage. Have an ERISA attorney or a document provider prepare the actual text.

Reading that list, the pattern behind it becomes clear. Roughly half the requirements are about identification: who runs this plan, who do I contact, where do I send legal process. The other half are about what happens when something goes wrong: how to claim, how to appeal, what can cause a benefit to be denied or reduced, and what rights you have if the plan does not respond. The regulation is designed around the moment an employee has a problem, which is a useful lens for judging whether a draft is adequate.

Do not draft this yourself from the list above. The requirements interact with plan design in ways that create real liability if summarized wrong, and the statement of ERISA rights has model language for a reason. Use an ERISA attorney or a benefits document provider. The list is for verifying that what you received is complete, not for producing it.

Distribution Deadlines

Producing the document is half the obligation. Getting it to people on time is the other half, and it is the half that fails quietly because the clocks are triggered by events rather than dates.

Within 90 daysAn employee becomes covered by the plan
The most commonly missed deadline, because it fires on every new hire who enrolls rather than on a calendar date you can plan around.
Within 120 daysA new plan becomes subject to ERISA
Applies when you establish a plan, not when you add a new carrier or a new benefit option inside a plan you already have.
Within 30 daysA participant makes a written request
The clock most likely to cost you money. Miss it and a court may impose a daily penalty for every day of delay.
Every 5 or 10 yearsRoutine reissue of an updated document
Every five years if the plan has been materially changed in that period, every ten years otherwise. Material changes in between generally require a separate summary of material modifications.
Deadlines per 29 CFR 2520.104b-2. Note the regulation sets the 90-day and 120-day tests as the later of the two, so a brand-new plan gets 120 days even for someone who enrolls on day one.

The 90-day clock is the one that breaks in practice, for a structural reason: it starts when an employee becomes covered, which means it fires on a different date for every hire and never appears on an annual compliance calendar. An employer who diligently reviews benefits every open enrollment can still miss it repeatedly, because open enrollment is annual and hiring is not. Attaching SPD delivery to your new hire paperwork process is the reliable fix, since that process already fires on exactly the right trigger.

What worked for me
The mistake I made was treating benefits documents as an open enrollment task. Once a year I would review everything carefully, feel organized, and move on. Meanwhile people hired in March were getting their coverage explained verbally and receiving nothing in writing until the following January, which is not what the rule asks for. What fixed it was moving the document out of the annual cycle entirely and into the onboarding checklist, where it fires per person. The obligation did not change. The trigger did, and that was the whole problem.

How to Deliver It, and Why Proof Matters

The governing standard is that you must use a delivery method reasonably calculated to ensure actual receipt. That phrasing matters: it is a standard about receipt, not about sending, which is why a few common approaches fall short.

Electronic delivery is permitted under conditions rather than freely. Broadly, employees who use a computer as an integral part of their regular duties can be furnished documents electronically at work, while others generally need to consent in advance. A separate framework applies specifically to retirement plan disclosures. The rules are detailed enough that if your workforce is mixed, some at desks and some not, it is worth getting the approach confirmed rather than assumed.

The failure mode worth naming: posting the document on an intranet or a benefits portal and treating that as distribution. Making a document available is not the same as furnishing it. If nobody is told it is there, the standard is not met.

Keep the Evidence, Not Just the Document
The practical question in a dispute or an audit is not whether you have an SPD. It is whether you can show this specific employee received it on this date. Storing the document is easy; proving delivery is the part that fails. Keep a record for each participant: what version they received, when, and by what method. An acknowledgment step in your onboarding workflow produces this automatically as a byproduct, which is a great deal easier than reconstructing it two years later from memory and email archives.

What Happens If You Do Not Have One

This is where most articles on the subject go wrong, and the error runs in both directions: they overstate the automatic penalty and understate the actual risk.

The correction first. There is no automatic fine for simply not having an SPD. No agency audits your document shelf and issues a citation for a missing summary. Descriptions of a flat penalty for failing to have one are inaccurate, and repeating them makes the whole subject easy to dismiss.

What actually exists is narrower and, in a specific situation, expensive. When a participant makes a written request for plan documents and does not receive them within 30 days, ERISA permits a court, at its discretion, to hold the plan administrator personally liable for up to $110 per day from the date of the failure. This amount is set in 29 CFR 2575.502c-1 and is not adjusted annually for inflation the way many other benefit-plan penalties are. Two features make it dangerous in practice: it is per day, and it accrues while nothing is happening. A request that sits unanswered for a year is a four-figure exposure before anyone has argued about the underlying benefit.

Separately, failing to produce plan documents requested by the Department of Labor carries its own per-day penalty with a cap per request, on a schedule the agency adjusts periodically. And there is a much rarer criminal provision for willful violations of ERISA disclosure requirements, which is worth knowing exists but is not the realistic risk for a small employer acting in good faith.

The Risk That Actually Costs Small Employers Money
Penalties are not the main exposure. The main exposure is losing a benefits dispute. When a plan term is missing, ambiguous, or contradicted by something an employee was told, that ambiguity tends to be resolved against the party who was supposed to have documented it clearly. An employer with no SPD is in a poor position to argue that a benefit was never promised. The document is not merely a compliance artifact. It is your evidence of what the plan actually says.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
See It in Action

Five Expensive Misconceptions

Each of these is common enough that I have heard it from multiple small business owners, and each leads to a believed-compliant employer who is not.

The booklet your insurance carrier sends is not your SPD. Carrier certificates are written to state insurance rules and generally omit the ERISA-required content, which is why wrap documents exist.
There is no small-employer exemption. ERISA applies to private-sector employers regardless of headcount, including sole proprietorships and nonprofits. Only governmental and church plans are excluded.
The Form 5500 small plan exemption is a different rule. Being excused from filing an annual report does not excuse you from producing and distributing an SPD.
Handing someone a login to a benefits portal is not automatically delivery. Electronic distribution has its own conditions, and posting a document without telling anyone it is there does not satisfy them.
Your broker is not the plan administrator. Under ERISA that role belongs to the employer by default, and the obligations attach to whoever holds it.
General information rather than legal advice. ERISA application depends on your specific plans and arrangements, so confirm your position with an employment benefits attorney.

The connecting thread is that all five feel reasonable. Assuming the carrier handles carrier documents, assuming small businesses get small-business rules, assuming a portal login counts as delivery: none of that is careless thinking. It is just wrong in a way you only discover when someone asks you to produce something.

SPDs for a Business Without an HR Department

The awkward reality of this obligation at five to fifty employees is that it is written for organizations with a benefits function, and applies identically to organizations without one. Here is what that means operationally.

You are not expected to draft it. Nearly every employer of any size obtains the document from an attorney, a benefits administrator, or a document service, and small employers should do exactly the same. A wrap SPD covering your existing carrier materials is a routine, bounded piece of work rather than a project, and it is far cheaper than the dispute it prevents.

Ask your broker directly. Many brokers will produce or arrange a wrap document as part of the relationship, and many small employers never ask because they assume it was already handled. If you are weighing whether to hand this whole area to someone else, the guide to the benefits of outsourcing HR covers what does and does not transfer. The question to put to them is specific: do I have a wrap document covering all my ERISA plans, and if not, what would it cost to get one. Vague questions about compliance get vague answers.

Bundle your plans deliberately. Wrapping several benefits into one ERISA plan simplifies the documents but can push you over the 100-participant threshold that governs certain reporting obligations. That is a real trade-off and worth raising with whoever prepares the document rather than discovering later.

Reimbursement arrangements count too. If you use a health reimbursement arrangement rather than a group plan, you have not stepped outside ERISA. A qualified small employer HRA is still a benefit arrangement with documentation and notice obligations, and the comparison of ICHRA and QSEHRA covers how the two structures differ before you choose one.

The broader context for how these documents fit into everything else you are obliged to keep is in the human resource laws guide and the HR document management guide.

When the Plan Changes: The Document You Will Also Need

An SPD describes the plan as it currently stands, which means changing the plan creates an obligation you should know about before it arrives.

When a plan is materially modified, participants generally have to be told through a summary of material modifications, unless the change is folded into an updated SPD distributed within the applicable window. The timing is not uniform: a material reduction in covered health services carries a substantially shorter deadline than other kinds of changes, on the reasonable theory that people need to know quickly when coverage shrinks.

The practical rule for a small employer: treat any change to eligibility, cost sharing, covered services, or carrier as a documentation event rather than an administrative one. Ask whoever maintains your plan documents whether the change requires a notice and by when. This is also worth coordinating with open enrollment, since that is when most plan changes take effect. Changing a plan and telling people informally is precisely the pattern that produces the ambiguity described earlier, where what employees were told and what the plan says diverge.

How to Actually Get an SPD

The sequence, for an employer starting from nothing or from uncertainty.

1
Inventory what you offer
List every benefit: health, dental, vision, life, disability, retirement, reimbursement arrangements, employee assistance programs. Some arrangements are covered by ERISA in ways employers do not expect, so list them all and let an advisor sort them.
2
Find out what documents already exist
Ask your broker and carriers what you have been given. You are looking specifically for a wrap document or a plan document, not for certificates and booklets, which you almost certainly already have.
3
Identify the gap in writing
For each plan, note whether you hold a plan document, an SPD, or only carrier materials. Most small employers discover the answer is carrier materials only, which is a normal starting point rather than a crisis.
4
Get a wrap document prepared
Through your broker, a benefits administrator, or an ERISA attorney. This supplies the required content the carrier booklet omits. It is routine work, and the cost is modest against the risk it removes.
5
Distribute both pieces to everyone currently covered
The wrap and the carrier booklet together form the SPD, so both must go out. Do this for existing participants, not only new ones, since the obligation runs to everyone covered.
6
Attach delivery to onboarding
Add SPD distribution to your new hire process so the 90-day clock is satisfied automatically by an event that already happens. This is the single change that prevents the most common failure.
7
Record who received what and when
Version, date, method, per participant. This is what you will need if anyone ever asks, and reconstructing it after the fact is far harder than capturing it as you go.
8
Set a review trigger, not a review date
Revisit documents whenever the plan changes rather than only annually, since material changes create their own notice deadlines that do not wait for your calendar.

A Ten-Minute Self-Audit

Six questions. If you cannot answer one of them confidently, that is where to start.

Can you name your plan administrator?
If the answer is your broker or your carrier, it is probably wrong. Under ERISA the employer holds this role by default, and the obligations attach to whoever holds it.
Do you have anything besides carrier booklets?
If your entire documentation is what the insurer sent you, you most likely do not have a compliant SPD. That is the normal starting position for small employers, and a wrap document is the normal fix.
Could you show that a specific employee received it, and when?
Having the document is the easy part. Proving delivery to a named person on a named date is the part that fails, and it is the part that matters in a dispute.
Did your last hire get one within 90 days of becoming covered?
This clock runs per employee rather than per year, so it is missed quietly. Check the most recent hire specifically rather than assuming the process worked.
Have your plans changed since the documents were last updated?
New carrier, changed cost sharing, altered eligibility, added or dropped a benefit. Any of these may require a notice on its own deadline, separate from your SPD refresh cycle.
If an employee requested plan documents in writing today, could you respond within 30 days?
This is the scenario where the daily penalty applies. It is worth confirming you know where everything is before someone asks rather than after.

None of this requires an HR department. It requires knowing that the obligation exists, which is the part most small employers are missing, and building the delivery step into a process that already runs. The wider set of documents you should be keeping and for how long is covered in the record retention guide, and the operational side of running benefits at this size sits in the benefits administration guide.

Key Takeaways
SPD has four common meanings. In HR it means Summary Plan Description; elsewhere it means surge protection device, sensory processing disorder, or sterile processing department.
A Summary Plan Description is the plain-language explanation of a benefit plan required under ERISA, and it must be understandable to an average participant rather than merely complete.
The employer is the plan administrator and carries the obligation. Brokers, carriers, and third-party administrators do not inherit it by being involved.
There is no small-employer exemption. The Form 5500 small plan exemption is a separate reporting rule and does not excuse disclosure.
A carrier certificate or benefit booklet generally does not satisfy the requirement on its own. A wrap document supplies the missing ERISA content, and both pieces must be distributed.
Required content spans roughly twenty categories covering plan identification, responsible parties, benefits and cost sharing, claims and appeals, and the statement of ERISA rights.
Three deadlines: 90 days after an employee becomes covered, 120 days after a new plan is established, and 30 days after a written request from a participant.
There is no automatic fine for lacking an SPD. The daily penalty of up to $110 applies when a written request goes unanswered for 30 days, at a court's discretion.
The larger practical risk is losing a benefits dispute, because missing or ambiguous plan terms tend to be resolved against the employer who should have documented them.
Attach delivery to onboarding rather than to your annual benefits cycle. The 90-day clock runs per employee, which is why an annual process misses it.

Frequently Asked Questions

What is an SPD?

It depends on the field. In HR and employee benefits, SPD means Summary Plan Description: the plain-language document that explains a benefit plan to the employees covered by it, required under the Employee Retirement Income Security Act. In electrical engineering, SPD means surge protection device. In healthcare it can mean sensory processing disorder, and in hospital operations it means sterile processing department. The abbreviation is genuinely ambiguous, which is why search results for it mix all four meanings together.

What is a summary plan description?

A summary plan description is the document that tells employees, in language they can actually understand, what an employee benefit plan provides and how it works. It covers who is eligible, what the benefits are, what the plan costs the employee, how to file a claim, how to appeal a denial, what can cause benefits to be reduced or lost, and what rights participants have under federal law. It is a legally required document, not a marketing brochure, and its content is governed by federal regulation.

Is an SPD required by law?

Yes, for nearly every private-sector employer that maintains an employee benefit plan covered by ERISA. That includes group health plans, dental, vision, life and disability coverage, and retirement plans. There is no exemption based on the size of the employer, so a business with five employees has the same obligation as one with five thousand. The main exclusions are plans maintained by governmental employers and by churches. Whether a specific arrangement is a covered plan is a legal question worth confirming with an attorney.

Who is responsible for providing the SPD?

The plan administrator, which under ERISA is the employer itself unless the plan document names someone else. This surprises small business owners who assume their insurance carrier or broker handles it. Carriers produce certificates of coverage and brokers help you buy plans, but neither is the plan administrator, and neither carries your disclosure obligation. If nobody at your company has been designated, the responsibility sits with you as the employer by default.

Is the insurance certificate from my carrier the same as an SPD?

Usually not. A carrier's certificate of insurance or benefit booklet is written to satisfy state insurance regulation and typically leaves out much of what federal law requires an SPD to contain: the plan administrator's details, the agent for service of legal process, the plan number, the claims and appeals procedures in the required form, and the statement of ERISA rights. The common fix is a wrap document, which supplies the missing ERISA content and, combined with the carrier booklet, forms the complete SPD.

When do I have to give an employee the SPD?

Three deadlines matter. A new participant must receive it within 90 days of becoming covered under the plan. For a newly established plan, the deadline is 120 days after the plan becomes subject to ERISA. And if a participant asks for it in writing, you have 30 days to furnish it. Beyond that, an updated document is generally required every five years if the plan has changed materially in that period, or every ten years if it has not.

What are the penalties for not providing an SPD?

The mechanics are frequently described inaccurately. There is no automatic fine simply for lacking an SPD. The exposure arises when a participant requests plan documents in writing and does not receive them within 30 days: a court may then, at its discretion, order the plan administrator to pay up to $110 per day until the materials are provided. Separately, failing to furnish documents requested by the Department of Labor carries a per-day penalty with a cap per request. The larger practical risk is that missing or vague plan terms tend to be resolved in the employee's favor in a benefits dispute.

What is the difference between an SPD and a plan document?

The plan document is the governing legal instrument that sets out the plan's terms in full and controls how it is administered. The SPD is the summary written for participants, which must accurately reflect that document while being understandable to an average employee. Employers are required to have both. In practice they are often produced together, and a wrap arrangement can serve both functions when paired with carrier materials. The plan document is not routinely distributed, but it must be furnished on written request.

Can I distribute the SPD by email?

Often yes, but electronic delivery has conditions rather than being automatically permitted. The general rule is that you must use a method reasonably calculated to ensure actual receipt. Employees who use a computer as an integral part of their job can typically receive documents electronically at work, while others generally need to consent first. A separate set of rules applies specifically to retirement plan disclosures. Merely posting a document on an intranet without notifying anyone is not sufficient, and keeping proof of delivery matters more than the delivery method itself.

Do I need an SPD if I only have a few employees?

Yes, if you offer benefits covered by ERISA. Headcount does not create an exemption. The confusion usually comes from a different rule: small plans with fewer than 100 participants are often excused from filing the Form 5500 annual report, and employers hear about that exemption and assume it applies to disclosure obligations too. It does not. A five-person company offering group health coverage needs an SPD and needs to distribute it on schedule.

Ready to transform your onboarding?

7-day free trial No credit card required
Start Your Free Trial