Use casesDelivery exception tracking

Keep a changed delivery plan visible to dispatch and customer service.

Keep delivery changes connected to the revised plan and customer agreement.

How to build your delivery exception tracking

  1. Describe the job

    Keep delivery changes connected to the revised plan and customer agreement.

  2. Review the first version

    Choose how the dispatch coordinator records the Consignment and how the delivery operations lead reviews the next step.

  3. Refine the views

    Ask First to adjust the fields and views for the people who will use the app.

  4. Test before sharing

    Walk through the process with a sample record and check who owns the next action.

Follow Exception DE-051 through the handoffs.

This fictional delivery exception tracking example shows the ordinary handoff and the decision that remains open.

Cedar Example TeamException DE-051

Delivery exception tracking example

Record
Exception DE-051
Consignment
CNS-204

Current stage · Dispatch coordinator

Capture the original delivery commitment

A fictional consignment misses its morning unloading appointment.

Read the full walkthrough
  1. Capture the original delivery commitment

    A fictional consignment misses its morning unloading appointment.

    Record:
    Exception DE-051
    Consignment:
    CNS-204
  2. Record the delivery exception

    Dispatch records that the receiving site could not accept the vehicle.

    Record:
    Exception DE-051
    Original window:
    Tuesday morning
  3. Agree a revised window

    Customer service agrees a new window with the receiver and records the contact note.

    Record:
    Exception DE-051
    Exception:
    Receiver unavailable
  4. Verify evidence before closure

    The reviewer keeps the case open until delivery evidence has been checked.

    Record:
    Exception DE-051
    Revised window:
    Wednesday afternoon

What to include in your delivery exception tracking

  • Keep the Consignment in context

    Keep Consignment, original window, exception reason, assigned coordinator, revised proposal, customer agreement and completion evidence together so the next person can understand the request or record.

  • When the next step needs a decision

    A sample consignment misses its morning unloading appointment. Dispatch records that the receiving site could not accept the vehicle.

  • Keep completion evidence visible

    Leave the exception open until the revised arrangement and completion are recorded.

  • Choose what each person needs

    Give the dispatch coordinator a working view and the delivery operations lead a review view. Keep Consignment and original window attached to the decision as the work moves between them.

Questions about delivery exception tracking

Start with Consignment, original window, exception reason, assigned coordinator, revised proposal, customer agreement and completion evidence. Describe who enters the information and who reviews the next step.

Try the workflow with your own process in mind.

Start with your workflow and make it yours.

Get started