You need players for a confidential project. You cannot name the game or describe everything they will see.
That does not mean the application has to be vague about everything else.
Applicants still need enough information to decide whether they can take part.
Agree with the client what can be shared at each stage.
The game’s identity may be confidential. Session duration, location, dates, equipment, payment and the broad activities involved can often be explained without revealing it.
Where a detail must remain undisclosed, explain the boundary as clearly as the approved wording allows.
Confidentiality should not leave applicants unsure whether they are applying for an interview, a playtest or several days of research.
Validation can explore approved games, genres, platforms and relevant behaviours without asking applicants to identify the confidential title.
The team needs clear guidance on what it can ask and discuss. Avoid improvising clues that reveal more than intended.
An applicant does not need insider knowledge of the project to demonstrate relevant experience.
Tell applicants when they will receive further information and whether an NDA is required before access.
Use the client’s approved process for sharing builds, links and materials. Keep recruitment adverts and public project pages within the agreed disclosure limits.
If restrictions affect participation, such as recording rules or device storage at a venue, communicate them before the participant commits.
Players should be able to understand who is contacting them, why information is being requested and how to ask questions.
A confidential opportunity still needs a clear application journey and realistic expectations. Mystery is not a substitute for trust.