Worked readings
A reading is one question, why lining the reports up by hand did not happen, and what Battlefield Analyst found on a real imported battlefield. The question atlas is the map. Recipes are how you ask. These pages are the result.
The screenshots are from battlefields that were actually imported. Names in them are the players on those reports. The point of the page is the question, not the roster.
| Reading | The question |
|---|---|
| Which hits on that keep actually mattered | A rally can look ugly on its own exchange and still be the hit that let later rallies trade better |
| When did our rallies turn into dust | Smaller march, worse tier mix, and a heal rebound are different facts |
| Who actually traded well on our rallies | Being on every full march is not Effectiveness, and Exchange Ratio is not the scoreboard |
| Who was in the city when it held | Who was on the tile, what was missing, and what moved between hits |
| What should we train after those defenses | Upside versus what that layer gives up if wiped — on these holds |
| How did we trade against one kind of incoming attack | One incoming type is a column, not an average of the night |
Why these questions used to be out of reach: why this used to be impossible.
Ask the same question on your next battlefield.
Pick the argument your team is already having. The trial is how you run it on your own reports.
New customers can start with a 7-day trial. Plans start at $14.99/month with full feature access.