A repeated deviation is a reason to investigate; its count alone gives neither a cause nor a decision.
Look for shared conditions
Fill date, run, time, location, vehicle, container and product fields consistently in each record.
Comparison steps
- State the deviation rule and time window.
- Count eligible runs with a deviation under that same rule.
- For each shared condition, divide deviations by eligible runs under that condition.
- Record denominators, missing files and measurement coverage with the result.
- Repeat the same comparison in the next period.
Threshold and pattern
Do not assume a universal repeat count; define the decision criterion in the site quality process and record any change.
A pattern guides investigation :: Denominators and record coverage show how comparable the repeats are.
A single record
Record a one-off finding too; if it recurs, match it to the earlier run using the same definitions and fields.
When a pattern appears. Separate an association from a possible explanation; if several processes changed at once, their effects cannot be distinguished.
Review by condition
| Shared field | Records to check together |
|---|---|
| Time | Loading, stop and delivery times |
| Delivery point | Run order and waiting record |
| Vehicle | Vehicle ID, route and eligible run count |
| Container | Container ID and matched measurement file |
| Product | Product requirements and authorized quality assessment |
