Use one register with the following fields:
| Field | What to record |
|---|---|
| Scope | Supplier, game IDs, domains, territories and delivery method |
| Requirement | The exact question or acceptance condition |
| Evidence | Document, clause, supplier response or test record |
| Evidence type | Documented; supplier-claimed; observed; inferred; unknown |
| Coverage and date | What was checked, when, and what remains outside the check |
| Decision | Accepted, unresolved, excluded or rejected |
| Accountability | Owner, next action and review date |
A document can record a supplier assertion without independently proving it. Preserve that distinction. Likewise, an observed successful launch is technical evidence, not permission evidence.
For the pilot, define these proposed measures before testing:
- Observed launch success: successful ready states divided by recorded launch attempts, with location denials, technical failures, timeouts and unknown outcomes reported separately.
- Game-ready time: elapsed time from the defined launch action to the defined ready state. Report timing for successful launches alongside failure counts; do not discard failed attempts from the assessment.
- Cost per usable game-month: total modelled operating cost divided by the sum of evidenced usable games in each month. Label forecast coverage as an assumption; if the denominator is zero or unsupported, report the metric as undefined or not yet calculable.
These are proposed procurement measures, not industry performance standards. Set acceptance thresholds from your requirements and testing plan, rather than inventing a universal load-time target or acceptable failure rate.
What should the final result card say?
- Scope assessed: supplier, domains, catalogue and audience.
- Score and band: __ / 45; __.
- Override status: scope hold, rights/risk hold, technical/release hold, or none identified by this self-assessment.
- Three priority gaps: each with an owner and evidence needed.
- Next decision: clarify, compare, test, renegotiate or conduct release review.
- Reassessment trigger: a material change to rights, territory, game build, data flow, integration or supplier terms.
The goal is not a perfect score. It is a decision supported by evidence you can retrieve, explain and update.