Tracker Notes
How to read the live pages.
The trackers are built to make large defense numbers legible. They are useful when read as evidence-backed estimates, not when treated as final accounting.
Global tracker
The flagship public counter is an approximation layer that turns annual spending into a readable live number. It is designed to show scale, not to mimic accounting in real time.
Scenario lab
Scenario work is comparative and directional. It helps readers think through relative burden, not forecast classified outcomes or hidden costs.
Conflict tracker
War-cost pages should be read as public estimates tied to the evidence available at the time, with obvious limits around off-budget activity and reporting lag.
Reading guidance
Treat the value as a live estimate, not a ledger.
Expect revisions when the underlying source set changes.
Use the timestamp to understand when the page last reflected a source refresh.
Compare the number against the methodology before quoting it as a settled figure.
Operational notes
Tracker pages may update when a source revision lands, when a baseline is refreshed, or when an estimate is corrected. That behavior is deliberate and should be visible in the page history when possible.
For the source trail behind any page, start with Sources. For the calculation layer, see Methodology.
Limits to keep in mind
Timing
Public data rarely lands on the same schedule as the event it describes, so a live page can lag reality even when the math is clean.
Scope
Some defense spending is visible, some is partially visible, and some is not. The tracker should not pretend otherwise.
Interpretation
The right question is usually whether the number is directionally useful and properly sourced, not whether it looks neat on a chart.