Procedures and Best Practices
What this domain tests
Whether you can execute the standard sequence without skipping a control point. Items place you at a counter or dock and ask what you do, in what order, and what you record. The documented sequence outscores the faster shortcut every time.
The acceptance sequence
- Confirm the item is not prohibited or restricted for the selected service.
- Verify the destination address is complete enough to deliver: street number, street, unit or apartment, city, postal code.
- Weigh the item and, where the service requires it, measure dimensions; compare with the declared service level.
- Confirm payment or postage and apply the correct label.
- Scan the item into the network at the point of acceptance - not later, in a batch.
- Hand off with a custody-transfer scan.
Scan discipline
Scan at every custody change and every exception. Never scan an item you are not physically holding. Never re-scan to "fix" a status; a correction is a new event carrying a reason code, not an overwrite.
Worked example
A parcel is addressed to "14 Rue Lafayette" with city and postal code but no apartment number, in a building the clerk knows has multiple units. The address is deliverable to the building but not to the addressee, so it is an address-quality exception raised at acceptance: ask the customer to complete it before payment and scanning. Accepting it and hoping the courier resolves it moves a fixable defect into the network, where it costs a failed attempt and a return cycle.
Traps that cost marks
- Scanning before the prohibited-item and address checks, locking in an error.
- Batch-scanning at end of shift, so timestamps misrepresent custody.
- Overwriting a status instead of posting a reason-coded correction event.
- Recording the exception but not the action taken and the customer contact.