Skip to content

Control · Free tool guide

Control Plan Builder: guide & examples

A Control Plan connects process steps or measures with operational definitions, monitoring ownership, targets or triggers and the response to unusual results.

5 practical steps · 2 worked examples · Editable practice worksheet

Reading is free. Tool access requires a verified account; no manual beta approval or payment is required.

What is it, and why use it?

A Control Plan connects process steps or measures with operational definitions, monitoring ownership, targets or triggers and the response to unusual results.

It provides an organized record of how a process improvement will be maintained after initial testing.

Explore the Control Plan Builder features and local-file workflow

When to use it

Use it when a process change needs a clear measurement and reaction framework.

When another tool fits better

Use Data Collection Plan to design a new measurement method first. Use Monitoring Plan or Reaction Plan for a focused operational view of those activities.

Before you start

  • An agreed process and locally validated measures.
  • Owners, review frequencies and data sources.
  • Reviewed targets, trigger conditions and authorized response procedures.

Use fictional or approved non-sensitive information. Do not include patient details or proprietary records in practice worksheets.

Step-by-step in CI Tools

  1. Enter Control Plan process and purpose, then choose Add Control Item.

  2. Expand an item and describe the process step or metric, operational definition, unit and measurement method.

  3. Complete ownership, frequency, sampling, targets or triggers and required reactions. Distinguish requirements from statistical control limits.

  4. Import Worksheet Records previews selected copies from supported tools; confirm only the records you want appended. Import Data supports reviewed table mappings.

  5. Use search and role filters to review items, then check the full plan. Exports retain all items even when a filter hides them. Save an editable .citools copy.

Requirements and process limits answer different questions

A specification describes an agreed requirement. Control limits describe expected variation under a selected baseline model. A process can be stable but fail requirements, or show a signal while every value is still within specification.

Completed worked examples

Demonstrations only: all organizations, observations, targets and results below are fictional. They are not clinical instructions or universal performance standards.

Healthcare operations — fictional

Referral intake control

Starting information: A fictional service wants to retain a reduction in rework.

Completed demonstration: Referral intake control
MeasureWeekly percentage of referrals needing missing information
Method / ownerAgreed eligibility definition; intake coordinator reviews the register
Trigger / reactionLocally agreed 20% trigger; review reasons and assign a test of change

What the result means: The plan specifies a human response. It does not automatically monitor the register, send alerts or prove that the improvement is sustained.

General business — fictional

Packing accuracy control

Starting information: A fictional warehouse checks packaging errors.

Completed demonstration: Packing accuracy control
Step / samplingPack and label / ten sampled orders per shift
DefinitionAn order with any mismatch between approved order and packing record
ReactionAuthorized lead reviews the affected process and documents follow-up

What the result means: A sample of ten does not establish the error rate for every order. Review the sampling approach and the consequences of missed errors.

Practise in a separate worksheet

Open the tool’s built-in synthetic sample as a new editable worksheet. It may differ from the worked demonstrations above. It never replaces an existing worksheet. Save any work you want to retain to your computer.

Open built-in practice worksheet

You’ll be asked to log in if needed. No worksheet is created just by reading this page.

Common mistakes and how to avoid them

  • Copying a CTQC definition without checking local applicability: review imports first.
  • Confusing target, specification and control limits: label their different purposes.
  • Assuming filters limit exports: exports contain every plan item.

Interpret the result

Read each item as an operational agreement: can the owner reproduce the measure and carry out the response? The plan itself provides no live assurance. Use observed time-ordered results to evaluate performance.

Record the assumptions and unanswered questions alongside the result. Use the relevant local review process before making operational decisions.

Credible further learning

These independent educational resources explain the methods. They do not endorse CI Tools Suite. Some external resources have their own access requirements.

Resource links reviewed 29 October 2026. Our interface instructions and fictional examples are original CI Tools learning material.

Put the method into practice

Start a new worksheet, use the guide beside your work and keep an editable .citools copy on your computer.

Try This ToolChoose another tool

Back to guide contents ↑