Control Phase Plan: Hold the Gain After the Project Team Moves On

The Control Phase Plan does one job. In the product's own words, it helps you plan the activities, owners, and timeline for the Control phase to lock in gains and transfer ownership.

That matters because the Control phase is where most improvement work quietly leaks away. The solution is in place. The measurements looked good during the pilot. Then the project team is pulled onto the next piece of work, and nobody owns the new way of working. Six months later the old behaviour is back.

Use this tool once your improvement is tested and you are preparing to exit. You list what still has to happen, who owns each item, and when it is due. The tool then counts what is complete, what is in progress, and what has slipped past its date. It gives you a single view of whether the handover is actually on track or only looks that way in a status meeting.

It sits in the Control phase of RDMAICS, between the Improve work and the Sustain work. Think of it as the bridge. Improve proves the change works. Control proves somebody else can run it.

The screenshots in this guide show the tool loaded with its built-in sample data. The case is fictional. It is there so you can see the shape of a finished plan before you build your own.

The scenario is an accounts payable improvement. The team has introduced OCR and auto-match controls on invoice processing. The defect rate has been the headline measure. Now the project needs to close, and the process needs to live with the AP function rather than with the improvement team.

Six activities make up the plan. They run from 5 May 2025 to 30 May 2025. That is a tight window, and deliberately so. A Control plan that stretches over months usually means the handover has no real deadline.

The activities cover the five things most Control phases need: the control plan itself, the monitoring method, the documentation, the training, and the verification. The sixth item is the tollgate review that formally hands the process to its new owner.

The input is a simple table. Each row is one activity. You give it a name, an owner, a target date, a status and a short note.

In the sample, the owners are spread across four roles rather than sitting with one person. The Black Belt holds two items: finalise the control plan for the invoice process, and verify the solution and revalidate the MSA. The Green Belt holds two: build SPC monitoring on the defect rate, and prepare the Control tollgate review. The AP Manager owns the SOP and work instruction update. HR and L and D own training the AP team.

That spread is the point. The Black Belt owns the technical verification. The line manager owns the documentation that the line will have to live with. Training sits with the function that runs training. If every row in your plan names the project lead, you have not transferred anything.

The notes column is short and specific. OCR and auto-match controls. A p-chart on DPMO. Seven SOPs revised. Two sessions. A Gauge R and R repeat. Handover to owner. Each note tells the owner what finished looks like without needing a separate document.

The result panel converts the table into counts you can act on. For the sample data it reports 6 activities, 0 of 6 complete, 1 in progress, and 6 past their date.

It then breaks the list by status: In Progress 1, Not Started 5. The one activity in progress is finalising the control plan for the invoice process, due 5 May 2025 and owned by the Black Belt. The other five have not been started.

The summary also names the earliest overdue items directly: finalise the control plan for the invoice process at 5 May 2025, build SPC monitoring on the defect rate at 10 May 2025, update SOPs and work instructions at 14 May 2025, and more. It tells you the target dates run from 5 May 2025 to 30 May 2025.

Each activity also appears as its own card with date, owner and status, so you can scan the plan without reading the table row by row. A built-in AI review is available to explain what the result means in context.

A plan where 0 of 6 activities are complete and all 6 are past their date is not a plan that needs encouragement. It needs a decision.

The first decision is whether to close the project at all. The sample plan includes verifying the solution and revalidating the MSA, due 25 May 2025, and preparing the Control tollgate review, due 30 May 2025. Neither has started. You cannot run a credible tollgate when the verification behind it has not happened. The honest call is to hold the gate.

The second decision is sequencing. Four of the six items depend on the first one. SPC monitoring, SOP updates and training all follow from a finalised control plan. The only activity in progress is that first item. So the realistic move is to finish it, then reset the five downstream dates rather than let them sit permanently overdue.

The third decision is capacity. The Black Belt owns two items and the Green Belt owns two. If both are already assigned to a new project, the plan has no hands. The tool does not tell you that. It does show you the concentration of ownership clearly enough that you can ask the question.

The most common mistake is writing the Control plan as a formality at the end of the Improve phase, then never updating the status column. A plan with every row at Not Started and every date in the past is the result. The sample data shows exactly what that looks like.

The second mistake is vague activities. Review the process is not an activity. Update SOPs and work instructions, with a note saying seven SOPs revised, is an activity. Somebody can tell you whether it is done.

The third mistake is leaving the monitoring method undefined. The sample names the method in the notes: a p-chart on DPMO. That tells the owner what chart to build and on what measure. Without it, build SPC monitoring on defect rate is an invitation to argue for a fortnight.

The fourth mistake is skipping measurement system validation. The sample includes revalidating the MSA with a Gauge R and R repeat. If the measurement system changed when the process changed, your before and after comparison is not safe.

The sample gives you a reusable skeleton. Control plan, monitoring, documentation, training, verification, tollgate. Most handovers need all six in some form.

Keep the list short. Six rows fit on a screen and in a conversation. A Control plan with thirty rows becomes a tracking exercise rather than a handover.

Keep the window tight. The sample runs twenty five days from first date to last. A short window forces the conversation about who actually has capacity, which is the conversation that decides whether the gain holds.

Review the plan at a fixed cadence until every row reads Complete. The count at the top is the only progress measure you need.

The Control Phase Plan counts and sorts what you type in. It does not verify any of it. If somebody marks an activity Complete without doing the work, the tool reports 1 of 6 complete and looks satisfied.

It does not know about dependencies. It does not know that SPC monitoring cannot start until the control plan is final. The sequence in the sample is sensible because a person made it sensible, not because the tool worked it out.

It does not measure whether the gain actually held. It plans the activities that make holding the gain possible. Whether the defect rate stays where you put it is answered by the SPC chart you build in activity two, not by this plan. That evidence lives in the Sustain phase.

It does not allocate capacity, chase owners, or escalate. Six activities past their date will stay past their date until somebody acts. What the tool gives you is a plain, unarguable picture of that fact, in a form you can put in front of a sponsor. The decision is still yours.