A control plan is the document that keeps an improvement alive after the project team disbands. For each critical characteristic of a process, it records what is measured, how, how often, by whom, against what limits or standard — and, crucially, what to do when a measurement signals trouble. It is the formal answer to the question that haunts every improvement effort: who will care about this in six months?
How it’s used
The control plan is the signature deliverable of the Control phase of DMAIC. During a project, discipline is supplied by the team’s attention; after handover, the process owner inherits the gains, and attention must be replaced by structure. The plan gathers that structure into one place: the control charts and their sampling schedules, the checklists and standard work, the audit cadence, and a reaction plan for each metric — the pre-agreed steps to take when a signal appears, written while heads are cool rather than improvised during a bad week.
A control plan is a living document. When the process, product, staffing, or equipment changes, the plan is reviewed and revised — otherwise it decays into a description of a process that no longer exists.
A worked example
An e-commerce fulfillment center finishes a project that cut mispicked orders by fixing bin labeling and slotting look-alike items apart. The control plan that closes the project fits on one page. It names the metric — mispicks found in a daily audit sample — and the p-chart that tracks it, maintained by the shift lead. It names the reaction plan: on any signal, re-check the audited orders, inspect bin labels in the affected zone, and escalate to the operations manager if a second signal follows. And it names the review trigger: any change to slotting or labeling reopens the plan. A year later, the gain is either still there or the plan says exactly who let it go.
- Write a reaction plan for every metric — a chart nobody is obliged to act on is decoration.
- Name one accountable owner per line of the plan; shared ownership is no ownership.
- Trace each control back to the root cause it guards, so future readers know why it exists.
- Keep it short enough to be used — a page or two that lives at the process beats a binder that lives on a shelf.
- Review the plan whenever the process changes; an outdated control plan protects a process that no longer exists.
An improvement without a control plan is a loan the old process will eventually call in.
Building a control plan is taught in the Control-phase material of our Green Belt program ($299, about 35 hours), and the 100-question proctored exam treats it as core knowledge — because in practice, the control plan is where certified skill turns into lasting results.
Put it into practice
Ready to make it official?
Our Six Sigma belt programs — White through Black — are self-paced, 100% online, and end in a proctored exam and a credential you can verify and share.