Why a trend line needs stored snapshots, not recalculated history
Most owner spreadsheets have a tab for the current position and a chart that claims to show the last twelve months. Look closely at how the chart is built. If the twelve historical points are formulas that reference today's registers, the chart is not showing history. It is showing what today's data would have looked like if it had always been this way.
That distinction matters the first time a change order is reclassified, a contingency draw is moved between funds, or a pay application is corrected. Each of those edits silently changes every historical point. The board approved a number in March. By September, the March number in the chart is different, and nobody can say what the board actually saw.
What a snapshot is
A snapshot is a copy of the full owner position taken at a fixed moment, usually the day the monthly report is issued, and never edited afterward. It holds the GMP as amended, the anticipated final cost, contingency remaining in each fund, buyout coverage, allowance status, the change order register with each item's classification at that date, and the certified pay application figures.
Next month a new snapshot is taken. The trend line connects the snapshots. If a classification changes in month nine, the month nine snapshot reflects it and the month eight snapshot does not. The chart shows a step, and the step is true: that is the month the owner's understanding changed.
What recalculated history does instead
A recalculated chart has no stored past. It computes each historical point by filtering current data by date. Change orders dated before August count toward August. That sounds reasonable until you ask what classification the change order had in August. Current data only holds the current classification. The August point is rebuilt with September's knowledge.
A fictional example. A fictional $29 million elementary school carries a $640,000 PCO for an MEP coordination conflict. In May it is unclassified and sits in the contractor's column. In August the owner agrees it was a design gap and it moves to the owner's column. A recalculated chart now shows the owner's exposure rising in May, because the PCO is dated May. The May report the board actually received showed no such rise. Any audit that compares the May report to the chart finds a discrepancy, and the owner's team cannot explain it.
Why it matters beyond the chart
Public owners answer to auditors, bond oversight committees and records requests. Developers answer to lenders and equity partners who received a monthly report and may later ask why the forecast moved. Owner's representatives answer to clients who remember what they were told. In every case the question is the same: what did we know, and when did we know it. Recalculated history cannot answer it. Stored snapshots can.
Snapshots also protect against a quieter problem. When the only history is recalculated, correcting an error in a register is risky, because it changes every report ever issued. Teams avoid corrections to avoid the disruption. With snapshots, the correction shows up in this month's figure, the previous figures stand as issued, and the change is visible as a step with a reason.
What the snapshot should record
At minimum: the date, who issued it, every headline figure, the state of each register, and a list of flags open on that date. Store it read only. If it needs to be changed, issue a corrected snapshot with a note, and keep the original.
Doing it without a spreadsheet
A spreadsheet can hold snapshots if each month is copied to a values only tab and never touched again. Most teams start that way and stop within a quarter, because the copy step is manual and the tabs multiply. The discipline fails for the same reason most monthly routines fail: it depends on someone remembering.
Costwitness takes the snapshot when the monthly report is issued, stores it as a separate record, and builds every trend line from stored snapshots rather than from current data. A reclassification in month nine appears as a step in month nine with the audit entry beside it. The software keeps the record. The owner's team decides what the step means and how to explain it to the board.
What to do this month
- Open your trend chart and trace one historical point back to its source. If it is a formula over current data, it is not a snapshot.
- Before issuing this month's report, save a values only copy of the full position with the issue date in the file name.
- Pick one past reclassification and check whether last year's report still shows the figure the board was given at the time.
Questions on this
Does storing snapshots mean historical errors can never be fixed?
No. It means they are fixed by issuing a correction, not by editing the past. The original snapshot stays, the corrected one is added with a note, and the trend shows both. That is the same approach an accounting close uses.
How long should snapshots be kept?
For the life of the project plus whatever retention your records policy or lender requires. Public owners should check their records retention schedule. Snapshots are small, so there is little cost to keeping all of them.
Is a PDF of the monthly report enough?
A PDF is a record of what was issued and is worth keeping. It is not a snapshot in the working sense because the figures cannot be compared or charted without retyping them. Keep both: the PDF as the issued document and the structured snapshot as the data.
In the product
Monthly owner report, Anticipated final cost, Change order register. Free tool: Pre-GMP Readiness Score, Cost Influence Curve.
Keep reading
Earlier: What a monthly owner report should contain, in order. Later: The anticipated final cost waterfall, step by step from the GMP. All articles on owner reporting.
See the report your board would read.
Thirty minutes on a call. We generate the twelve page report on a fictional project and hand you the sample PDF.