Facility Expansion

2026-11-16

What is a baseline declaration in arms control treaty verification?

A grassy embankment crest with a wooden post-and-rail fence and gate, beside a paved road, under a stormy sky.

A baseline declaration is the inventory a state party submits when a verification regime starts, or when a new facility first comes under a treaty's scope. It lists what exists at a given site on a given date: structures, equipment counts, item types, sometimes coordinates and floor plans. Everything that happens afterward under that treaty gets checked against this one document.

Call it the zero point. Inspectors don't walk into a site cold. They walk in with the declared facility list in hand and compare what they find to what was declared. If a structure wasn't there at baseline and it's there now, that's a discrepancy somebody has to explain, either through a routine update or through a question nobody wants to field at the next review conference.

What actually goes into one

The contents vary by treaty, but the shape is consistent. CFE Treaty baseline data covered holdings of treaty-limited equipment by unit and location. New START's declarations run through facility lists and telemetry on deployed systems. IAEA comprehensive safeguards agreements use an initial declaration that inventories nuclear material and the facilities that hold, process, or store it, with design information for each site that gets updated as a facility changes.

What's common across all of them: a site identifier, a date, and a description detailed enough that a later inspector can tell whether the ground still matches the paper. Annual updates or notifications layer on top of the baseline, but the baseline itself is the fixed reference everything else gets read against. Lose track of it, or let it go stale, and every later comparison loses its footing.

Why the list outlives the paperwork

A declared facility list is a working reference analysts pull every time there's reason to look at a site again: a scheduled inspection cycle, an on-site complaint, or a periodic check nobody flagged as urgent. Declarations get submitted once, or updated on whatever cadence the treaty sets. A site itself doesn't wait for the next reporting cycle to change.

A declared footprint can grow between declarations: a building gets added, a yard gets excavated for a new foundation, a perimeter gets a second fence line. The paperwork catches none of it until the next update is due, by which point the construction is already finished. The gap between what the baseline says and what the ground shows is exactly where a compliance question starts.

Keeping a baseline honest between updates

Treaty secretariats and national technical means both lean on imagery to fill that gap, historically by pulling archive scenes for a site and comparing them by eye, one pass against the last one, looking for anything that wasn't there before. It works, but it's slow, and a single analyst doing it for more than a handful of sites on a recurring basis runs out of hours before they run out of sites.

A tighter way to hold a baseline is to watch the declared footprint on a fixed schedule rather than revisit it only when a report is due. Facility Expansion does that for one named site at a time: a weekly optical pass flagged for new construction, excavation, or hardening against the footprint that was there before, with a volumetric read on dug ground and a footprint read on anything newly built, laid out on a site map with the changes marked. That's the same comparison an analyst runs by hand against the baseline, just run every week instead of once a cycle.

None of this replaces the declaration itself or the inspection process built around it. What it does is shorten the distance between "the baseline says X" and "the site still looks like X," so that when the next formal review comes around, the gap it has to explain is measured in weeks, not however long it's been since anyone last pulled the archive.

If you're sitting on a declared site that hasn't had an eyes-on check since its last update, it might be worth putting it on a weekly watch instead of waiting for the next cycle to find out what changed.

Get started

← Back to the blog