Approach · Governance
Engagement governance.
The decision rights, cadence, change control and reporting that sit underneath every commercial model.
The model behind the model.
An engagement model describes how work is scoped and paid for. It does not describe how decisions are made, how change is controlled or how the client knows whether the engagement is healthy. Those are governance questions.
NexPath makes governance explicit for every engagement, regardless of size. The structure is kept light, but it has clear decision rights, a reporting cadence and an escalation path.
This page describes the mechanics that sit underneath the commercial model. For the commercial options themselves, see the services engagement models page.
Who decides what.
Ambiguous decision rights are a delivery risk. We agree the roles below at the start and record any delegation.
| Decision | Client | NexPath |
|---|---|---|
| Business priority and scope | Owns and decides | Advises on impact and sequence |
| Architecture and technical standards | Approves within the agreed governance | Recommends and owns the technical design |
| Acceptance of deliverables | Owns, against agreed criteria | Demonstrates and provides evidence |
| Change to scope or schedule | Approves | Assesses and documents the consequence |
| Operational readiness | Confirms with the operating owner | Prepares, tests and evidences |
| Security and privacy exceptions | Owns the risk decision | Provides the assessment and options |
If a decision owner is unavailable, the engagement pauses at that decision rather than assuming. A recorded assumption is better than an unrecorded guess, but neither replaces a real decision.
The rhythm of a healthy engagement.
The cadence is designed to surface issues while they are still small and to keep the client close to the work without micromanaging it.
Delivery review
What was completed, what is next, what is blocked and what decision is required. Demonstrated in the working environment where possible.
Scope and risk review
A focused review of assumptions, dependencies, change requests and the risk register. Attended by the decision owner or a delegated representative.
Commercial review
Progress against milestones, forecast to complete, invoice status and any commercial issue that needs resolution.
Architecture and quality gate
A formal review at the end of discovery, architecture and each major release. The gate has defined criteria and a recorded outcome.
Change is normal. Unmanaged change is not.
Every engagement experiences change: a new requirement, a discovered dependency, a regulatory shift or a commercial constraint. The question is whether the effect of change is understood before it is absorbed.
A change request records what is changing, why, the impact on scope, schedule, cost and risk, and the decision. Small changes can be handled through the weekly review; significant changes require a written variation.
We do not use change control to punish the client for learning. Discovery often reveals that the original scope was incomplete. We use it to keep the plan honest and to make sure the people funding the work can see the consequence.
What a useful status report contains.
- Delivered since the last report, with evidence.
- Planned for the next period, with dependencies.
- Decisions required and the consequence of delay.
- Risks and issues, with owner and next action.
- Scope, schedule and cost position against the agreed baseline.
- Changes approved since the last report.
A report that omits decisions and risks is a summary of activity, not a status report.
Governance questions clients ask.
Do we need a steering committee?
Only if the engagement is part of a larger programme or requires cross-functional decisions. For most engagements, a decision owner and a weekly review are sufficient.
How quickly can a change be approved?
Small changes can be approved at the weekly review. Significant changes require a written assessment and a decision from the nominated owner. We aim to turn around an impact assessment within two business days.
What if we disagree on acceptance?
We return to the acceptance criteria agreed before build. If the criteria are ambiguous, we resolve the ambiguity in writing before continuing. The goal is a shared definition of done, not a negotiation at the end.
Can you report into our programme office?
Yes. We can align to existing reporting templates and governance forums, provided they do not create a parallel decision structure.
What governance looks like in a small engagement.
A small engagement does not need a steering committee. It needs a decision owner, a weekly review and a written record. The client owner approves scope and acceptance; NexPath owns the technical design and delivery; the review examines what was delivered, what is next and what decision is required.
If a dependency is late, the review records the effect on the plan. If a requirement changes, the change is assessed against the agreed scope and accepted or rejected by the owner. If a risk emerges, it is added to the register with an owner and a next action.
The same model scales to a larger program by adding a program forum and a stage gate, not by creating a parallel reporting structure. Governance should make the decision path shorter and clearer, not longer.
Need governance that helps delivery rather than slows it?
Tell us about the programme and the decision structure. We will propose a model that fits.