Completing a Screener using our Template

Turnaround Screeners in Less Time

Jonny avatar
Written by Jonny
Updated over a week ago

Step 1: Defining the project:

Here we would place the amount of sessions the Participant needs to complete alongside the amount of time each session will take.

Note: The Payment information is at your discretion as the recruiter.

Step 2: Define Participant Location

We ask the Participant early for their country of residence. This includes logic to reject the Participant if they are not within a “Tier 1” country (US, UK, IRE, CA).

We would also install webhooks to pull this information into our Screener Response document automatically

Step 3: Playtest Details

In this section, we define what is expected of the Participant - we ask for 3 simple agreements in order to be rewarded:

  1. The Participant must submit all sessions by our deadline

  2. The Participant must begin within 24 hours of receiving their link

  3. The Participant must use headphones to participate.

Step 4: Hardware & Internet Speed Check

Here we ask for the Participant to identify their hardware to ensure they will be able to run the game they will be testing. We provide a hyperlink to a broadband speed checker in the first question.

NOTE: We would change this based on the customer expectation.

However we would keep a baseline “minimum” spec if the customer has not defined a specification.

  1. When running PC Tests:

    1. I5 Processor or equivalent

    2. Nvidia 1060 or equivalent

    3. 6GB RAM

    4. 50GB Storage

  2. When running Android tests:

    1. Android 11 or above

    2. 4GB RAM

    3. 50GB Storage

We would also install webhooks to pull this information into a Google Sheet automatically

Step 5: Capturing Participant Profiling

Here we begin to capture Participant profiling information for the purposes of creating an identity of the specific Participant.

  • We do not include logic here as default, but if the customer were to request a specific time investment, we would include rejection logics here

  • Cheat Logics: We would stop Participants from answering affirmatively and disqualify anyone who answers 30+ hours to every option.

Examples of Profiling Questions:

  • What input method will you be using in this study? (Xbox Controller, KB&M)

  • What other indie titles are you currently playing? (Open Question)

  • What other narrative driven titles are you currently playing? (Open Question)

  • Do you play with 2,3 or 4 fingers? (Android Playing style)

  • what other puzzle games are you playing or have played within the last 6-12 months

  • What other steam games have you played within the last 12 months

    • What is your experience level with these games?

  • What other platforms do you play on? (e.g. Playstation, Xbox)

Step 6: Profiling Continued

A key aspect of our screening process - here we capture the customers genre preference.

  • We randomize the genres on most screeners - splicing in the required genres for the project

  • We have included a list of Genres in a google sheet here

  • We would also include examples of the games involved in this genre, to ensure the Participant understands

  • We include logic here to progress or reject Participants based on their selections

  • Cheat Logics: Any Participants that answer “I Love them” to all answers will be disqualified

  • We would also install webhooks to pull this information into a Google Sheet automatically

  • We include the same principles when querying games, randomizing the games list to ensure Participants do not familiarize themselves with our screener

  • We then splice in the games relevant to the recruitment spec, qualifying or disqualifying Participants based on their selections

  • Cheat Logics: Any Participants that answer “Played in the last month” to all answers will be disqualified

Step 7: Non Disclosure Agreement

Here we explain the NDA at a base level to ensure the Participant understands what is expected of them.

  • This will be built upon with VideoAsks/Adobe Signs etc, if required by the test security level.

  • Participants must tick every option to proceed.

Step 8: Capturing Participant Information

We capture all Participants identifiable information here:

  • Some logics may be included here to exclude Participants based on their gender, however this can be controlled via targeting demographics with invites.

  • We use webhooks to import this information into a Google Sheet upon submission.

  • Participants can be identified by their email address if an instance of repeat Forename appears.

Step 9: Installing Webhooks

Webhooks are automated messages sent from apps when something happens. They have a message—or payload—and are sent to a unique URL—essentially the app's phone number or address.

  • We use these features to move successful participants to our test.

  • If an applicant is fully successful in completing the screener, we use a URL redirect action to redirect participants to the project. This would be the test invite link.

  • We use the google spreadsheet action to automatically update our spreadsheets with Participant information that they have provided.

  • Most modern Survey Tools will include this functionality in some capacity

  • Information on how we do this is below

Step 10: Automating the implementation of information into a spreadsheet

  • This spreadsheet integration allows us to enter fields that we wish to update our Screener response document with

  • Doing this completely removes a task from us, as we no longer need to update the document as we get more applicants

  • We can handpick fields from the screener to be added automatically and present us with all relevant information to the customer recruit

  • We input the field we wish to pull into the Google Sheet, then assign a Column Name for it to be represented by.

  • Most typically, this is the following information:

    • Participant Demographics

    • Participant hardware (internet speed, PC/Phone spec)

    • Participant Genre preferences

    • Participant Profiling Information

You should now be able to use our template to create a screener that gets the audience you need for your test! If you have any questions, contact, or click the bubble at the bottom of the page and a member of our team will be happy to help!

Did this answer your question?