Process family

Project delivery process: governance, change, risk and closure templates

Nine templates for running a project under control: governance from charter to closure, change requests, the risk register and escalation tree, go/no-go decisions, formal closure, and two full-lifecycle delivery SOPs.

Project delivery is the set of controls that keep a project inside its agreed scope, cost and schedule and end it properly. The templates here are a group rather than a sequence: one governance backbone, the change and risk processes it calls, two decision trees for gates and escalations, a closure process, and two end-to-end delivery SOPs from engineering firms.

Project governance is the backbone the others plug into: charter, roles, baselines, status and RAID, stage gates and closure. A forecast outside tolerance goes to steering as an exception; two other steps hand off to their own charts. When a change is raised, the change request process assesses scope, schedule, cost and quality impact, approves within the project manager's tolerance or escalates to the steering group, and re-baselines. The RAID update feeds project risk management: log, assess, respond and review each risk until it closes or becomes an issue.

Two decision trees settle the judgment calls. The risk escalation decision tree decides, from written tests on exposure, tolerance and authority, whether a risk stays with its owner, goes to the project board or executive risk committee, or is raised as an incident. The go/no-go decision is the launch readiness gate: acceptance criteria, defects, dependencies, rollback, support and change window, each answered by a named role, ending in go, conditional go, pilot, no-go or abort. Project closure is where every project ends, planned or terminated: acceptance, snag list, handover, final invoicing, contract closure, lessons and sponsor sign-off.

Two SOPs draw the whole lifecycle as one chart: an instrumentation and automation solution from inquiry through engineering, FAT and commissioning to operator training, and a turnkey marine electrical project from requirements to acceptance and closeout. Both carry the gates the generic templates isolate (design approval, test before install, acceptance at handover); the IT consulting project lifecycle is the same shape from a services firm's side. The typical failure in all of them is a change taken on without a request, so the baseline stops meaning anything and closure has nothing to accept. The program such projects serve is digital transformation.