Implementation is complete when the business can use and sustain the outcome.
Start with a delivery mandate
Bring the buyer business owner, supplier delivery lead, sourcing owner and relevant technical or operational leads together before work starts. Confirm the awarded scope, success measures, budget, milestones and unresolved conditions. Make the selection rationale and accepted risks available to the people who must deliver.
Name a buyer owner who can resolve dependencies and approve changes. Supplier project management does not replace buyer accountability for data, access, decisions, training or operating readiness. Agree who can accept deliverables, authorize a cutover and escalate a material delay.
Build milestones around evidence and dependencies
| Workstream | Readiness evidence | Typical dependency |
|---|---|---|
| Data and access | Approved access, validated data and agreed transfer controls. | Data owners, identity teams and security review. |
| Configuration and integration | Representative workflows and interfaces pass agreed tests. | Environment access and downstream system owners. |
| People and process | Users can perform the changed work and handle exceptions. | Training time, communications and process ownership. |
| Service transition | Support, escalation and knowledge transfer are usable. | Incumbent cooperation and retained buyer roles. |
| Acceptance | Named approver reviews results against agreed criteria. | Test data, review capacity and defect decisions. |
| Cutover | Continuity, fallback and support coverage are approved. | Scheduling, business readiness and contingency capacity. |
Sequence milestones around what must be true, not only dates on a plan. Record each dependency, its owner and the consequence if it is late. A milestone can be on schedule while the next step is blocked by an unassigned buyer action.
Separate completion, acceptance and useful operation
Agree acceptance criteria before testing begins. Use realistic volumes, ordinary tasks and exception cases. Record observed results, defects, workarounds and the owner’s decision. Distinguish technical installation from the ability to produce the business outcome.
When partial acceptance is necessary, document which outputs are accepted, what remains open, the residual risk and the deadline for resolution. Follow the actual agreement’s acceptance and payment procedures. Do not allow an informal “looks fine” message to substitute for the authorized review.
For project services, the deliverables and acceptance guide helps bound outputs. For outsourced operations, connect the service transition plan to continuity and retained responsibilities.
Control changes without freezing delivery
New evidence may justify changing scope or sequence. Record the reason, impact on cost and timing, dependencies, risks and approval before committing the changed work. Compare the proposed change with the original outcome; a convenient implementation shortcut may weaken the business case.
Track supplier and buyer delays separately, with evidence and agreed corrective action. Keep a forecast of work and cost to completion. An apparently healthy budget can conceal unfunded internal effort or a major later phase. Escalate early when the operating model is no longer achievable within the approved boundary.
Make the operating handoff explicit
- Transfer documentation, access ownership and the support and escalation model.
- Confirm the service baseline, reporting sources and responsible governance owners.
- Train the actual users and test how exceptions will be handled.
- Close or assign defects and open implementation obligations.
- Approve continuity arrangements and an executable fallback for cutover.
- Carry the commercial schedules and renewal dates into ongoing management.
Keep a limited early-life review period after go-live. Check adoption, service experience, invoice accuracy and performance against the original outcome. Use evidence from real operation to verify assumptions that a test environment could not resolve.
Close implementation against the outcome
The business owner should confirm that the delivered capability is usable, the remaining risks are understood and ongoing responsibilities have been accepted. Preserve a short lessons record: what changed from selection, which assumptions failed and what should inform the next event.
Continue into vendor management with a verified baseline, not a fresh blank scorecard.
Original buyer guidance and illustrative examples. See our editorial approach for scope, evidence standards and limitations.