How to Squad Lead: A Practical Guide

Every Squad match is decided by six to ten volunteers who clicked “Create Squad” and took the hardest job in the game. This guide is for the moment you’re considering becoming one of them — and for making your first attempts feel survivable rather than heroic.

The honest pitch: squad leading is more work and more fun. You see the whole match instead of your corner of it. And it’s a skill, which means it’s learnable, which means your first few rounds will be rough and that’s the tuition.

What the job actually is

Strip away the mystique and an SL does four things:

1. Decide where the squad goes and what it does there (attack, defend, build, logistics).
2. Communicate that decision — to your squad on squad radio, and to the other SLs on command radio.
3. Place spawns — rally points continuously, HABs when the situation calls for one.
4. Adapt when the plan meets reality.

Notice what’s not on the list: being the best shot, knowing every map corner, or sounding like a drill instructor. The best SLs are mostly calm people who keep making decisions.

Before your first time

• Play a few dozen matches as a rifleman or medic first, watching your SLs. Steal what works.
• Read your server’s SL rules. On Command Squad: working mic, English, SL kit equipped, active leadership (Rule 5). Creating a squad without intent to lead (“squad baiting”) is kickable.
• Learn the map screen cold: marking enemies, drawing moves, placing rally/HAB markers. Jensen’s Range is a judgment-free place to practice the interface.
• Optional but smart: tell the squad “first time SLing, bear with me.” Squads rally around honest SLs. On our servers, that sentence gets you patience and volunteers.

The rally point habit

If you learn one mechanical habit, learn this: keep a fresh rally down. A rally point is your squad’s private respawn. Without one, every death sends your people to a distant HAB or main base, and your squad evaporates as a fighting unit.

Working rules of thumb:

• Place it behind cover, 75–150m from where you expect to fight — close enough to rejoin fast, far enough not to be overrun.
• Refresh it when you move. Stale rallies behind enemy lines feed the enemy kills.
• If the squad wipes, a good rally is the difference between “regroup and re-attack in 60 seconds” and “walk five minutes in a line.”

HABs, FOBs, and logistics

Your squad can build a FOB (radio + HAB spawn bunker + emplacements) when you have supplies nearby, usually driven in by a logistics truck. Three SL-level truths:

• A well-placed HAB wins a sector; a lazy HAB feeds the enemy. Offset it from the objective (300–500m is a common pattern), hide the radio, and think about which direction attackers will come from.
• Logistics is a squad task, not a punishment. Announcing “we’re running one logi, then attacking” keeps supplies flowing and nobody resents it.
• Proxied or camped HABs need a decision — retake it or dig it down and rebuild elsewhere. Announce which; indecision costs tickets.

Giving orders people follow

You’re leading volunteers in a video game. Orders stick when they’re short, concrete, and explained just enough:

“We’re taking the compound east of the point. Fireteam Alpha left side, everyone else with me. Go on my mark.”

Three upgrades that separate good SLs:

• Name people. “Miller, watch north” beats “someone watch north” every time.
• Give the why in one clause. “Hold this side — they’ll counterattack from the river.” People who know why improvise correctly when you’re dead.
• Close the loop. After an order, listen for acknowledgment; after a fight, one sentence of where you stand (“we held, rally’s fresh, ammo check”) keeps the squad synchronized.

And use your fireteams: promoting two fireteam leads and giving them halves of a problem scales you from micromanaging nine people to coordinating two teams.

The command net

Command radio is where SLs trade information and stitch squads into a team. Two disciplines:

• Report what you know, briefly. “Two squads plus a BTR pushing the north point” is gold to every other SL.
• Coordinate, don’t broadcast. Ask the specific SL: “Bravo, can you cover our west while we push?” If a commander is present, they’ll set priorities — work with them.

Don’t neglect your own squad while you’re on command net; the classic failure mode is an SL having a great conversation with other SLs while their squad wanders leaderless. Alternate.

When everything goes wrong

It will. The measure of an SL isn’t avoiding chaos — it’s the next 30 seconds after it:

1. Say something. “Rally’s down, fall back to the treeline, medics work as we move.” Any plan beats silence.
2. Reset spawns first. A fresh rally converts a wipe into a delay.
3. Skip the blame. “That was rough — here’s what we’re doing differently” and move forward.

Growing into it

• Lead during seeding hours — low stakes, small squads, perfect practice.
• Watch your own decisions in the after-match: which orders got followed? Which got silence?
• Squad-lead alongside our regulars and ask for feedback in the Discord — mentoring SLs is something this community actively does, and a formal Squad Leader Development Program is on the roadmap.

Command Squad note: helicopters must be flown by their squad’s SL and heli squads cap at 4 players (Rule 8); MBT squads need the SL in the tank (Rule 7). If you lead armor or air, those rules shape your squad composition.