How do you prepare a demo before esports coaching starts

Prepare a demo before esports coaching by sending one recent match that shows your normal problems, then add a short note with your goals and a few timestamps where you felt unsure. Do not send a highlight reel, a stomp win or a match you barely remember.

A coach needs context more than perfection. The best demo shows your habits under pressure: the rotate you always delay, the duel you keep forcing, the utility you buy but never spend, or the silence that appears when the round becomes hard.

You are not trying to impress the coach. You are trying to give them enough material to find the pattern faster.

Which match should you choose?

Choose a recent competitive match that was close enough to reveal decisions. A 13-2 win often hides mistakes because the opponent gives you space. A 2-13 loss can help if the same issue appears clearly, but it can also become a long record of being outmatched. The best choice is usually a close loss or a narrow win where you felt the game could have gone either way.

Pick a match from your usual role, map pool and queue type. If you normally solo queue, send a solo queue match. If you want team coaching, send a scrim or team match with voice if possible. A coach cannot read your normal problems from a one-off experiment where you played a different agent, role or position for fun.

Use the Review Your Own Demos guide before sending the file if you have time. You do not need to solve the demo yourself. You just need to arrive with a few honest observations.

What should your note include?

Keep the note short. The coach is going to watch the game, not grade an essay.

Send:

• Your rank or level and the game mode.
• Your usual role or positions.
• What you think is going wrong.
• What you have already tried.
• Three to six timestamps that confused you.
• Any technical context, such as missing voice audio or a substitute role.

The key sentence is: "I think the problem is..." That sentence may be wrong, and that is fine. It tells the coach where your own model of the game sits. If you think your aim is bad but the demo shows late crosshair placement or rushed peeks, the gap between those two views becomes useful coaching material.

Which timestamps are worth marking?

Mark timestamps where a decision felt unclear, not only where you died. Deaths matter, but coaching is often about the ten seconds before the death.

Good timestamps sound like this:

"Round 5, 0:48. I did not know whether to rotate or stay."

"Round 9, 1:12. We had space, but I was unsure where to hold after plant."

"Round 14, 0:36. I took the fight because I felt trapped. Was there a better route?"

Bad timestamps sound like this:

"Round 7. I missed."

"Round 11. Teammate threw."

"Round 18. This guy is cheating."

The useful timestamp asks a question the coach can answer from the round. The weak timestamp asks the coach to share your frustration.

Should you send wins or losses?

Send the match that teaches the problem, not the match that protects your ego. For most players, that means a loss. Losses expose the decision points that wins often cover up.

There is one exception. If you only send losses where the team collapsed early, the coach may spend the whole session separating your problems from the match state. A close win can be useful when you still felt lost, rushed or dependent on lucky fights.

The real test is whether the same behaviour appears more than once. If the demo has one strange death and no repeated pattern, choose another match. Coaching time is too valuable to spend on a single odd round.

What should you avoid editing out?

Do not hide the ugly rounds. Coaches need to see the panic, the late calls, the missed utility and the bad peeks. A polished clip pack is almost useless unless the session is specifically about mechanics.

Leave in the economy mistakes. Leave in the round where you stopped talking. Leave in the timeout where the team changed nothing. Leave in the death that embarrassed you. These are often the moments that reveal the habit.

If comms are part of the issue, send audio when you can. The Comms Under Pressure guide explains why the timing and shape of a call matter. A text summary cannot show whether the call arrived before the fight or after the damage was already done.

How much should you review before the session?

Enough to have questions, not so much that you arrive defensive.

Watch the demo once and write down what you notice. Then stop. If you watch it five times, you may build a case for your first theory and start filtering out anything that challenges it. Coaching works better when you bring curiosity rather than a closing argument.

Use three buckets:

1. Decisions I did not understand.
2. Fights I keep losing in the same way.
3. Team moments where our plan broke.

Those buckets help the coach move quickly. They also stop the session from becoming a death-by-death tour with no main thread.

What if you play several games?

Send the game you want coached now. Soarne covers multiple titles, but a useful session still needs a clear target. A CS2 demo and a Valorant VOD in the same hour will usually split attention too far unless the coach specifically asked for both.

If your issue is general, such as panic in ranked or poor warm-up transfer, say that in the note. The coach can still start from one match and connect it to broader habits. The Pre-Match Routine and the First Round guide is useful if your demo always starts badly before settling down.

What should you expect the coach to do with it?

They should look for repeatable decisions, not isolated mistakes. They may ignore the timestamp you cared about and spend ten minutes on a quieter round that shows the real issue. That is normal. You saw the match from inside your own stress. The coach is looking from outside it.

The coaching page explains the broader session shape, but the useful principle is simple: a prepared demo lets the coach spend less time finding the problem and more time making it trainable.

A good demo is recent, ordinary and honest. Bring one match, a short note and the moments that confused you. That gives the session a clear start without pretending you already know the answer.