Player Retention Audit Checklist

🖨️ Print / Save as PDF

Work through each section against your current build, ideally with a fresh playtester who hasn't seen the game before — self-audits catch less because you already know where everything is. Where a checklist item asks about your data, pull your own D1 (day-1 return rate), D7 (day-7 return rate), and D30 (day-30 return rate) numbers and compare them against your own past cohorts, not a generic benchmark. For deeper background on any single section, see the full resource library.

Onboarding Pacing

• Most core mechanics are not all unlocked or explained within the first session — some novelty is deliberately held back for day 2 and beyond
• A first-time player can identify at least one thing they haven't tried yet by the end of session one
• Time-to-first-meaningful-reward has been measured directly (with a stopwatch or session logs), not estimated from memory
• The tutorial teaches systems in the order players actually need them, not the order that's easiest to script
• Session length in the first few days has been checked against your intended pacing — sessions that run much longer or shorter than planned usually signal a pacing mismatch, not just player preference

Early Economy Check

• A fresh playtester can name at least one currency or resource they're actively saving up for by day 3
• Early-game currency income has been modeled far enough forward to confirm the shop or unlock list isn't already "empty" (nothing left the player wants) by day 5-7
• Early-game costs have been checked against early-game income to confirm players aren't hitting a hard grind wall before they've built any attachment to the game
• No single early source (login bonus, tutorial reward, first-time offer) accidentally floods the player with more currency than the first week of content can absorb
• At least one sink exists that stays relevant past the first week, so the early economy doesn't get "solved" the moment the tutorial ends

Illustrative example Imagine a hypothetical puzzle game that awards a generous currency bonus for finishing the tutorial. Players immediately buy every early booster on offer, the shop looks "empty" of anything worth wanting by day 4, and there's no economic pull to open the app again — even though the puzzles themselves are fine. A pass through the Early Economy Check section above, done before launch, would have caught the mismatch between the tutorial reward and the shop's pacing.

Goal Clarity After the Tutorial

• A player five days in can answer, without hesitation, what they're currently working toward
• At least one visible mid-term goal (a milestone, an upcoming unlock, a build to chase) exists beyond whatever the tutorial explicitly assigned
• Progress toward that mid-term goal is shown somewhere on screen, not just tracked invisibly on the backend
• The gap between "tutorial ends" and "first self-directed goal appears" has been measured in minutes or sessions, not assumed to be instant
• Players who go off the critical path (skip a suggested quest, ignore a prompt) still have a legible next step available to them

Daily-Return Loop

• There is a specific, nameable reason the game is different tomorrow than it is right now (a reset resource, a login curve, a rotating objective)
• That reason is visible to the player before they close the app today, not something they'd only discover by opening it again tomorrow
• The daily loop doesn't rely purely on loss-aversion (streak breaks, expiring rewards) without also offering something to look forward to
• Your own D1/D7/D30 numbers have been compared against your prior releases to see whether the return loop is holding steady, improving, or eroding release over release
• The daily loop has been checked against comparable games you can actually observe in your genre, rather than against an unverified "industry average" figure

What to Do With the Results

A checklist tells you where to look, not automatically what to change — the fix for a failed onboarding item and the fix for a failed economy item are entirely different disciplines. The LiveOps economy best practices guide and the LiveOps economy checklist go deeper on the economy and return-loop side once you've narrowed down which section is flagging the most problems.