Design gateways: defining what ready really means
Admin · 22 October 2026
Illustrative image. Photo by Cherrydeck on Unsplash. Unsplash License.
A design gateway should establish whether the project has enough dependable information for a defined next step. It loses value when it becomes a calendar event at which the team declares a stage complete despite unresolved requirements and interfaces. The useful question is not whether every possible detail exists. It is whether the evidence supports the commitment being requested and whether the remaining uncertainty has an accountable route to resolution.
For clients and design managers, the first task is to define the gateway’s purpose. This article concerns internal project governance. It does not describe or replace any statutory approval process that may apply to a particular building. The project’s advisers should identify those requirements separately and ensure the programme and responsibilities reflect them.
Name the commitment the gateway controls
Identify what approval would allow the team to do. It might release a tender package, authorise a further design phase or support a procurement decision. These commitments need different evidence. A generic stage-complete declaration can obscure the distinction and encourage participants to assume that approval covers more than the meeting actually considered.
Write a concise decision statement and identify the authority required. The sponsor, operator and technical reviewers may have different roles. Attendance does not necessarily establish permission to approve a commitment. Clarify who advises, who reviews particular matters and who makes the decision under the project’s actual governance and contractual arrangements.
Agree readiness criteria in advance
Define what the team must demonstrate before the gateway, rather than invent the criteria after reviewing the submission. Link them to the brief, scope and intended use of the information. Criteria should be specific enough for participants to identify the supporting evidence. A phrase such as suitably coordinated needs explanation of the interfaces and checks relevant to the commitment.
Keep the requirements proportionate. The project may not need every final detail to authorise the next stage, but it should identify what can remain open and why. Ask the relevant specialists to establish technical maturity needs. The gateway process coordinates that evidence; it does not replace professional judgement with a generic checklist.
Prepare an identifiable evidence set
List the documents, models, assessments and decisions submitted for review, including revisions and status. Participants should know what they are assessing and which information remains outside the submission. A gateway pack that refers vaguely to the latest drawings can become difficult to interpret later when those drawings have changed.
Allow the agreed review time and make significant late information visible. If a consequential item arrives too late for proper assessment, the decision maker should understand the limitation. The scheduled meeting date is not evidence of readiness. The project may need to narrow the approval, defer it or obtain further review through the appropriate route.
Expose assumptions and unresolved matters
Identify the assumptions on which the proposed commitment depends. State their source, owner and consequence if they change. Some may be acceptable for the next step, while others could materially alter the scope or delivery basis. The gateway should make that distinction explicit rather than hide all uncertainty in a long general risk register.
Consider a hypothetical tender release that assumes a client equipment selection will fit within an agreed envelope. The project needs to understand whether that assumption is sufficiently supported for pricing and what happens if it changes. A conditional release may be appropriate under the actual arrangements, but the condition and decision owner must remain visible to the receiving team.
Review interfaces as well as disciplines
A submission can contain complete-looking discipline outputs while leaving their relationships unresolved. Ask the relevant teams to identify the interfaces consequential to the next commitment. These may concern information, physical connections or operating requirements. The readiness evidence should explain which have been assessed and which remain subject to further work.
Assign any unresolved interface to a clear owner with the required response. A shared issue still needs someone responsible for coordinating the answer, while the technical responsibilities remain with the appropriate parties. Dates should connect to the affected activity. An action simply marked later does not give the decision maker a credible management plan.
Separate review findings from approval
Technical reviewers may recommend proceeding, identify conditions or request more information. The gateway decision should record how those findings were treated. Do not assume a reviewer’s silence implies acceptance or that a comment has been resolved because a response was written. The responsible person should assess the evidence required to close the matter.
Where reviewers disagree, record the question and the route for resolving it. The decision maker needs a factual account of the consequence and advice, not a forced consensus that conceals uncertainty. Appropriate specialist or commercial input may be needed before the issue can be addressed within the project’s authority.
Make conditions actionable
If approval is conditional, state what may proceed and what remains restricted. Identify the condition, its owner, required evidence and deadline. The receiving team should be able to understand the boundary without reconstructing the meeting. A broad approval followed by a long list of unprioritised actions can leave participants with incompatible interpretations.
Track conditions through the project’s action and information processes. Confirm closure using the agreed evidence and communicate the result to affected parties. Approval of the next step does not automatically complete the work needed to implement it. The gateway should establish a controlled transition rather than become the point at which unresolved issues lose attention.
Preserve a clear decision record
Record the commitment authorised, the information considered and the principal reasoning. Keep the decision linked to the approved evidence set. The APM overview of change control provides general context for decisions affecting an approved basis. Any subsequent change should follow the project’s relevant procedures and preserve the reason for revisiting the earlier conclusion.
Use the appropriate terminology for the project’s actual agreements. An internal governance approval should not be presented as a contractual instruction or statutory consent unless the relevant process establishes that effect. Clear boundaries protect the usefulness of the record by making its purpose understandable to people outside the meeting.
Learn from the next stage
After the transition, ask whether the receiving team had the information it expected and whether gateway conditions were realistic. Late discoveries can reveal missing criteria or insufficient review time. Examine the cause rather than assume the answer is always a longer checklist. The project may need clearer ownership or a better-defined information exchange.
Update the approach for the next gateway using those findings. A successful process creates dependable decisions at the right time, with evidence proportionate to the commitment. Its practical value is a shared understanding of what is ready, what remains uncertain and who must act before the next part of the project relies on the answer.
Prepare the receiving team for the transition
Before the gateway closes, ask the people responsible for the next stage to review the proposed handover. They can identify information they need to proceed and clarify any condition that would otherwise emerge during mobilisation. This does not create a second approval route; it tests whether the intended transition is understood by the people who must carry it out.
Capture their consequential questions in the same decision and action record. If the next team is not yet appointed, identify who will preserve that context and provide it at appointment. A gateway can otherwise produce an apparently complete internal record while the receiving supplier or delivery manager starts without knowing the assumptions that justified the release.
Record who confirms that the agreed handover has occurred and where the receiving team can find the approved information.
