Explain changes in a report accurately
Separate new work, changing populations and late-arriving information when comparing results.
Explain changes in a report accurately
A percentage can change for several reasons. More items may qualify, the population may grow, or earlier events may arrive late. Check which explanation applies before attributing an improvement to a new process.
Compare the same definitions
1. Keep the earlier report’s source version, population and time boundary. Do not silently overwrite the baseline.
2. Compare the included record identities. Identify new or removed items separately from changes to existing items.
3. Recalculate both the qualifying count and total population. For example, a change from 3 of 9 to 7 of 10 combines more qualifying results with a larger denominator.
4. Explain the difference in plain language. Use the two counts alongside percentages rather than presenting only a dramatic relative increase.
Handle late information
An event has a time when it happened and a time when it reached the reporting source. A review received today may describe work completed yesterday.
If that changes a previous snapshot, label the new result as a restatement and explain the late-arriving information. Do not change the event’s time just to make it fit the reporting narrative.
Check freshness at the record level
A Last updated label is useful, but it does not by itself prove that a particular source change is present. Find the changed record and check its new value in the report.
If the value is absent, check the source, mapping and reporting process with the responsible owner. Do not promise a refresh interval from one observed example or assume that repeatedly refreshing will fix missing data.
Your result is an explanation readers can trust: what changed in the work, what changed in the population and what changed in the information available.
Continue learning
In this series: Build useful business reports — guide 7 of 8.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.