Before you take a seat
The creator has already paid for the playtest. New playtests currently request feedback in English. Check the platform, language, play time and report format. Only book if you can meet these requirements and the deadline. If you apply, wait for acceptance before the seat and private access details become available.
How many seats you can hold
You can keep up to 3 direct seats at once, on different campaigns. You can also have up to 5 engagements on campaigns where the creator confirms who plays: requests still waiting, plus seats already accepted whose report you have not sent. Sending a report frees that place. A refusal, your withdrawal, or a request that expires after 24 hours frees a request. An expired direct seat does not count. These two limits are separate.
Follow the brief
Once reserved, read the private brief and access instructions. Play for the requested time, try the areas the creator asks about and answer every required question. Use the requested language. Keep private builds, access keys and unreleased material private.
Explain what you experience
Describe what you tried, what you expected and what actually happened. Mention what works as well as what feels confusing or frustrating. You don’t have to find a bug or suggest a technical fix. Specific observations are more useful than a score or a vague “good game”.
Record only when the mission asks for it
For a video mission, record the game, check that your voice is audible, and talk through what you notice. Follow the video length shown on that mission; the qualification’s 2–5 minute limit is separate. For a written-only mission, give the same useful detail in your answers — no video is required.
Send before your seat expires
Submit the report by the deadline shown on your reservation. An expired seat cannot receive a first report. You can submit while an attached video is transferring, but keep the tab open until the upload finishes. Check the confirmation and resume an interrupted upload so the creator can review it.
Review and corrections
The creator is paying for an attentive playtest that follows the brief, not for praise. Honest negative feedback is welcome. The creator has 7 days, starting when the report is ready to read, to accept it. For a video mission, that clock starts when the recording has finished processing. If they do not decide, the playtest is accepted and your reward becomes due. An administrator may ask you to correct an incomplete report. A negative opinion is not, by itself, a reason to refuse payment. If you run into a technical blocker, explain it clearly and contact support instead of filling the report with placeholder answers.
Make your feedback concrete
“The menu is confusing.”
“I wanted to change the sound volume. I opened the pause menu, but didn’t realise the gear icon was Settings. A text label would have helped me find it.”
You don’t need specialist vocabulary. Describe the moment so the creator can understand it.