Tie proof to parcel identities
Synthetic shipment S-P contains P1,P2,P3. Recipient acknowledgement POD-A explicitly lists P1 and P2; P3 has no delivered evidence. The local completion rule requires each parcel delivered or given a recorded exception disposition. A shipment-level signature without parcel scope cannot silently mark every parcel delivered.
| Constraint | Required record | Example decision rule |
|---|---|---|
| Parcel membership | Shipment S-P → P1,P2,P3 | All three remain visible |
| Proof scope | POD reference + named parcels | POD-A covers P1/P2 only |
| Parent completion | Disposition per parcel | P3 absent proof keeps work open |
Test partial and unscoped acknowledgement
| Case | Input | Expected decision |
|---|---|---|
| POD-A | Lists P1/P2 | Two delivered; P3 pending |
| Unscoped signature | S-P named; parcels unspecified | Clarify before allocating proof |
- List expected parcels
- Read actual proof scope
- Update named parcels only
- Resolve remaining parcel disposition
A recorded exception may close a task under the local rule, but it must not be labelled delivered.
P3 later has a recorded return-to-sender disposition. How many were delivered?
Show the worked answer
Two, P1 and P2. P3 has a different disposition; it does not become a third delivery.
Ask for parcel-level evidence links in the export, not only one shipment-wide complete checkbox.