A phase gate review is only as useful as the preparation behind it. When teams arrive at a gate without a clear checklist, the session becomes a status meeting rather than a go/no-go decision. In regulated industries, that matters more than most: a gate passed without proper evidence creates compliance gaps that surface months later, usually at the worst possible time.
This post sets out a practical checklist for each major gate in a regulated manufacturing or med-tech project. It draws on the stage gate model described in ISO 21502:2020 (Guidance on project management), which defines project governance as the framework of authority, accountability, and decision-making structures that direct a project. Use it as a starting point and adjust to your organisation's specific development lifecycle and regulatory environment.
Note on terminology: "Phase gate," "stage gate," and "toll gate" are used interchangeably across industries. This post uses "phase gate" throughout. The underlying principle is the same: a formal decision point where the project must satisfy defined criteria before proceeding.
In a commercial software project, a missed deliverable at a gate is an inconvenience. In a regulated manufacturing or med-tech context, it can mean incomplete design history files, unreviewed risk assessments, or verification activities that cannot be traced back to approved requirements. These gaps do not just slow down your next audit; they can void a design freeze or trigger a regulatory submission delay.
A gate checklist serves three functions:
Regardless of the number of gates in your lifecycle, every gate review should cover four areas. The specific deliverables within each area will vary by phase.
The four-area framework above applies at every gate. The items below are additions specific to common phases in regulated manufacturing and med-tech projects.
| Gate | Typical phase transition | Key additions to the core checklist |
|---|---|---|
| Gate 1 | Concept to Feasibility | Business case approved, regulatory pathway identified, initial risk assessment complete |
| Gate 2 | Feasibility to Design | User needs documented, design inputs drafted, supplier qualification plan agreed |
| Gate 3 | Design to Verification | Design freeze confirmed, design history file complete to this point, verification plan approved |
| Gate 4 | Verification to Validation | All verification protocols executed and results reviewed, design transfer plan confirmed |
| Gate 5 | Validation to Launch | Validation complete, regulatory submission filed or approved (as applicable), production readiness confirmed |
Common gap at Gate 3: Teams often arrive at the design freeze gate with unapproved design inputs or a partial design history file. This is the gate most likely to result in a conditional proceed. Build a dedicated design history file review into your Gate 3 preparation, at least two weeks before the gate date.
The project manager owns the checklist preparation. Their job is to gather evidence from the workstream leads in the week before the gate, identify gaps, and either close them or flag them to the sponsor before the meeting.
The gate board does not fill in the checklist. They use it to make the decision. If the PM presents a completed checklist with all items confirmed, the board can focus on the judgement calls: are the risks acceptable? Is the team ready? Is there anything in the phase that has not been captured?
In practice, the most effective gate reviews are those where the project manager has pre-briefed the sponsor on any amber or red items before the formal meeting. There should be no surprises at a gate.
One of the most useful habits a project manager can build is a gate readiness review held five to seven working days before the formal gate. This is an internal session with the project team, not the gate board, to work through the checklist and confirm what is done, what is in progress, and what is at risk.
Any item that is at risk at this point needs an owner and a plan to close it before the gate date. If it cannot be closed, the PM should either propose a gate delay or prepare a documented rationale for a conditional proceed.
This approach is consistent with the governance principles described in ISO 21502:2020, which emphasises that project oversight mechanisms should be applied proactively, not just at formal review points.
A gate checklist only creates an audit trail if it is stored alongside the gate minutes and the project documentation. The completed checklist, the gate decision, and any conditions attached to a conditional proceed should be stored in the project record system, version controlled, and traceable to the specific phase transition.
In a regulated environment, this is not optional. An auditor reviewing a design history file will expect to find evidence of gate decisions at each phase transition. A verbal decision that was never documented does not exist for compliance purposes.
A phase gate review (also called a stage gate review) is a structured decision point between project phases where a review board assesses whether the project has met the criteria to proceed to the next phase. In regulated industries, gate reviews also confirm that the project has produced the required documentation and evidence for compliance purposes.
A phase gate checklist should cover four areas: deliverable completeness (are all required outputs from the current phase signed off?), risk status (have open risks been assessed and mitigated?), resource readiness (are the right people and budget confirmed for the next phase?), and governance (has the gate decision been documented and authorised by the appropriate sponsor or review board?).
There is no fixed number. Most regulated manufacturing and med-tech projects use four to six gates aligned to their product development lifecycle: concept approval, feasibility sign-off, design freeze, verification, validation, and launch readiness. The number and naming should reflect the organisation's own development process and any applicable regulatory requirements.
The gate review board typically includes the project sponsor, functional leads (engineering, quality, regulatory, manufacturing), and the project manager. In regulated industries, a quality or regulatory representative should attend every gate to confirm documentation status. The project team presents; the board decides.
Arcturus Pro gives regulated project teams a single place to manage gate readiness, track deliverables, and record gate decisions with a full audit trail. Book a 30-minute walkthrough.
Book a Demo