2026-11-02
No-strike list vs. battle damage assessment: what's the difference?

A no-strike list and a battle damage assessment show up in the same targeting cycle, sometimes in the same briefing, and that's probably why people conflate them. They're not close to the same thing. One is a restriction you check before weapons release. The other is a grade you produce after the strike to decide whether you need to go back.
What a no-strike list is
The no-strike list (NSL) is a standing restriction. It's a compiled set of objects, facilities, and geographic areas that are protected from attack under the law of armed conflict, ROE, or policy guidance, things like hospitals, religious sites, cultural property, embassies, and anything else the JAG and the collateral damage estimate (CDE) process has flagged. It's maintained by the joint targeting working group and it gets checked at the target validation step, before a target ever makes it onto a target deck.
The NSL defines what's permitted before a strike happens. A target can sit on the list for an entire campaign without a single sortie flown against it, because that's the point: nothing gets flown against it.
This is also where people mix up a no-strike list with a collateral damage avoidance list. They overlap in spirit, both exist to keep weapons away from things you don't want hit, but a CDE is a target-specific calculation run during mensuration and weaponeering, estimating expected collateral effects for a given aimpoint, weapon, and fuzing. The NSL is the standing roster of places that are off-limits regardless of what weapon you're considering. One is a list. The other is a math problem you solve for each target.
Where a target deck fits in
A target deck is the working list of validated, vetted targets nominated for a given ATO cycle or operation, the things you're planning to hit. The no-strike list sits upstream of it as a filter: nothing on the NSL should ever appear on a target deck, and any target nomination gets cross-checked against it during vetting. The real relationship is restriction against candidate list. The no-strike list narrows what can land on a target deck; the deck holds the things nominated to hit, already filtered against the NSL.
Where battle damage assessment comes in
Battle damage assessment (BDA) happens after the fact. It's the post-strike judgment of what a weapon actually did to a target that was already on the deck, already struck. Physical damage assessment looks at the structure itself, hole patterns, roof collapse, wall shear. Functional damage assessment asks whether the target can still do its job. Target system assessment rolls individual BDA calls up into a picture of the whole network. None of this touches the no-strike list, because by definition a BDA is written against a target you were cleared to hit in the first place.
The practical difference comes down to timing and purpose. The NSL is checked before weapons release to keep a strike from happening. BDA is produced after weapons release to decide whether a second strike needs to happen. If you're asking "can we hit this," you're in no-strike list and CDE territory. If you're asking "did that hit do enough, and do we need to go back," you're asking for a BDA.
Where the confusion usually causes real friction is in the re-strike decision. A commander looking at a structure that took a hit three hours ago doesn't need the NSL pulled back up, that question was already answered before the ATO was built. What's needed is a per-structure read on what the strike did to the structure, dated and itemized against the before imagery, so the call to re-task or stand down doesn't rest on a grainy frame grab or a gut call from the strike video.
That's the gap Battle Damage Assessment is built to close: a before/after VHR read of the structure, graded and dated, run the moment a strike happens rather than waiting for the next scheduled pass. If your re-strike call is still waiting on imagery, see how the assessment gets built before the next tasking goes out.