PBGC Reportable Event Notices: Form 10 Deadlines, Advance Notice Rules, and the Filing Record Plan Sponsors Must Keep

Scope and reporting framework

ERISA section 4043 and 29 CFR Part 4043 require plan administrators and contributing sponsors to notify the Pension Benefit Guaranty Corporation (PBGC) of specified events that may affect a sponsor's ability to continue a pension plan.

This guide addresses reportable events for single-employer defined benefit plans. The rules are distinct from multiemployer-plan withdrawal liability notices, which arise under a different regime. Part 4043 expressly waives its reportable-event requirements for multiemployer plans.

Most reportable-event notices are filed after the event using Form 10. Certain covered sponsors must provide advance notice using Form 10-Advance. Large cumulative funding underpayments have a separate notice requirement using Form 200.

Form 10: the post-event deadline

The plan administrator and each contributing sponsor generally must notify PBGC within 30 days after that person knows or has reason to know a reportable event occurred. The filing deadline therefore depends on the event-specific facts and when the responsible person knew, or had reason to know, that it occurred.

Form 10 covers these events:

The table identifies the principal event categories, not a substitute for analyzing each definition, waiver, extension, or exception. Some events have specific thresholds and measurement rules. A transaction, for example, can trigger more than one event category, with each obligation assessed under its own rule.

PBGC's reportable events guidance provides the event list and filing instructions. The responsible parties should verify the applicable regulation and current instructions before closing an event review.

Form 10-Advance: when advance notice applies

Advance notice is not a general requirement for every nonpublic sponsor or every reportable event. Under § 4043.61, it generally applies when the relevant contributing sponsor and controlled-group members are nonpublic, aggregate unfunded vested benefits exceed $50 million, and aggregate plan assets are less than 90% of the aggregate premium funding target. The calculation applies across relevant plans maintained by the sponsor and controlled group.

For a covered event, Form 10-Advance is generally due at least 30 days before the event's effective date. Subpart C identifies the event categories subject to advance reporting:

The 30-day advance period is a default, not a universal deadline in every fact pattern. The regulation provides event-specific waivers and extensions. For example, the notice date for a minimum funding waiver application is extended until 10 days after the event. For certain insolvency proceedings begun against a controlled-group member, the notice date is extended until 10 days after the proceeding begins. PBGC can also shorten the advance period after reviewing a filing.

When an event is subject to both post-event and advance reporting, a notice filed first satisfies both requirements under § 4043.3. Confirm this rule against the specific event and filing circumstances before relying on it.

Active participant reductions: check the current waiver

The active-participant reduction rule in § 4043.23 distinguishes single-cause events from attrition events. Single-cause events include reductions resulting from circumstances such as a reorganization, discontinued operation, mass layoff, or early-retirement incentive program. The rule generally tests whether the reduction attributable to a new single cause exceeds 20% of the plan's active participants at the beginning of the plan year.

PBGC's Technical Update 26-1, issued September 18, 2026, prospectively waives reporting of an attrition event under § 4043.23(a)(2) when the notice deadline falls on or after that date. The waiver remains in effect until the effective date of a final regulation addressing attrition events. It does not waive reporting for a single-cause event or another reportable event. Review the Technical Update and document whether it applies to the particular event.

Form 200: a separate missed-contribution notice

Form 200 is not a substitute name for Form 10. Under § 4043.81, Form 200 is required when the unpaid balance of a required contribution, including interest, combined with prior unpaid required contributions and interest, exceeds $1 million. It is due within 10 days after the due date for a required payment that was not made.

A timely Form 200 filing for the same missed contribution also satisfies the Form 10 notice requirement under § 4043.25. The filing remains a separate statutory notice and does not receive the confidentiality protection that applies to reportable-event notices filed under ERISA section 4043.

Electronic filing and submission evidence

PBGC requires reportable-event notices to be prepared and submitted electronically through its e-Filing Portal's 4043 module. The PDF forms on PBGC's website are illustrative only. They are not substitutes for completing and submitting a filing in the portal.

Form 10 instructions state that a filing is considered submitted when the notice and required additional information have been submitted through the portal. A partially completed draft or saved filing is not a completed filing. Each required event must be filed separately, and a single occurrence may require notices for more than one plan.

A filing record should preserve:

• The event type, applicable regulation, and event date.
• The date the responsible person knew or had reason to know of the event.
• The deadline calculation and any claimed waiver, extension, or exception.
• The person responsible for preparing, reviewing, certifying, and submitting the notice.
• The completed filing, supporting documents, and exact versions submitted.
• The portal submission confirmation and filing date.
• Any PBGC correspondence, requests for additional information, and responses.
• Any correction, amended submission, or related internal decision record.

This record connects the triggering facts to the deadline determination and final submission. A structured evidence process also supports audit-trail controls for legal notices.

Filing controls for plan sponsors and administrators

A repeatable workflow clarifies ownership and preserves the basis for each filing decision.

1. Identify the event. Compare the relevant transaction, funding, benefit, or controlled-group facts with the event definitions in Part 4043.
2. Identify the responsible filer. Confirm the plan administrator, contributing sponsor, and any authorized representative responsible for the filing.
3. Set the correct clock. Record the event date, knowledge date, effective date where applicable, and applicable deadline.
4. Test reporting pathways. Determine whether post-event reporting, advance reporting, Form 200, or more than one requirement applies.
5. Review waivers and extensions. Verify each applicable provision and retain the factual basis for relying on it. Do not assume that one waiver covers multiple reportable events arising from the same occurrence.
6. Submit and retain evidence. Complete the filing through the portal, confirm submission, and preserve the complete supporting record.
7. Monitor follow-up. Assign an owner for PBGC requests, corrections, and deadlines for additional information.

PBGC regularly monitors compliance with Part 4043. Failure to file required information on time can result in penalties under ERISA section 4071 and 29 CFR Part 4071, in addition to other available remedies. See PBGC's reportable events page for filing assistance and current instructions.

A controlled filing process preserves the event analysis, clarifies accountable ownership, and produces a defensible submission record. National Compliance Registry's services support secure records, assigned accountability, and controlled evidence practices across regulated workflows.

General compliance information, not legal advice.