OPS.9:4.2 - Reconstruct where completion is lost

Follow representative matters through the relevant services and joins. Recover entry, eligibility, start, completion, return and acceptance events. Distinguish processing, setup, starvation, blocking, unavailability and rework only where they can explain the shortfall.

Use the event sequence and the resource calendar together. A snapshot identifies a population at one time; it does not explain a week of waiting. A utilization average can hide a critical peak. Record uncertainty and missing events before calculating a causal-looking rate.

If the result is delayed by many small waits, inspect cadence, handoff and decision timing across the path rather than forcing one scarce-resource answer.