A population figure changes in a new download, and a neighborhood chat immediately supplies a story: more people must have arrived since the old figure was published. That may confuse a revised estimate of an earlier date with a new event. The Census Bureau's Population Estimates Program explains why its annual versions can alter earlier estimates. Our original release note below uses invented figures to keep the date being estimated separate from the dates on which estimates were released.

Invented releasePublishedReference dateInvented estimate
A2025-03-202024-07-0150,000
B: revision of same date2026-03-202024-07-0150,300
B: a different reference year2026-03-202025-07-0151,300

A version can reach backward

The Census FAQ uses vintage for a particular version of estimates. It says each vintage contains the annual series back to the most recent decennial census, and the latest vintage supersedes the earlier estimates for those dates. Its revision explanation names updated input data, methodology changes and legal boundary changes as usual reasons for revisions.

The important consequence for a reader is that a new file can contain a new estimate of an old reference date. The release date belongs to the publication of the estimate; it is not necessarily the date of the population being described. Reading only the file's newest timestamp can therefore turn a revision into an event the data never claimed.

Keep one reference date through two releases

Imagine an entirely fictional place called Example City. Teaching release A, published March 20, 2025, estimates its population on July 1, 2024 at 50,000. Teaching release B, published March 20, 2026, estimates the same July 1, 2024 population at 50,300. These release names, dates and values are invented; they are not Census releases or measurements for a real city.

The difference is 300, but both numbers still refer to July 1, 2024. In this example, the new release has changed the estimate assigned to that date. It has not supplied evidence that 300 people moved in on March 20, 2026, or during the interval between our two publication dates. The difference might prompt a question about the revision, but it cannot answer that question by itself.

A compact revision note would read: reference date July 1, 2024; previous teaching release A, March 20, 2025, value 50,000; replacement teaching release B, March 20, 2026, value 50,300; revision published March 20, 2026. Keep the explanation of the change unresolved unless the source actually supplies it. A reason named in a general FAQ is not proof that it caused this particular invented revision.

A different reference date asks a different question

Now add one more invented entry to release B: 51,300 for July 1, 2025. Comparing 50,300 for July 1, 2024 with 51,300 for July 1, 2025 compares two reference dates within the same teaching version. The arithmetic difference is 1,000. That is a different comparison from the 300-person revision of the 2024 estimate.

The temptation is to use whichever pair creates the strongest sentence. Instead, name the comparison before selecting the numbers. Are you describing a changed estimate for one date, or a difference between estimates for two dates? Preserve the relevant geography and definitions too. Matching calendar labels alone would not repair a change in which place or population a row describes.

Publish the version note beside the conclusion

For the fictional revision, a defensible sentence is: release B revises Example City's July 1, 2024 estimate from 50,000 to 50,300. It is shorter and more precise than saying the city gained 300 people since the earlier file appeared. The sentence identifies the action performed by the release rather than inventing a demographic cause.

For a real data note, keep the source's version identifier, reference date and release or revision publication date with the value you use. If you need to explain an older report, retain the older version as historical evidence of what that report used, while making clear which estimate now supersedes it. Replacing a number should improve the account of the evidence, not erase the route by which a reader can understand the change.

Sources & further reading

Published sources for the details and examples discussed in this story.