# Revisions and Status Transitions

## How does a figure move from Forecast to Preliminary to Final? {#how-does-a-figure-move-from-forecast-to-preliminary-to-final}

Each figure follows a three-stage lifecycle. A **Forecast (F)** is a model prediction for a period that has not yet been reported. Once that period becomes current but official data has not yet arrived, the figure becomes a **Preliminary (P)** estimate produced by the same model. When verified official statistics are released, the figure becomes **Final (Fi)**. Each transition replaces the prior value as better data becomes available.

## What causes a published number to be revised? {#what-causes-a-published-number-to-be-revised}

A published figure is revised for three main reasons. First, official statistics arrive and replace earlier estimates — the normal Preliminary-to-Final transition. Second, continuous model reviews and methodology improvements introduce corrections that refine previously published values. Third, a submitted assessment complaint is resolved, prompting an adjustment to the affected figure. How errors are detected and how the assessment-complaint process works are detailed in the Validation & Accuracy section.

## Where are changes to published data announced? {#where-are-changes-to-published-data-announced}

Every change is documented in the Intratec Release Notes, published each month and publicly available. The Release Notes record data revisions, methodology changes, assessment additions and retirements, and corrections — so any reader, subscriber or not, can trace how and why a figure changed over time. This monthly, public record keeps the published data auditable: a number never changes silently. Each monthly release follows the same workflow — report and database updates, a test-presentation check, the Release Notes, and communication of the changes to readers:

:::text-center
![The monthly release workflow: report and API database update, test presentation display, release notes, and communication.](/static/images/release_workflow.png)
:::