Start with the turn after your best unit dies
Most army lists look excellent while every unit is alive. The centre brick holds the middle, the fast unit reaches the far objective, the shooting piece opens a lane and the cheap squad waits politely for a late-game job. Unfortunately, tournament opponents are rarely considerate enough to leave the plan intact.
The useful question is not whether your key unit can survive. It is what your army does if it does not. Pick the most important piece in the list, remove it from the table in your head, then play the next scoring turn. If the answer is that three other units suddenly have no sensible job, you have found a structural weakness before the event finds it for you.
That matters particularly in the current tournament format. Your chosen Force Disposition is fixed when the list is submitted, giving you a predictable set of five primary missions to prepare for, while the opponent and terrain layout still change the route through each game. [1] Redundancy is not about preparing for every possible battlefield. It is about making sure one casualty does not remove your only route through the battles you already know are coming.
Duplicate jobs, not necessarily datasheets
Two copies of the same excellent unit can be sensible, but duplication and redundancy are not quite the same thing. Redundancy means two pieces can complete the same essential job under different conditions. One may be fast and fragile; the other slower but difficult to shift. One may arrive from reserve; the other begins hidden on the board. They do not need matching profiles. They need overlapping responsibilities.
Write four jobs beside the list: hold, reach, remove and screen. Hold means controlling the scoring area that keeps your primary alive. Reach means getting a unit into the place demanded by the next mission check. Remove means clearing the enemy piece that prevents either of those jobs. Screen means protecting the space and timing on which the plan depends.
Now put at least two unit names beside every job you cannot afford to fail. If only one unit can reach the far side, your opponent has been handed a very tidy target-priority decision. If only one gun can threaten a tough vehicle, that gun is carrying more than its own points. If only one cheap unit can protect your backfield, its loss may drag an expensive unit away from the fight. A list can contain plenty of models and still have a single point of failure.
Match the backup to the mission, not the damage sheet
The five Force Dispositions reward different broad behaviours, and the mission is created by comparing yours with the opponent's. [2] That means the backup unit should be judged by what it preserves on the mission, not by whether it produces the same damage as the first choice.
If your primary plan needs a unit to occupy a terrain area, the substitute must be able to reach it, fit into it and survive the likely response. Current missions use terrain areas as objectives, with the number of objective areas varying between missions. [3] A second damage dealer on the opposite flank is not a true backup if it cannot take over the position before the next scoring check.
This is where many efficient-looking lists become brittle. They contain several units that are good at fighting, but only one that can fight and stand where the points are. Before adding another weapon, ask whether the list already has a second way to complete its hardest positional task. Damage is useful. Arriving one turn late with immaculate damage is merely an expensive view of the scoreboard.
Run the one-unit-down test
Take your planned event list and run four short exercises. You do not need a full game for each one. Use the event layouts and play only deployment plus the first two battle rounds.
First, remove the toughest unit before turn two and identify who inherits the central job. Second, remove the fastest unit and find a legal route to the distant scoring area. Third, lose the main ranged threat and decide how the army contains the enemy piece it was meant to kill. Fourth, remove the cheapest screening unit and check whether the replacement exposes something more valuable.
For each exercise, record the cost of the substitution. Does the backup arrive a turn later? Does it need Command Points? Does it abandon another objective? Does the replacement work only if you go first? Those are not automatic failures. They are the real price of the plan, and knowing the price lets you decide whether the list can pay it.
Use the map-practice method to test the actual route rather than describing it vaguely, and then apply the two-scoring-check test to the unit taking over. If the backup saves this turn but collapses the next one, the list has delayed the problem rather than solved it.
Keep redundancy lean
There is a trap at the other end of this idea: filling the list with cautious duplicates until it has no sharp edge. A tournament army still needs a plan that creates pressure. The aim is not to make every unit replace every other unit. It is to protect the two or three jobs that decide whether your Force Disposition can score.
Start with the job that appears in all five of your likely missions, then the job opponents can most easily interrupt. Give those a second route. Leave specialised pieces specialised where failure is inconvenient rather than fatal. A reserve unit may cover reach and late screening. A durable midfield unit may hold and remove. Good overlap earns its points twice without requiring two identical datasheets.
Check the current Munitorum Field Manual and faction documents before locking the list; the official downloads page showed the MFM updated on 14 October 2026 when checked for this article. [4] Points and detachment access decide what the overlap costs, but they do not answer the strategic question for you.
The final test is pleasantly brutal: cover the name of your best unit and explain how the army scores the next turn. If the plan still has a route, the list has resilience. If the answer begins with ‘hopefully they do not kill it’, you have not built a backup plan. You have written a hostage note.
