04 / Reels and applications

Edit for evidence

A reviewer should not have to guess what you contributed. Present a small, coherent set of clips that makes your role, decisions and current capabilities easy to understand.

Decide what the reel needs to prove

Begin with the role you are presenting. A play-by-play reel should show accurate live selection, controlled intensity and clear outcomes. An analyst reel should reveal explanations supported by visible evidence. A hosting reel should demonstrate questions, listening, transitions and time management. A compilation of exciting moments can be entertaining while showing very little about any of these skills.

If an opportunity provides submission instructions, follow those before adopting general advice. Required duration, file format and game coverage may vary. There is no universal reel length that guarantees attention. Keep your selection proportionate to its purpose and remove clips that repeat evidence already established more clearly elsewhere.

Give every clip enough context

Identify your voice, role and the nature of the recording. A short label can distinguish a live community event from a solo practice cast. If a partner is audible, credit them accurately and obtain any permissions needed to use the recording. Do not make an informal rehearsal look like a commissioned appearance by adding misleading titles or event graphics.

Include enough of the setup for a reviewer to understand the decision you make. A final elimination shouted in isolation may reveal energy but not match awareness. A slightly longer passage can show how you establish the stakes, prioritise the action and return to a useful reset. Context is evidence when it helps explain your contribution.

Select complementary examples

Look for range within your chosen role. A play-by-play selection might contrast a tense, quiet setup with a chaotic finish. An analyst might include a concise replay explanation and a short desk exchange. A host might show a prepared introduction alongside a responsive follow-up question. Variety should serve a coherent claim, not disguise uncertainty about what you want to do.

Do not choose a clip solely because the match itself was spectacular. Ask whether your contribution makes it easier to follow. Sometimes the strongest evidence comes from an ordinary reset in which you identify a strategic change and hand over cleanly. Professional judgement is often easiest to hear when the game is not supplying all the drama.

A useful clip label

“Practice cast / Rocket League / play-by-play / my voice enters first.”

Add the source and permission context where relevant. A clear label is more valuable than an inflated credit.

Edit for clarity, not disguise

Balance speech and game sound so a reviewer can understand the commentary without constantly adjusting volume. Remove unnecessary waiting, but do not splice individual words to create a fluency you did not demonstrate. Avoid background music that masks diction or changes the apparent intensity of the original moment. Basic, transparent editing supports assessment.

Use DaVinci Resolve, Shotcut or another editor you can operate reliably; the software brand is not the achievement. Keep an uncut source passage available when you have the rights to share it. Some reviewers may want to hear how you handle the moments around your selected highlight, particularly recovery and interaction with a partner.

Check rights before publishing

Being able to watch a match does not automatically give you permission to redistribute its footage, music, graphics or commentary. Tournament organisers, publishers and other rights holders may set separate rules for community broadcasts and clips. Read the current terms for the material you intend to use. Permission for a private practice session may not cover a public portfolio.

Keep a record of permissions and credits alongside your source files. Avoid including private production communications, personal contact details or material covered by a confidentiality agreement. If you cannot establish a suitable basis for publishing a recording, choose a different source or seek permission. This is general editorial guidance, not individual legal advice.

Make the application easy to review

Test your link in a signed-out browser and on a phone. Make sure access settings match the submission instructions and that the opening frame identifies the purpose of the reel. Captions can improve accessibility; check names and game terminology manually rather than trusting automatic transcription. Keep contact details readable and avoid displaying information you do not want made public.

Your accompanying note should state the role, relevant experience and any practical availability requested. Distinguish paid work, volunteering and rehearsal honestly. Avoid claims such as “industry-ready” unless you can explain the standard behind them. Concrete details about what you have done are more useful than broad claims about passion or professionalism.

Use responses as information

A rejection or lack of reply does not isolate the quality of your commentary. Selection can depend on language, game coverage, timing, budget and the wider team. Do not promise yourself a predictable career outcome from a particular reel or course. Instead, ask a trusted reviewer whether the material makes the intended skills easy to assess.

Update the reel when you have stronger evidence, not simply because another month has passed. Keep a small archive of earlier versions and the reasoning behind your changes. If reviewers repeatedly miss a skill you think is present, reconsider the selection or labelling. The reel is a communication task of its own: it should reduce uncertainty about your work, not add another layer of performance around it.

Show the handover

Leave enough of the exchange to show that you listen. Collaboration is difficult to assess when every partner contribution has been removed.

State what is practice

A carefully labelled rehearsal can show real skill. It does not need an invented event credit to become useful evidence.

Can I start without event experience? →