The audit process, step by step

Studios often ask what happens between “we should talk” and “here is the brief.” This page is the working answer for our flagship Engine Performance Audit. Sibling engagements borrow the same bones with shorter cycles.

1. Briefing and scope lock

   We confirm your milestone, device priority list, known complaint themes, and whether thermal captures are in play. You leave with a written scope and deposit invoice when applicable.

2. Access and glossary alignment

   Build links, analytics permissions, and event naming are settled before the analysis clock starts. Missing access is the most common reason audits slip a day.

3. Session sampling and hitch tagging

   We review instrumented sessions across the agreed device bands, annotate hitch clusters, and cross-check against depth bands when session mapping is also in scope.

4. Findings brief

   You receive a ranked brief that separates player-visible issues from lower-reach noise, with uncertainty called out where evidence is thin.

5. Readout and follow-up window

   A ninety-minute readout with your leads, then five days of follow-up questions. Owners for next observations are named in the room whenever possible.

What you should prepare

• Playable build or closed track link
• Target frame budget and store markets that matter this quarter
• Three leadership questions you expect on day three of launch or after the next patch

Natural next actions

If this process matches your milestone, open the Engine Performance Audit brief or request a briefing with your device list attached.