Engagement
What we collect, whom we speak with, and what the report contains.
This page is the working shape of a Release Readiness Review. Hotfix gates use a shorter list. Cadence audits look backward across versions instead of at a candidate build.
Evidence we usually ask for
Release notes for the candidate version, including features pulled after the last planning meeting. Crash extracts for current production and for the candidate, cut by screen if you have that cut. The staged rollout plan with percentages and — this is the part often missing — the named person who can halt the next step.
The support rota for the first 72 hours after launch, including public holidays in Malaysia. Draft store listing copy and questionnaire answers in every language you claim. Known defects you are already willing to ship, written as user-facing limitations rather than ticket IDs. Rollback steps, marked rehearsed or untested.
If a document does not exist, say so. A missing artefact becomes a finding. A late artefact slipped in after the draft is issued may not make the final PDF.
People we need in the room, or on the call
A release owner who can speak for the freeze date. One support or operations lead who will take the first tickets. Optional: the person who owns listing copy. We do not need the whole engineering group. Large meetings produce restated test summaries.
What the PDF contains
A dated recommendation: ship, hold, or ship with named conditions. A blockers list. A limitations list intended for the launch note. Unanswered questions that were still open at freeze. Citations to the packet or the interview. A short appendix for crash cuts if they exist; we do not lead with a chart.
You may correct facts in the draft. You may not ask us to delete a finding because it will be awkward in the meeting. If a fact was wrong, we change it. If a fact is merely unwelcome, it stays.
A typical calendar
Days 1–2
Intake confirmed. Evidence list sent. You upload what you have. We record gaps instead of waiting for a perfect folder.
Days 3–5
Reading and the two interviews. If we are in Kuala Lumpur together, this is when we come to Taman Supreme or to you.
Days 6–7
Draft for factual correction. Twenty-four hours is the usual window. Then the final PDF.
Day 8
Walkthrough with the go/no-go room. If you want a separate stakeholder briefing, that is booked as its own half-day.
If this calendar no longer fits your freeze, write with the date and we will say so plainly.