Skip to content
Dashboard
A practical driver field handbook · Chapter 3 of 4

At delivery: count goods, capture POD and record collections

At the receiver, record what really happens. Confirm the intended site and authorised receiving contact, count accepted goods and note damage or refusal. Delivery proof must identify the correct job and actual outcome. Money collected under instructions needs its own receipt and handover; it is not a substitute for delivery evidence. If a receiver will not accept goods or provide required proof, use the exception process rather than inventing a successful result.

HiVAM product guides · About 3 minutes to read, plus practice · Reviewed

Your learning goals

What you’ll learn

  • Record quantity-wise delivery facts.
  • Capture readable, relevant evidence.
  • Keep collections and handover accountable.

Useful terms

Accepted quantity
The goods the receiver actually acknowledges receiving.
Collection handover
Transfer of collected money and evidence to the responsible finance process.

Step-by-step operating routine

  1. Confirm receiver and instructions

    Check the job, site, receiving contact and expected pieces. Follow access and handling instructions. Ask dispatch to resolve a changed receiver or conflicting collection request before acting.

    Record or confirm
    • Job
    • Site
    • Receiver
    • Expected pieces
    • Instructions
  2. Count the delivery outcome

    Record accepted pieces and separate refused, short or damaged goods. Note reasons factually. Goods still with you or another custodian need a location and authorised next action.

    Record or confirm
    • Accepted
    • Refused / damaged
    • Reason
    • Remaining custodian
  3. Capture clear proof

    Use the permitted evidence method. Check booking identity, date, accepted quantity and readable acknowledgement. Capture only necessary information. A blurred upload or unrelated photo should not be treated as approved proof.

    Record or confirm
    • Evidence
    • Job reference
    • Quantity
    • Quality
  4. Record actual collection

    Collect only under current authorised instructions. Record amount, method and receipt reference. A pending digital payment remains pending until verified through the proper process; do not record it as cash received.

    Record or confirm
    • Amount
    • Method
    • Receipt
    • Verification state
  5. Hand over money and documents

    Follow the company’s tracked handover process for cash and original papers. Retain acknowledgement and report mismatches. An uploaded copy does not mean the original document reached finance or the customer.

    Record or confirm
    • Cash handover
    • Original POD holder
    • Acknowledgement
    • Mismatch
Worked example

18 accepted, two refused

A receiver accepts 18 of 20 cartons. The driver records 18 accepted and two refused with their reason and custodian. The POD reflects the actual outcome. A separately instructed collection is recorded with verified evidence and handed over; the two refused cartons remain open for dispatch’s disposition decision.

  • Count 18 + 2 = 20.
  • Keep proof quantity accurate.
  • Retain cash and original-document handover evidence.

Exceptions and mistakes to avoid

  • Do not sign on behalf of a receiver without proper authority.
  • Never mark refused goods delivered to finish the app task.
  • Do not store customer cash without following the accountable handover routine.
Put it into practice

Driver delivery handoff

Complete while safely stopped and reconcile with dispatch or finance as appropriate.

Illustrative row—replace it with your own private operating information.
JobAccepted / outstandingPOD quality / referenceCollection stateHandover owner
LR 02018 accepted / 2 refusedReadable, linked proofVerified or pending explicitlyDelivery coordinator / finance
Download CSV worksheet

Includes the illustrative row and blank rows. This is a planning worksheet, not a HiVAM import format. Keep your completed copy private; do not add credentials.

Check your understanding

Try answering first, then open the explanation. Use the worksheet and source records to practise the task.

Does uploaded POD mean it is approved?

No. It must meet the agreed quality and review requirements.

What if the receiver refuses two packages?

Record refusal, quantity, reason and continuing custody, then obtain an authorised next action.

Connect the workflow

Put it to work with HiVAM

Use these connections to explore the relevant product workflows. Confirm access in your deployed release; API capabilities require an integration or an available interface.

Compare all capabilities and availability

Keep your learning moving.

0 chapters marked complete. Reading progress stays in this browser; it is not a qualification or your company’s setup progress.

Try the workflow with your team.

Bring a representative job and an exception to a HiVAM demonstration. Review saved records, permissions and handoffs alongside the interface.