Editorial & Corrections Policy

How Pages Are Produced

PlainPension's data pages are generated from the Public Plans Database (PPD), the upstream public-pension dataset used by this portal. We load that source into a structured database and render the figures, counts, rankings, rates, dates, and breakdowns from those records; they are not hand-typed or estimated by us.

This is a data-publishing model: the same template renders many pages so that every record is covered consistently. We are transparent that these data pages are produced programmatically from the source records rather than written individually. The editorial work goes into the pipeline, how data is sourced, normalized, deduplicated, and presented, into the methodology, and into the written guides.

Sourcing Standards

• Named upstream source. Each plan figure traces to the PPD dataset used by this portal, with the source and its limitations described on the methodology page.
• Attribution in context. Pages name the source and link to it where applicable, and show the date the data reflects.
• Derived values are labeled. Numbers we compute ourselves, rankings, trends, ratios, are presented as our analysis of the source data, distinct from the publisher's own figures.
• No invented data. Where a field is unavailable for a record, the page says so rather than filling the gap with an estimate.

Update Cadence

We refresh the underlying data on a regular schedule as the source publishes updates, so there can be a lag between an official release and its appearance here. Historical records remain in our database for reference, and the data-vintage date is shown on the relevant pages.

Corrections Process

If a record on PlainPension looks wrong, please tell us. Because our pages are generated from the source datasets, a genuine error almost always traces back to either the source data or our processing of it, so this is how we handle a report:

1. Report. Use the contact page with the page URL and the value that looks off.
2. Verify. We compare the record against the published source.
3. Fix at the source. If the value is wrong on our side, we correct it in the database and pipeline that generate the page, not just on the single page, so every affected page is fixed at once. If the record faithfully reflects the published data, we explain that and point to the primary source.
4. Note it. Material corrections are recorded in the public changelog below when the corrected data or method ships.

We aim to acknowledge data-error reports within a few business days.

Data Changelog

• July 23, 2026: corrected the ARC-payment field from the official PPD API and removed records without an authoritative value rather than retaining the prior corrupted values.
• July 23, 2026: added the PPD source-release monitor and a scheduled 90-day source check.

Editorial Independence

PlainPension is an independent publisher and is not affiliated with the agencies or organizations that publish the underlying data. We do not accept payment, sponsorship, or promoted placement from any covered entity. Our only revenue is contextual display advertising served by Google AdSense; advertisers do not influence what we cover or how we present it.

Appropriate Use

PlainPension is for informational purposes only and does not constitute medical, safety, or other professional advice. Details can change after we ingest a record. For any important decision, confirm the current information with the primary source or a qualified professional (such as a licensed clinician or pharmacist). See our full disclaimer.