How to write a battle report people actually read

A good written battle report is short, honest and easy to scan. Readers want to know who played, what they brought, what happened and what they can learn. This is the structure we use for every report on this site.

1. A hook, not a spoiler

Open with the setting and what was at stake: "A US Army platoon has to clear a French village before dark." Hold the result until the end.

2. The facts box

Players, scenario, points, table size and theatre. Put it near the top so people can see at a glance whether the game matches what they play.

3. Both army lists

Lists are what experienced players come for. Show them in full, in the same format for both sides. See how to share an army list.

4. Deployment

One overhead photo and a paragraph on where each player set up and why. This is where readers learn the most about planning.

5. Turn by turn

One short paragraph per turn. Focus on the dice draws that mattered, the key shots and assaults, and where the pins piled up. If there is a video, add the timestamp for each turn.

6. Result and takeaways

Give the result as it happened, then one lesson for each player. Keep it fair. The best reports are generous to the opponent.

Photo tips

• Shoot from table height for drama, overhead for clarity. You need both.
• Clear dice, rulers and drinks out of the frame for the turn photos.
• Use the same angle at the end of each turn so readers can compare.

Linking the units

On Dice Bag Dispatch, each report ends with the units used and links to the matching kits, so readers can build the same force. We only link kits that were actually on the table.

Have a written report with photos and a video? Submit it here.