What does it mean for a process to be “under control”?

We often say that a process is “under control.” But what does that actually mean? Does it mean the procedure is documented, employees have been trained, and the required records exist? Or perhaps that the last audit found no major problems?

All of those things can provide evidence that a system has been operating as intended. But they do not necessarily tell us whether it is under control right now.

Operations do not stand still. People change. Equipment changes. Materials change. Priorities change. Workloads change. Risks change. Procedures change. Customers change. Even when the documented process stays the same, the conditions surrounding the work may not.

That creates an important distinction between proving control and maintaining control.

An audit, inspection, assessment, or record review can help reconstruct what happened. It can show whether work was completed, whether requirements were followed, who performed the work, and what the result was.

That information is valuable. But management also has a different question: What is happening now?

What work should be occurring, and who is responsible? What conditions should exist? What is due next, and what has not happened when expected? Are conditions beginning to move outside acceptable limits? Where is risk increasing, waste appearing, or intervention needed?

Those are questions about the current operating condition of the system.

Maintaining process control means understanding what's happening on the production floor, not just documenting what happened.

Maintaining control in a changing environment

It is tempting to think of control as something that is established. We write the procedure, train the people, qualify the equipment, establish the limits, and begin collecting records. The process is now “under control.”

But control does not persist simply because it existed yesterday.

A process remains under control only when the organization can continue to recognize meaningful changes and respond to them. That might mean noticing that a temperature is moving toward an unacceptable limit, recognizing that a required sanitation activity is overdue, or seeing that rework is increasing. It might mean identifying that a workaround employees created six months ago has quietly become the normal way the work gets done. Or it might simply mean recognizing that the work expected today has not happened yet.

In each case, the important issue is not merely whether a requirement exists. It is whether the organization can recognize the difference between what should be happening and what actually is happening.

Historical evidence vs. operational awareness

This does not make records, audits, inspections, or assessments less important. Quite the opposite. Organizations still need reliable evidence of what happened. That history supports audits, investigations, corrective action, root cause analysis, continual improvement, training, accountability, and regulatory compliance.

But historical evidence and operational awareness serve different purposes. Records help us understand what happened. Operational awareness helps us decide whether something needs attention now. A strong system needs both.

The problem arises when historical evidence becomes the primary way management discovers that control has been lost. By then, the organization may be investigating a condition that existed for hours, days, weeks, or even months.

So what does “under control” mean?

Perhaps a more useful definition is this:

A process is under control when the organization knows what should be happening, can recognize meaningful differences between the expected and actual condition, and can respond before those differences become larger problems.

That does not require monitoring everything continuously. Different risks operate at different speeds. Some conditions may need immediate attention. Others may reasonably be reviewed hourly, daily, weekly, or when a specific event occurs. The important point is that the frequency and method of awareness should match the consequence and speed of change.

Control, then, is not simply a collection of procedures and records. It is an operating capability. It requires knowing what should happen, knowing enough about what is happening, recognizing when the two begin to diverge, and taking appropriate action.

Control is not something an organization has. It is something an organization continuously does.

In this series, we'll explore what control means in practice: how expectations are defined, how actual conditions become visible, why controls gradually decay, and how firefighting can become self-reinforcing. We'll also examine how organizations can move beyond periodically proving that a system was under control to continuously knowing whether it is.