Automatic enrollment notices are one of the simplest requirements in your plan document and one of the most frequently missed. If your 401(k) enrolls employees by default unless they opt out, ERISA and the Internal Revenue Code require the plan to tell each affected employee — in advance, in language they can understand — what will happen to their pay, where the money goes, and how to change it. Miss the notice and you have an operational failure in a plan feature that touches every new hire’s paycheck. Here is what employers must send, to whom, and when.
Why the notice exists at all
Automatic enrollment reverses the default: instead of an employee choosing to defer, the plan defers for them and the employee must act to stop it. That design works legally only because the employee was warned first and given a real chance to say no. The notice is what makes a default deduction lawful rather than an unauthorized withholding.
That framing matters. The notice is a condition of the plan feature, not an onboarding nicety. If it does not go out, the automatic deferral that follows is not properly supported, and correcting it can mean refunding deferrals, making up missed opportunity, or both. Like late deferral deposits, this is a compliance issue hiding inside a payroll process.
Which plans have to send one
Any plan with an automatic contribution arrangement in its document owes notices. Sponsors encounter three flavors, and notice content differs among them:
- Basic automatic contribution arrangement (ACA) — defaults employees into deferrals at a stated rate. Notice required.
- Eligible automatic contribution arrangement (EACA) — lets employees withdraw automatic deferrals within a short window after the first deduction. The notice must describe that permissible withdrawal right, and timing rules are stricter.
- Qualified automatic contribution arrangement (QACA) — a safe harbor design with required employer contributions and an escalating default rate. The notice must describe the contribution formula and escalation schedule, and doubles as the safe harbor notice.
So step one is not “what does the law say” but what does my plan document say it is. Read the adoption agreement. Sponsors routinely call their plan a QACA when the document says EACA, then send the wrong notice content for years — exactly the kind of question a plan review settles in an afternoon.
Who must receive a notice
Think in terms of two populations, and note that the second one is the one employers forget.
1. Newly eligible employees
Everyone who becomes eligible for the automatic contribution feature needs a notice before deferrals begin — including rehires re-entering the plan and part-time employees who cross into eligibility.
2. Every covered employee, every year
The notice is an annual obligation, not an onboarding document. Employees already deferring, those who opted out, those at 0% — all are covered by the arrangement and all get the annual notice. The classic failure is a sponsor who notices every new hire and has never sent an annual notice to the existing population.
3. Employees whose defaults are changing
If your plan escalates the default deferral rate, each year’s notice must state the rate that will apply to that employee. “The default rate increases annually” is not enough.
What the notice has to say
The standard: accurate, comprehensive, and written so the average covered employee can understand it. Content tracks plan design, but a compliant notice generally covers:
- The default deferral percentage that will be withheld if the employee does nothing, and the employee’s specific rate if escalation applies.
- The employee’s right to elect out entirely, or to elect a different percentage, and how the plan treats each choice.
- How to make that election — the actual mechanism, with the recordkeeper’s portal or phone number, not “contact HR.”
- Where default contributions are invested, meaning the plan’s default investment alternative, described specifically enough that the employee could look it up.
- Vesting and withdrawal rules for the contributions, including employer money.
- Employer contribution formulas for QACA and safe harbor designs.
- The permissible withdrawal right and how to exercise it, for EACAs.
- When deductions begin, so the employee knows how long they have to act.
Two notes. Incorporation by reference is limited — pointing at the summary plan description instead of stating the default rate does not satisfy the requirement. And notices are often bundled with the qualified default investment alternative (QDIA) notice and the safe harbor notice. Bundling is fine, but every required element must appear in the combined document; QDIA content is what sponsors lose when consolidating.
When the notice must go out
The rules set a window that is a reasonable period before the start of each plan year, with a parallel advance-notice requirement for employees who become eligible mid-year. EACAs and QACAs carry their own timing constraints, and a notice delivered after deferrals have already started generally does not cure the period it was meant to cover. This is the worst place to rely on memory.
What that means operationally:
- Annual notices run off your plan year and must be scheduled well before the year turns — not squeezed into late December.
- New-hire notices are payroll-gated. The notice must land before the first automatic deduction, so your onboarding workflow — not your benefits calendar — controls compliance.
- Confirm exact deadlines each year against the plan document and your recordkeeper’s compliance calendar. Never carry a date forward unchecked.
Our audit readiness checklist shows how notice deadlines sit alongside the other recurring obligations sponsors track.
Delivery and proof: the part auditors actually test
Sending the notice and proving you sent it are two different projects. Auditors ask for evidence tied to specific employees and specific dates.
- Use a permitted delivery method. Paper works. Electronic delivery works only under the applicable safe harbor conditions, which generally turn on work-related computer access or affirmative consent. A notice sitting on an intranet page nobody must visit is not delivery.
- Keep the version, not just the template. A dated PDF of the exact notice sent each year, with that year’s rate figures.
- Keep the distribution list at the employee level, with dates, reconciled against your eligibility census for the same period.
- Keep transmission evidence — email send logs, recordkeeper confirmations, or mail records.
- Reconcile against payroll. For each newly enrolled employee, confirm the notice date precedes the first deduction date. This one check catches most notice failures before an auditor does.
Where sponsors most often go wrong
- Assuming the recordkeeper handles it. Many produce and distribute notices, but the obligation stays with the plan. Confirm in writing what your provider does — and does not — do.
- New hires only. Skipping the annual notice to existing employees is the single most common gap.
- Missing the QDIA content when notices are combined.
- Electronic delivery without a basis — emailing employees who have no work computer access and never consented.
- No reconciliation. Nobody compares the notice list to the eligibility census, so gaps compound quietly.
- No owner. The task lives with whoever remembered last year; when they change roles, notices stop.
Turn it into a system, not an annual scramble
The fix is boring and it works. Name one accountable owner. Put the annual notice on the compliance calendar with lead time that clears your plan-year deadline. Wire the new-hire notice into onboarding so it triggers off the eligibility date, ahead of the first payroll deduction. Re-read the notice content against the plan document after every amendment. Archive each year’s notice, distribution list, and transmission evidence in one place so audit prep is retrieval, not reconstruction.
The deeper question is who is responsible when the system fails. Notice distribution is an administrative function a 3(16) plan administrator can take on with the rest of the day-to-day compliance load — and knowing which fiduciary role covers what tells you whether you offloaded the work or just outsourced the typing.
This is where Admin316 differs. We accept the ERISA 402(a) named fiduciary appointment — the role most providers decline — taking on named responsibility for plan administration rather than performing tasks while the liability stays on your desk. Notices get sent, delivery gets documented, and accountability sits with the party doing the work. Why sponsors make the change.
Not sure your automatic enrollment notices went out on time — or at all? Book a short call and we will walk your notice process against your plan document and tell you plainly where the gaps are.
Want more? Browse the full 401(k) & ERISA resource library for every Admin316 guide on plan administration, fiduciary duties and compliance.
