Operations Software
Record the gap before passing the task onward
A fictional workshop brief requests twelve chairs in Room Pine. The outgoing coordinator reports ten chairs arranged there. The next coordinator will take over preparation. This original exception note preserves the requested state, the reported state and the next action. It does not claim that anyone has inspected the room or completed the reset.
01
Keep the request and the report in separate fields
Record the requested count as twelve, with the workshop brief named as its source. Record the reported count as ten, attributed to the outgoing coordinator’s handoff. Their difference is two chairs, but the note should retain both original counts rather than replacing them with the gap alone. Add a time to the report when one is actually available. This exercise supplies none. An untimed report may still be useful, but the next person should know that its freshness has not been established.
02
Assign a next action without inventing an available supply
The proposed next action is to check the room count and locate two suitable chairs if the report is confirmed. The incoming coordinator can be named as the proposed owner, with acceptance left pending until they acknowledge the assignment. Do not invent a storage location or assume spare chairs are available. If the shortage cannot be resolved, the organiser needs a clear update describing the remaining gap. That is a separate decision point; the handoff should not silently reduce the requested count to match what happens to be present.
03
Define closure in terms of an observed condition
For this narrow task, the proposed completion condition is twelve chairs present in the requested arrangement, confirmed by the responsible person. Other room-readiness requirements remain outside this count example. The reusable note contains request, source, reported state, report time, gap, proposed owner, next action and completion condition. Acknowledging the note is not the same as meeting that condition. Leave the confirmation field blank until an observation exists, then record who checked and when. The note can be closed without erasing the earlier exception or how it was resolved.