Evidence ledger / 03 / Team trials

PREPARE FOR A STRUCTURED TRIAL

A trial should answer agreed questions—not ask a player to guess what will count.

Preparation guidance, not legal advice or an invitation to apply.

Verify the invitation first

Before accepting a trial, check who is contacting you and whether they have authority to speak for the organisation. Follow a contact route independently from the organisation’s official website or established public account. Do not rely only on a display name, a copied logo or a private message saying that an opportunity is urgent. A genuine conversation can withstand a reasonable request for verification.

Be cautious if someone asks for account credentials, recovery codes, remote access to your device or a payment to unlock an unspecified team opportunity. A trial may involve legitimate software requirements, but those should be explained and traceable to official sources. Do not install an executable supplied in an unverified message merely because it is described as an anti-cheat or voice tool.

A practice workspace with keyboards, screens and headsets prepared for a team session
Practice-space context from Unsplash. The scene does not identify trial participants or imply a recruitment relationship.

Agree the shape of the assessment

Ask for the trial’s purpose, expected duration, number of sessions and intended role. Confirm the time zone, server region and communication channel. Where a team expects preparation, ask for the material early enough to use it. A candidate should not have to infer whether the assessment prioritises immediate results, adaptation to a system or longer-term development potential.

Clarify practical terms before committing to substantial time or expense. If travel, accommodation, compensation or equipment are involved, request the arrangement in writing. A practice invitation is not an employment contract. If a proposed agreement affects exclusivity, intellectual property or future opportunities, take appropriate independent advice rather than treating an informal reassurance as a complete explanation.

Trial preparation checklist

  • Verify the organisation and the person arranging the session.
  • Confirm role, objectives, timing, time zone and expected preparation.
  • Check official software, server access and equipment beforehand.
  • Agree recording, audience access and retention expectations.
  • Understand any payment, travel or contractual terms.
  • Identify the feedback contact and the next decision point.

Protect communication and recordings

Voice communication can reveal tactical information and personal details. Agree whether the session will be recorded, who will see it and whether any part may be published. A team’s internal review copy is not automatically permission for a public highlight. Players should also ask before recording private sessions themselves, and everyone should follow applicable law and event rules.

If Discord is used for coordination, check the server and account carefully. Keep direct-message privacy settings proportionate to your needs and use the platform’s reporting tools when appropriate. Moving a conversation to a familiar service does not verify the person on the other side. Keep relevant written arrangements without collecting or sharing unnecessary information about other participants.

A trial tests the working relationship as well as the player. Clarity, respect and feedback are evidence too.

Make the session useful

Arrive ready to perform the agreed role rather than trying to demonstrate every possible skill. Ask a concise question when an instruction is unclear. During play, prioritise the team’s information needs and avoid turning every mistake into a lengthy explanation. There will usually be a better moment for detailed review after the game or between planned blocks.

Staff should create comparable opportunities where possible. If candidates receive different roles, instructions or opposition, record those differences. Introduce the communication structure and give unfamiliar players enough context to participate. A single chaotic session may say as much about the trial design as about the candidate. Breaks and realistic schedules support a more interpretable assessment.

Close with an explicit next step

After the session, write brief notes while the examples are fresh. Separate what happened from how you felt about it. Players can record which instructions helped, where expectations were unclear and whether the environment felt respectful. Staff can connect observations to the original criteria rather than retrofitting a justification to the match result.

Ask when a decision or update should be expected. Feedback can be concise without being vague: identify a relevant strength, a specific gap and whether another assessment is planned. A rejection does not require a public announcement or an argument. If communication stops, one measured follow-up is reasonable; continued pressure rarely improves the quality of the process.

For younger players, involve a parent, guardian or appropriate trusted adult before unfamiliar travel, financial commitments or agreements. Check the applicable competition’s age and eligibility requirements; they vary by game, region and event. This website does not set those requirements or replace safeguarding procedures.

Next: platform checks