Resolve an exception

Move a specific operational issue through reasoned review and verify the corrective work before resolution.

Step by step

Identify the open issue Operations Manager

Operations Manager selects the Open exception and reads its reason under the linked work order. Confirm the actual issue before requesting a corrective action.
- Select the specific Open issue in authorized scope
- Updates Exceptions, Work orders
Submit reasoned review Operations Manager

Operations Manager invokes the authorized resolution action. It validates the linked order and moves the exception into Review with the context needed to explain the correction.
- Open to Review after parent validation
- Updates Exceptions, Work orders
Record the correction Operations Manager

The action appends an attributed corrective work log against the same order. The acting person's identity and recorded activity keep the correction connected to the original operational case.
- Append attributed corrective activity to the same work order
- Updates Work logs, Work orders, People
Verify resolution Operations Manager or Operations Reviewer

The action verifies the persisted effects before moving the exception to Resolved and recording the resolved date. Operations Reviewer inspects the resulting evidence; reading it does not grant direct write access.
- Review to Resolved after verified effects; retain resolved at
- Updates Exceptions, Work logs

And how to keep it from happening.

Correction on another order. The exception and corrective log must retain the same parent throughout the operation.
Premature resolution. A requested action cannot stand in for a corrective effect that has not persisted.
Unexplained issue. A vague reason leaves the next person unable to identify what evidence would resolve the case.

Start free, then use Proto to change fields, steps and approvals before your team goes live.