Action Closed. Why Is the Problem Back?

The new procedure was issued. The briefings were completed. Then the same handoff failed again. What evidence should it take to close the action this time?

ORR IMS is an evolving learning example, currently connecting five starter kits. It is not a complete implementation of the four standards in its intended scope.

An action can be genuinely completed without delivering the intended outcome. That is an uncomfortable possibility when the tracker has already turned green, but it is useful information.

For an IMS practitioner, the next question is how the system responds. Does the recurrence reach someone who can reconsider the risk and the response? Or does the completed action become a reason to stop examining the problem?

A learning system needs a route back into the decision.

Follow what actually happened

In the fictional Cedar Estuary story, the revised procedure becomes effective after the initial release conditions are satisfied. Later, one eligible change lacks the required night-shift acknowledgment.

The September objective is missed. The procedure’s release history remains intact, and the missed execution is recorded as a subsequent control failure.

This prevents two different questions from being mixed together. Was the identified implementation action completed? Did the arrangement achieve the intended result on later occasions?

The answer can be yes to the first and no, or not yet established, to the second.

Keeping both answers visible gives management something more useful than a single completed/not-completed field.

Reopen the question at the right level

The fictional management review reopens the risk and assigns a follow-up action addressing the relief-supervisor handoff. It does not simply reissue the earlier email and declare the matter settled.

The point is to revisit the conditions that allowed the missed execution. What did the substitute receive? Which responsibilities were transferred? Was the pending change visible? Were time, access or authority part of the difficulty?

These are questions to investigate with evidence. The narrative does not justify inventing a personal failing or a convenient root cause.

A useful review also asks whether the original response addressed the relevant mechanism. Perhaps it covered the initial briefing but left future relief arrangements unclear. That would call for a different intervention from repeating the same launch activity.

Make the leadership decision visible

In the case, a handoff session receives resources, the action has a responsible person and a date, and follow-up evidence is required. The result is connected to an accountable management decision.

This is an important role for management review. A discussion can identify a concern without resolving the resource conflict that sustains it. The decision needs to establish what will change, who can deliver it and how progress will return for review.

Record unresolved matters too. A meeting should not imply that every subject was reviewed satisfactorily when important inputs were absent.

The Cedar Estuary record leaves other applicability and continuity work open. Closing one handoff action does not close those separate questions.

Define the outcome before deciding it passed

The fictional follow-up criterion is successful coverage on the next two eligible changes. If too few occur, observation is extended and the outcome remains pending.

That detail prevents the due date from manufacturing a result. Time passing is not evidence that an opportunity to test the change occurred.

The criterion is deliberately scoped. Two successful executions are not a universal recommendation or evidence of sustained company-wide effectiveness. The appropriate observation for a real organisation depends on the claim, risk, variability and relevant operating conditions.

Agree the criterion before examining the outcome. Otherwise, it becomes easy to select whatever evidence is available and redefine success around it.

Ask whether the test challenges the weakness

Suppose a follow-up sample contains only occasions handled by the experienced day supervisor. It may not examine the relief-handover condition that prompted the action.

This is an illustrative challenge to the test design, not an additional fact in the source case.

Select observations that are relevant to the failure mechanism and the intended claim. Explain the limits where the relevant condition has not occurred or cannot be examined safely.

The ORR IMS acceptance protocol calls for recording criteria, evidence, limitations and retest conditions. These details help a later reader understand what closure means.

They also make it possible to challenge a closure decision without dismissing the work already completed.

Keep the original miss in the record

After the fictional follow-up succeeds, the September result remains 80%. It is not rewritten as 100% because a later action worked within its stated criterion.

That history explains why the action existed and what was learned.

A correction to an erroneous entry should preserve its reason and the relevant audit trail. An improvement in later performance should be recorded as a later result. Combining the two can conceal whether the system learned or merely changed its account of the past.

This matters for people too. An honest record allows a team to acknowledge a failure, investigate it and demonstrate the response without pretending that the difficulty never occurred.

Decide what would reopen the matter again

Closure should describe the exact action and outcome criterion satisfied. It should also connect to continuing monitoring and any trigger for renewed attention.

In Cedar Estuary, the risk returns to a monitored state with a review point and an earlier-failure trigger. The scoped action is closed; the organisation does not acquire permanent immunity from the problem.

For your own improvement, ask what would change the conclusion. A new shift pattern, a changed system or another missed execution may require reconsideration.

That question makes closure part of an ongoing management arrangement.

Define an outcome test before closure

A fictional digital agency adds a review step after sending the wrong file version. Issuing the new checklist completes an action. Follow-up must examine whether the version-selection weakness recurs under relevant conditions, including substitute reviewers where appropriate.

Separate implementation evidence from outcome evidence. Define the test, observation opportunities, closure authority and reopening trigger before judging the result.

Start with the management-review worksheet. What evidence would persuade you that the response worked? Leave a comment below; a question or fictional example is enough. If you want to propose a document change, the contribution guide explains the optional GitHub route.

Use fictional examples only. Do not share employer or client records, personal information or copied standards text.

Images are AI-generated illustrations, not photographs or evidence of actual implementation.

Part 11 of 12 in Making IMS Work with ORR IMS. Explore the series.