Project Delivery · Project Control Methods
Directing a Project Through Decision Gates
Project direction is a sequence of investment and authority decisions. The governing body authorises initiation, the project, each stage, exception plans and closure; gives advice when requested; tests continued justification and risk; and delegates daily management through tolerances. Effective direction intervenes at decisions and exceptions, not in every operational detail.
Executive summary
What this guide enables
Project direction is a sequence of investment and authority decisions. The governing body authorises initiation, the project, each stage, exception plans and closure; gives advice when requested; tests continued justification and risk; and delegates daily management through tolerances. Effective direction intervenes at decisions and exceptions, not in every operational detail.
Learning outcomes
- Explain the purpose and lifecycle position of directing a project through decision gates.
- Recognise the entry triggers, control evidence and completion conditions.
- Assign activities and decisions to the correct governance, management and delivery roles.
- Tailor the process without weakening accountability, product focus or exception control.
Control guidance
Purpose and lifecycle position
The purpose is to enable the governing body to be accountable for project success by making key decisions, exercising overall control and delegating day-to-day management to the project manager. It creates an auditable chain of authority while protecting senior time through stage and exception governance.
Lifecycle position: This process begins when startup requests authority to initiate and continues across every management stage until closure is authorised. Direction runs across the lifecycle rather than as a single phase. It receives initiation, stage, exception, advice and closure requests from project management and communicates decisions to both the project and the commissioning authority.
Control depends on the resulting decision and evidence, not on reproducing a particular flowchart. The process begins on a recognised trigger, uses current controlled inputs and ends with an explicit status, product, authorisation or request.
Control guidance
Entry triggers and prerequisites
Treat the trigger as the reason to act and the prerequisite as evidence needed to act safely. Confirm authority, applicable tolerance, status date and current product or plan versions; expose missing inputs rather than silently assuming them.
Initiation request
Startup presents a project brief and initiation-stage plan.
Project authorisation request
Initiation presents the complete project baseline and robust business case.
Stage or exception request
A stage boundary or forecast breach requires renewed authority.
Advice or closure request
The project manager needs direction or recommends planned or premature closure.
Control guidance
Activity sequence
Activities may overlap or be combined, but each outcome must remain visible: what was considered, who acted or decided, and which authorised position now applies.
- 1
Authorise initiation
Review the project brief and initiation-stage plan; approve only the limited effort needed to create a decision-ready project baseline.
- 2
Authorise the project
Assess justification, products, plan, risk, approaches, governance, resources and assurance before committing to delivery.
- 3
Authorise a stage or exception plan
Review current performance, project forecast, updated business case, risk and the detailed next or replacement plan.
- 4
Give ongoing direction
Respond to advice requests, major issues and external events without bypassing the project manager's delegated daily authority.
- 5
Authorise closure
Confirm acceptance, objective status, operational handover, residual actions, benefit reviews and project evaluation before closing authority.
- 6
Communicate upward and outward
Notify the commissioning authority of major decisions, exceptions, closure and any matter outside project tolerance.
Control guidance
Management products and evidence
The record may be a document, workflow item, database entry or integrated view. Give every item a purpose, owner, status, update trigger and audience; protect baselines from silent change and ensure reports trace back to source evidence.
| Management product or evidence | Control purpose |
|---|---|
| Initiation authorisation | Releases the initiation-stage plan and its resources. |
| Project authorisation | Approves the project baseline and first delivery commitment. |
| Stage authorisation | Sets project-manager authority and tolerance for one stage. |
| Exception-plan decision | Approves, modifies or rejects a replacement plan. |
| Advice and direction record | Clarifies governing decisions outside routine stage authorisation. |
| Closure authorisation | Ends the temporary project authority and notifies the commissioning level. |
Control guidance
Roles, decision rights and assurance
Keep direction, day-to-day management, product delivery and independent challenge distinguishable. If compatible duties are combined, map responsibilities and add an independent decision or review wherever self-authorisation, self-acceptance or self-assurance would otherwise result.
| Role or level | Core responsibility | Decision or evidence |
|---|---|---|
| Commissioning authority | Sets mandate and project tolerance; receives major escalation | Authorises matters outside project authority |
| Business lead | Owns project justification and overall accountability | Leads governing decisions |
| User representative | Protects need, acceptance and benefits | Advises and decides from the user perspective |
| Supplier representative | Protects feasibility, capability and technical integrity | Advises and decides from the supplier perspective |
| Project manager | Provides evidence, requests authority and executes decisions | Manages within stage tolerance |
| Project assurance | Independently challenges evidence and control | Advises governing decisions |
Control guidance
Interfaces and control logic
Map incoming evidence, outgoing authority and response deadlines so products or decisions do not stall between roles. Forecast breaches move to the tolerance-setting authority; baseline impacts follow change control; weakened justification returns to the accountable business authority.
- The governing body sets direction and tolerance; it should not assign routine work directly to delivery teams.
- Every authorisation should identify the plan, version, tolerance, conditions and decision owner.
- Advice does not silently change a baseline; required changes follow issue and configuration control.
- An exception is decided by the authority that set the exceeded tolerance or escalated higher when required.
| Control question | Evidence to inspect | Decision or response |
|---|---|---|
| Is the input authoritative? | Version, status, owner, approval and data date | Use, clarify or reject the input |
| Is action within delegated authority? | Plan, tolerance, budget, role and external constraints | Act locally or escalate |
| Has the activity produced a usable output? | Defined completion, assurance, decision and conditions | Pass forward or return for action |
| Has the overall forecast changed? | Integrated impact and remaining-work evidence | Update plans, business case, risks and reports |
Control guidance
Tailoring the process
A small project may use one accountable business lead supported by named user, supplier and independent reviewers, with decisions recorded outside formal meetings. A complex project may use scheduled gates, specialist assurance and reserved decision sessions. Direction can align with portfolio, contract or regulatory gates when the project decision purpose and authority remain explicit.
Record the selected form, role mapping and evidence route in the initiation baseline. Revisit it when risk, suppliers, obligations, pace or decision lead time changes; tailoring must preserve purpose and authority even when format and frequency change.
Tailoring and readiness check
- The trigger and decision authority are explicit
- Inputs are current, approved where required and linked to their source
- Products and activities have one accountable owner
- Forecast impact covers time, cost, quality, scope, benefits and risk
- Issues, decisions and assumptions are recorded at the appropriate level
- Interfaces with the preceding and following processes are controlled
- Tailoring preserves the process purpose and required evidence
- The completion decision and any conditions have a traceable record
Control guidance
Worked application
Keeping governance out of daily micromanagement
Situation: A governing member begins directing individual team members after seeing a minor schedule variance, even though the current forecast remains within stage tolerance.
- The project manager confirms the authorised stage plan, tolerance and corrective action already in progress.
- The business lead redirects operational questions through the project manager and asks assurance to check whether control evidence is reliable.
- Normal highlight reporting shows the recovery forecast and a decision trigger if conditions deteriorate.
- Governance reserves intervention for a forecast exception or a requested decision, preserving clear accountability for delivery management.
Control outcome: Direction gains confidence without creating conflicting instructions or removing the project manager's responsibility.
Control guidance
Failure modes, recovery and common questions
| Failure mode | Consequence | Control response |
|---|---|---|
| Rubber-stamp gates | Investment proceeds without challenge | Require current case, risk, product and plan evidence with assurance input |
| Micromanagement | Authority and accountability become confused | Use tolerance and route delivery instruction through the project manager |
| Unavailable decision-makers | Exceptions and commitments stall | Set response times, deputies and reserved decision capacity |
| Verbal decisions | Conditions and authority cannot be traced | Record decision, basis, plan version, tolerance and actions |
Must the governing body meet regularly?
It needs timely decisions and oversight. Reports can replace meetings when no decision is required.
Can governance change stage tolerance?
Yes within project authority, with impact understood and the revised boundary recorded.
Who gives daily instructions?
The project manager through agreed work packages and delivery interfaces, not individual governing members.
What goes to the commissioning authority?
Matters outside project tolerance, required strategic decisions, major status and closure notification.