Process Owner Acceptance: Make the Handover Stick Long After the Project Closes

Process Owner Acceptance does one thing. It documents the process owner's formal acceptance of the improved process and its ongoing control responsibilities. That is the whole job.

The tool sits in the Sustain phase of RDMAICS. By the time you reach it, the improvement has been designed, tested and controlled. The project team is about to step back. The question that matters now is not whether the process works. It is who owns it on Monday, and whether that person has said so in writing against specific criteria.

Use it at the point of handover, when the control plan is live and the training is done. Use it again if ownership changes hands. A new owner inheriting an undocumented acceptance is one of the most reliable ways for a gain to quietly disappear.

Everything below is built on the sample data that ships with the tool. The case is fictional. It is there so you can see the shape of a completed record before you build your own.

The scenario is an accounts payable process that has been through an improvement cycle. The named owner is the AP Manager, recorded with the role of Process Owner. Five acceptance criteria are listed. Each has evidence attached and each is signed off on the same date, 2025-06-02.

Five criteria is a sensible number. They cover performance, control, documentation, capability and responsibility. Between them they answer the question a steering group will ask six months later: was this actually handed over, or did the project team simply stop attending the meeting.

The table has six columns. Acceptance Criterion, Evidence, Accepted By, Role, Date and Signature or Sign-off. Four of those are marked as required. Evidence and Role are not, but leaving them blank weakens the record considerably.

In the sample, each criterion is paired with a specific artefact rather than a general assurance. Performance to target points to a 30/60/90 review. Controls point to a control plan and SPC. Documentation points to SOPs v2.0. Training points to training records. Ongoing responsibility points to a handover document.

That pairing is the discipline the tool enforces. A criterion without evidence is an opinion. A criterion with a named, locatable artefact is something a successor can go and read.

The result panel summarises the table into a small set of figures. Criteria: 5. Signed off: 5 of 5. Pending or rejected: 0. Accepted by: AP Manager (Process Owner). Date: 2025-06-02. The summary line states that all 5 criteria were signed off by the AP Manager on that date.

Below the summary, each criterion is restated as its own card with its status, its evidence location, the date, the name and the role. So Process performs to target shows Signed, with evidence of the 30/60/90 review. Controls in place shows Signed, with the control plan and SPC. The same pattern repeats for documentation, training and ongoing responsibility.

The tool also carries a plain note worth reading twice. A recorded approval is an operational confirmation, not a digital signature. The record tells you that an acceptance was captured. It does not carry the legal weight of a signed instrument.

An AI review is available alongside the result. It explains what the pattern of sign-offs means in context. Treat it as a second reading, not as the decision itself.

A completed acceptance record changes the conversation at three separate moments.

At closure, it is the evidence that the project can stand down. With 5 of 5 signed and 0 pending, the team has nothing left to hold. If two criteria were pending, the honest answer would be that closure is premature and the remaining items need owners and dates.

At review, it is the checklist. The five criteria in the sample are exactly the five things to re-test at a sustain review. Is the process still performing to target. Are the controls still being run. Are the SOPs still current. Has the team changed since the training records were signed. Does the owner still accept the responsibility.

At handover of ownership, it is the briefing pack. A new manager can read the five criteria and the five pieces of evidence and understand what they are inheriting within an hour.

Acceptance decays quietly. Nobody announces it. The record gives you a baseline against which decay becomes visible, provided you go back and look.

Watch for evidence that has gone stale. SOPs v2.0 is a specific version. If the process has changed twice since and the documentation still reads v2.0, the documentation criterion is no longer satisfied even though the record says Signed. The same applies to training records that predate half the current team.

Watch for the control artefacts falling out of use. The sample points to a control plan and SPC. If the charts are no longer being reviewed, or the control plan has not been opened since the sign-off date, the controls criterion is accepted on paper and abandoned in practice.

Watch for ownership drift. The record names the AP Manager as Process Owner. If that role has changed hands and no new acceptance has been captured, nobody currently owns the five responsibilities. That is the single most common failure, and it is also the easiest to fix. Run the tool again with the new owner.

Most problems with this tool come from treating it as paperwork rather than as a decision record.

The first mistake is vague criteria. Something like the process is working cannot be tested later. Process performs to target can, because there is a target and a review to check it against.

The second mistake is signing everything on one date without actually checking each item. The sample does show a single date across all five rows, which is normal for a handover meeting. The risk is that the meeting becomes a formality and the evidence is never opened.

The third mistake is recording acceptance from the wrong person. The role column exists for a reason. A sponsor or a project lead signing on behalf of the owner produces a record with no operational force. The fourth is never revisiting it. A record created once and never reopened tells you about June, not about today.

Process Owner Acceptance records a commitment. It does not create one, and it does not verify one.

It will not tell you whether the process is actually performing. The sample shows Process performs to target as Signed, with a 30/60/90 review as evidence. The tool has not read that review. It has recorded that someone said the review supports the claim. Performance belongs to your control charts and your measurement system, not here.

It will not check that the evidence exists. Evidence fields are free text. If the control plan is a file nobody can find, the record still reads Signed.

It is not a digital signature, as the tool itself states. It is an operational confirmation. If you need legal weight, you need a separate instrument.

It will not alert you when acceptance lapses. There is no decay built into the figures. All 5 of 5 will keep reading 5 of 5 a year from now, regardless of what has happened to the process. The discipline of reopening the record at each sustain review is yours to supply. The tool gives you the baseline. It does not watch it for you.