How do I combine multiple enemies into one squad in a tabletop RPG?

What you are actually building

Five separate orcs give you five turns, positions, health pools and chances to act. You can speed up their handling without combining them: let them share initiative and batch routine rolls while keeping their positions, health and targets distinct, as described in the related answer on making combat faster without making it less exciting. If you want them to act as one squad instead, choose what kind of consolidation you mean; the three common approaches behave differently at the table.

Naming the abstraction up front prevents confusion later, especially if your group already uses terms like troop, mob or squad differently. Use the table below to match your table's need to the right tool, then build only that tool. Do not treat them as interchangeable dialects of the same idea.

Three encounter-scale options and how they differ

How this differs from an army battle

This page covers the middle row: a handful of ordinary opponents that you treat as a single encounter unit so a normal combat moves faster whilst still feeling like a group. If the player characters are soldiers inside a larger field battle, with fronts, reserves and orders that outlive one encounter, use the army-scale method instead. That method keeps the wider war as a changing environment around player-scale scenes, not as a bigger squad stat block. For the distinction and army procedure, see the related answer on running a large battle with the player characters inside an army.

Pathfinder Second Edition's NPC Core has published troop rules; see the system note below. To compare games with published squad or mass-battle subsystems, see the related answer on tabletop RPGs with squad and mass-battle rules. The recipe here is a separate, system-neutral method, not an official rule set.

A system-neutral squad recipe

Use these six decisions in order. Each one answers a question your players will ask within a round or two, so settling them before initiative avoids mid-fight rulings.

• Size, footprint and whether they share a space Pick how many creatures the squad stands for, usually three to six for this technique, and what space the unit occupies. State whether the members genuinely share one battlefield position or stand shoulder to shoulder across a defined area. A single base works for a shield wall or a tight knot of goblins in a corridor; a small zone works for a loose skirmish line that can still be flanked. Note how the squad can be blocked, squeezed through a doorway, or split by terrain, so movement has a cost.
• Shared health, casualty thresholds or a strength track Give the squad one way of showing losses that the players can see. Options include a single hit point total, a set of thresholds where one member falls, or a strength track that degrades as damage accumulates. Record how many members that represents and what visibly changes when the count drops. The squad should become less capable as it takes casualties, not fight at full effect until it collapses.
• One coherent activation, not five stacked attacks Resolve the squad once with a combined attack or a pool of attacks that shrinks as it loses members. Consolidation changes burst damage, target choice and opponents' chances to intervene; expected damage can stay similar, but is not the only measure of threat. Choose output that suits your system and encounter, rather than treating GM handling time as a balancing resource or assuming damage must always fall.
• Movement, surrounding and area effects Decide how the unit moves, how much space it controls, and whether an area effect hits all or only some of it. Say how area and single-target effects change the casualty track; for example, area damage might affect several members while a single-target attack can name one member only when the attacker can reach or see them. Write the ruling down before it matters.
• Morale, suppression, breaking and surrender Groups of ordinary fighters rarely fight to the last member. Set a point where the squad checks, wavers or breaks: after serious losses, after its leader falls, after it is flanked or surprised, or after a round of heavy fire. Decide what failure looks like at your table. Options include falling back to cover, scattering into individuals, surrendering, or routing off the battlefield. Make the trigger visible to the players, such as a standard bearer falling or half the squad going down, so the shift feels earned rather than arbitrary.
• When players engage the whole unit versus a part of it State how a player can target the squad as a whole, pick out a specialist or officer inside it, or isolate one member. A melee fighter pressed against a shield wall plausibly engages the formation; an archer on a balcony may plausibly pick a single figure; a duellist who pushes through the line may force a one-to-one exchange whilst the rest of the squad turns. Clarify whether those choices require a check, extra movement, or simply being in the right fictional position. The same clarity helps when the party commands or fights alongside a friendly squad, as covered below.

Tuning the recipe for different groups

A tight melee formation that holds a doorway behaves differently from a scattered band of archers, even if both use the same track. For close-quarters squads, emphasise shared position, limited facing, and the ability to block or be flanked. For ranged squads, emphasise dispersed placement, cover, and how suppression or a charge can break their line. A mixed-quality group with a leader, a standard bearer and ordinary fighters needs a way to recognise the leader: perhaps losing the leader triggers morale earlier, or the specialist grants one distinct ability that is lost when that member falls. Elite units should not simply be ordinary squads with higher numbers; give them better thresholds, slower degradation, steadier morale, or a cleaner split into individuals rather than a rout when they are reduced.

Whatever you choose, check the output against your system's action economy and encounter maths. A squad changes burst damage, targeting and chances for players to intervene; run a short mock combat with the party's actual abilities, including area damage and conditions, then adjust for the kind of threat you intend.

Squad prep checklist

Set these rulings before initiative:

• Confirm the enemies are similar enough to act as one unit, and note how many creatures it represents.
• Choose the squad's footprint and decide how it handles doors, cover and difficult terrain.
• Set a visible casualty or strength track, including the thresholds where members fall and capabilities change.
• Write one attack for each strength threshold and resolve the squad only once per activation.
• Decide how area effects and single-target attacks affect the track, including when a named member can be targeted.
• Choose a morale trigger and what the survivors do if they fail: retreat, scatter, surrender or rout.
• Check the rules against the party's actual attacks and control effects, then adjust the threat before play.

Player characters commanding, joining and fighting formations

A squad is not only something to place opposite the players. It is also something they may lead, stand beside, or be asked to break, and each role needs a slightly different ruling.

When a player commands a friendly squad, treat their contribution as positioning, orders and plausible leverage rather than an extra set of attacks the squad gains for free. A character who can see the field, shout a clear order, or hold a position that anchors the formation may let the squad act more reliably or hold morale longer. A character who is hidden, silenced, separated by distance, or busy fighting for their own life cannot credibly steer the whole unit at once. Let a command take an action or invoke a check where your system expects one, so the squad's turn remains the fiction of the squad acting, not a silent extension of a single hero's activation.

When the party fights alongside a squad, keep the squad's fictive role distinct: it holds ground, covers a flank, or fixes part of the enemy line whilst the player characters handle the decisive problem inside that context. Let players see the consequence of where the squad holds or breaks. If the allied line gives way, the party faces enemies from a new direction; if it holds, they keep a corridor to reach a leader or an objective. Avoid letting the squad quietly solve the encounter whilst the party watches, or vanish without consequence when it is convenient to do so.

When a player singles out a leader, specialist or exposed member, let the fiction decide the cost. Reaching a figure in the middle of a tight formation should plausibly require getting through the formation first, whether that means movement, a check, or assistance from another character. An exposed skirmisher on the edge may be targetable directly. If the singled-out figure matters to the squad's capability, state so before the attack, and remove that capability when they fall rather than letting the squad fight as if nothing happened.

Judge a hero's effect on the formation by the genre, the system's actual abilities and the established fiction. In grounded play, support, position or terrain may be needed to overcome a formed line; in heroic play, a character's abilities may themselves provide that leverage. Honour what a legal ability can do, and let a collapsed gate, a turned leader or timely aid matter when the fiction supports it. Do not add restrictions simply to preserve the squad's threat.

When to keep enemies individual

A squad is a shortcut. It repays its cost only when individual distinctness matters less than the group's collective pressure. Keep ordinary combat individual when:

• The group is small and each member has a distinct job Two guards and a mage, a captain with two specialists and a hound, or any trio where each figure's ability would be lost if folded into one attack, deserve separate turns. Their variety is the puzzle.
• Positioning and distinct abilities create the challenge A fight built around flanking, isolated roles, a hostage surrounded by different foes, or a ritual that one specific enemy maintains loses its point when everything shares one position. Let the map do its work.
• Complex terrain or interiors make a single footprint dishonest A tangle of rooms, pillars, chokepoints and cover is often the most interesting part of the encounter. Forcing a single token into a kitchen, a cloister or a crowded market squeezes the fiction to fit the shortcut rather than letting it breathe.
• You need every foe to have individual stakes When surrender, capture, interrogation or mistaken identity matters for specific members, tracking them individually preserves those branches. A shared pool blurs which figure actually fell or was taken.

Common pitfalls to avoid

Groups that feel wrong usually fail in one of these ways. Each has a simple correction you can apply before the next round.

• Turning a group into an inexplicable giant A squad should not mysteriously gain reach, movement or durability that none of its members had alone. Size, speed and resilience should stay close to what a tight group of ordinary creatures could achieve together, with any extra capability explained by formation or equipment rather than by scaling numbers into a brute.
• More bookkeeping than the individuals would have needed If the track, conditions and exceptions for the squad cost more time than five health bars, retire the shortcut. A good squad reduces what the GM tracks to position, current strength and morale state, with at most one extra condition from a leader or specialist.