Scrim schedule planner

How the planner builds a session

A scrim evening is a stack of blocks laid end to end from the start of your window: a warm-up, then for each opponent a series of maps with a break between maps, a longer break between opponents, and finally a review block. The planned length of one session is therefore:

warm-up + opponents × (maps × map length + (maps − 1) × map break) + (opponents − 1) × opponent break + review

With the default CS2 preset (three BO1 opponents, 45-minute maps, a 20-minute warm-up, 10-minute breaks and a 30-minute review) that is 20 + 3 × 45 + 2 × 10 + 30 = 205 minutes, or 3 h 25 min, which fits a window from 20:00 to 23:45 with 20 minutes to spare. Add a fourth opponent and the plan is 260 minutes, 35 minutes past the window; the planner tells you that and how many opponents do fit. Choose “after every opponent” for the review and each series gets its own review block before the break.

Choosing block lengths

The presets use 45 minutes for a CS2 map and 40 for a Valorant map. These are planning numbers, not measurements: both games play first to 13 rounds, and overtime, tactical pauses and technical issues push individual maps well past the average. The best figure is your own. Look at the last ten scrims, take the median map length including the pause between rounds, and use that. Keep the warm-up honest as well: 15 to 20 minutes of aim work or a short deathmatch is enough if everyone is in the lobby on time, and it is wasted if half the team joins during it.

A review block is the part that turns practice into improvement, and it is the first thing people cut when the schedule runs late. As a starting point, aim for a review worth roughly a quarter to a third of the time spent playing, split between a quick reset after each opponent and a longer session at the end. If you find yourself trimming it, remove an opponent instead.

Time zones and clock changes, without surprises

The plan is written in wall-clock time in the zone you pick, because that is how your players think about it. Internally every block is a real span of elapsed time counted from the window start, and the calendar file stores each event in UTC. That combination keeps the plan correct in three situations that normally cause missed scrims.

• Different clock-change dates. The United States moves its clocks on the second Sunday of March and the first Sunday of November; the EU and the UK on the last Sunday of March and October. For a few weeks each year a US team and a European team are one hour closer or further apart than usual. Pick the opponent’s zone under “Also show times for” and the planner flags plans where the difference changes.
• Zones without clock changes. Turkey has used UTC+3 all year since 2016, so a Turkish team scrimming a European team sees the gap change twice a year even though its own clocks never move.
• Windows that contain the change. A 01:00 to 04:00 window on the night the clocks go forward is only two real hours. The planner counts real minutes, so it warns you when a plan no longer fits instead of silently overlapping.

A wall-clock time that does not exist (02:30 on the night the clocks go forward) is moved to the same time after the change; one that happens twice (01:30 when the clocks go back) is taken as the first occurrence.

Exports: text, CSV and calendar

Copy as text gives you a plain schedule to paste into Discord or a team channel, including the second time zone when you chose one. CSV has one row per block and opens in any spreadsheet; it is written as UTF-8 with a byte-order mark so accented characters in a team name survive Excel. .ics is the standard calendar format that Google Calendar, Apple Calendar and Outlook all import. Choose one event per session, with the timeline in the description, or one event per block if you want a reminder at the start of each map. You can also add a reminder that fires a set number of minutes before each event.

Before the first map

The plan only works if both teams agree on the details it cannot know: who hosts, the map pool and veto order, the server settings, whether to record demos, and what counts as a no-show. A short message the day before with the schedule from this page, the lobby details and the agreed rules saves the first ten minutes of the evening. Treat the plan as a promise to the other team too: finishing on time is what makes them come back.