- A downloadable Build is useful, but not automatically playable or publish-ready.
- Runtime reports must match the Build they describe.
- Unknown rights, permissions, or device evidence remain unknown—not passed.
Check each evidence layer
First identify the exact Build ID and hash you intend to publish. Review the structural Build report for missing files and known blockers. In Studio, test the player loop, respawn or round transitions, rewards, and any persistence behavior; use separate multiplayer and device sessions where those claims matter. Confirm every imported asset's ownership, license, and Roblox permission state. A generated fallback is not proof that a pending asset will appear in a published Experience.
A release decision record
Record Build ID; Studio test date and result; two-player and device results if applicable; asset IDs and rights status; open issues; and the person approving publication. Mark missing evidence as pending. This page is a checklist, not automatic Roblox publishing or a certification that your current Build is ready.