Control Plan for Transactional Projects

For a Control Plan, I usually use a four column table.  The first column identifies the variables that have shown themselves to be important (quality of oncoming data, time allotted to task, operator skill, for example).  The second lists what changes were made in order to better control those key variables.  The third tells what "signal" would indicate an adverse change to the variable, and the fourth gives a short reaction plan.

In some cases, you'll want to Control Chart the input variable.  In that case, adverse variation would be an out of limit point, and the reaction plan might assign someone to investigate the cause, and list a typical action that might be taken to correct the problem.

If you use poka yoke as your control mechanism, then there isn't any anticipated indicator of adverse variation, because the input variable should not be able to "misbehave".

If you change the process documentation, then perhaps you will make those instructions a controlled document, and your company's document control system would be a control mechanism.

The right half of the FMEA contains most of this information.  Personally, I consider copying and pasting of the right half of the FMEA to be a suitable Control Plan in some cases.