2026-11-16
How to read a five-level damage grade scale for post-strike assessment

If you've sat through a BDA brief, you've seen the legend before you've seen the imagery: a row of five boxes, empty on one end, filled on the other. Before anyone talks about which buildings took the strike, someone has to agree on what each box means. That agreement is the whole point of a damage grade scale.
The five grades, structure by structure
Most working scales land on five bands, and they map roughly to what an analyst can distinguish from overhead imagery without walking the site:
- Grade 0, no visible damage. Roofline intact, no debris field, no scorching. The structure reads the same as the pre-strike frame.
- Grade 1, light damage. Surface marking, broken glazing, minor roof penetration. The structure is standing and most likely still functional.
- Grade 2, moderate damage. Partial roof collapse or a damaged section, visible structural deformation, debris on the ground. Functional capacity is in question.
- Grade 3, severe damage. Major structural failure. Walls down, roof largely collapsed, but enough of the footprint remains to confirm what was there.
- Grade 4, destroyed. Footprint gone or reduced to a debris field. Nothing standing that resembles the pre-strike structure.
Five grades sound coarse next to the resolution of the imagery underneath them, and they are coarse on purpose. A planning officer deciding on a re-strike doesn't need a damage percentage, they need to know whether a given structure is still a viable target or already a crater. The grade answers that question in one glance per structure, which is what makes the legend work as a scan-down-the-list tool rather than a report you have to read end to end.
Why the grade is assigned per structure, not per site
A site-level damage call hides the thing a re-strike decision actually depends on: which of the individual buildings, revetments, or hardstands inside that site are still standing. A compound can take a hit that reads as "moderate" in aggregate while one building in it is a 4 and the one next to it is a 0. If the tasking is deciding whether to put another round into that compound, the aggregate number is close to useless. The per-structure grade is what tells you the admin block is down but the fuel point, three buildings over, wasn't touched.
This is also why the scale has to sit on a before and after pair rather than the after image alone. Grading a single frame tells you what a structure looks like now. It doesn't tell you what changed, and change is the only thing a re-strike call cares about. A structure that looks damaged in the after frame but looked the same way in the before frame was never a hit. It was already in that state, maybe from an earlier strike or simply from age. The grade has to be a comparison, dated against both frames, or it's just a damage guess with no reference point.
Reading the legend in a brief
In practice the legend gets used two ways. The first is scanning a target list where every structure has been assigned a grade, looking for anything still sitting at 0, 1, or 2 that was on the original target set. Those are your re-strike candidates. The second is spot-checking a single structure someone's flagged as ambiguous, where the grade comes with the dated before/after pair attached so you can see the call being made rather than take it on faith.
The scale earns its keep when every grade on the list has been assigned off a matching before/after pair with a date on it. That's the itemised, per-structure assessment Battle Damage Assessment is built around: a tasking that runs when a strike happens, grading each structure on the five-level scale from VHR optical imagery, delivered dated and itemised rather than as a single site-wide call.
If you're assembling a re-strike list and need the grading done structure by structure rather than guessed at from one frame, that's the gap this fills.