The US Department of Labor's Form 5500 — the annual report of employee benefit plan that Section 104(a) of the Employee Retirement Income Security Act of 1974 (ERISA) and Section 6058(a) of the Internal Revenue Code require the plan administrator of each ERISA-covered employee benefit plan and each plan subject to the IRC's reporting requirements to file annually with the EBSA jointly with the IRS and PBGC under the EFAST2 electronic filing system by the last day of the seventh month following the close of the plan year — produces one of the most comprehensive publicly accessible records of customer-side employee-benefit-plan activity in the United States. The EFAST2 public document system returns approximately eight hundred thousand Form 5500 filings per year, the related Form 5500-SF short-form filings cover plans with fewer than one hundred participants that satisfy the simplified-reporting conditions, and the Form 5500-EZ filings cover one-participant retirement plans. The filings are submitted in the EFAST2 XML structured-data format that enables programmatic extraction of the plan sponsor's identification, the plan number, the plan type, the participant count, the schedule attachments, the service-provider identifications on Schedule C, and the financial-information schedules. Together with the Form M-1 for multiple employer welfare arrangements, the related Schedule SB (single-employer defined-benefit-plan actuarial information), the Schedule MB (multiemployer defined-benefit-plan actuarial information), the Schedule H (large-plan financial information), the Schedule I (small-plan financial information), the Schedule C (service-provider compensation), the Schedule A (insurance information), the Schedule D (DFE/participating plan information), the Schedule G (financial-transaction schedules), and the Schedule R (retirement-plan information), the DOL Form 5500 archive is the largest publicly accessible source of customer-side product mentions in the retirement-plan recordkeeping, third-party administrator, group-health benefits, investment-management, custodial, and ERISA fiduciary technology sectors in the US — and almost none of it is being systematically extracted as social proof by the recordkeepers, TPAs, group-health vendors, fiduciary technology providers, and investment managers whose products are being mentioned.
The under-extraction is not because the archives are inaccessible. The EFAST2 system publishes the filed documents in real time, the DOL's Form 5500 search interface allows full-text and metadata queries across the filing corpus, and the EFAST2 Data Sets program provides annual structured-data extracts that enable programmatic processing of the XML-tagged elements at the corpus scale. The under-extraction is because the employee-benefit-plan social-proof workflow has not been constructed to handle the highly regulated and fiduciary-sensitive disclosure source format — the Form 5500 filings read as ERISA-compliance documents rather than as product endorsements, and the adjacent Schedule C service-provider compensation disclosures read as fee-transparency documents rather than as customer outcomes. This guide formalizes the four-stage extraction workflow that converts the archives into citable customer outcomes, the discrimination between the large-plan Schedule H axis and the small-plan Schedule I axis, and the attribution-safe quoting framework that meets the DOL's ERISA fiduciary-marketing restrictions, the IRS's qualified-plan-marketing restrictions, and the SEC's investment-adviser-marketing rules that apply to plans whose service providers are also SEC-registered investment advisers under the Investment Advisers Act of 1940.
Why the Form 5500 archive is under-extracted as social proof
The Form 5500 filings are the most counterintuitive social-proof sources in the US employee-benefit-plan service-provider sector. The filings are submitted by plan administrators as required ERISA disclosures under Section 104(a) of ERISA, and the surface content is the plan-administrative reporting record — the plan-identification fields in Part I, the plan-characteristics fields in Part II Line 8 (plan-characteristic codes that identify the plan type, the funding arrangement, the benefit features, and the special-status conditions), the participant-count fields in Part II Line 6, the financial-information schedules (Schedule H for large plans of one hundred participants or more, Schedule I for small plans of fewer than one hundred participants), the Schedule A insurance-contract information for benefits provided through insurance contracts, the Schedule C service-provider-and-compensation disclosure for plans required to file Schedule H, the Schedule D direct-filing-entity disclosure for plans that participate in master trusts or pooled separate accounts, the Schedule G financial-transactions schedules for non-exempt party-in-interest transactions, and the Schedule R retirement-plan-distribution disclosure. The technology platform names — the specific recordkeeper, the specific third-party administrator, the specific custodian, the specific group-health platform, the specific fiduciary-technology compliance vendor, the specific managed-account-program provider, the specific stable-value investment manager, the specific target-date-fund provider — are directly named in Schedule C as the service providers receiving direct or indirect compensation in excess of the five-thousand-dollar reporting threshold, and the platform mentions appear with the service provider's EIN, the service codes (forty-five distinct service codes that identify the nature of services provided), the relationship code (whether the provider is a fiduciary, an investment adviser, or another type), and the gross and indirect compensation amounts.
The surface read of the Form 5500 archive is therefore product-neutral — the filings document the plan's compliance with ERISA's reporting and disclosure requirements without editorializing about any vendor. The under-extraction is the failure to recognize that the Schedule C disclosure is the fiduciary-verified attestation that the service provider was retained for the disclosed service codes and received the disclosed compensation — the disclosure is signed by the plan administrator under penalty of perjury and is subject to the DOL's Schedule C audit-and-enforcement program, and the disclosure carries higher attestation reliability than a customer testimonial that the service provider has solicited and that may have been edited. The extraction workflow that joins the Form 5500 plan-identification fields with the Schedule C service-provider disclosure produces a social-proof asset that documents both the service provider's retention by the plan and the plan's regulated-ERISA-plan status — the Schedule C disclosure establishes the service relationship, the Form 5500 plan-identification establishes the plan's ERISA-covered status, and the joined record establishes the citable customer outcome that the recordkeeper, TPA, or group-health-platform vendor can use as social proof.
The Schedule A insurance-contract information is the second source. Schedule A is the insurance-information attachment that the plan administrator files for each insurance contract that provides plan benefits, and the schedule discloses the insurance company's name and NAIC code, the contract number, the premiums paid, the policy fees, and the benefits paid under the contract. The Schedule A filings include the disclosure of group-health stop-loss carriers, the group-life insurance carriers, the group-disability insurance carriers, the group-dental and group-vision insurance carriers, the group-long-term-care insurance carriers, and the captive-insurance arrangements that the plan has placed for risk-funding purposes. The Schedule A filings are extractable as social proof of the insurance carrier's role in the plan's risk-financing architecture; the surface-read approach misses the proof because the schedule is framed as insurance-contract financial disclosure rather than as a customer success story.
The Schedule MB and Schedule SB actuarial-information attachments are the third source. The Schedule MB is the actuarial-information schedule that the multiemployer defined-benefit plan files annually, and the schedule discloses the actuarial firm's name and certification of the funded status, the actuarial assumptions and methods, the funding-improvement-plan or rehabilitation-plan status if the plan is in endangered or critical zone status under Section 432 of the IRC, and the withdrawal-liability schedule for employers that have withdrawn from the plan. The Schedule SB is the actuarial-information schedule that the single-employer defined-benefit plan files annually, and the schedule discloses the actuarial firm's name and certification of the plan's funded status, the actuarial assumptions, the contribution requirements, and the funding-target-attainment-percentage that drives the at-risk-status determination under Section 430 of the IRC. The Schedule MB and Schedule SB filings are extractable as social proof of the actuarial firm's role in the plan's funded-status certification and the firm's specialization in the multiemployer or single-employer defined-benefit context.
The three sources are complementary because they cover different stages of the plan's operational relationship with the service-provider ecosystem. The Form 5500 main filing and Schedule C cover the recordkeeper, TPA, custodian, and fiduciary-technology service relationships. The Schedule A covers the insurance-carrier relationships that fund the welfare-benefit-plan risk transfer. The Schedule MB and Schedule SB cover the actuarial-firm relationships that certify the defined-benefit-plan funded status. The extraction workflow that handles all three sources produces a social-proof asset library that covers the recordkeeping axis, the insurance-funding axis, and the actuarial-certification axis — and the library reads as more credible than a marketing-constructed social-proof library because the source materials are public DOL filings that the prospective customer can independently verify against the EFAST2 system.
The four-stage extraction workflow
The extraction workflow consists of four sequential stages that convert the source archives into citable customer outcomes. The workflow is designed to maintain the legal and reputational safety of the extracted content; the staged construction prevents the premature publication of content that has not been verified for the attribution-safe quoting requirements that ERISA-fiduciary, SEC-investment-adviser, and DOL-marketing rules require.
Stage 1 — Source-archive identification and corpus construction
The first stage identifies the source archives relevant to the service-provider company and constructs a corpus of source documents for extraction. The EFAST2 search interface and the EFAST2 Data Sets are queried by the plan-type filter (single-employer defined-contribution, single-employer defined-benefit, multiemployer defined-benefit, multiple-employer welfare arrangement, fringe benefit plan, group insurance arrangement), the plan-size filter (large plans of one hundred or more participants that file Schedule H, small plans of fewer than one hundred participants that file Schedule I, one-participant plans that file Form 5500-EZ), the schedule-attachment filter (Schedule C for service-provider mentions, Schedule A for insurance-carrier mentions, Schedule MB or Schedule SB for actuarial-firm mentions, Schedule H for large-plan financial-detail mentions), and the platform-mention filter (the service provider's EIN, the service provider's name, the service codes that match the company's service offering); the query returns the filings that mention the company's services on the Schedule C, Schedule A, Schedule MB, or Schedule SB attachments.
The corpus construction is the foundation of the extraction workflow because the corpus determines the upper bound of the extractable customer mentions. The corpus should be constructed broadly in the first iteration — all Form 5500 filings within the past three plan years, all plan types and sizes relevant to the company's service offering, all service-code categories the company is positioned in — to maximize the recall of the extractable mentions, and then narrowed in subsequent iterations to focus on the highest-yield sub-corpora that produce the most citable mentions.
Stage 2 — Product-mention extraction with structured-attribute capture
The second stage extracts the product mentions from the corpus and captures the structured attributes that support the attribution-safe quoting framework. The extraction is performed on the Schedule C service-provider-compensation disclosure, the Schedule A insurance-contract disclosure, the Schedule MB and Schedule SB actuarial-certification disclosure, and the Schedule H financial-information narrative — the documents that contain the structured-data identification of the service providers and the contextual narrative that supports the customer-outcome construction. The extraction identifies the service provider's name and EIN, the plan sponsor's name and EIN, the plan number, the plan-characteristics codes that define the plan's structure and benefits, the participant count and active-versus-retired participant breakdown, the service codes that the service provider was retained for, the gross and indirect compensation, the relationship-to-plan status (fiduciary, investment adviser, recordkeeper, TPA, or other), and the source-document citation (the EFAST2 acknowledgment ID, the filing date, the plan-year-end date, the schedule attachment, the Schedule C line reference).
The structured-attribute capture is the workflow's protection against the attribution-safe quoting requirements under the DOL's ERISA Section 408(b)(2) fiduciary-disclosure regulations, the SEC's Marketing Rule under Rule 206(4)-1 of the Investment Advisers Act, and the IRS's qualified-plan-marketing restrictions. The extracted mentions are stored as structured records with the EFAST2 acknowledgment ID as the anchor; the citation allows the workflow to reconstruct the original context of the mention when the marketing team uses the mention in a social-proof asset. The citation also allows the workflow to detect mention-context decay — when a plan administrator has changed the recordkeeper in a subsequent plan year, when the plan has merged with another plan, when the plan has terminated, when the plan-sponsor employer has been acquired or has consolidated, when the service provider has been acquired or has consolidated — and to retire or update the mention before it becomes inaccurate.
Stage 3 — Attribution-safe quoting framework application
The third stage applies the attribution-safe quoting framework that converts the extracted structured mentions into publishable social-proof assets without violating the DOL, SEC, IRS, and state marketing rules. The framework is built on four principles. The first principle is the public-record-only attribution principle — the social-proof asset cites the EFAST2 acknowledgment ID and the public-filing URL as the source, never representing that the plan administrator has authorized the use of the mention in marketing, and never representing that the named plan participants have endorsed the product. The second principle is the service-code-bounded outcome-attribution principle — the social-proof asset attributes only the outcomes that fall within the service codes the service provider was retained for, never extending the attribution to outcomes that are outside the disclosed service scope (a recordkeeper retained under service code 64 for participant-account recordkeeping should not be attributed for outcomes that fall under service code 27 for investment-management discretion). The third principle is the no-performance-guarantee-implied principle — the social-proof asset uses the structured-data citation to describe historical fact, never representing that the historical performance is predictive of future results, never combining the citation with promotional language that implies guaranteed outcomes for prospective plans. The fourth principle is the plan-fiduciary-respectful tone principle — the social-proof asset avoids language that could undermine the plan administrator's fiduciary discretion, particularly avoiding any suggestion that the plan administrator's selection of the service provider was anything other than a fiduciary decision made in the interest of the plan participants.
The framework application produces a social-proof asset library that the marketing team can use across the company's website, sales-enablement collateral, and prospective-client outreach. The library is organized by service code, plan type, plan size, and outcome category, and the marketing team selects the assets that match the prospective client's plan-characteristics profile to construct the customer-specific social-proof presentation.
Stage 4 — Mention-context decay monitoring and library maintenance
The fourth stage monitors the source archives for mention-context decay and maintains the library currency. The monitoring is performed on a quarterly cycle that ingests the EFAST2 system's new filings, re-runs the platform-mention queries against the new filings, identifies the new mentions that should be added to the library and the existing mentions whose context has decayed (the plan has changed recordkeepers, the plan has merged or terminated, the plan-sponsor employer has been acquired, the service provider's service codes have changed, the relationship-to-plan status has changed), and updates the library. The decay monitoring is the workflow's protection against the use of mentions that have become inaccurate; the marketing team that uses a mention from a plan that has subsequently changed recordkeepers is presenting the prospective client with a mention that does not reflect the current state of the customer relationship.
The large-plan-Schedule-H-versus-small-plan-Schedule-I-axis discrimination
The large-plan Schedule H axis and the small-plan Schedule I axis are the two analytical axes that calibrate the social-proof construction. The large-plan Schedule H axis applies to plans with one hundred or more participants at the beginning of the plan year that are required to file Schedule H and the related Schedule C service-provider-compensation disclosure — the axis includes the substantial-employer single-employer retirement plans, the multiemployer plans, and the large welfare-benefit plans, and the axis triggers the audit-by-an-independent-qualified-public-accountant requirement under ERISA Section 103(a)(3)(A) (with limited audit-waiver conditions for certain plans). The small-plan Schedule I axis applies to plans with fewer than one hundred participants at the beginning of the plan year that are permitted to file Schedule I instead of Schedule H — the axis includes the small-employer retirement plans and the small welfare-benefit plans, and the axis does not require the Schedule C service-provider-compensation disclosure (the small plan reports only summary financial information without the service-provider-detail attachment). The axis discrimination determines the social-proof construction strategy: large-plan mentions are constructed from the structured Schedule C disclosure with the service provider, service codes, and compensation data fully captured, while small-plan mentions are constructed from the Schedule A insurance-contract disclosure (when present) or the plan-characteristics codes that identify the funding arrangement (when the small plan's service provider is not separately disclosed on a schedule attachment).
The eight-week implementation routine
The extraction workflow is implemented across an eight-week routine that builds the social-proof asset library at scale.
Week 1 — Corpus construction and platform-mention query design
The implementation team constructs the source-archive corpus and designs the platform-mention queries. The corpus targets the past three plan years of Form 5500 filings, the plan types relevant to the service offering, and the schedule attachments that contain the service-provider mentions. The queries are designed to match the company's name, EIN, service codes, and product names against the Schedule C, Schedule A, Schedule MB, and Schedule SB attachments.
Week 2 — Initial extraction and structured-attribute capture
The implementation team runs the initial extraction across the constructed corpus and captures the structured attributes for each mention. The week's output is the initial mentions database with the EFAST2 acknowledgment ID, the plan-sponsor identification, the service-code identification, the compensation data, and the relationship-to-plan status fully captured.
Week 3 — Attribution-safe quoting framework drafting
The implementation team drafts the attribution-safe quoting framework templates that the marketing team will use to convert the extracted mentions into publishable social-proof assets. The templates incorporate the four attribution principles and produce a consistent voice across the library.
Week 4 — Compliance review and legal sign-off
The implementation team submits the drafted social-proof templates to the company's compliance and legal teams for review. The review confirms that the templates satisfy the DOL, SEC, IRS, and state marketing rules that apply to the company's service offering.
Week 5 — Initial library publication
The implementation team publishes the initial library of attribution-safe social-proof assets across the company's website, sales-enablement collateral, and prospective-client outreach materials.
Week 6 — Mention-context decay monitoring setup
The implementation team sets up the quarterly mention-context decay monitoring that will maintain the library currency as new Form 5500 filings are submitted to the EFAST2 system.
Week 7 — Sales-team enablement and training
The implementation team trains the sales team on the use of the library, the selection of assets that match the prospective client's plan-characteristics profile, and the attribution-safe presentation of the assets in the sales conversation.
Week 8 — Library performance measurement and refinement
The implementation team measures the library's performance against the company's sales-pipeline metrics and refines the corpus construction, query design, and attribution-safe quoting templates based on the measured performance.
The Form 5500 archive is the highest-volume employee-benefit-plan source-document corpus in the US, and the ProofShow extraction workflow converts the corpus into a defensible, attribution-safe social-proof asset library that the recordkeeper, TPA, insurance carrier, actuarial firm, and fiduciary-technology service provider can use to construct credible customer-outcome narratives for the prospective-client pipeline. For broader ERISA-and-fiduciary social-proof workflow guidance, see the ProofShow customer SR 11-7 model risk management governance and validation report product mentions extraction workflow and the ProofShow customer SOC 2 audit report and ISO 27001 certification product mentions extraction workflow.