Most employers shopping for outsourced 401(k) administration learn quickly that 3(16) providers are not interchangeable. Two vendors can use the same label, quote a similar fee, and still leave you holding very different amounts of fiduciary work and fiduciary risk. The difference is not marketing polish — it is what each one will actually sign for in writing, how deeply it plugs into your payroll, and whether recordkeeping, compliance testing and TPA support are one coordinated stack or three vendors pointing at each other.
This is a sponsor-side buying guide: what ERISA Section 3(16) covers, what it deliberately leaves with the employer, and the questions that separate a true administrative fiduciary from a vendor doing paperwork.
What ERISA 3(16) actually means
ERISA Section 3(16) defines the plan administrator: the party responsible for the day-to-day operation of the plan. That includes government filings, participant notices and disclosures, processing of distributions and loans, eligibility tracking, and keeping plan operations consistent with the plan document. By default, that party is the employer. When you appoint an outside 3(16) administrator, you are moving named, defined administrative duties — and the fiduciary responsibility for performing them — to a service provider that accepts them in the service agreement.
Two things follow from that definition, and they are where most confusion starts:
- 3(16) is administrative, not investment. Investment selection and monitoring sit under 3(21) or 3(38). A 3(16) appointment does not touch your fund lineup. If you want a clean map of the roles, see our breakdown of 3(16) vs. 3(21) vs. 3(38) vs. 402(a).
- 3(16) is scoped by contract. ERISA does not publish a standard 3(16) checklist. Whatever the agreement lists is what transfers; everything else stays with you, whether or not anyone says so out loud.
Why “we’re a 3(16)” tells you almost nothing
Because scope is contractual, the label is the beginning of the conversation, not the answer. In practice, 3(16) offerings cluster into three very different tiers.
1. Paperwork support that is not fiduciary at all
The vendor prepares notices, assembles filing data and gives you forms to sign. Useful, but you remain the plan administrator and you carry the fiduciary responsibility for every item. If the agreement never says the provider is a fiduciary for a named function, it isn’t.
2. Limited 3(16) with carve-outs
The provider accepts fiduciary status for a short list — often distributions and loan approvals — and carves out the rest. Common carve-outs: eligibility determination, payroll-file accuracy, plan-document interpretation, correction of prior-year errors, and signing the annual return. The carve-outs are usually the tasks that generate the most employer work and the most exposure.
3. Full-scope 3(16) with a named-fiduciary appointment
The provider takes the administrative function end to end and also accepts the 402(a) named fiduciary role identified in the plan document. This is the tier most vendors decline, and it is the sharpest test of how much responsibility a provider will genuinely stand behind.
Payroll integration is the part that decides whether it works
Nearly every operational 401(k) failure traces back to the payroll file: deferral changes applied a cycle late, the wrong definition of compensation, bonuses excluded when the document includes them, new hires entering after their true entry date, or a terminated employee still coded active. A 3(16) provider that receives a file and processes it without validating it has not removed your risk — it has added a handoff.
Ask specifically:
- Which payroll systems do you integrate with directly, and is it a real integration or a manual file upload with a different name?
- Who reconciles each payroll to the trust? Contributions withheld should be traceable to deposits every cycle, not once a year during audit prep. This is exactly the control that prevents late deferral deposits.
- Do you validate compensation against the plan document’s definition, or do you use whatever column payroll sends?
- Who tracks eligibility and entry dates, and do you push the enrollment notice or wait for us to ask?
- What happens when you find an error you didn’t cause? A provider that flags but won’t help correct leaves the hardest part with HR.
Compliance support: a calendar, not a scramble
The compliance side of plan administration is predictable. Nondiscrimination and coverage testing, the annual return, participant notices, required disclosures, plan-document restatements and amendments all run on a repeating cycle. A strong 3(16) provider runs that cycle for you and tells you what is coming; a weak one sends a data request when the deadline is close.
Look for: a written annual compliance calendar with owner names, preliminary testing run before year-end while corrective action is still cheap, notice delivery with proof of distribution retained, and one accountable contact rather than a ticket queue. Our plan audit readiness checklist is a fair benchmark: a provider that keeps you audit-ready year-round is running real administration.
Who signs the annual return?
This question sorts vendors fast. Some 3(16) providers prepare the Form 5500 and hand it back for the employer’s signature; a full-scope administrator can be the signer. It changes who attests to the filing, so get the answer in writing before you sign the service agreement — details in who signs the Form 5500.
TPA support: one stack or three vendors
Third-party administration — document drafting and maintenance, testing, allocation work, distribution processing, government filings — is often split across a recordkeeper, a TPA and an “administration” vendor. Splits create seams, and seams are where plan errors live: the recordkeeper says the document controls, the TPA says the data was wrong, and the employer is the only party with a fiduciary duty to fix it.
Consolidating 3(16) administration and TPA work under one accountable provider removes the seam. It also shortens every correction: the party that finds the issue is the party that can fix the document, the data and the filing. If you’re weighing structures, our comparison of 401(k) providers vs. 401(k) administrators explains which functions each type of vendor really performs, and what 401(k) management companies do covers where their scope typically stops.
What you cannot outsource
Even with a full-scope appointment, some duties stay with the employer, and a provider who implies otherwise is a warning sign:
- Selecting and monitoring the provider itself. Choosing a fiduciary is a fiduciary act. Document the search, the fee comparison and the periodic review.
- Funding the plan. Withheld deferrals must be remitted; no appointment moves that.
- Plan design decisions. Eligibility rules, match formula, vesting and features are settlor decisions.
- Providing accurate data. A provider can validate and reconcile, but the source records are yours.
A short due-diligence sequence
- Request the service agreement, not the brochure. Read the fiduciary-status language and list every carve-out.
- Ask what the provider signs. Filings, notices, distribution approvals — name each one.
- Ask whether they accept the 402(a) named fiduciary appointment. Note who says no; that answer is the real scope statement.
- Test the payroll workflow. Walk through one cycle end to end, including how a mid-cycle deferral change is applied and reconciled.
- Get the compliance calendar in writing with owners and dates.
- Confirm the TPA boundary. Who drafts the document, who runs testing, who fixes an error found two years later.
- Compare total cost against internal HR hours, not against a headline fee — our true cost of outsourcing piece frames the math.
- Document the decision for your plan file, and calendar the next review.
Where Admin316 is different
Admin316 delivers 3(16) plan administration as one stack: payroll-integrated data validation and trust reconciliation, a year-round compliance calendar with testing and notices handled, and TPA support so document, data and filing work sit with the same accountable team. And where most providers stop, Admin316 continues — it accepts the ERISA 402(a) named fiduciary appointment, the role most vendors decline. That is the practical difference between a provider that processes your plan and one that owns the administrative function alongside you. For a structured evaluation of any provider, including us, use our 401(k) administrator selection checklist.
If you want a direct comparison of your current provider’s scope against a full-scope 3(16) plus 402(a) appointment, book a short call with Admin316. We will walk your service agreement with you and show you exactly which duties are still sitting on your desk.
Want more? Browse the full 401(k) & ERISA resource library for every Admin316 guide on plan administration, fiduciary duties and compliance.
