How a playtest playbook is put together
Every playtest answers two separate questions. Pick one from each column, then read both playbooks.
A multi session playtest is still either open or closed. “Multi session” and “closed” answer different questions, so they are never alternatives to each other.
Run a playtest
Single session
One sitting, one survey. First impressions or a feature check.
Multi session
Players come back a few times. Watch a first impression change.
Longitudinal
Sessions spread across days. Retention and habit formation.
Survey only
Hand out a build, ask questions, record nothing.
Open to anyone with the link
Recruit through the link itself, up to a player cap.
Closed to a roster
Only the people you seed by email can join.
Screen for the right players
A questionnaire and an eligibility rule that decide who gets in.
Test a confidential build
An NDA, a closed roster, and a short retention window.
Playtest with Discord members
Require Discord identity and recruit from the server you already have.
Playtest with Steam players
Require Steam identity, hand out keys, and read back playtime signals.
Set the playtest up
Brief players and set objectives
What players read before a session, and what stays on screen during it.
Design a post-session survey
Ask the questions that pair with what you watched.
Distribute a build
Hand players something to download and launch.
Configure gameplay recording
Screen, audio, and events, and whether a player can decline them.
Launch it
Launch a playtest
Preview, publish, share the link, announce it.
Announce a playtest in Discord
Post a rich embed with a Join button to a Discord channel.
Take a playtest offline
Unpublish, get the unused reservation back, reset the link.
Check what a playtest will cost
Reservations, refunds, top-ups, and what your plan actually caps.
See how it went
See how your playtest went
Read the results in order, from headline numbers to one player’s session.
Find where players dropped off
Who never started, who stopped partway, and who was screened out.
Read what players told you
Survey answers question by question, and across sessions.
Look up one player
One player’s sessions, answers, and recordings in one place.
Compare early and late sessions
What changed between a player’s first session and their last.
Work out what to fix next
Recordings, transcripts, highlights, and answers into a list to act on.
Generate transcripts and highlights
Turn insights on, spend credits deliberately, fill the gaps by hand.
Share a session externally
Open a session to someone outside the studio, then close it again.
Export your playtest data
Datasets, recordings, and the same data over the API.
Reviewing a session
The reference for the panel beside a recording.
Change or archive it
Change a live playtest
Work out whether you need to unpublish at all, then edit safely.
Reuse a playtest setup
Duplicate rather than rebuild, and fix up what does not travel.
Take a playtest offline
Pause it for a while without archiving anything.
Archive a finished playtest
Export the findings, reclaim the capacity, archive cleanly.
Run a survey
Run a survey
Create it, publish it, and read the responses.
Write survey questions
Build a set that answers something, before it freezes.
Welcome survey respondents
The identities to ask for, and a landing screen worth reading.
Tell respondents what happens next
Say what the answers were for, then follow through.
Share a survey link
Get it circulating, and rotate it if it travels too far.
Announce a survey in Discord
Post an embed with a Take the survey button.
Run a waitlist
Set up a waitlist
Let players sign up and qualify themselves for your roster.
Screen waitlist signups
Questions a rule can read, and the rule that decides who gets in.
Welcome waitlist signups
The identities that pay off later, and a screen that sells the spot.
Set waitlist expectations
Say what a spot means and when they will hear from you.
Share a waitlist join link
Post it broadly and let the rule do the filtering.
Announce a waitlist in Discord
Collect interest before you are ready to run anything.
Email your players
Sync your players with Mailchimp
Connect an audience, pick a direction, get the first sync running.
Turn subscribers into playtesters
A newsletter list becomes a roster you can recruit from.
Email one playtest's players
Mail exactly the people who took part, with no CSV in the middle.
Segment a campaign with player data
Target a send on playtest activity, profile answers, and Steam signals.
Your players
Build a group you can reuse
A roster you seed every future playtest from.
Sort players into groups
Filter the directory and save the selection as a roster.
Invite past players back
Seed a new playtest from one you have already run.
See who your players are
The studio-wide picture, rather than one playtest’s numbers.
Recruit with a waitlist
Publish a waitlist so players join your roster, screened on the way in.
See what players own and play on Steam
Connect Steam for ownership, playtime, and wishlist signals.
Keep Steam data fresh
Tracked apps, key rotation, and clearing a rejection.
Archive a group you are done with
Retire a roster without dropping people out of your directory.
Hand out keys
Stock a key vault
Create a vault, set its key type, and load it with keys.
Hand out game keys
Give each player a key automatically as they join a playtest.
Hand out DLC or bundle keys
Grant DLC or a bundle to players who already own the game.
Give keys away with a redeem link
A standalone claim link, with screening, outside any playtest.
Give keys to a group
Assign keys to a roster you already have, with no link to share.
Screen who gets a key
Questions between a public link and your inventory.
Check how many keys were claimed
Read the vault analytics and decide whether to restock.
Migrate your key inventory
A pile of Steam keys or codes, into vaults.
Your studio
Set up your studio
The first run: studio, game, public URL, and your first teammate.
Make it look like your game
The logo, colors, and link preview players see on every screen.
Brand the emails players get
Reply-to address, banner, and colors on player-facing email.
Decide how long to keep recordings
Choose a retention window, and export before it closes.
Pick the right plan
Read your usage, compare limits, and switch when you outgrow one.
Invite your team
Owner, Admin, and Member, and what each one can do.
Move in from another tool
Migrate to Userplay
What order to bring things over in, and what does not come over at all.
Migrate your players
An existing tester list, by CSV or over the API.
Migrate your key inventory
A pile of Steam keys or codes, into vaults.
Set up a playtest from the command line
Build a draft from the CLI, then publish it in the studio.
Automate with the API
An access key, the REST endpoints, the CLI, and exports.
CLI
Install the command line tool the migration playbooks lean on.
Next steps
Quickstart
Never run a playtest here before? Start with the fifteen-minute path.
Core concepts
The core building blocks every playbook is built from.