What War Worksheet Actually Is
War Worksheet is a spreadsheet-based framework for running wargames and combat simulations without specialized software. You build it in Google Sheets or Excel, and it handles unit tracking, dice rolls, movement calculations, and combat resolution all in one place. Some people buy pre-made versions online. Most people who run these games seriously just build their own because the templates out there are usually garbage. Start with a blank sheet. Name your first tab "Units" and set up columns for Unit ID, Name, Type, Strength, Movement, Defense, and a few other stats relevant to your game system. The second tab is where the actual work happens. Call it "Turn Tracker" or whatever makes sense. This is where you log each round, record actions, and resolve combat. I spent probably two weekends building my first proper version. The template I downloaded from some hobby forum was designed for a system I'd never heard of, and half the formulas were broken. I ended up rewriting everything from scratch. My current setup runs five separate armies, handles about forty units per scenario, and the whole thing calculates results in under two seconds when you hit recalculate.
Here is the practical structure most people should follow. First tab: unit roster with all the stats locked in. Second tab: the battlefield grid, either a coordinate system or a hex grid represented as cells. Third tab: turn log where you record what happened. Fourth tab: results summary. Keep it simple. Every extra tab is overhead you will not use.
How It Actually Works In Practice
The core mechanic is straightforward. You enter unit positions, select which units take actions, and the worksheet applies modifiers based on terrain, range, and unit type to produce an outcome. Dice rolls happen through formulas like =RANDBETWEEN(1,6) multiplied by relevant modifiers. Combat results come from comparing modified attack values against defense values. The tricky part is making the formulas flexible enough to handle different scenarios without becoming impossible to maintain. I learned this the hard way when a scenario had overlapping zones of control that my original worksheet could not track. Units were being marked as free to move when they clearly should have been pinned. The fix was adding a separate "Zone of Control" lookup table that cross-referenced every unit position against every enemy unit's range. It added about twenty lines of array formula but eliminated the problem entirely. For terrain, I use a separate sheet that maps elevation, cover types, and movement penalties on a grid. You reference it with INDEX and MATCH formulas rather than hardcoding values. This means you can swap terrain layouts between scenarios without touching the main worksheet. It took me longer to build initially, but now I can switch between forest, urban, and open field scenarios in about three minutes.
Get the Full Details
Common Mistakes People Make
The biggest issue I see is overcomplicating the combat resolution. People try to model every possible variable in a single formula. The result is a spreadsheet so fragile that one typo breaks the entire turn. Break combat into steps. Calculate base attack value. Apply terrain modifier. Apply range modifier. Apply unit-specific bonus. Compare to defense. Roll for result. Each step on its own row. If something breaks, you can find which step failed within ten seconds instead of spending an hour hunting through nested formulas. Another problem is not planning for scenarios that fall outside the expected range. I once ran a scenario where one army had twice the units the worksheet was designed for. The grid cell references started overflowing because I had hardcoded column ranges. The workaround was switching to dynamic named ranges that adjust based on how many units you actually enter. It adds one line of setup but saves you from rebuilding everything when a scenario scales up.
Where War Worksheet Falls Short
There are legitimate limitations you should know about before committing to this approach. Spreadsheet-based combat resolution is fine for small to medium engagements, maybe thirty to fifty units per side. Beyond that, calculation speed drops noticeably, and the interface becomes unwieldy. If you are running large-scale battles, dedicated simulation software like Steel Beasts or even open-source tools like Springlobby will serve you better. Another issue is collaborative play. Google Sheets supports real-time editing, but multiple people entering data simultaneously will cause conflicts and overwrites. I have had two players edit the same turn at the same time and lose an entire round of data because of it. The workaround is assigning one person as the referee and giving others view-only access, but that defeats the purpose of collaborative play somewhat. Also, spreadsheets do not handle visual mapping well. If your game requires a graphical board with tokens and counters, you will end up maintaining two separate systems. I tried using conditional formatting to create a visual board, but it got messy fast. For visual-heavy games, look into TableTop Simulator or similar platforms and use the spreadsheet only for the numerical tracking portion.
War Worksheet Download and Templates
I do not maintain a public download link anymore. My personal worksheet has been modified so extensively over the years that sharing a blank version would not be useful. What I can tell you is that building one from scratch takes roughly four to six hours for a functional version, depending on how complex your game system is. The investment pays off if you plan to run more than a dozen scenarios. Search for existing templates if you want to save time, but expect to spend at least an hour customizing anything you download. Pre-made templates are usually built for specific games and will not generalize well. The formulas might work, but the structure will not match your needs. Building your own gives you control over every variable and makes debugging significantly easier later. The real value of a War Worksheet is not the spreadsheet itself. It is the discipline of thinking through every mechanic your game requires before you start playing. The process of building it forces you to confront edge cases and inconsistencies you would otherwise discover during an actual game. That lesson alone justifies the time spent.
