Most ranked players just ban the map they hate. That's leaving a quarter of a tournament series on the table — and in OCE-region scrims and TetraCup, it's the single most common identifiable mistake we see on losing teams. This is the ban-pick framework we teach for both ranked map-veto (now live in OCE Comp) and tournament BO1/BO3/BO5 series. It's not magic, it's math + a small amount of psychology.
Methodology + caveat: map pool, agent meta, and OCE win-rate tendencies described below are TetraGG coach observations aggregated 2024-2026 from our booster + student games, plus public Riot patch notes verified against the current client. Map pool rotates patch to patch — confirm the active competitive pool in your Valorant client before applying any specific map-by-map advice here. OCE meta also shifts with each agent rebalance; expect this article's specifics to drift across 2-3 patches. As of May 2026.
The current OCE competitive map pool (verify in client)
At time of writing, the rotation includes (alphabetically, not in client order):
- Ascent
- Bind
- Haven
- Icebox
- Lotus
- Pearl
- Split
- Sunset
Riot keeps a working pool of 7-8 maps active in competitive at any given time. Maps cycle out for re-work (e.g., Breeze, Fracture, Abyss historically). Always confirm the current pool in your client before tournament prep — this list will go stale.
Riot's official map roster page is at playvalorant.com/en-us/maps if you want the canonical reference.
The four kinds of map bans
People conflate these and end up with bad decisions. Separate them mentally:
| Ban type | What you're avoiding | When to use |
|---|---|---|
| Avoidance ban | A map you hate / lose on | Solo ranked, when veto comes to OCE comp |
| Counter ban | A map your opponent is strong on | Scrims, tournament where you've scouted |
| Comp ban | A map your agent pool can't run | Stack queue, fixed-roster team |
| Pool-cycling ban | A map likely to rotate out soon | Long-form prep — don't invest deep prep into a map about to leave |
The mistake is using avoidance logic in a tournament (you ban Bind because you personally hate it, but your team's actually strong there) or using comp logic in ranked (you ban Lotus because your 5-stack lacks a Killjoy, but you're solo-queueing anyway).
Ranked solo-queue: the simple ban heuristic
If/when ban-pick comes to your ranked queue (Riot has tested it region-by-region; OCE has had partial rollout), the right simple rule:
Ban the map with your worst personal stats over the last 30 games.
Not "the map you hate." Hate and stats often diverge — students who hate Icebox sometimes have a 58% WR on it because they sweat. Open tracker.gg or the in-client career tab, look at win rate per map, ban the lowest.
If you have <10 games per map on record, fall back to: ban the map you have the fewest agent options on. A Phoenix-Reyna OTP banning Lotus is rational. A Cypher main banning Lotus is irrational (Cypher is one of the strongest Lotus setups).
Tournament BO1 ban-pick: the formal version
In TetraCup format and most OCE community tournaments, the ban-pick sequence is generally:
- Team A ban
- Team B ban
- Team A ban
- Team B ban
- Team A picks (or coin flip / higher seed)
- Side select by the other team
That leaves 4 maps after step 4, of which Team A picks one. So you're not just banning your weakest — you're shaping what the opponent's forced pick set looks like.
For TetraCup specifics on format, see our TetraCup format breakdown.
The two-ban logic for BO1
Your ban 1: Eliminate your worst map (avoidance). This is uncontroversial.
Your ban 3: This is where most teams go wrong. Don't just remove your second-worst. Instead:
- Look at what's left after your ban 1 + opponent's ban 2.
- Identify the map you'd most want to play in the remaining set.
- Now ask: "What's the map the opponent would most want to pick if I leave it in?"
- Ban that.
You're forcing them to pick from your top 3 maps, not their top 3.
The "pick" decision (BO1 only — BO3+ different)
Once 4 maps remain and you pick: don't always pick your best. Pick the map where the gap between your skill and theirs is widest, even if it's not technically your #1 strongest.
Example: you're 65% on Ascent and they're 60% on Ascent (5% gap). You're 55% on Lotus and they're 35% on Lotus (20% gap). Pick Lotus, not Ascent.
This is the math most teams miss. You don't pick where you're strongest. You pick where the asymmetry is largest.
Tournament BO3 / BO5: the longer game
In BO3, you and the opponent are committing to a multi-map narrative. Sequence matters.
| Map slot | Strategy |
|---|---|
| Map 1 (your pick) | Your strongest pick where you can win in regulation (no need for OT-resilience). Set the tone. |
| Map 2 (their pick) | You're on their strongest. Survive. Don't lose 13-3. A 13-9 loss bleeds less morale and keeps your team mental. |
| Map 3 (decider) | The remaining map after bans. Prep your top 2 decider candidates equally before the series. |
Strong / weak / unknown — the 3-bucket model
Before any tournament, classify each map in the active pool:
- STRONG: 60%+ scrim win rate over the last 4 weeks, full agent comp drilled
- NEUTRAL: 45-59%, comp viable but not memorized
- WEAK: under 45% OR no agent comp drilled
A healthy roster has 3 STRONG, 3 NEUTRAL, 2 WEAK. Don't go in with 5 STRONG and 3 WEAK — opponents will ban your STRONGs and force you into your WEAKs.
If you have only 2 STRONG and 5 WEAK, you're not ready for the bracket. Spend the week before scrimming to bring one NEUTRAL up to STRONG, not five WEAKs up to mediocre.
OCE meta tendencies (and why they matter for bans)
Aggregate observations from our scrim notes — not Riot-verified, but consistent with what scrim review surfaces:
| Map | OCE meta tendency | Ban implication |
|---|---|---|
| Bind | Attacker-side WR for teams with A-tele execution | No Skye/KAY-O flash A-short → ban Bind early |
| Ascent | Mid control = round. Teams without mid-market smokes pre-fold | No Omen/Astra/Brim → expect Ascent to punish |
| Haven | Three sites = chaos rotation. Often 13-11 either way | High variance — ban if you want a stable series |
| Split | Defender-favored at OCE Asc+. Sentinel meta | Pick if Cypher/Killjoy mains; ban if not |
| Sunset | Newer pool. Comp innovation still happening | Less veteran teams over-perform here |
| Pearl | Mid pillar control round-defining. Operator-heavy | No Operator player → weight-ban Pearl |
| Lotus | Most rotation-complex map. Punishes solo chaos | Strong for organized 5-stacks; ban in pug tournaments |
| Icebox | Vertical. WR split between teams with Sage and without | No Sage on roster → lean toward banning |
These shift with each agent patch — tendencies from our scrim pools, not OCE-wide tournament data. Starting framework, refine from your own history.
The psychology of ban order
A subtle thing pros do that beginners miss: what your ban order reveals about your prep.
If your team always bans Icebox first, the opponent learns: "they don't have a Sage." Strategic data leak. The fix: occasionally ban your second-worst map first as a feint — small EV cost, obscures your prep to scouts.
The "ban around their pick" trick
If you've scouted the opponent's last 2 series, identify their comfort pick. Don't ban it. Ban the maps adjacent to it — the ones they'd pivot to. Forces them to either pick the known map (which you've prepared counter-comps for) or pick something they're less comfortable with.
Small-sample observation from our own scrim coaching but the directional pattern holds.
Common mistakes (from our scrim VOD reviews)
1 — Banning emotionally after a loss. One bad scrim is sample of 1. Trust your 4-week WR, not last 24h.
2 — All five players agreeing. Designate a "veto challenger" who argues against the consensus ban.
3 — Picking your "fun" map. If your WR on it is 38%, save it for unrated.
4 — Ignoring side-pick. Defender-favored map = take defender first half if you have the choice.
5 — Forgetting tournament patch ≠ ranked patch. Tournaments often lock on a prior patch. Re-confirm before drilling.
Side selection: the often-forgotten second decision
After ban-pick, you usually choose starting side. 50/50 in solo ranked, a real call in tournament prep:
| Map | OCE side tendency | Note |
|---|---|---|
| Bind | Slight defender favor | Defender util holds well |
| Ascent | Defender favor at high ranks | Strong default site holds |
| Haven | Even / slight attacker | Three sites favor mobile attackers |
| Split | Strong defender favor | Sentinel meta map |
| Sunset | Even, patch-dependent | Newer map, data still settling |
| Pearl | Attacker favor at Asc+ | Operator-heavy mid control |
| Lotus | Roughly even | Rotation complexity favors organized teams |
| Icebox | Defender favor (Sage walls) | Sage absence inverts this |
Tendencies subject to patch changes — refresh from your own scrim data each patch.
When to bring this to a coach
The ban-pick decision tree is teachable in a 1-hour Master-tier coaching session if your team is already drilled on comps. The harder part — knowing which maps are realistically STRONG / NEUTRAL / WEAK for you — usually takes a coached scrim block to assess honestly (your own internal estimates are usually 1 tier too optimistic).
For 5-stack tournament prep, see our coaching tiers on /services. Pro-tier coaching includes a full ban-pick walkthrough against a hypothetical opponent's expected ban pattern.
City-specific note
Sydney and Melbourne university teams that have made TetraCup deep runs tend to share a common pattern: they pre-script their bans in a shared doc 24h before the match, then don't deviate on the day unless they see a comp surprise in pick-phase. Brisbane community teams over-improvise in our experience — and improvisation in ban-pick under tournament pressure usually costs.
FAQ
Q: How often does Riot rotate the OCE map pool? Roughly every 6 months a map enters or exits competitive pool. Sometimes alongside an Act change, sometimes mid-Act. Verify in client — this article will go stale within 1-2 patches.
Q: My solo ranked doesn't have ban-pick. Why prepare? For tournaments and scrims, where ban-pick is decisive. Even in solo ranked, knowing which maps you statistically lose on lets you swiftplay-warmup on those maps before queueing — proactive prep, not just reactive bans.
Q: Should I ban the same map every series? If your weak map stays consistently weak across 4 weeks — yes. If you've improved on it (run a 5-game block on Swiftplay or Unrated to test), reconsider. Don't update bans based on a single scrim.
Q: What if my team disagrees on ban order? Use the STRONG/NEUTRAL/WEAK bucket method as a forcing function. If you can't agree, you've probably bucketed maps differently — surface that disagreement (it usually reveals a teammate who hasn't been honest about their map weakness).
Q: Is there an OCE-specific map pool different from NA? Generally no — the competitive pool is uniform globally. Regional meta differences come from agent preferences and player tendencies, not map availability.
Q: How do I know I've actually improved on a map? 3-week WR uptrend on tracker.gg + comfort in the comp + ability to draw the site defaults from memory. If you can't draw the map's default util setup on paper, you haven't internalized it yet.
Related reads:
- TetraCup Format Explained
- Valorant Agents Tier List · OCE Meta 2026
- Valorant Placement Matches Strategy 2026
For Riot's canonical map list, see playvalorant.com/en-us/maps.
Want a coach to walk through your team's ban-pick logic before a tournament? A Master-tier 1-hour session covers the full STRONG/NEUTRAL/WEAK assessment plus opponent scouting. Book at /services, browse our coach roster, or drop into our Discord at discord.gg/muDANR4ex6 — we're an ABN-registered Melbourne service (ABN 70 767 210 027), 32 boosters, 1247 completed orders, 4.94 rating.