How to Choose a 401(k) Provider: 25 Questions for Your RFP
Choose a 401(k) provider through a documented RFP that tests service, fees, implementation, security, and accountability on the same facts.
Choose a 401(k) provider through a documented RFP that tests service, fees, implementation, security, and accountability on the same facts.
The best RFP is less about collecting glossy answers and more about exposing operational assumptions before a contract is signed. For plan sponsors, the practical goal is not to produce a perfect spreadsheet or outsource every judgment. It is to make a clear decision on complete information, retain the supporting record, and revisit the result when plan facts change.
At a glance
- Core question: What decisions, evidence, and owners does this provider RFP need?
- Focus: Build a comparable record before choosing a direction.
- Reading path: Define the issue, compare options, then implement and review.
Define the decision
DOL guidance identifies provider experience, practices, security information, service quality, and fees as areas a fiduciary should examine when hiring providers.[1] The section 408(b)(2) regulation addresses disclosures of direct and indirect compensation from covered providers.[2] In practice, define the decision in one sentence before gathering data. Identify the plan population, the affected process, the participant impact, the contract or document involved, and the owner who can approve a next step. That boundary prevents a discussion from drifting into unrelated vendor claims or generic plan commentary.
Organize the RFP into five groups. Governance questions: who owns decisions, what reports are delivered, and how escalations work? Administration questions: how are payroll files validated, loans processed, and testing roles divided? Participant questions: what service channels, languages, education, and accessibility are provided? A useful file also distinguishes facts from assumptions. Facts are dates, records, plan terms, invoices, reports, and written commitments. Assumptions are estimates, expected service levels, or future savings. Labeling the difference helps a committee ask the right follow-up question and avoids presenting a projection as a guarantee.
Compare before concluding
| Comparison lens | What to collect | Decision question |
|---|---|---|
| Plan facts | Population, assets, design, payroll, documents | Are the options evaluated on the same baseline? |
| Scope | Deliverables, exclusions, owner, timing | What service difference explains the result? |
| Evidence | Contracts, reports, disclosures, tests | Can the committee verify the statement? |
Ask fee questions that compel a full answer: What is charged to the plan, sponsor, and participant? Which charges are asset-based, per-head, or transactional? Is compensation received from investment providers? What fees can change and when? Require the same response table from every bidder. A comparison should state the same assumptions for every option and note what is unavailable. If a provider cannot answer a question, record that as an information gap rather than silently filling it with a favorable inference. The process is stronger when it identifies uncertainty early.
Ask implementation questions: What data is needed? Who validates balances and payroll mapping? What is the blackout communication plan if applicable? Which milestones have named owners? How are defects logged, cured, and signed off? A provider should explain the controls, not merely promise a smooth conversion. This approach is deliberately neutral: a higher-cost or more complex option may be appropriate in some circumstances, and a streamlined approach may be appropriate in others. The decision record should explain why the selected arrangement fits the plan’s needs, not declare that one model is universally best.
Implement with owners and evidence
Decision flow
- Set criteria: define needs, constraints, service scope, and evidence.
- Score options: score options against cost, controls, and responsibilities.
- Choose fit: choose the documented fit and assign implementation owners.
- Monitor: monitor delivery, changes, and unresolved tradeoffs.
Define the evidence → compare consistent options → implement assigned actions → review results and exceptions.
Ask security and exit questions: what independent assessments can be shared, how are access privileges reviewed, how are incidents reported, and what data/export assistance is available at termination? Score answers against written requirements, interview finalists, and record the reasons for the selected arrangement. Convert the decision into a short action register with a task, owner, due date, dependency, completion evidence, and escalation route. Shared ownership is not the same as no ownership: each item should have one person accountable for moving it forward and one location where the current status can be found.
| Implementation step | Owner | Evidence to retain |
|---|---|---|
| Confirm scope and documents | Plan sponsor or committee lead | Reviewed materials and approval |
| Execute operational change | Named internal or vendor owner | Test results, notices, and exception log |
| Validate outcome | Independent reviewer where practical | Reconciliation and follow-up record |
Before closing the work, compare the result to the agreed scope, document unresolved exceptions, and confirm that the responsible people know the next review date. Use a pilot, parallel check, or sample review when the change touches payroll, participant data, investments, elections, or communications. Decide in advance what would cause a pause, who can approve an exception, and how participants will receive accurate information. A documented validation step is often more valuable than an ambitious launch date.
Review and improve
Schedule a review after implementation, then at an interval that matches the risk and pace of change. Ask whether the intended service or control occurred, what exceptions appeared, which assumptions proved wrong, and whether a document, training, provider report, or control owner needs updating. Preserve the review in the governance file so the next committee can understand the decision trail.
Use a simple review packet rather than relying on memory. Include the original objective, documents reviewed, current metrics or reconciliations, open exceptions, vendor representations, participant questions, and the action register. Ask whether the control works in normal conditions and during unusual events such as a payroll correction, employee departure, system outage, or provider handoff. Where an item depends on another party, obtain a dated response and identify what evidence would close the issue. If a deadline moves, record why, who accepted the change, and any participant or operational consequence. This makes later monitoring faster because the next reviewer sees both the decision and the facts that supported it. It also creates a practical feedback loop: recurring exceptions should lead to a revised process, clearer training, a contract discussion, or a request for specialist guidance rather than a series of isolated workarounds.
This article is educational and is not tax, legal, investment, actuarial, cybersecurity, or compliance advice. Plan terms, contracts, facts, and applicable law matter. Consult qualified advisers and review official guidance before making or implementing plan decisions.
Takeaway
A structured question set helps a sponsor compare providers fairly and preserve a record of the decision. The repeatable habit is simple: define the decision, compare complete evidence, assign implementation work, and review what actually happened.
References
- [1] DOL/EBSA, Meeting Your Fiduciary Responsibilities — https://www.dol.gov/agencies/ebsa/about-ebsa/our-activities/resource-center/publications/meeting-your-fiduciary-responsibilities
- [2] Official government source — https://www.ecfr.gov/current/title-29/subtitle-B/chapter-XXV/subchapter-F/part-2550/section-2550.408b-2
- Supporting source: Official government source — https://www.dol.gov/agencies/ebsa/key-topics/retirement-benefits/cybersecurity
Discuss your plan with Yang's Pension Consulting
Decision pathway
Use this page to frame the decision, collect the plan documents and operating facts that matter, and then confirm the facts with the appropriate plan, tax, actuarial, legal, or compliance professional.
- Define: identify the plan terms, workforce facts, and timing involved.
- Compare: separate operational choices from questions that require professional analysis.
- Implement: document the approved approach and align payroll, providers, and communications.
- Review: revisit the process when plan design, workforce, or rules change.
Try a related planning aid: Plan Sponsor Responsibility Mapper.
Continue learning
Use comparable evidence instead of marketing claims
Provider selection is a fiduciary process for ERISA-covered plans. A useful RFP asks every finalist for the same service, compensation, implementation, fiduciary, contract, and cybersecurity information so the sponsor can compare like with like.
What to document before acting
Request service scope, direct and indirect compensation, affiliates, investment/recordkeeping roles, implementation timeline, payroll integrations, participant support, termination terms, security controls, incident response, references, and transition responsibilities.
How to use the evidence
Start with the written plan and the current service agreement rather than relying on a prior email, a payroll default, or a vendor label. Compare the operative terms with the current payroll configuration and provider report. If they disagree, pause the change, identify the source record that controls, and document the resolution before the next processing cycle.
A useful review file answers four questions: what fact was confirmed, who confirmed it, what action was taken, and when the result will be checked again. That record gives the sponsor, its providers, and any reviewer a shared basis for resolving future exceptions without reconstructing decisions from memory.
Before releasing a change, run one normal example and one edge case through the proposed workflow. Compare the expected output with the plan terms, confirm who receives the result, and define a stop-and-escalate point for incomplete data. After release, perform a short reconciliation and retain the sign-off with the underlying report.
Implementation checkpoint
- Confirm the written terms: identify the plan provision and effective date that govern the decision.
- Reconcile operating data: compare payroll, provider, and participant records before finalizing an action.
- Assign an exception owner: document who resolves a mismatch and how the correction is reviewed.
- Retain the decision record: keep the inputs, approvals, provider communications, and follow-up evidence together.
Important boundary: An RFP is not a one-time safe harbor and does not require selecting the lowest-cost proposal. Record the process and monitor the selected arrangement.
Reference
- Official source: https://www.dol.gov/agencies/ebsa/employers-and-advisers/small-business-owners/working-with-service-providers