Guide
How to write scrim reports your team will actually read later
Most "scrim reports" are either skipped entirely or written once, in detail, and never opened again. Neither is useful. Here's what to record, what to skip, and a template you can start using today — no tool required.
What to actually record
A scrim report that takes fifteen minutes to write gets written once and abandoned. Keep it short enough that someone will actually do it after every scrim, not just the ones that go badly.
- The result and the map(s). The bare fact, so it's searchable later by opponent or by map.
- One thing that worked. Specific enough to repeat — not "good teamwork," but the actual read, execute, or rotation that landed.
- One thing that didn't. Named plainly. A report that only lists what went well isn't a report, it's a highlight reel.
- One change for the next scrim. Exactly one. A list of ten adjustments gets ignored; a single, specific one gets tried.
Three mistakes that quietly kill team knowledge
Nothing gets written down until someone asks
The report only happens reactively — a new player asks "what happened against that team last month?" and now someone is reconstructing a scrim from memory, days or weeks later, with the details already gone soft.
One person becomes the archive
The IGL or coach remembers everything, so nobody else bothers writing it down. That works fine right up until that person misses a week, changes teams, or graduates — and takes the only copy of the season with them.
Notes are scattered across five different places
A result in one Discord channel, a tactical adjustment in a DM, a demo timestamp screenshotted and never referenced again. Technically it's all "written down" somewhere. Practically, nobody can find any of it three weeks later.
A template you can copy today
Paste this into whatever you already use — a notes app, a shared doc, a pinned Discord message. It doesn't need a tool to work; it needs someone to fill it in every time.
Date & opponent: _______________
Map(s) played: _______________
Result: _______________
What worked: One or two things you'd do again
What didn't: One or two things you'd change
One change for next scrim: Pick one. Not five.
When a pinned message stops being enough
The template above works fine with a notes app for a while. It stops working once you're running more than one or two scrims a week, once you actually need to search past reports instead of scrolling for them, or once someone new joins mid-season and has to read through months of them at once. That's the specific point where a dedicated place — not a pinned message, not a spreadsheet three people half-maintain — starts paying for itself.
That's what CompeteSync is built for: the same report, structured and searchable, kept alongside your schedule and tactical notes instead of separate from them. See how it works or apply for the Founding Teams program.