The Open Enrollment Communication Timeline That Actually Works

Most employers treat open enrollment communication as a single deadline-driven push instead of a timeline to when people actually need each piece of information. The typical approach is one dense email sent two or three weeks before the deadline, covering plan changes, costs, deadlines, and login instructions all at once. The email usually isn't badly written. It just tries to do six jobs in one send, and employees only have so much mental bandwidth.

Spread that same information across a six-week sequence instead, assigning one specific job to each message, and question volume drops in a way that editing the single big email never quite manages. Timing does work that better sentences cannot.

Why one big push doesn't work for open enrollment communication

The standard approach treats enrollment communication as a deadline problem. Pick a date two or three weeks out, write one thorough email covering plan changes, costs, deadlines, and instructions, and send it. It feels efficient: one draft, one send.

A single message carrying six different jobs asks the reader to do triage on your behalf. They have to decide, mid-workday, which parts apply to them and skip the rest. Most people skim and catch the deadline date, then ignore everything else until the deadline feels close enough to matter. Of course, they come back to you with a question the original email already answered, because they never read that far.

Length isn't really the problem. Every piece of information arrives at the same moment, regardless of when the employee is ready to use it. A person deciding whether to switch plans needs cost detail right away. A person who already knows their plan just needs the portal link and the date. Fitting both needs into a single message means one of them skims past what actually matters to them.

What a six-week open enrollment communication sequence looks like

A six-week sequence assigns one job to each message, so no single email has to carry the whole picture.

• Week 6: Dates only. Enrollment opens on X, closes on Y. Nothing else.
• Week 5: What's changing this year. New carrier, new rate tier, a dropped plan, or a shifted deductible. Nothing about mechanics yet.
• Week 4: What's staying the same. Same network and deductible, same FSA rules carried over.
• Week 3: How to actually enroll. Portal link, login steps, what a completed enrollment looks like on screen.
• Week 2: Where to get help deciding. Who to call, what comparison tool exists, office hours if you have them.
• Week 1: The deadline, restated plainly, plus what happens if someone does nothing. Default enrollment or loss of coverage, depending on your actual policy.

The week 4 message just confirms what isn't changing, and it tends to matter more than it looks like it should. Most enrollment anxiety comes from uncertainty about the parts nobody mentioned rather than from the changes themselves, so naming what's staying the same closes that gap directly.

Each message is short enough to read in the time it takes to open it. That's the whole design: nobody has to hold five previous messages in memory while reading the sixth, because each one stands alone and asks for exactly one action.

Isn't six emails more work than one?

Six short messages are not six times the writing. It's the same content already headed into the single big email, broken into small nuggets and sent on a schedule instead of all at once.

The dates message is two sentences. The plan-changes message is a short paragraph per change, not a full comparison chart. And the deadline reminder practically writes itself, because the real explanation went out four weeks earlier. Each message stays shorter than the section of the big email it replaces, since it isn't competing for attention with five other topics in the same paragraph.

The real shift is in scheduling, not in total writing time. Draft the six messages in one sitting before the sequence starts, then queue them on your calendar the way you'd queue a single email send. The afternoon you'd have spent on one big draft covers all six, and what's different is what happens after send.

As someone who's written thousands of marketing messages in his life and tested all of them, I can tell you with certainty, people have short attention spans and adding more than one call to action to an email get's you one thing... no action at all.

How this actually reduces question volume

Questions cluster around the moment someone feels behind or confused, not around the moment they receive information. Someone who gets six weeks of plan-change detail in one email, then forgets it by week five, will ask what changed even though you told them already. Information sent early doesn't help if it arrives before anyone is ready to use it.

A phased sequence puts each answer closer to the moment the question would naturally occur. The mechanics message lands right when people are ready to log in and enroll, not three weeks before they can act on it. The deadline reminder lands when the deadline is actually close, which is the only week it will feel urgent enough to prompt action instead of another skim.

Most cycles produce a familiar set of repeat questions. People ask what changed even after reading the change email. They ask how to log in even after the mechanics message went out. And they ask what happens if they miss the deadline, right up until the deadline itself. This is why open enrollment communication works better as a phased sequence than as one exhaustive email: it puts the answer to each of those questions near the moment the question would actually get asked, instead of relying on someone to remember an email from five weeks earlier.

How to start this year without rebuilding everything

You don't need six polished templates to try this. Take whatever draft already exists for the big enrollment email and split it along the six jobs above. Send the dates section this week, then hold the rest for the weeks that follow.

If six feels like too many to start, cut it to four: dates, changes, mechanics, deadline. The sequence works because each message has one job, not because there are exactly six of them. Building open enrollment communication this way doesn't call for new software. It only calls for a different schedule for content that already exists, and next year the remaining weeks can be added once it's clear which questions still come up.

FAQ

Do all six messages need to go to everyone? Yes, in most small and mid-size teams. Segmenting by plan or eligibility adds complexity that isn't worth it unless you already have a system built for it. The sequence works because it's simple enough to run manually.

What if enrollment is only two weeks long? Compress the cadence into whatever window you have rather than skipping steps. Two messages a week for two weeks still separates the jobs, which is the part that matters.

Should the deadline reminder go out more than once? A short second reminder on the actual last day is reasonable, but it should only restate the deadline and the consequence of missing it. Adding new information at that point undoes the benefit of the sequence.