2026-11-09
Target folder vs. battle damage assessment report: what's the difference?

If you've sat in on a targeting board, you've heard both terms thrown around like they're interchangeable. They're not, and mixing them up in a brief is the kind of thing a J2 will quietly correct you on in front of the room.
A target folder is what you build before a strike. A battle damage assessment report is what you build after. One sets up the shot. The other tells you whether it landed and whether you need another one.
What's actually in a target folder
A target folder, sometimes bundled into a broader target intelligence package, is the dossier that justifies putting weapons on a specific aim point. For a planning officer, it typically carries:
- Target identification: coordinates, elevation, a BE number if one's assigned, and the collateral damage estimate that cleared it for the target list in the first place.
- Imagery annotations: current overhead shots marked up with the structure, access points, and anything nearby that changes the weaponeering math.
- Target system context: what function this node serves. A transformer yard matters differently depending on whether it feeds one facility or a regional grid.
- Desired effects: what "success" means for this aim point. Functional kill, structural collapse, denial of use for X days. This line is the one the BDA report gets measured against later.
- Weaponeering and collateral estimates: fuzing, approach, expected fragmentation pattern, and the CDE that cleared the strike package.
None of that folder tells you what happened. It tells you what's supposed to happen and why hitting this particular building, bridge, or hardstand is worth the ordnance.
What a BDA report covers instead
A battle damage assessment report starts where the target folder ends: after weapons impact. It's graded off fresh imagery against whatever baseline the target folder used, and it runs through the standard phases:
- Physical damage assessment: what's visibly destroyed, cratered, or structurally compromised, usually graded on a destruction scale rather than a yes/no call.
- Functional damage assessment: whether the target can still do its job, which doesn't always track one-to-one with physical damage. A roof can be gone and the equipment underneath still operational.
- Target system assessment: how this one node's loss ripples through the wider system it belonged to, which is where the target folder's "why this node" section gets its payoff.
The report is dated, itemized per structure, and exists for exactly one decision: re-strike or no re-strike. It doesn't justify the original target selection. It grades the outcome.
Why planning officers need to keep them separate
The confusion usually shows up at the re-strike decision itself. Someone pulls the original target folder, sees the desired effect listed as "functional kill," and assumes the strike achieved it because the structure looks destroyed in the post-strike shot. Physical damage and functional damage aren't the same grade, and a folder written before the strike has no way to tell you which one you got.
Keeping the two documents distinct also matters for the paper trail. The target folder shows the clearance process, the CDE, and the intended effect. The BDA report shows the measured outcome against that intent, structure by structure, dated to the imagery pass. A re-strike board answering "did we get it" needs both documents side by side: the folder for what was intended, the report for what the imagery actually shows.
For the actual grading step, that means working from a before/after image pair, not a single post-strike frame and a memory of what the target folder said. Battle Damage Assessment handles that comparison directly: it pulls VHR optical imagery from before and after the strike, grades each structure on a damage scale, and tasks the pass the moment a strike happens rather than waiting on the next scheduled collect.
If your re-strike board is still working off a single annotated photo and a judgment call, it's worth seeing what a dated, itemized assessment looks like instead.