A checkpoint checklist for percentage-based rollouts

Staged rollouts give you more than one chance to notice harm, but only if someone asks consistent questions at each gate. Here is the checklist we use with release managers in Shah Alam and remote teams across ASEAN.

At 5–10% Confirm crash-free sessions against the prior build for the same OS mix. Scan support for new phrases that match the release notes. Check that the adoption curve is moving — a stuck gate is not a clean signal.

At 25–40% Look at day-1 retention for the upgrade cohort only. Review the conversion step tied to the change. If feature flags still hide the new path for some users, say so in the note; mixed exposure muddies release impact measurement after version updates.

Near full population Re-run the original baseline comparison. Document confounders. Decide whether a fix release is required before marketing leans on the new version in campaigns.

Write the answers in sentences, not only screenshots. Future you will thank present you when the next version ships under time pressure.