Skip to main content
GullySystem
Logistics

Task Management for Last-mile delivery companies

Coordinate specific rider pickup, delivery-attempt and return work with actual parcel handover references.

Project Management

Does this function belong in your operation?

Use where hub and dispatch teams assign delivery work and retain failed attempts or reassignments.

An accepted merchant request needs a named worker and an agreed operational next action.

Dispatch work needs an actual rider, parcel references and a specific pickup, delivery attempt or return outcome. Assignment does not establish physical custody, so retain the handover acknowledgement when work moves between people. A failed attempt closes that attempt with its reason while the parcel still needs an authorised next action. Planned sequence and due information support coordination; they do not establish route feasibility, rider readiness, location tracking or a delivery-time commitment.

Bring the records the workflow depends on.

  • Accepted parcel and merchant request references
  • Work type, destination and permitted recipient instructions
  • Actual worker assignment and custody acknowledgement
  • Outcome evidence requirements and next-action authority

Outputs to check

  • Assigned pickup, attempt and return work list
  • Custody handover and reassignment history
  • Failed or unperformed work awaiting authorised next action

Follow the task management workflow.

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

  1. 1. Define the work event

    Specify pickup, delivery attempt or return with the actual parcel references. Keep a planned sequence separate from completed work.

  2. 2. Assign a responsible worker

    Review actual availability and the operator’s readiness decision. An assignment does not itself transfer the parcel.

  3. 3. Acknowledge custody

    Retain the physical handover when a parcel moves to a worker or between workers. Resolve missing parcels separately from changing the task owner.

  4. 4. Record the attempt outcome

    Capture successful, failed or unperformed work and the reason. Refer evidence to the agreed reviewer rather than treating every closed task as delivery.

  5. 5. Follow remaining work

    Create the authorised reattempt or return action with earlier history intact. Keep unresolved custody and collection matters visible after an attempt closes.

Who uses the module, and who approves?

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

Dispatcher

Assigns actual work and retains blockers, changes and authorised next actions.

Rider or delivery worker

Acknowledges received parcels and records the actual work outcome.

Hub reviewer

Checks custody differences and returned parcels against their handover evidence.

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.

Worker becomes unavailable

Reassign work with its history, then separately confirm any physical parcel transfer.

Recipient cannot be reached

Record the attempt and request the agreed next instruction without marking a delivery.

Task closed with missing evidence

Retain the reported outcome under review and request the missing record or authorised exception.

Can this work independently?

The operator decides worker and resource readiness and reviews the accepted service scope. Manual handover and outcome records can supply evidence; route optimisation, live location and customer notifications require separately confirmed connections. Task dates are coordination inputs, not independent service commitments.

Systems and records it connects with

  • Delivery orders: Authorised merchant instructions and parcel identifiers.
  • Service reports: Actual attempt and return evidence.
  • Collection records: Money reported for the affected parcel, verified separately.

Configure, test and introduce the workflow.

  • Trace a hub issue and a merchant pickup to their actual work assignments.
  • Define outcomes and decision owners for failed, unperformed and returned work.
  • Test reassignment with parcels still held by the first rider, then reconcile the physical handover before closing the work.

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.

  • Assignments identify actual work and parcel references.
  • Reassignment does not silently transfer custody.
  • Failed completion does not count as successful delivery.
  • Reattempts preserve the previous attempt and decision reference.
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 task management?

Use where hub and dispatch teams assign delivery work and retain failed attempts or reassignments. An accepted merchant request needs a named worker and an agreed operational next action.

What should we bring to the requirements discussion?

Bring anonymised examples of Accepted parcel and merchant request references; Work type, destination and permitted recipient instructions; Actual worker assignment and custody acknowledgement; Outcome evidence requirements and next-action authority. 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. Coordinate specific rider pickup, delivery-attempt and return work with actual parcel handover references. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Task status does not establish route feasibility, legal operating readiness, recipient receipt or payment settlement.

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. Assignments identify actual work and parcel references. Use this check when reviewing the first working version.

Related functions for last-mile delivery companies.

    Talk to us

    Discuss task management 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