Action Closure Criteria define the evidence required before an action can be considered complete.
A common weakness in daily management is that actions are closed because someone says:
Done.
The better question is:
What evidence shows that the expected result now exists?
Start with a specific action
A strong action should state:
- what will change;
- who owns it;
- when it is due;
- what completion looks like.
Daily Accountability Process helps make ownership and due dates visible.
If the action itself is vague, closure will also be vague.
Match evidence to the action
Different actions require different evidence.
Examples include:
- repair completed and equipment verified;
- standard updated and released;
- training completed and competence demonstrated;
- data collected and reviewed;
- containment removed after permanent control is active.
The evidence should show the required condition exists, not simply that effort occurred.
Separate completion from effectiveness
An action can be complete without solving the problem.
For example:
- sensor replaced = action completed;
- repeat failures stopped = effectiveness verified.
Improvement Effectiveness Review helps determine whether the implemented change actually improved the process.
Daily action closure should not pretend these are the same decision.
Define objective evidence where possible
Useful evidence may include:
- photo;
- system record;
- signed standard;
- measured result;
- observation;
- completed verification test.
The method should be proportional to the risk.
A low-risk housekeeping action does not need the same evidence as a critical quality-control change.
Clarify who can close the action
Closure authority may belong to:
- action owner;
- supervisor;
- process owner;
- requester;
- cross-functional reviewer.
For significant actions, the person who performed the work may not be the best person to verify completion independently.
Use aging to expose weak closure
Action Aging Review helps identify actions that remain open because:
- evidence is missing;
- ownership is unclear;
- dependencies remain unresolved;
- completion criteria were never defined.
If actions repeatedly age because teams argue about what “done” means, the closure rule needs improvement.
Reopen when evidence does not hold
An action should be reopened when:
- the expected condition was not achieved;
- the issue recurred;
- the standard was not sustained.
Reopening is not failure.
It is evidence that the previous action was incomplete or ineffective.
Common mistakes
Closing actions based on verbal confirmation only, defining no evidence, confusing task completion with effectiveness, allowing the owner to interpret closure differently each time, keeping irrelevant actions open forever, and refusing to reopen actions when the condition returns are common mistakes.
Practical sequence
- define the action clearly.
- assign owner and due date.
- define required closure evidence.
- complete the work.
- collect the evidence.
- verify the expected condition.
- close the action.
- monitor effectiveness where required.
- reopen if the condition fails.
- improve closure rules when ambiguity repeats.
The practical lesson
Action Closure Criteria protect the credibility of the action system.
An action is not done because activity stopped; it is done when the required condition can be verified.