In Company of Heroes 3: Final Stand, Steam says you construct a custom battlegroup during a run and choose randomized units or abilities after waves. Those choices persist for that run. A battlegroup choice should therefore be read as an answer to the next pressure you can see, not as a permanent unlock and not as a copied build from the separate Company of Heroes 3 product.
Read the offer after you name the problem
Before the between-wave screen opens, describe what the last wave exposed. Did an approach have no coverage? Did the defense rotate too late? Did the protected objective become the only place left to respond? This gives the option screen a purpose. A name alone does not tell you whether an offer helps your current line, especially when the official description says choices are randomized.
Record the exact option wording, the faction, the wave after which it appeared, and the result you expect. If the next wave brings a comparable problem, watch whether the selection changes it. If the situation is completely different, keep the note provisional rather than declaring the option good or bad.
Build around an observable role
A selection can have a role even before you know a full meta. It might help you protect a route, keep a fallback open, or make a future response easier to time. Phrase that role as a test, not as a hidden statistic: “I selected this because the next wave needed coverage on this approach.” Then record what occurred.
Avoid stacking several unknown offers merely because they sound related. When all three change at once, a later success cannot tell you which choice mattered. Take one understandable option, let it encounter the issue it was meant to solve, and then choose the next layer of the run around what you learned.
Coverage role
Use it when a route forces a late rotation. Observe whether the team can keep the objective protected while the route is handled.
Recovery role
Use it when the outer line failed. Observe whether it creates another decision point rather than another single point of failure.
Information role
Use it when the loss was unclear. A visible, testable effect is more valuable than a complicated interaction you cannot diagnose yet.
Keep battlegroup choices out of the permanent record
Final Stand also has persistent upgrades and faction-specific progression trees between runs. Those are not the same as a battlegroup selection. Keep a run list and a persistent list. The run list ends with the attempt. The persistent list includes only items still shown after the match, with their exact requirement and current wording.
This distinction matters for both writing and play. A friend may describe a result that came from a temporary option, while you are looking for it in the long-term progression screen. A guide that blurs the two sends players to the wrong menu and makes a current run feel inconsistent for no reason.
Do not import an older battlegroup guide
Older Company of Heroes 3 battlegroup articles can name the same factions, but they may target a different AppID, mode, version, or DLC. Treat them as non-matching until they explicitly identify Final Stand. Steam’s standalone product description is the relevant boundary here: Final Stand has its own wave-defense runs and post-wave randomized choices.
If a specific ability or tree name appears in a search result, confirm it in the current Final Stand client or a current official AppID 4836540 source before adding it to a page. Do not use a historical tier list to fill an unknown table cell.
Finish a run with a usable battlegroup note
List your post-wave choices in order, the issue each one addressed, and the first moment where a choice changed the defense. Add difficulty, faction, map name if displayed, and an event or boss label only when the client supplies one. Steam confirms events and boss units, but not their full public catalogues.
The next run should test one conclusion: repeat an option in a comparable need, or select a different answer to the same route. This is enough to create a useful early battlegroup guide without inventing a permanent build order. Dedicated pages for persistent upgrades and faction progression trees are added after their source review is complete.
Sources
- Company of Heroes 3: Final Stand on Steam — official custom battlegroup and after-wave randomized-choice wording; checked 2026-08-13.
- GameReactor review by Patrik Severin — independent released-game wave-defense context; published 2026-07-30, checked 2026-08-13.