Core Sources
Form 5500
The module is built primarily from Form 5500 filing datasets and related processed rows.
Business
About The Business Module
The Business module turns Form 5500 filing data into searchable company, filing, and plan-level views with stable URLs and historical context.
Primary Entities
Companies
Sponsor-centered company pages aggregate filings, plans, trends, and related detail.
Time Horizon
Historical
The module is built to expose trends across years, not only the latest filing.
Use Case
Comparison
The structured fields are designed for future cross-company comparison and ranking features.
What The Business Module Covers
This module focuses on public retirement-plan filing data and the sponsors behind those filings.
It is intended to make large filing datasets usable through stable company pages, filing detail pages, historical aggregates, and search.
How The Data Is Structured
Filings remain first-class records, but the module also projects sponsor-level company summaries so people can see aggregated activity rather than isolated filing rows.
Address, location, and trend data are normalized in the backend so the web UI does not need to reconstruct those relationships on every request.
What To Expect
The Business module is strongest when you need stable sponsor identity, filing history, or large-scale aggregate trends.
It should not be treated as a substitute for filing-by-filing legal review; the source filings still matter.
FAQ
What is the main public data source here?
The current Business module is centered on Form 5500 data and related normalized sponsor and filing projections.
Are the company pages direct source records?
No. Company pages are platform-built projections that group and summarize sponsor-level filing history from the underlying filing data.
Can I rely on the module for historical trends?
Yes, that is one of the main goals of the module. It is designed to make year-over-year filing and asset trends easy to inspect.
Will this module get compare pages too?
Yes. The URL and UI patterns are being built with reusable compare behavior in mind, even where a domain-specific compare page is not live yet.