How to IGL in CS2: The Amateur Captain's Guide
Nobody teaches you how to IGL. Pros learn it from coaches and years of tier-two grinding. You got the job because nobody else wanted to talk.
The main problem for new IGLs: "When I try to IGL it's like my brain just can't handle all the info. I find it impossible to still perform at the same individual level while I'm also trying to get 4 guys to coordinate together." (source) The same complaint shows up in threads from ten years ago, almost word for word. The mental load of calling is the oldest unsolved problem in amateur CS, and every guide that ranks for "how to IGL" answers it with a list of pro players to admire.
This guide is the other answer: how to structure a round so there is less to think about, what to say and when to shut up, and how to prepare so you are not inventing strats mid-round.
In my case it was a group decision. My CS:GO team around 2021, low 99damage division, thought I could do it best, so I got the job. I was very inexperienced and it was a lot to take in: the stress, the constant talking, managing five players instead of only myself. What kept me in the role was that the others liked that someone finally put a structure in place, for pracs and for calling.
What does an IGL actually decide?
Strip the role down and there are three moments in a round where the IGL earns his slot. Everything else is noise.
The freeze-time call. Buy or save, and the plan for the round. This happens in freeze time and it is the only call you make while nothing else is happening.
The default. Where your five players spread out while you gather information. If your team has a practiced default, this phase runs itself and your brain is free to read the enemy. If it doesn't, this phase is five people improvising, and you are one of them.
The mid-round call. The moment information turns into a decision: we hit A now. This is the call people mean when they say IGLing is hard, and it is the one the rest of this guide keeps coming back to. This is where most IGLing is happening and where a good IGL shines.
Notice what is not on the list: micromanaging positions, calling every utility throw, coaching your anchor mid-clutch. The bad IGL that comes up in every team is the caller who tries to decide everything. Your players should know their own utility and their own positions. The IGL takes the information they give him and decides where the team goes. That is the whole job description.
The rest of the round belongs to your players. If that feels like giving up control, it is the opposite. You are trading control you never really had for the three decisions that actually swing rounds.
Freeze-time calling: the economy comes first
The plan for a round must be based on what your team can afford. A perfect execute with two pistols and an MP7 in the lineup is not gonna work.
Amateur economy calling needs exactly two rules, and both are about the team, not the math.
Rule one: buy with your team. Nobody buys alone, nobody saves alone. The half-buy hero with an MP9 in a save round costs you the next round too, because now the team is split again.
Rule two: say the number out loud. "Save, keep 1900" beats "save" every time. Without the number, the player with 1700 sees a teammate with 3400 pick up a Deagle and forces up as well, against his own better judgement. The confusion is not stupidity, it is missing information. The number fixes it.
The one real judgement call: force when a save would not give you a full buy next round anyway. If you are double-saving either way, take the cheap guns and the free chance.
That is the whole system. If your buys follow those rules, you will best most teams in your division, because most teams don't think enough about their money.
On my team there were no written buy rules. I called the buy type at freeze time and the rest just followed. That was enough, because the point was never the math, it was that nobody bought alone.
How do you make mid-round calls without freezing?
Freezing is the moment amateur IGLs are most ashamed of, and the one with the least reason for it. You have taken map control, nothing is happening, four people are waiting, and your mind is blank. The team ends up holding angles with no plan until someone gets picked in a 1v1 and the round is gone. The round does not die to a bad call. It dies to no call.
Three things get you out of it.
Prepared branches beat live invention. You cannot design a strat under time pressure, and you do not have to. The call "A is dry, B has two" should map to something your team already practiced: a prepared A hit, a set of known utility, roles everyone knows. The decision left for you mid-round is which strat, not what the strat contains. This is the real reason to write strats down (more on that below): not to have forty of them, but so that the three you trust are available to your brain when it is busy.
An early wrong call beats a late right one. Call something. Even a mediocre plan that five people commit to trades better than five people improvising, because the improvisers arrive one at a time. Say it with confidence and trust your team to execute it. If it was the wrong call, you will find out in the review, not mid-round.
Repeat what works. If a play worked, run it again until it stops working, then fake it. Your opponents in a league match are not anti-stratting you between maps. Punish that.
My own team ran off a long Google Doc. Mid-round, my job was usually just deciding which site to hit with which execute. The doc had already decided the rest.
Comms discipline is the IGL's job
Nobody else on the team is going to enforce how the team talks. That is up to you.
The good news is that comms rules are short. The team needs about three, and they are all about bandwidth.
Info is short and shaped the same every time. "Two B" is a call. "B B B they're all B oh my god" is noise that costs the exact seconds you needed for the retake call. If a call runs longer than a sentence or two, people stop processing it. That applies to you most of all. Anything longer than three sentences is a call nobody hears.
Dead players give their info once, then go quiet. Dead players talk over the information the living need most. The rule does not need to be polite: say what you saw, then stop talking until the round ends.
Clutches are silent. One player, one round, zero coaches. "Let him play" is a complete sentence, and saying it is your job when someone else starts backseat-calling.
And the rule for you specifically: critique calls after the match, not between rounds. The round after a blown call is the round your team most needs you to sound normal. Agree on this once, before the season: when a call fails, nobody says "had we done Y instead" mid-half. The strat discussion happens later, together. That one agreement is worth more than any single call you will make this season.
The IGL's homework between sessions
Most of the IGL's job is done before and after the match. Strats, defaults and setups are built before. What went wrong is reviewed after. During the match you are just picking from a menu you already wrote.
That sounds like a pro workload, and at pro hours it is. At amateur hours it is about 30 minutes between sessions, spent on three things.
Keep the stratbook current. Not forty strats. A default per side, two or three named executes, the utility that makes them work. Written where the whole team can see it, updated when a prac shows something is broken. If it is not written down, it does not survive a week, and you are back to inventing rounds live. The full system is its own guide: how to build a CS2 stratbook your team will actually use.
Skim your own demo at 4x. You are not doing a full team review (that is also its own guide). You are looking for one thing: the rounds where your call, not your aim, lost the round. Tag two or three. Those become the note you reread before the next official.
Steal one thing a week. Watch one pro demo half, not for aim, for structure: when do they commit, what does their default look like, how does the caller spend utility. One stolen idea per week, written into the book, is a lot of new looks over a season.
The point of the homework is not discipline for its own sake. Every item on that list removes a decision from the live rounds, and the live rounds are where your brain is already full. Written strats exist so you stop juggling everything in your head.
Managing the human layer
Everything above assumes four people who listen. Some nights you do not have that, and no call survives the discussion with a teammate who has decided the IGL is the reason the team is losing.
Three things that hold up in practice.
Ask, don't order, until you have earned that right. "Want to split B?" gets five people moving where "split B" gets an argument. This is not weakness. Authority with a new team is bought round by round, and the currency is calls that put people in positions where they get kills. Set your players up for multi-kills and the respect problem solves itself.
Give sites away. The anchor who owns B knows things about B that you do not. Letting him design the B setup costs you nothing and buys you a teammate who defends his own plan instead of tolerating yours. The IGL who is not open to ideas even though his strats keep failing is the one players leave teams over.
Know when to stop calling. This is a skill, not a surrender. When the team is not receptive, over-calling makes it worse. Drop to destination calls, keep the economy tight, win your own fights, and try again next map. A structured team is built in pracs, not forced into existence mid-match.
The pattern in everything above: the IGL's real enemy is not the other team, it is his own working memory. Every section of this guide ends the same way, with something written down before the match so it does not have to be invented during it. Buy rules. Prepared branches. Comms rules. Learnings.
That written layer is what The Ultimate CS2 Playbook is: the stratbook, per-player pages, demo review log, and the issues and learnings system, in one Notion workspace the whole team shares. It is the system my own team runs. If you are the caller, it is built for you.