01Review checkpoint
Qualification
Decision makers, requirements, budget constraints and feasibility questions.
- Qualification note · Initial risk register
MANAGED PROJECT DELIVERY
Clear responsibility from discovery to handover.
A governance-led approach for multi-phase and specialist-supported projects. Delivery capacity, responsibilities and controls are confirmed for every engagement, rather than implied by an agency label.
All scope, specialist availability, deadlines and commercial terms require project-specific confirmation.
EIGHT GATES
A project moves when its evidence is ready.
Each phase has an intended output. The precise documents and approvals are tailored to the project size.
02Review checkpoint
Discovery & feasibility
User flows, system dependencies and delivery options.
- Requirements summary · Feasibility assumptions
03Review checkpoint
Commercial agreement
Approved SOW, milestones, exclusions, responsibilities and payment terms.
- Signed contract/SOW · Milestone schedule
04Review checkpoint
Kickoff & roles
Delivery owner, communication cadence, access and change procedure.
- RACI/contact plan · Kickoff note
05Review checkpoint
Engineering & design
Version control, issue tracking, demonstrations and agreed engineering standards.
- Reviewable increments · Decision log
06Review checkpoint
QA & review
Functional checks, defect prioritisation, relevant security and performance review.
- Test checklist · Defect records
07Review checkpoint
Acceptance & handover
Client review against agreed acceptance criteria and agreed asset transfer.
- Acceptance record · Handover checklist
08Review checkpoint
Post-delivery support
Support scope, applicable response windows and ownership of ongoing costs.
- Support arrangement if contracted
PROJECT CONTROL
Define the change, then approve its impact.
A new request is evaluated against scope, effort, dependencies and the existing schedule. In-scope bug fixes remain governed by the agreed defect and warranty provisions.
SOW
Scope & acceptance
Document what is included, excluded, who approves it and how completion is judged.
- Deliverable register
- Acceptance criteria
- Client dependencies
CR
Change requests
Record scope deviations, cost and timeline effect before implementation.
- Change description
- Impact assessment
- Written approval
QA
Release readiness
Use a documented release and handover process matched to the project.
- Test evidence
- Known issues
- Access and source handover
RESOURCE MODEL
Specialists as needed, not a fictional full-time department.
Projects may require design, engineering, QA or specialist review. Exact roles, availability, contracting and data access are discussed before commitment.
Contractor and security controls
Where third-party specialists are engaged, appropriate agreements, confidentiality and intellectual property provisions, access restrictions and reviews should be established. This description is not a claim that a permanent specialist network is already staffed.
Can you guarantee a large multi-disciplinary team?
No. Named roles and confirmed capacity depend on project scope and contractual arrangements.
Does work begin before scope approval?
Development should begin after an agreed scope and commercial terms; a separate discovery engagement may come first.
Is every change request charged?
No. Work already included in the contract, agreed revisions and in-scope defect corrections must be handled under the signed terms.
Are service levels included?
Only if the specific signed engagement includes support levels and schedules.
MANAGED DELIVERY
Give the engagement a clear owner and acceptance process.
Discuss project size, stakeholders, responsibilities and the documents your procurement team requires.