A good scrim post answers an opponent's questions before they ask. Start with a one-line header: LFS, region, rank range, time with its zone, and length. Under it, add a details block: team name, Discord tag, BattleTag, host, stagger, hero bans, kill cam and map pool. The other team can then say yes without a long DM thread. The fields suit Overwatch and Marvel Rivals, and a team in another game can drop the lines that don't apply.
Key takeaways
- A post that answers an opponent's questions up front lets a reply simply be a yes.
- Always give your region, and add your platform where your game splits players by it.
- Always give the time zone, and name the day if the scrim isn't today.
- Write the hero ban number, since "same as ranked" changes with the game and the season.
- Before reusing a saved post, check the time, length and map pool.
The scrim post template to copy
Copy this block and swap in your own details: the parts of the first line, and everything after each label. Then post it in your LFS (looking for scrim) channel. Discord keeps the line breaks and turns the stars into bold.
LFS | region | rank range | time and time zone | length
**Team name:** your team name
**Discord tag:** the person who can confirm
**BattleTag:** a player who will be in the lobby
**Host:** we host, you host or your call
**Stagger:** no staggering, or allowed
**Hero bans:** none, or the number per team
**Kill cam:** on, off or your call
**Map pool:** the maps you will play, or the mode order
Add your platform after the region if your game splits players by platform. If the scrim isn't today, add the day to the time.
Here is a filled Overwatch example, with a made-up team and tags.
LFS | EU | Plat1 - Dia5 | 20 CET | 2hr
**Team name:** Sample Squad
**Discord tag:** samplecaptain
**BattleTag:** SampleCaptain#0000
**Host:** We host
**Stagger:** No staggering
**Hero bans:** 2 each
**Kill cam:** Off
**Map pool:** Mode order is Control, Hybrid, Escort, Push
Now compare a one-line post: LFS | Plat | 8pm. A team reading it still has to ask which Plat, which time zone, how long, who hosts and which modes. The filled example answers all five.
Here is a filled Marvel Rivals example, again with made-up details. It's our own adaptation: your in-game tag replaces the BattleTag, the ban number is your team's offer, and the maps should come from the current rotation. We left out the kill cam line, so add it back if your lobby has that setting.
LFS | EU | PC | Plat1 - Dia3 | 19 CET | 4 maps
**Team name:** Sample Squad
**Discord tag:** samplemanager
**In-game tag:** SamplePlayer
**Host:** You host
**Stagger:** No staggering
**Hero bans:** 3 each
**Map pool:** Shin-Shibuya, Krakoa, Yggdrasill Path, Hell's Heaven
What does a complete scrim post need?
A complete scrim post has twelve fields: four in the one-line header after the LFS tag, and eight in the details block under it. The header helps a team decide whether to stop scrolling, and the details block lets that team say yes without asking you anything else.
| Field | What the opponent learns | Where it goes |
|---|---|---|
| Region, plus platform where it matters | Whether you can play each other | Header |
| Rank | Whether the match looks even | Header |
| Time | When you play, and in which time zone | Header |
| Length | Whether the session fits their evening | Header |
| Team name | Who they would be playing | Details block |
| Discord tag | Who to message to confirm | Details block |
| BattleTag | Who to add in the game | Details block |
| Host | Who runs the lobby, and by Overwatch etiquette who picks map 1 | Details block |
| Stagger | Whether a team may keep an enemy alive to block a reset | Details block |
| Hero bans | The ban rule for this scrim | Details block |
| Kill cam | Which setting the lobby uses | Details block |
| Map pool | Which maps you will play | Details block |
The fields are written for Overwatch and Marvel Rivals. A team in another game can swap the BattleTag for its in-game tag and drop any line that doesn't apply.
Why do so many scrim posts end in a long DM thread?
A scrim post ends in a long DM thread because the other team has to settle several things before it can say yes, and every detail the post leaves out becomes a question. Who hosts? Which maps? What are the bans? Who do we add?
Picture a typical Friday night for a captain. There's a slot tonight, the roster finally lines up, and a one-line post goes into the LFS channel with a rank and a time. A team answers, and the questions start. Each one takes a message, and both captains are also rounding up their players. If the deal falls through an hour later, the whole exchange starts again with someone new.
A one-line post gets noticed but can't answer those questions, so the real negotiation happens in DMs. The fix is a post that answers them up front.
Should the details block go in the post or wait for DMs?
Put the details block in the post, under the one-line header. That's our view, and it differs from British Esports' guide to Overwatch 2 scrim etiquette, the closest thing to a published LFS format we found. It dates from when the game was still called Overwatch 2.
The guide treats the LFS post as a notice. The post carries the rank and the time, and the teams settle the host, map pool, team name and BattleTags in DMs afterward. Short lines are quick to write and easy to scan.
The cost shows up after someone replies. The DM turns into an interview, and the interview repeats with each new team.
Our version keeps the header teams already know and adds the details block under it, so a reply can simply be a yes. The block is your starting offer, and the other team can still ask to change a map or a ban rule.
The twelve fields are our own list, because we found no industry standard for scrim posts.
We have no numbers on how many scrim posts get answers, so we can't promise this format brings more replies. It does leave fewer questions to ask.
If a channel expects one line, respect that. Post the header alone from the account that can confirm the scrim, then send the details block in your first DM.
The header line: LFS tag, region, rank, time and length
The header is one line a captain can read while scrolling: the LFS tag, your region, your rank range, the time with its zone, and the length. Put a | between the parts, so the eye can jump straight to the rank or the time.
These three examples come from the LFS format in British Esports' guide:
- LFS | EU | PC | 18 BST | 4.1k | 4 maps
- LFS | PC | Plat1 - Dia5 | 19h BST | 2hr
- LFS | Master 1-3 | 22 CEST Saturday | 1hr
The guide's order shifts between examples and some leave parts out, so use our order: tag, region, rank, time, length. Numbers like 4.1k are skill ratings.
The guide treats platform as optional in Overwatch because the game has cross-play, which is why the last example leaves it out. Cross-play doesn't settle region, so we're firmer: always give your region, and add your platform where your game splits players by it. Marvel Rivals is the clear case, because its ranked mode keeps PC and console players apart, so your platform tells a team which ladder your rank comes from.
The guide's examples are all Overwatch. We found no published LFS format for Marvel Rivals, so a Rivals team can treat this shape as a starting point.
Rank: give a range another team can judge
Give a rank range narrow enough for another team to judge at a glance. British Esports' guide says to be as specific as possible, and it singles out a range like 2-3k as hard for others to read.
Compare that with a tighter range from the same guide, 2.5 - 2.7k, or with Plat1 - Dia5 above. Either one tells a captain whether the match looks even without opening a DM.
A new team, or one playing with a ringer (a stand-in from outside the team), may not know its rank yet. The guide's advice is to make your best guess in the post and tell the opponent in DMs that it's a guess. They then have the real picture before the scrim starts.
Keep rank in the header and leave it out of the details block. A number written twice is one more thing to update when you reuse the post.
Time: always include the zone, and name the day if it isn't today
Write the time with its zone on every post, and name the day if the scrim isn't today. A bare "8pm" forces a question, because one channel can hold teams playing on different clocks, and the guide's own examples mix BST and CEST.
A start time and a range both work. The guide shows 18 BST and 20-22 BST, and the range also shows how long you plan to play.
In our experience scrims are booked the same day, so a reader will assume tonight unless told otherwise. A post for another day has to say so, as in 22 CEST Saturday. Leave the day off and someone may turn up on the wrong night.
If you keep a saved copy of your post, check the zone as well as the time. When the clocks change, BST becomes GMT and CEST becomes CET.
Length: give it in hours or maps
State the length in hours or in maps, whichever your team counts in. The guide uses both: 1hr, 2hr, 4 maps and 6 maps.
This part of the header answers one plain question for the other team: does this session fit our evening? If they can stay for an hour and you wrote 4 maps, you both find out before anyone loads into a lobby.
Hours and maps don't convert neatly, so we'd use hours if your team has a hard stop, and maps if you're working through a set practice plan.
Team name, BattleTag and Discord tag say who you are and who to add
These three fields let an opponent act right away, without asking who to message or who to add.
- Team name: use the name another team will recognize or can look up. It tells them who they would be playing and gives them something to check.
- Discord tag: give the tag of the person who can confirm the scrim, even if someone else made the post. If a manager posts but the captain decides, the captain's tag belongs here. A reply that lands with someone who has to go and ask costs as much time as a thread.
- BattleTag: British Esports says BattleTags are usually exchanged on both sides, so giving yours up front saves a step. Use a player who will be online and in the lobby around scrim time, since that's who the other team will try to add. Marvel Rivals teams give their in-game tag instead.
If you'd rather not leave your BattleTag in a public channel, hold it back and send it in your first DM. Keep the Discord tag in the post, since the other team needs it to reach you.
Host: say who runs the lobby, because etiquette lets the host pick map 1
Name the host in your post, because under British Esports' etiquette the hosting team also picks map 1. The pick then alternates between the teams, and the host asks the opponent for its map when that turn comes. So one field settles two things: who runs the lobby and who picks map 1.
Write one of three options:
- We host
- You host
- Your call
No guide we read says how to choose, so this part is our view. If you care about map 1 or your lobby is already set up, offer to host. If you don't mind, write "your call", and the other team has one less thing to ask.
Stagger: agree on the rule before the opening fight
Stagger belongs in the post because it's a rule two teams agree on, and the time to agree is before anyone fights. Staggering here means leaving an enemy alive on purpose so that player's team can't reset. British Esports says players and teams should avoid it unless it was agreed before the scrim, and it names Mercy and D.Va as the players usually left alive.
With nothing in the post, each team shows up with its own idea of what's fair, and the question comes up mid-scrim. One line closes it:
- Stagger: no staggering
- Stagger: allowed
As far as we could find, no custom-game setting or tournament rule covers this, so the two teams have to settle it themselves. The guide is about Overwatch. A Marvel Rivals team can keep the line if staggering matters to it, and drop the line if it doesn't.
Hero bans: write the number, because "same as ranked" changes
Write the number of bans per team, because "same as ranked" depends on the game and the season. Ranked rules change over time, so two teams can read those three words and picture different numbers.
- Overwatch: Blizzard's Director's Take announced Hero Bans for Competitive in Season 16, when the game was still called Overwatch 2. At launch that meant four bans in total, two per team.
- Marvel Rivals: the Season 7 patch notes raised bans to three per team, up from two.
Those ban counts date from those seasons, so check the current rules before you quote one.
Neither source covers custom games, so we can't say what a scrim lobby does by default. The host should check how the lobby applies your rule before map 1.
Either of these lines does the job:
- Hero bans: none
- Hero bans: 2 each
Kill cam: write on, off or your call
Write "on" or "off", or "your call" if it makes no difference to your team. The setting changes what players see after they're eliminated, and the host needs the answer either way.
Map pool: list what you will play this week
List the maps you'll play this week. Start from the live competitive rotation, checked against the latest patch notes the week of the scrim, then trim it to what your team wants to play.
A new season can change the rotation, so a pool copied from an old post can be out of date. Marvel Rivals' Season 7 notes, for example, put Tokyo 2099: Shin-Shibuya back in Competitive.
If you'd rather not name maps, write the mode order instead. British Esports gives this order of game modes for Overwatch when no pool is agreed:
- Control or Push
- Hybrid
- Escort
- Whichever of Push or Control was not played on map 1
The order sets only the mode: the host picks map 1, and the choice of map then alternates. The teams decide maps 5 and 6 between them. This order is Overwatch's, so a Rivals team should name its maps.
A tournament-specific pool can go in the post too, though British Esports' guide says it's usually discussed later. If that pool is the reason you want the scrim, we'd put it in, because the other team needs to know before saying yes.
Before you post: can your team play that slot?
Check your own lineup before the post goes up, because a team that answers will plan its evening around your time. A slot you can't fill sends both teams back to the start.
Supatimer, our free Discord bot for team scheduling, does that check with its availability calendar. With the bot in your server and your team set up on the Supatimer web dashboard, run /avail to post the week's calendar, and players mark when they can play. A calendar with several time slots, or with the maybe answer turned on, draws a heatmap board. Each day or time slot there shows its total on a small square, and that square turns green once the free players can make a full lineup. A yellow corner on the square means at least one maybe is counted in that total. A calendar with one time slot and maybe turned off lists names instead, so you count the lineup yourself, or switch its Board layout setting to Heatmap.
We'd post on a green square, or once the names make a full lineup. If a green square also has a yellow corner, check whether your lineup needs a maybe. If it does, wait for that player, or tell the other team in your first DM that your lineup isn't settled yet.
What should you do once a team says yes?
Cross out or delete your post as soon as a team says yes, so others stop messaging you. If the other team's reply didn't give its team name, Discord tag and BattleTag, ask for them, since your post only covers your side. Then tell your own players what you agreed and get ready to start on time.
Supatimer's /scrim command confirms the scrim and posts the match announcement, so your players see what you agreed. /update adds the score to the announcement afterward. The command docs cover both. Players who connect Google Calendar get the confirmed scrims they're tagged in on their calendar.
British Esports suggests a few habits for the hours that follow:
- Ping your team's whole server only when it's urgent, such as five minutes before a scrim or after an opponent cancels.
- Expect delays of about five minutes, and don't let yours pass ten.
- After 15 minutes the other team may look for another scrim. The guide calls this an unwritten rule, and says they should tell you they're leaving.
One habit of our own: tell the other team about any ringers before the scrim starts.
Which fields change when you reuse a saved post?
The time, the length and the map pool change on almost every post. The other fields change only when something else does. Go through this list before you paste a saved post:
| Field | When to check it |
|---|---|
| Time and its zone | Every post |
| Length | Every post |
| Map pool | Every post |
| Rank | When your lineup changes |
| Hero bans | When a new season arrives |
| Region and platform | When you play somewhere else |
| Team name, tags | When the name or the person behind a tag changes |
| Host, stagger, kill cam | When your team's habits change |
Can Supatimer read an opponent's post for you?
Yes, if your Overwatch or Marvel Rivals server is in the closed beta. Besides the /scrim command, a form on the Supatimer web dashboard can make your match announcement. The closed beta adds our scrim parser to that form: instead of retyping the opponent's details, a manager pastes the opponent's LFS post. The parser, one of Supatimer's AI features, uses Google Gemini to fill in their team name, rank, BattleTag, Discord tag, host and stagger, and whether hero bans are on. Their map pool goes into the announcement's notes.
Time, length, region, the kill cam and the ban number stay yours to check, so read the form before you send the announcement. Access is set per server, so not every team has it yet. To ask about it, join our community server.
What to do next
Copy the template, fill in your details and post it for your next open slot.
To check your lineup first, add Supatimer to Discord. Our Discord scrim bot is free, and the /scrim command and the availability calendar need no beta access.
For the rest of the week's routine, start with our step-by-step guide to organizing scrims. We also have guides to Overwatch team practice and SupaScrim (the Overwatch workshop mod that records scrim stats), and for other games, Valorant scrims and CS2 scrims.
Frequently asked questions
What does LFS mean in a scrim post?
LFS stands for looking for scrim. It marks a post as coming from a team searching for an opponent, and it usually opens the header line.
What if my LFS channel only allows one line?
Keep the channel post to the header, and put the details block in your first message to whoever answers. The other team still gets every field.
Does this template work for Marvel Rivals?
Yes, as a starting point. Marvel Rivals has no published LFS format we could find, so our Rivals example adapts the same fields and swaps the BattleTag for your in-game tag.
What should I write if my team has no preference on a field?
Write "your call" for the host or the kill cam. That still answers the question, so the other team doesn't have to ask. Stagger, hero bans and the map pool still need an answer, so write the one you would accept.
Can Supatimer read an opponent's scrim post for me?
In the closed beta, yes. A manager pastes the post into the form that makes your match announcement on the Supatimer web dashboard, and the scrim parser fills in what it finds, such as the team name, rank and host. It covers Overwatch and Marvel Rivals, and access is set per server.













