Definition
A readiness gate is a go-live check that confirms the work is built. The product launch playbook describes readiness gates as the questions that must have a yes before launch, written at kick-off, each with a named owner and reviewed at every stand-up as the date approaches. Its typical gates cover the product, locked messaging, built and checked assets, trained sales and support teams, tested tracking, paid campaigns through platform review, and approved claims where approval is needed.
The gate is the question and its pass condition, not the meeting. A go or no-go meeting is where the gates are read together and a decision is taken, but each gate exists from the start of the work and shapes it. The launch playbook's point is that a gate set the week before launch only documents what already happened, while one set at kick-off changes what gets built.
Readiness criteria versus performance criteria
The phase-gate reviews framework draws the line that defines the term. Readiness criteria ask whether the work is built: tracking, pages, stock, support, legal review. Performance criteria ask whether the market responded: sign-ups, costs, retention against a stated threshold. A readiness gate is therefore binary and internal, and can be passed by effort; a performance gate can only be passed by customers.
Both are needed, and confusing them is costly in either direction. The framework warns that a gate checking only readiness approves a launch that is well built and unwanted. The opposite error, treating a performance question as a readiness item, turns a hope into a box to tick. In a phased plan, the readiness gate usually sits just before go-live, while the performance gates sit at the end of each phase, judged on evidence written in advance.
In practice: launches, new markets and peak trading
Three playbooks use the gate in the same way, with different contents.
- Product launches. The launch owner hears from each gate owner, who reports pass, fail or at risk, and makes the call. The launch playbook allows three honest outcomes when a gate fails: delay, launch with reduced scope, or launch with a named risk and a mitigation, with the choice written down.
- New markets. The international market entry playbook ends its build phase with a go-live gate: the localised site and offer, search, the channel mix, consent, reporting and support in the market's language and hours, each signed by its owner before the market launch lead decides.
- Peaks and sales. The peak season trading playbook puts a readiness gate after the build, the service brief and the change freeze: every team's checks done and tracking verified before the promotion goes live, with the trading lead deciding and the decision recorded.
The go-to-market plan template records the gates at kick-off alongside the segment, offer and channel sequence, so that the plan and its go-live checks are agreed together.
An e-bike retailer delays its spring launch by a week
Thrumweald Cycles planned to launch a new folding e-bike on a Monday in March, with a £14,000 paid social budget and an email to 22,000 subscribers. Its kick-off set 6 readiness gates with owners. At the go or no-go meeting on the Thursday before, 5 were green: product pages, ads through review, tracking tested, stock of 340 bikes in the warehouse, and claims approved. The support gate was red: the service team had not been trained on the new battery-removal procedure, and its help article was still in draft. The launch owner delayed by 7 days rather than launch with a named risk. The brief and the article were finished on the Tuesday, and the launch went ahead the following Monday.
Related terms
A Go-to-Market StrategyThe plan for how a product or offer reaches and wins its target customers. strategy sets what is launched, to whom and through which channels; the readiness gates check that the parts of it are built before the date. A Change FreezeA set period around a peak when changes that are hard to reverse are stopped while routine, reversible work continues through an agreed route. usually follows a peak's build phase and comes before its readiness gate, so the checked work stays as it was checked. A Decision RuleA rule written before a test starts that says which result ships the change, which leads to another round and which abandons it. plays the matching role for a test, written before launch to say what result leads to which decision. Release NotesNotes published with a product release telling the people who use it what changed, who has it and from when, written for users, not as ticket titles. are the note most smaller releases ship with instead of a campaign, the kind of item a lighter go-live check confirms is written before the release goes out.
Common confusions
- A readiness gate is a performance gate. Passing every readiness gate shows the launch is built, not that it will work; the performance question needs its own criteria.
- The gate is the go or no-go meeting. The meeting reads the gates. Gates first appear at kick-off, with owners, and are tracked throughout.
- A failed gate means the launch is cancelled. The playbooks offer delay, reduced scope or a named risk with a mitigation, and the point is that the choice is recorded.
- Everything belongs on the gate. A gate list with every task on it becomes a project plan. The gates are the conditions that would make going live a mistake if they were not met.
- Gates can be written late. Gates set in the final week describe what has already been done, and catch nothing.
