The project reaches the end of discovery and begins implementation because that is what the timeline shows. A stage gate should be an explicit decision about the next commitment, with an authorised person checking the evidence and conditions. Reaching a date does not itself authorise more work or expenditure.
APM's governance guidance addresses decision authority. For a small project, a proportionate gate may be a short decision record and supporting evidence. Its value comes from the choice, not the size of the meeting pack.
Photo by Vitaly Gariev on Unsplash.
Put the gate before the commitment
Identify a point where proceeding materially changes exposure: selecting a supplier, authorising configuration or committing to a release. Place the decision early enough to change course without pretending already-spent effort is reversible.
Avoid adding a gate to every minor task. Follow your organisation's actual funding, procurement, technical and operational authorities. One sponsor signature cannot replace every specialist approval.
Write a gate card
For each important point, specify:
Decision and next-stage work being authorised.
Required evidence and person validating it.
Continuing business purpose and major assumptions.
Resource, cost and operational commitments proposed.
Unresolved conditions and their consequences.
Decision-maker and authority limits.
Permitted outcomes and how they affect the plan.
Possible outcomes can include proceed, proceed within stated limits, request more evidence, replan or stop. Use outcomes that match the actual governance rather than a copied template.
A hypothetical conditional decision
A team finishes discovery for a new booking service. It has enough evidence to confirm the preferred operating design, but a supplier access question remains unresolved. The sponsor authorises a bounded preparation activity while withholding the dependent configuration commitment.
The record states exactly what may start, who resolves access and when the condition must return for review. “Approved subject to sorting the details” would leave too much room for interpretation.
If the team cannot separate the preparation from the unresolved dependency, conditional approval may not be a workable option. The gate should reveal that limitation rather than create a convenient label for proceeding anyway.
Keep evidence and authorisation distinct
A completed test or review supplies information. It does not automatically grant the authority to spend, change scope or release a service. Identify which decisions the evidence supports and who must make each one.
Likewise, approval to begin one stage is not standing permission for every later stage. Make the next decision point visible and identify the information required before reaching it.
Review the gate after using it
Ask whether it exposed a real choice, arrived at the useful time and gave the decision-maker enough evidence. If it simply rubber-stamps work already underway, change its timing or purpose. A smaller, earlier decision can be more valuable than a polished retrospective approval.
The small-team project plan keeps the stages and dependencies connected. For the connected task, read What Should a Project Sponsor Actually Decide?. If your project moves between stages without a clear commitment decision, discuss your project requirements.
