Brief Case

29 C.F.R. § 4233.6

Partition information.
CFR 2015 annual edition (revised as of 2015-07-01) · superseded Jul 1, 2016
Back to current
The earliest stored text of this section is effective Jul 1, 2015. Showing that version.
An application for partition must include the following information with respect to the proposed partition:
(a) A detailed description of the proposed partition, including the proposed structure, proposed effective date, and any larger integrated transaction of which the proposed partition is a part (including, but not limited to, an application for suspension of benefits under section 305(e)(9)(G), or a merger under section 4231 of ERISA).
(b) A narrative description of the events that led to the plan sponsor's decision to submit an application for partition (and, if applicable, application for suspension of benefits).
(c) A narrative description of significant risks and assumptions relating to the proposed partition and the projections provided in support of the application.
(d) If applicable, a copy of the plan sponsor's application for suspension of benefits (including all attachments and exhibits). If the plan sponsor intends to apply for a suspension of benefits with Treasury, but has not yet submitted an application to Treasury, a draft of the application may be filed, which must be supplemented by filing a copy of the completed application within the timeframe established in § 4233.10(d).
(e) A detailed description of all measures the plan sponsor has taken (or is taking) to avoid insolvency, and any measures the plan sponsor considered taking but did not take, including the factor(s) the plan sponsor considered in making these determinations. Include all relevant documentation relating to the plan sponsor's determination that it has taken (or is taking) measures to avoid insolvency.
(f) A detailed description of the estimated benefit amounts the plan sponsor has determined are necessary to be partitioned for the plan to remain solvent, including the following information:
(1) The estimated number of participants and beneficiaries whose benefits (or any portion thereof) would be transferred, including the number of retirees receiving payments (if any), terminated vested participants (if any), and active participants (if any).
(2) Supporting data, calculations, assumptions, and a description of the methodology used to determine the estimated benefit amounts.
(3) If applicable, a description of any classifications or specific group(s) of participants and beneficiaries whose benefits (or any portion thereof) the plan sponsor proposes to transfer, and the plan sponsor's rationale or basis for selecting those classifications or groups.
(g) A copy of the draft notice of application for partition described in § 4233.11.
29 C.F.R. § 4233.6 — Partition information. · CFR 2015 annual edition (revised as of 2015-07-01) · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4233.6&asof=2015-01-05 · printed Oct 16, 2026
On this page
  • (a) (a) A detailed description of the proposed partition, inclu…
  • (b) (b) A narrative description of the events that led to the p…
  • (c) (c) A narrative description of significant risks and assump…
  • (d) (d) If applicable, a copy of the plan sponsor's application…
  • (e) (e) A detailed description of all measures the plan sponsor…
  • (f) (f) A detailed description of the estimated benefit amounts…
  • (g) (g) A copy of the draft notice of application for partition…
Implements
ERISA § 4233 (29 U.S.C. § 1413) Partitions of eligible multiemployer plans
Cited by (code & regs)
Guidance addressing this section

No documents are primarily about this section.

Also cited in 2 other documents
PBGC
Final Rules
  • 80 FR 79687 Dec 23, 2015 — Partitions of Eligible Multiemployer Plans (e)(g)
  • 80 FR 35220 Jun 19, 2015 — Partitions of Eligible Multiemployer Plans

No court rulings in the library cite this provision yet.

No private letter rulings in the library cite this provision yet.

Each row is a version of the text as published by the official source. Code dates are the edition/release point that first reflected the change; regulation dates are eCFR effective dates. The library checks the official sources automatically, so new versions appear here on their own; “run” opens the sync that recorded a version.

EffectiveThroughSourceAmended by
Jul 1, 2015Jun 30, 2016CFR 2015 annual edition (revised as of 2015-07-01) run 127View
Jul 1, 2016currenteCFR amendment effective 2017-01-01 run 280 FR 79694, Dec. 23, 2015View · Redline (sign in)
Provision-level history (blame)