Facility Expansion

2026-10-13

How to annotate a site map for a treaty verification report

Cooling towers of different heights at a nuclear power plant, the kind of declared site tracked in a verification report.

A verification report gets picked apart by people who know the site as well as you do. The annotation layer on your site map is where most of that scrutiny lands, so it has to carry more than a circled area and a caption. It has to show what changed, where, and when you first saw it. Leave any of those vague and a reviewer sends the report back asking you to reconcile a date against the archive, which is the exact work you were trying to skip.

What each annotation needs to carry

Tie every marked feature to the acquisition date of the image it first appeared in. The date you drew the polygon doesn't count. If a new pad shows up in this week's pass but the archive shows it already poured in last month's image, your annotation date is wrong and so is your report. Pull the prior clean pass before you mark anything.

A few things belong on every annotation, whether it's a new structure, an excavation, or a hardening feature:

  • The acquisition date of the image it was first visible in
  • A footprint or extent, drawn to the pixel resolution you're working at, not eyeballed
  • A classification: new construction, excavation, hardening, or no change
  • A reference back to the prior baseline annotation, if one exists, so a reader can trace the feature's history across passes

That last point is the one people skip and regret. A single annotation on a single map tells you a structure exists. A chain of annotations across passes tells you when it started, how it grew, and whether the pace changed. That chain is what a non-proliferation reviewer wants to see, because it's the difference between "this is here" and "this started appearing six weeks ago and hasn't slowed down."

For excavation specifically, note the volume if you can get it, not just the footprint. A hole that's two meters deep and a hole that's twelve meters deep look similar from directly overhead at some resolutions. The footprint alone understates what's happening on the ground.

A weekly change log format that holds up

If you're monitoring one named site on a recurring basis, keep the annotations in a running log rather than a fresh map each week. The format that survives review usually looks like this:

  1. Pass date and imagery source
  2. Site sector or grid reference
  3. Change type and a one-line description
  4. Comparison baseline (the prior pass it was checked against)
  5. Status: confirmed new, confirmed change in progress, or reverted/no longer visible

That last status matters more than people expect. Construction sites don't move in one direction. Equipment gets cleared, excavation gets backfilled, a structure that looked like it was going up turns out to be formwork that came back down. A log that only records additions and never records reversals will eventually contradict itself, and a careful reader will notice before you do.

Keep the log format identical week to week. If sector labels, classification terms, or the comparison baseline convention shift partway through a monitoring period, every entry after the shift becomes harder to cross-reference against everything before it. Pick the format once and don't improvise it mid-stream.

Where the manual version breaks down

All of this is doable with a GIS layer and a spreadsheet, and plenty of analysts run it that way. It breaks down on cadence. Pulling a fresh archive comparison every week, by hand, for one site, is the kind of task that gets deprioritized the week something more urgent lands on your desk, and a skipped week is exactly when the thing you needed to catch happens. A weekly watch on a named site that flags construction, excavation and hardening as they appear, with a footprint read on new structures and a volumetric read on excavation, turns that archive-comparison task into a standing map you annotate against instead of one you build from scratch each time.

If you're monitoring a site where a missed week in your log is the problem, it's worth seeing what that weekly watch looks like for your site.

Get started

← Back to the blog