Required notices are the part of benefits communication nobody wants to write and everybody can get wrong in a way that is expensive. The usual failure is not a missing document. It is a document that was “sent” to a work email nobody reads, with no record that the people without email ever saw it.
This is not legal advice. It is an operations guide for the thing legal already told you to send: Summary Plan Descriptions, Summaries of Benefits and Coverage, annual notices, and the pile of wrap documents that show up every fall. The goal is twofold — you can show a regulator or a plaintiff’s lawyer a real delivery trail, and an employee can still find a plain-language version when they need to make a decision. Those are different artifacts. Most teams produce only the first and hope it serves as the second.
Delivery is a reach problem with a statute attached
Electronic delivery only works for the population that actually receives electronic mail and has consented the way your counsel requires. Frontline, seasonal, and newly hired people are where this breaks. A blast to @company.com is not a distribution plan for a plant that lives on paper checks and a shared kiosk. Treat notice delivery with the same segmentation you use for deskless reach: who has a usable email, who needs mail, who needs a handoff at the shift meeting with a sign-off sheet you keep.
Keep the proof. Date sent, address or email used, bounce list, mail vendor file, and the alternative method for anyone who opted out of electronic delivery. If you cannot produce that file 18 months later, you did not deliver. You hoped.
Do not make the SPD do the job of a decision guide
The SPD is the legal description of the plan. It is allowed to be long. It is not allowed to be your only enrollment communication. Pair it with a short decision guide — cost per paycheck, two or three real visit examples, how to start — and say clearly that the SPD controls if they disagree. That pairing is how you stay accurate without pretending a 90-page PDF is education. The education half is in the strategy guide and the enrollment checklist.
The SBC is the comparison tool employees will actually open if you put it next to the decision, not in a zip file named “Notices_2026_FINAL_v3.” One page, current year, next to the plan choice. If your SBC is still last year’s because someone missed a carrier drop, that is a process failure, not a design one. Put an owner and a date on the file name.
A calendar that does not rely on memory
Map every required notice to a month, an owner, and a delivery method per segment. Open enrollment is not the only week. Medicare Part D, CHIP, women’s health, and surprise-billing notices have their own clocks. If the calendar lives in one person’s head, it will fail the year they take leave. Put it next to the communication calendar so the legal send and the human send do not contradict each other — nothing confuses people faster than a required notice that says one deductible and a campaign that says another.
When the plan changes mid-year, the notice and the decision guide both update, or you freeze the campaign until they match. Fluent marketing copy that is ahead of the SPD is how you create a grievance.
Language and household
If you have a significant non-English population, ask counsel about required translations and then do the practical thing anyway: a Spanish decision page for the elections, plus the official English notices delivered in a way you can prove. A translated marketing email is not a substitute for a required English notice if that is what your plan requires. It is also not a substitute for household reach. Spouses do not get your work email. They get claims.
What good looks like in an audit
You can show who got what, when, and by which method. Bounces were retried or mailed. People without email were not ignored. The current SPD and SBC are the ones on the open resource page, dated. The campaign copy matches the numbers in those documents. That is the bar. Pretty is optional. Consistent and provable is not.
Key takeaways
- Electronic delivery is not universal. Segment like you do for deskless reach, and keep the proof file.
- The SPD is the legal source. It is not the enrollment explainer. Pair them and say which wins.
- Put the current SBC next to the plan choice, not in a zip of “notices.”
- Give every required notice a month, an owner, and a method — not a memory.
- If campaign numbers and SPD numbers disagree, stop the campaign until they match.
Frequently asked questions
Can we email the SPD and call that delivery?
Only for people who meet the electronic-delivery rules your counsel has signed off on — typically a work system they actually use, plus the right notices and opt-out path. For everyone else, you need mail or another method you can prove. A blast to addresses that bounce is not delivery.
What is the difference between an SPD and an SBC?
The SPD describes the plan in the detail ERISA expects. The SBC is the standardized comparison snapshot — deductibles, out-of-pocket maximums, example visits. Employees will use the SBC if you place it at the decision. They will not read the SPD for fun. You still have to deliver both.
How do we handle employees with no company email?
Mail, a documented shift-meeting handoff, or a kiosk process with a record — whatever your counsel accepts and you can staff. Do not invent a fake email for them so the vendor report looks clean. The people without email are the ones most likely to be missed, and the ones most likely to show up in a complaint.
Should compliance notices be written in plain language?
The required text often cannot be rewritten. The companion decision guide can and should be. Do not replace required language with friendlier language and call it the notice. Do not refuse to explain the plan because the notice exists. You need both.
Compliance and comprehension are not opposites. See where your program stands.
A co-founder of Touchpoints with two decades of experience in employee benefits communication. He partners hands-on with benefits firms and employers nationwide to build strategies that deliver real outcomes.
