Skip to main content
GullySystem
Logistics

Service Reports and Proof of Visit for Last-mile delivery companies

Record the actual parcel delivery attempt or return handover and its reviewed evidence.

Field Service

Does this function belong in your operation?

Use for documented delivery field activity; the report records a parcel event rather than a technician’s repair visit.

A worker reports a pickup, delivery attempt or return event requiring an operational record.

Use the report as a record of the actual delivery attempt or return handover, with the parcel and assigned worker identified. Capture the agreed outcome and permitted acknowledgement or image evidence, including what could not be confirmed. A photograph at an address does not establish that the intended recipient received the parcel. Retain corrections as versions and restrict evidence access. Report approval must remain separate from collection verification, merchant remittance and customer-service billing.

Bring the records the workflow depends on.

  • Parcel, merchant request and actual assigned worker
  • Event type and reported outcome with time source
  • Agreed evidence requirements and access permissions
  • Recipient or return-receiver acknowledgement and unresolved observations

Outputs to check

  • Versioned attempt or return-handover report
  • Permitted acknowledgement and evidence references
  • Unconfirmed, disputed or missing-evidence follow-up

Follow the service reports and proof of visit workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Identify the event

    Link the actual parcel and worker to the specific attempt or return. Keep separate events distinguishable even where the address is the same.

  2. 2. Record what occurred

    Capture the reported handover or failed attempt and its reason. Identify unperformed checks and anything the worker could not confirm.

  3. 3. Attach permitted evidence

    Use only evidence required under the agreed process and appropriate permissions. A location image alone does not identify rightful receipt.

  4. 4. Review inconsistencies

    Compare the report with assignment and custody records. Keep missing or conflicting evidence pending review rather than forcing a successful outcome.

  5. 5. Issue and revise

    Share the approved record only with authorised recipients. Preserve earlier versions and the reason for corrections to delivery or return evidence.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Delivery worker

Records the actual event and distinguishes observations from assumptions about the recipient or contents.

Evidence reviewer

Checks missing information, permissions and inconsistencies against the parcel record.

Merchant account coordinator

Follows unresolved merchant instructions and shares the approved record within agreed access.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Recipient acknowledgement unavailable

Record that fact and seek the agreed evidence review; do not insert a signature or assume acceptance.

Photo and parcel reference conflict

Keep approval pending while identity and event are investigated.

Outcome corrected after issue

Retain the original, issue a reasoned revision and identify authorised parties needing the correction.

Can this work independently?

The operator and merchant agree evidence requirements and authorised recipients. Tasks and custody acknowledgements provide context. Collection verification and fee billing remain separate processes. Any mobile capture or storage connection needs confirmed scope; no automatic proof service is assumed.

Systems and records it connects with

  • Delivery orders and tasks: Parcel identity, authorised work and assignment.
  • Custody records: Actual issue and return acknowledgement.
  • Collection and service accounts: Reviewed event references without automatic financial settlement.

Configure, test and introduce the workflow.

  • Compare a successful handover, failed attempt and physical return record.
  • Agree required evidence, permitted access and treatment of unconfirmed observations.
  • Test a missing acknowledgement and corrected outcome, ensuring neither automatically settles collections or service charges.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Reports identify the correct parcel and specific event.
  • Failed attempts and unperformed checks remain explicit.
  • Evidence access follows the agreed recipient permissions.
  • A correction preserves the earlier record and responsible reviewer.
Last-mile delivery companies

How the business operates.

A last-mile delivery company takes custody of a merchant’s parcels at a hub or pickup point and coordinates their delivery attempts and authorised returns. The goods are entrusted for delivery under the accepted merchant instructions and remain outside operator-owned stock; the delivery operator manages the service and custody records. This proposed software scope connects merchant instructions, actual parcels, rider assignments, attempt evidence and commercial reconciliation. Where cash on delivery is contracted, money collected for the merchant must remain separate from the operator’s delivery-service revenue. A completed rider task can represent a failed attempt, so delivery, return and cash outcomes need their own evidence.

Merchant instructions and hub intake

Accept delivery requests within the actual service agreement. Match parcel identifiers and counts at receipt, preserving shortages, visible concerns and information still needed from the merchant.

Dispatch and rider coordination

Assign the actual work and record parcel handover. Keep delivery instructions, accepted changes and parcel custody visible when work is reassigned.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Merchant order and accepted delivery-service reference
  • Parcel identifier, expected and actual piece counts and custody acknowledgements
  • Recipient instructions and authorised changes with access restrictions
  • Rider assignment, attempt outcome and supporting evidence

Operational bottlenecks to check

Assignment changes but parcels stay with the first rider

A reassigned task is not a custody transfer. Both workers’ acknowledgements and unresolved parcels need to remain visible.

A closed attempt appears as a delivery

Failure, refusal and incomplete evidence need explicit outcomes. A closed work item must not inflate the delivered-parcel count.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Accept the merchant request

    Confirm the actual delivery service, parcel references and collection instruction if contracted. Keep specialised goods or handling outside acceptance until separately reviewed.

  2. 2. Receive and allocate custody

    Match physical parcels to the request and record exceptions. Assign the work and acknowledge the actual handover to the rider.

  3. 3. Record each attempt

    Capture the attempt outcome and required evidence without turning an address visit into delivery. Refer refused, inaccessible or disputed handovers for the agreed decision.

  4. 4. Resolve undelivered parcels

    Retain prior attempts while recording an authorised reattempt or return. Confirm physical custody and merchant receipt rather than closing a return from its instruction alone.

  5. 5. Reconcile money and fees

    Review any customer collection, rider-to-office handover and actual merchant remittance. Separately bill the accepted delivery services and approved additional work.

Industry reports to connect with

  • Parcels by merchant, custodian and unresolved mismatch
  • Unassigned work and attempts awaiting review or instructions
  • Delivered, failed, reattempted and physically returned parcels
  • Collection differences by rider, payment evidence and merchant

Questions before implementation.

When should last-mile delivery companies consider service reports and proof of visit?

Use for documented delivery field activity; the report records a parcel event rather than a technician’s repair visit. A worker reports a pickup, delivery attempt or return event requiring an operational record.

What should we bring to the requirements discussion?

Bring anonymised examples of Parcel, merchant request and actual assigned worker; Event type and reported outcome with time source; Agreed evidence requirements and access permissions; Recipient or return-receiver acknowledgement and unresolved observations. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Record the actual parcel delivery attempt or return handover and its reviewed evidence. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A report does not certify contents, rightful receipt or payment. It does not provide technician certification, location tracking or automatic recipient authentication.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Reports identify the correct parcel and specific event. Use this check when reviewing the first working version.

Talk to us

Discuss service reports and proof of visit for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements