Floemdata
BI & Reporting

Report Changes: Versioning and Transition

Why old numbers stop matching when a report definition changes. Version numbers, change notes and a transition period to manage report changes; Floemdata status.

Floemdata · · 4 min read
Two banks joined by a solid deck; below it a dashed older span stops short at an amber bar

In the March meeting someone said “net sales were 4.2 million”; in April the report shows 3.9 million for the same March. Nobody broke the data: the report's definition of net sales changed in between, and returns are now deducted. The figures are a fictional example, but the situation is common. The problem is not that the definition changed; it is that nobody was told.

Why old numbers stop matching

  • The definition changed: a filter, scope or formula was updated, and past periods were recalculated with the new definition.
  • The source changed: a retroactive correction was made in the source system, or a different table started to be used.
  • The data was refreshed: the report read from a cache, and on reload the late-arriving records were added.

Only the first is a report change, but to the reader all three look the same: “the number changed.” That is why the reason for a change needs to be on record.

Three simple habits

  • Version number: give every report definition a version. When the definition changes the version goes up, and the report shows which version it was calculated with.
  • Change note: three lines are enough: what changed, why, and which periods it affects. The note should be readable next to the report.
  • Transition period: for a large definition change, show the old and new figures side by side for one or two periods and explain the gap.

Deciding whether to recalculate the past

When a definition changes, do you recalculate past periods with the new definition or freeze the old figures? Both are defensible; the choice must be written down. If you recalculate, numbers in earlier meeting records no longer match the report; if you freeze, comparing two periods may become meaningless. If an official figure such as a financial close is involved, do not change it; add the new definition as a new report.

Where Floemdata stands

In Floemdata the dashboard and the assistant pass figures through the same compiler; this is written in the product documents as a design decision so that one definition gives the same result everywhere. We could not find in the product documents a feature that gives a report definition a version number, shows a change note, or presents earlier versions side by side; the product does not provide these today. The habits in this post can be applied by hand with any tool.

To start, write the current form of your most used report definition and its last change date on one page, and open a heading for change notes. Questions are welcome at info@floemdata.com or via Floemdata.

← All guides