What counts as a reportable change in topographic database revision?
Every revision program runs into the same argument sooner or later: a field tech flags a change, and someone back at the office asks whether it clears the bar for an edit. "Reportable change" sounds like it should have a tidy definition somewhere in the specification. In practice most agencies work from a mix of written rules and accumulated judgment, and the line moves depending on feature class, scale, and what the database is used for downstream.
Still, a few criteria show up across most programs, and they're worth separating out if your revision cycle is still built on area-by-area resurvey rather than a targeted worklist.
The three questions that decide reportability
Does it clear the minimum mapping unit for that feature class? A shed under the MMU for buildings at your working scale isn't a database change even if it's brand new and clearly visible on imagery. A new arterial road almost always clears it. This is the easiest filter to apply and the one most techs already know cold.
Is it persistent, or is it seasonal and temporary? A gravel stockpile, a flooded field, a construction laydown yard. These show up on current imagery and then vanish in six months. Most specs explicitly exclude anything expected to be transient, which is why a single capture date is a weak basis for a revision decision. Confirm the change across more than one pass before it goes on the worklist.
Does it change how the feature should be symbolized or classified? Widening a two-lane road to four lanes can change the feature's class, and therefore how it renders, even when the centerline itself barely moves. A change in classification without a change in geometry still counts.
Where agencies differ is in the judgment calls: how much a river has to meander before the hydro layer gets touched, how many new rooftops in a subdivision trigger a full area push versus individual point edits, whether a parking lot resurfacing counts as attribute maintenance. Nobody is handing out a universal number for these, and any blog post that claims to is guessing. Your own spec, or your agency's revision manual, is the authority here. What this post can do is flag where the ambiguity tends to live so you know which cases need a second look before a tile gets dropped from the list.
New construction vs. demolition on the basemap
The two directions of change don't get treated the same way, and that trips people up.
New construction usually needs to reach a defined completion state before it's reportable. A foundation poured and framed doesn't count yet in most specs, because the footprint can still change and the structure might stall for a year. Roofed and substantially complete is the more common bar. A construction site can sit "in progress" on imagery across several revision cycles before it ever earns an edit, which is one reason new subdivisions lag behind on topo bases more than people expect.
Demolition works almost the opposite way. A structure that's been torn down to slab or bare lot is reportable the moment it's confirmed gone, because there's no ambiguity about whether it's "finished" being demolished. The database is now actively wrong rather than just incomplete, and most specs treat a wrong feature as a higher priority to fix than a missing one.
That asymmetry matters for how you prioritize a worklist. A demolished structure still standing on the map is a worse error than a new building not yet added, because the map is actively lying about something that's gone, not just silent about something new.
Where this gets practical
Finding the changes in the first place is the expensive part. Reportability criteria only matter once you know where to look, and most revision cycles still spend the bulk of their field hours re-walking tiles that haven't moved. National Change Alerts is built around the other half of the problem: a continuously updated worklist of tiles where the basemap and the ground have actually diverged, so your revision criteria get applied to a shortlist instead of the whole map.
If your crews are still working a fixed resurvey cycle, it's worth seeing what a change-driven worklist looks like for your next revision pass.