The record must separate the attempt, obstruction and next decision using categories agreed by operations and the customer.
Index
Scheduled work may fail because access is unavailable, a contact is absent or a resource is missing; labeling everything canceled loses the explanation.
The rule that changes the scope
The record must separate the attempt, obstruction and next decision using categories agreed by operations and the customer.
A calendar can cancel events; additional development organizes attempt evidence and ownership of rescheduling.
Obstruction categories must help choose the next action rather than exist only for reporting. Missing access may need customer contact, while missing resources may require the supplier's own decision. Make those different owners visible. When the visit resumes, retain the link to the earlier attempt and record actual execution separately. This avoids counting two visits as two completed services and preserves an explanation of the service sequence.
Specify operational deliverables
- Associate the obstruction with the planned activity and the contact used during the attempt.
- Show who must act to enable another visit.
- Keep the original window and the proposed reschedule that is not yet confirmed.
Test the exception before acceptance
In a hypothetical scenario, the team arrives but receives no access; the appointment must retain the attempt without claiming the service was performed.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a failed visit and the process used to negotiate its next attempt.