Skip to main content
401kROBSCheck eligibility
Plan document control

ROBS Plan Amendments

A ROBS amendment file should prove who changed the qualified plan, what authority allowed the change, when it was adopted, when it became effective, when operations followed it, what participants were told, and why the change preserved qualification, fiduciary and employer-stock controls.

By Dennis Shirshikov · Updated July 31, 2026 · Sources accessed July 31, 2026

The short rule

The signed document controls the plan, the adoption agreement chooses elections, and operations must match both. Dates are evidence fields, not decoration.

Direct Answer: Amend the Document Before the Business Treats the Plan Differently

A ROBS amendment is a governance event, an employee-benefit event, and often a corporate event.

A Rollover as Business Startup, or ROBS, uses a qualified plan sponsored by a C corporation to buy employer stock. IRS ROBS guidance treats the plan as a separate qualified plan with ongoing filing, employee-access, valuation and discrimination risks, and it specifically flags amendments that block later participants from stock access or participation after the founder's purchase.[7][8] The sponsor should therefore start with the signed plan document and adoption agreement, then confirm that payroll, recordkeeping, notices, valuation, testing, corporate approvals and filings follow the same version.[1][6][19]

Use the amendment file to decide whether governing terms changed and to route each consequence to the correct operational lane. Participant-notice guidance covers SPD, SMM, 204(h), safe harbor and blackout communications. Restatement guidance covers replacing the whole document. Annual administration, eligibility, hiring, testing, Form 5500, prohibited-transaction, audit, valuation, setup, tax and IRS-rules guides handle the related work after the amendment question is classified.

Technical Terms Before Use

Define terms before decisions so the same amendment is not described five different ways.

Plan document

The governing written plan terms, including amendments and incorporated provisions.[1][6]

Adoption agreement

The election document used with many pre-approved plans to choose available provisions.[1][6]

Adoption date

The date the authorized signer approves the amendment.[1][6]

Stated effective date

The date the amendment says the changed provision applies.[1][6]

Operational implementation date

The date payroll, recordkeeper, trustee, administrator or participants actually operate under the changed rule.[1][6]

Restatement

A replacement plan document that republishes the plan as a whole rather than changing one provision or election.[1][6]

Protected benefit

A benefit, optional form, early retirement benefit or retirement-type subsidy protected from impermissible reduction under anti-cutback rules.[11][12][13]

Benefits, rights and features

Plan features such as forms, options, investment rights or employer-stock access that can raise nondiscrimination issues.[7][36]

Five Amendment Types to Classify at Intake

Classification controls deadline, authority, evidence, notice and correction review.

Discretionary amendment

A sponsor-chosen design change, such as eligibility, compensation, match, vesting, loan, distribution, investment or employer-stock access terms. Adopt before operation unless a specific authority permits another sequence.[1][3][11][22][40]

Required or interim amendment

A change needed to keep the plan document current with qualification requirements or other law changes. Track RAL, OC List, pre-approved document sponsor notices and statutory notices separately.[1][2][3][4]

Conforming amendment

A document change intended to conform written terms to a law or authorized operation. It needs a source-specific deadline and an evidence trail showing operation matched the rule from the required effective date.[2][3][25][26][27]

Corrective amendment

A correction tool considered under EPCRS or another applicable process after a document or operational mismatch is found. Treat it as a correction analysis, not as ordinary housekeeping.[23][24]

Corporate-event amendment

A change triggered by acquisition, controlled group change, merger, spinoff, stock issuance, redemption, plan merger, plan termination, provider replacement or payroll conversion. Coordinate plan, corporate and participant lanes.[7][19][20][21][37]

Adoption Date, Effective Date, Operational Date and Evidence Must Stay Separate

Most amendment files fail when dates are collapsed into one field.

The adoption date proves when authority acted. The stated effective date controls the document's intended legal operation. The operational implementation date proves what payroll, investments, notices, recordkeeping and testing actually did. A retroactive effective date needs a cited source, such as statutory amendment relief, IRS guidance, RAL framework, or EPCRS correction authority. Do not infer retroactive authority from convenience.[2][3][4][23][24][25][26][27]

Document packet

Signed amendment, adoption agreement page, board or sponsor consent, drafter version, counsel memo and source authority.

Operation packet

Payroll screenshots, recordkeeper mapping, trust directions, valuation assumptions, allocation report and participant account proof.

Communication packet

SMM, SPD insert, safe harbor notice, 404a-5 change notice, blackout notice, 204(h) handoff or no-notice memo as applicable.

Current Remedial Amendment Framework, RAL and OC List Boundaries

The RAL and OC List answer different questions.

The IRS Required Amendments List is an annual list of changes in retirement plan qualification requirements and establishes amendment deadlines for individually designed plans. The IRS states that most items use the end of the second calendar year after the list is issued unless the list says otherwise.[2] The Operational Compliance List helps sponsors identify qualification changes effective during a calendar year, may include items that are mandatory or discretionary depending on the plan, and is not comprehensive. IRS states that a plan must operate in compliance with a relevant requirement from the effective date even if the item is absent from the OC List.[3]

Individually designed plans and pre-approved plans have different responsibilities. Individually designed sponsors track RAL items, determination-letter windows and their own document. Pre-approved users track document-sponsor updates, opinion-letter cycles, adoption-agreement elections and operational choices. The employer still owns adoption and operation in both lanes.[1][4][5][6]

Anti-Cutback, Protected Benefits and Carefully Sourced Exceptions

Before signing, ask what protected right would shrink and who already earned it.

Code section 411(d)(6), ERISA section 204(g) and Treasury regulations protect accrued benefits and certain optional forms of benefit, early retirement benefits and retirement-type subsidies from impermissible reduction by amendment.[11][12][13][15] The protected-benefit review should cover vesting, distribution forms, distribution media when protected, in-service withdrawal rights that are protected under the applicable rule, and allocation conditions after a participant has satisfied them. Loan availability, ordinary investment direction, employer-stock access, redemption mechanics, claims procedures, QDRO administration and communications require separate fiduciary, benefits-rights-features, notice, valuation, operational and correction analysis unless a specific protected-benefit rule applies.[12][19][21][36][38][39]

Exceptions exist in regulations and specific statutes, but this guide does not generalize them into a ROBS safe harbor. SECURE, CARES and disaster provisions have source-specific relief, effective-date and amendment-timing language. Use the exact notice, statute or regulation before treating a retroactive or reducing amendment as permitted.[12][13][25][26][27]

ROBS Employer-Stock Amendment Risks

Founder-only economics make ordinary document changes more dangerous.

IRS ROBS materials identify problems where the sponsor amends the plan after the founder's stock purchase to prevent other participants from purchasing stock or from participating. Those facts can affect coverage, discrimination and benefits-rights-features requirements.[7] Any amendment involving employer-stock authorization, valuation date, participant investment direction, allocation formula, redemption rights, liquidity windows, transfer restrictions, voting, diversification, share class, dilution or outside investor rights should receive fiduciary, corporate and testing review before signature.[8][19][20][36][38]

Amendment Trigger Cards

These are intake triggers, not automatic instructions to amend.

Eligibility, exclusions and entry

Changing age, service, class exclusions, entry dates, rehired employees, long-term part-time handling or controlled-group coverage can affect participation and testing before payroll knows it.[3][33][37]

Compensation and contributions

Compensation definitions, deferral eligibility, match formulas, nonelective contributions, safe harbor design and allocation conditions must reconcile to payroll codes and participant notices.[9][22][34][40]

Vesting, distributions and loans

Vesting schedules, in-service withdrawals, hardship, loan availability, loan default rules, QDRO procedures, claims and rollover notices can be protected-benefit or participant-communication issues.[11][12][14][15]

Employer stock

Stock authorization, valuation date, investment direction, allocation, liquidity, redemption, diversification, share class and private-value disclosures create ROBS-specific fiduciary and discrimination risk.[7][8][10][20][38]

Testing and rights

Coverage, nondiscrimination, top-heavy and benefits-rights-features impacts must be modeled before a founder-favorable amendment is signed or operated.[7][33][34][35][36]

Provider and payroll changes

A new TPA, recordkeeper, trustee, payroll system, payroll code or investment platform can require amendment, blackout, 404a-5, mapping, signature and reconciliation controls.[19][21][38][39]

Acquisition, merger, spinoff or controlled group

Entity changes can alter the employer, covered employee population, plan sponsorship, assets, fiduciaries, filing status and whether plan merger or spinoff documents are needed.[19][30][31][37]

Plan termination or exit

When the sponsor terminates the plan, the file should include the termination amendment or governing authority, participant communications, full vesting analysis, final valuation, distribution package, final Form 5500-series filing and corporate coordination.[1][30][31][32]

Board, Sponsor, Trustee, Administrator, Provider, Payroll, Counsel and CPA Owner Map

Assign ownership by function and written authority.

Board or corporate officer

Approves corporate authority, share issuance, redemption, sponsor resolutions, service contracts and officer signature authority.[7][19][20]

Plan sponsor

Adopts plan amendments, confirms document choice, controls pre-approved adoption-agreement elections and owns business decisions that change plan design.[1][6][7]

Plan administrator

Maintains governing documents, participant communications, SMM and SPD handoffs, Form 5500 coordination, request responses and records.[16][17][18][30][31]

Trustee or directed trustee

Signs trust changes when required, verifies authority before plan asset movement, and preserves trust and employer-stock transaction records.[19][20][21]

TPA or recordkeeper

Drafts or implements only the work in its engagement, such as plan-document updates, census testing, account mapping, statements and filings.[1][21][30]

Payroll owner

Implements eligibility, compensation, deferral, match, loan and vesting changes only from an approved effective-date packet.[3][22][23]

ERISA counsel or benefits adviser

Reviews anti-cutback, protected benefits, safe harbor, correction, controlled-group, employer-stock and participant-notice questions before the sponsor acts.[11][12][14][22][23][40]

CPA or filing owner

Coordinates corporate Form 1120, Form 5500-series, Form 1099-R, Form 945, amended filings and retention when amendments alter reporting inputs.[7][30][31][32]

Amendment Intake Workflow, Decision Tree and Version Controls

Use this sequence to stop undocumented operation before it becomes a correction problem.

Intake workflow

  1. Name the business event and affected plan provisions.
  2. Classify the amendment type.
  3. Identify whether plan is individually designed or pre-approved.
  4. Locate current authority, document-sponsor instruction or counsel memo.
  5. Model anti-cutback, testing, employer-stock, safe harbor, notice and Form 5500 effects.
  6. Approve, sign, implement and retain the evidence package.

Decision tree

If the change is required by law, track RAL, OC List, statutory effective date and plan type. If the change is sponsor-chosen, adopt before operation and run protected-benefit review. If operation already changed, stop further use, preserve evidence and classify EPCRS or other correction path. If employer stock, founder rights, liquidity or participant access changes, add valuation, fiduciary and discrimination review before signature.[2][3][7][11][22][23][40]

Twelve operational controls

  • • Use one amendment-intake form for every proposed change
  • • Assign an amendment number before drafting
  • • Separate adoption date, stated effective date and operational implementation date
  • • Require cited authority for every retroactive effective date
  • • Block payroll implementation until signature authority is confirmed
  • • Map every amendment to SPD, SMM, safe harbor, 404a-5, blackout, 204(h), QDRO, claims and rollover-notice effects
  • • Run coverage, nondiscrimination, top-heavy and benefits-rights-features screening before founder-favorable changes
  • • Require employer-stock valuation and liquidity review for stock features, redemptions and allocations
  • • Keep pre-approved document-sponsor notices with adoption-agreement elections
  • • Keep an amendment log tied to Form 5500 plan-characteristic, participant and asset reporting
  • • Use EPCRS classification before labeling a late amendment corrected
  • • Store final signed documents, drafts, board approvals, delivery proof and implementation screenshots in one evidence package

Annual Amendment Calendar and Evidence Package

Use a calendar because amendment duties are law-change, provider-cycle, transaction and correction driven.

Quarterly

Review payroll changes, employee events, provider releases, law-change alerts, stock transactions, participant complaints and pending corrections before they age into annual-close problems.[3][7][21][23]

Year-end

Reconcile amendment log to plan provisions used for census, allocations, testing, safe harbor status, valuation, participant statements and Form 5500-series reporting.[30][31][32][33][34][35]

Document cycle

For pre-approved plans, calendar provider restatement or amendment packages and adoption windows. For individually designed plans, calendar RAL items and determination-letter opportunities by current IRS procedures.[1][2][4][5][6]

Event cycle

Open an amendment file before acquisitions, controlled-group changes, stock redemptions, plan mergers, spinoffs, provider conversions, payroll conversions, terminations, IRS or DOL notices and correction submissions.[7][19][23][30]

Nine Reproducible Date and Version Scenarios

Each scenario states assumptions and arithmetic so another reviewer can reproduce the control result.

Scenario 1: 2025 RAL item for an individually designed calendar-year plan

Facts: the 2025 Required Amendments List is issued in 2025 and the IRS table states a general plan amendment deadline of December 31, 2027. Arithmetic: 2025 plus two later calendar years equals 2027. Result: use December 31, 2027 only for that RAL item unless the notice states another date.[2][29]

Scenario 2: 2024 RAL item

Facts: the 2024 Required Amendments List is issued in 2024. Arithmetic under the IRS RAL table: 2024 plus two later calendar years equals 2026. Result: December 31, 2026 is the general deadline shown for the 2024 list.[2][28]

Scenario 3: OC List item effective January 1, 2026

Facts: a rule is effective January 1, 2026 and appears later on an IRS operational list. Result: operations must comply from the effective date. The OC List helps identify the item, but absence from the list before effective date does not excuse operation.[3][4]

Scenario 4: Safe harbor notice content changes April 1, 2026

Facts: a safe harbor midyear change alters required notice content and is effective April 1, 2026. The deemed reasonable notice window is 30 to 90 days before April 1. Arithmetic: January 1, 2026 through March 2, 2026. Result: provide updated notice in that window and allow a reasonable election period before effective date when applicable.[22][40]

Scenario 5: 204(h) general timing check

Facts: an applicable pension plan amendment significantly reduces future accruals effective July 1, 2026. The general 45-day rule points to May 17, 2026. Result: identify plan type first because many profit-sharing or stock-bonus individual account plans fall outside 204(h), while covered pension facts need counsel review.[14][15]

Scenario 6: SMM for calendar-year amendment adopted November 15, 2026

Facts: a retirement plan amendment is a material modification adopted during a calendar plan year ending December 31, 2026. ERISA's general SMM timing is 210 days after plan-year close. Arithmetic: December 31, 2026 plus 210 days equals July 29, 2027. Result: use an earlier notice if another rule controls.[16][17]

Scenario 7: Founder-only stock-access amendment

Facts: founder completed a ROBS stock purchase, then the sponsor drafts an amendment to stop later employees from buying employer stock. Result: stop before signature because IRS specifically flags this ROBS pattern as a problem tied to coverage, discrimination and benefits-rights-features concerns.[7][8][36]

Scenario 8: Operation preceded signature by 120 days

Facts: payroll began applying a new match formula on March 1, 2026, but the amendment was signed June 29, 2026. Arithmetic: 120 calendar days elapsed. Result: classify whether a cited law allowed retroactive operation or whether EPCRS or counsel review is needed for an operational/document failure.[3][23][24]

Scenario 9: Form 5500 amended filing trigger

Facts: an amendment changes participant account allocations for a prior plan year after Form 5500 was filed. Result: preserve the signed amendment, allocation workpapers, participant correction records and filer conclusion about amended Form 5500 or related schedules before closing the file.[30][31][32]

Frequently Asked Questions

Use these answers to classify amendment authority, timing, notices, corrections, employer-stock access and records before the sponsor signs or operates a change.

What is a ROBS plan amendment?

A ROBS plan amendment is a signed change to the qualified retirement plan document, adoption agreement, trust, or related governing instrument of the C corporation's plan. It is separate from payroll practice, provider instructions, board minutes, participant notices, and corporate documents, although each may need to be coordinated.[1][7][9][19]

Who signs a ROBS plan amendment?

The signer depends on the plan document, corporate authority, adoption agreement, trust provisions and service contracts. In practice, the plan sponsor or authorized corporate officer signs sponsor amendments, trustees sign trust changes when required, and the administrator keeps the evidence file. A provider draft does not replace authorized adoption.[1][6][19][21][37]

Can operations change before the document is signed?

Sometimes a law or published relief requires operation before a later conforming amendment, but that conclusion needs a cited authority and a version-controlled operating memo. A discretionary design change should be documented before operation unless a specific rule permits another sequence.[2][3][4][25][26][27]

What is the difference between an adoption date and an effective date?

The adoption date is when the authorized signer approves the amendment. The stated effective date is when the amendment says the changed provision applies. The operational implementation date is when payroll, recordkeeping, notices, investments, testing and administration actually began following the changed rule.[2][3][12][13]

Does a Required Amendments List cover every change?

No. The IRS RAL is an annual list of changes in qualification requirements and establishes amendment deadlines for individually designed plans. The IRS RAL process adds an item only after guidance is issued, and the IRS RAL table uses the end of the second calendar year after issuance for listed items unless the list states another deadline.[2][4]

Does the Operational Compliance List create a grace period?

No. The IRS says a plan must operate in compliance with a relevant requirement from the effective date even if the item is absent from the OC List. The OC List helps identify changes effective during a calendar year and is not comprehensive.[3][4]

Do pre-approved ROBS plans follow the same amendment process as individually designed plans?

No. A pre-approved document usually has provider or document-sponsor update cycles, adoption-agreement elections and opinion-letter reliance limits. The employer still must adopt required updates, choose elections that match operation, and coordinate discretionary changes with the document sponsor.[1][4][5][6]

What is an anti-cutback issue?

An anti-cutback issue arises when an amendment would reduce or eliminate a protected accrued benefit, optional form of benefit, early retirement benefit or retirement-type subsidy. ROBS plans should flag distributions, loans, employer-stock rights, allocation rules, vesting and retirement options before adoption.[11][12][13][15]

Can an amendment remove employees from employer-stock access after the founder's ROBS stock purchase?

That is a high-risk ROBS fact. The IRS ROBS page identifies amendments that prevent other participants from buying stock or prevent employee participation after a determination letter as specific problems that may create coverage, discrimination and benefits-rights-features failures.[7][8][33][34][36]

Are safe harbor 401(k) midyear amendments allowed?

Some are allowed when Notice 2016-16 conditions are met. An updated safe harbor notice and election opportunity may be required, some changes are expressly prohibited, and reductions, safe harbor status changes or plan-year changes depend on separate regulations and current guidance.[22][40]

Do SECURE and SECURE 2.0 changes share one amendment deadline?

No. SECURE, CARES, disaster, governmental, collectively bargained, 403(b), qualified plan, and SECURE 2.0 items have source-specific effective dates and amendment deadlines. Use current IRS RAL, OC List and notices rather than a single universal date.[2][3][25][26][27][28][29]

Can EPCRS fix a late or wrong amendment?

EPCRS may be available only when the failure type and facts fit current IRS correction rules. IRS describes SCP, VCP and Audit CAP, but eligibility, timing, practices and procedures, participant impact, DOL issues and correction method must be analyzed before any outcome is promised.[23][24]

Does a determination letter approve the ROBS amendment or transaction?

No. IRS ROBS guidance says a favorable determination letter is based on plan terms meeting Code requirements and does not protect a sponsor from incorrect application, discriminatory operation or prohibited transactions. A later amendment needs its own document and operational review.[6][7]

What records should be kept for each amendment?

Keep the signed amendment, adoption agreement, board or sponsor authority, effective-date memo, operational-date evidence, payroll and recordkeeper changes, notices, SMM or SPD updates, testing impact, valuation impact, Form 5500 handoff, counsel or provider notes, and correction analysis if operation preceded documentation.[16][17][18][19][30][31][32]

When to Recheck a ROBS Plan Amendment

Recheck the amendment decision when law, document cycles, operations or business facts change.

Professional review points

Use qualified ERISA counsel, a benefits professional, tax adviser, fiduciary adviser, valuation professional, corporate-governance adviser, participant-notice reviewer, correction specialist, Form 5500 filer or plan-administration professional when the amendment affects that specialty. A provider draft or checklist should not be treated as professional approval of the sponsor's facts.

Update conditions

Recheck the file when IRS RAL, OC List, SECURE, CARES, disaster, safe-harbor, EPCRS, determination-letter, pre-approved document, Form 5500, DOL disclosure, eCFR, employer-stock valuation, corporate transaction, provider-cycle, participant-notice, testing or correction guidance changes in a way that affects the amendment decision.

Official Sources and Limits

Legal, timing, notice, correction, employer-stock and responsibility claims cite official sources nearby.

Sources were accessed July 31, 2026. The guide relies on official IRS, DOL, OLRC and dated eCFR API materials. OLRC pages state laws in effect on July 31, 2026 for cited Code and ERISA sections. eCFR API URLs use the latest verified dated API snapshot available because ordinary HTML access can be unreliable. IRS and DOL page review dates vary and are disclosed in each source note. This guide does not approve a specific ROBS transaction, document, amendment, correction, determination-letter reliance, safe harbor status, filing choice, valuation, notice delivery or participant outcome.

  1. [1] IRS amend or update a plan

    Accessed July 31, 2026. IRS page last reviewed August 26, 2025. Used for amendment resources, Operational Compliance List, Required Amendments List, pre-approved cycles, and document-update framing.

  2. [2] IRS Required Amendments List

    Accessed July 31, 2026. IRS page last reviewed July 21, 2026. Used for individually designed plan RAL boundaries and the general deadline of the end of the second calendar year after list issuance unless another date is stated.

  3. [3] IRS Operational Compliance List

    Accessed July 31, 2026. IRS page says updated February 2023 and explains OC List limits. Used for operational effective-date separation and the warning that plans must operate from the effective date even if an item is absent from the OC List.

  4. [4] Rev. Proc. 2022-40

    Accessed July 31, 2026. Used for the current RAL and OC List framework and remedial amendment system boundaries.

  5. [5] Rev. Proc. 2016-37

    Accessed July 31, 2026. Used for the post-2017 individually designed plan determination and remedial amendment-cycle framework.

  6. [6] IRS determination, opinion and advisory letters

    Accessed July 31, 2026. Used for document-letter scope and the distinction between document reliance and operation.

  7. [7] IRS ROBS compliance project

    Accessed July 31, 2026. Page last reviewed November 16, 2025. Used for ROBS structure, determination-letter limits, discriminatory amendments, benefits, rights, features, Form 5500, Form 1120, valuation, employee access and Form 1099-R concerns.

  8. [8] IRS ROBS examination guidelines

    Accessed July 31, 2026. IRS memorandum dated October 1, 2008. Used as examination context for ROBS stock, valuation, adequate consideration, records, fees, discrimination, and prohibited-transaction development, not as current approval.

  9. [9] 26 USC 401

    OLRC text contains laws in effect on July 31, 2026. Used for qualified trust, exclusive benefit, 401(k), safe harbor, and employer-security context.

  10. [10] 26 USC 401(a)(35)

    OLRC text contains laws in effect on July 31, 2026. Used for publicly traded employer-securities diversification boundaries and why private ROBS stock needs separate analysis.

  11. [11] 26 USC 411(d)(6)

    OLRC text contains laws in effect on July 31, 2026. Used for anti-cutback protection of accrued benefits, optional forms of benefit, early retirement benefits and retirement-type subsidies.

  12. [12] 26 CFR 1.411(d)-4

    Dated eCFR API, July 21, 2026; accessed July 31, 2026. Used for protected benefits, optional forms, section 411(d)(6) limits and regulation-level exceptions.

  13. [13] 26 CFR 1.411(d)-3

    Dated eCFR API, July 21, 2026; accessed July 31, 2026. Used for applicable amendment dates and anti-cutback concepts.

  14. [14] 26 CFR 54.4980F-1

    Dated eCFR API, July 21, 2026; accessed July 31, 2026. Used for 204(h) notice recipients and timing when an applicable pension plan amendment significantly reduces future accruals or subsidies.

  15. [15] 29 USC 1054

    OLRC text contains laws in effect on July 31, 2026. Used for ERISA anti-cutback and significant-reduction handoff.

  16. [16] 29 USC 1022

    OLRC text contains laws in effect on July 31, 2026. Used for SPD and SMM content standards.

  17. [17] 29 USC 1024

    OLRC text contains laws in effect on July 31, 2026. Used for SMM, SPD, SAR, furnishing and request timing.

  18. [18] 29 USC 1027

    OLRC text contains laws in effect on July 31, 2026. Used for six-year report and disclosure record-retention floor.

  19. [19] 29 USC 1104

    OLRC text contains laws in effect on July 31, 2026. Used for fiduciary duties, prudence, documents, diversification and service-provider monitoring.

  20. [20] 29 USC 1108(e)

    OLRC text contains laws in effect on July 31, 2026. Used for qualifying employer-security acquisition or sale conditions including adequate consideration and no commission.

  21. [21] DOL Meeting Your Fiduciary Responsibilities

    Accessed July 31, 2026. DOL publication dated September 2021. Used for fiduciary process, following documents, service-provider monitoring, disclosures and records.

  22. [22] IRS mid-year safe harbor changes

    Accessed July 31, 2026. Page last reviewed November 16, 2025. Used for Notice 2016-16 safe harbor midyear amendment, notice, election opportunity, permissible and impermissible change boundaries.

  23. [23] IRS EPCRS overview

    Accessed July 31, 2026. Page last reviewed July 31, 2026. Used for SCP, VCP, Audit CAP, correction principles, practices and procedures, records, and limits on correction promises.

  24. [24] Rev. Proc. 2021-30

    Accessed July 31, 2026. Used as the governing EPCRS procedure identified by IRS for correction method boundaries and retroactive-amendment limits.

  25. [25] Notice 2022-33

    Accessed July 31, 2026. Used for SECURE Act, Miners Act and CARES Act section 2203 amendment-deadline extension distinctions.

  26. [26] Notice 2022-45

    Accessed July 31, 2026. Used for CARES Act section 2202 and Relief Act disaster amendment-deadline extensions.

  27. [27] Notice 2024-02

    Accessed July 31, 2026. Used for SECURE 2.0 guidance and statutory amendment timing as modified by later authority.

  28. [28] Notice 2024-82

    Accessed July 31, 2026. Used as the 2024 Required Amendments List with a general December 31, 2026 deadline from the IRS RAL page.

  29. [29] Notice 2025-60

    Accessed July 31, 2026. Used as the 2025 Required Amendments List with a general December 31, 2027 deadline from the IRS RAL page.

  30. [30] IRS Form 5500 Corner

    Accessed July 31, 2026. Used for Form 5500-series plan-year filing coordination and extension handoff.

  31. [31] DOL Form 5500 Series

    Accessed July 31, 2026. Used for EFAST2 annual reporting coordination and amended filing handoff.

  32. [32] 2025 Instructions for Form 5500

    Accessed July 31, 2026. Used for amended return, signature, final return and record controls for annual reporting.

  33. [33] 26 USC 410

    OLRC text contains laws in effect on July 31, 2026. Used for participation and coverage boundaries.

  34. [34] 26 USC 401(a)(4)

    OLRC text contains laws in effect on July 31, 2026. Used for nondiscrimination framing.

  35. [35] 26 USC 416

    OLRC text contains laws in effect on July 31, 2026. Used for top-heavy impacts.

  36. [36] 26 CFR 1.401(a)(4)-4

    Dated eCFR API, July 21, 2026; accessed July 31, 2026. Used for benefits, rights and features nondiscrimination analysis.

  37. [37] 26 USC 414

    OLRC text contains laws in effect on July 31, 2026. Used for employer, plan administrator, controlled-group and related-employer concepts.

  38. [38] 29 CFR 2550.404a-5

    Dated eCFR API, July 21, 2026; accessed July 31, 2026. Used for participant-directed investment and employer-securities disclosure controls.

  39. [39] 29 CFR 2520.101-3

    Dated eCFR API, July 21, 2026; accessed July 31, 2026. Used for blackout notice handoff when direction, diversification, loan or distribution rights are suspended.

  40. [40] Notice 2016-16

    Accessed July 31, 2026. Used for the safe harbor 401(k) midyear-change conditions, supplemental notice timing, election opportunity, and examples of prohibited midyear changes.

Treat every amendment as a controlled change record

Keep the signed version, date logic, operational evidence, participant handoff and correction analysis together.

Notice handoff Annual checklist