Why Variance Reports Mislead: Reading Baseline-Versus-Actual Without Fooling Yourself
A variance report is supposed to tell you whether a project is on track. Too often it tells a story that is comforting, alarming, or simply wrong, because the people reading it skip past how the numbers were built. Comparing actuals to a baseline is one of the most useful disciplines in project delivery, but it is also one of the easiest to misread. The pandemic recovery has made this worse: schedules built before supply disruptions are still in use as baselines, and teams now spread across home offices interpret the same figures very differently. Here are the mistakes that recur, and how to avoid each one.
Mistakes that flatter or frighten you
Treating money spent as progress made. If you compare actual cost to your time-phased budget and call a project 'under budget,' you may simply be behind schedule and not spending yet. Cost variance only means something next to the value of work actually completed, which is why earned value pairs cost with physical progress.
Comparing against a stale baseline. A baseline frozen before a major scope or supply shock is no longer a fair yardstick. Re-baseline through a controlled change, and keep the original visible, rather than quietly measuring against a plan everyone knows is dead.
Reading a single snapshot as a trend. One period's favourable variance can reverse the next. Look at how variance has moved over several periods before declaring a direction; a point is not a line.
Ignoring how percent-complete was estimated. If progress is self-reported by the people doing the work, optimism creeps in. Tie percent-complete to objective milestones or deliverables, not to gut feel.
Read schedule and cost together
Earned value gives you two indices worth watching side by side. The schedule performance index compares the value of work performed to the value planned; below 1.0 means you are behind. The cost performance index compares the value of work performed to what it cost; below 1.0 means you are overspending for the progress made. Read in isolation, either can deceive.
Behind schedule but on cost can mean a resource shortage, not waste; the fix is capacity, not penny-pinching.
On schedule but over cost often means you bought speed through overtime or expediting; decide whether that pace is still worth it.
Favourable on both can still hide trouble if early easy work front-loaded your progress and the hard work is yet to come.
Treat a variance as a question, not a verdict. A red number is a prompt to ask why, where, and whether it will persist, not an instruction to punish whoever owns that line. Teams that use variance to assign blame quickly learn to manage the report instead of the work.
Make the report trustworthy
The fix for most of these errors is upstream of the report itself. Define what counts as complete before work starts, capture actuals on a consistent cadence, and write down the cause of any variance over a threshold so the explanation travels with the number. With hybrid teams, that written cause matters more than ever, because the hallway conversation that once filled the gap no longer happens. A variance report that records why is far more useful than one that only records how much.
If your variance reports raise more questions than they answer, XNM's program & project delivery advisory can help you set up controls that measure real progress and surface problems while there is still time to act.