Delivery change log template

A free Excel log for delivery changes that arrive by phone, text, email or chat. Each row records what the order said before and after, who asked and who took it, and stays Open until the customer has confirmed the change and the route or pick list has been updated.

Download Excel (.xlsx)Download CSVFree. No sign-up. Works in Excel and Google Sheets.

What's in the sheet

Sample rows. Shaded columns calculate themselves.

Changes
Received	Source	Customer	Order	Change	Before	After	Requested by	Taken by	Confirmed	Route updated	Status	Notes
2026-09-15 08:12	Phone	Green Valley Market	PO 30418	Date	Deliver Tue 9/16	Deliver Wed 9/17	Dana, receiving	Chris	Yes	Yes	Done
2026-09-15 09:40	Text	Harbor Deli	INV 7712	Quantity	12 cases romaine	8 cases romaine	Luis, owner	Chris	Yes	No	Open	Update the pick list before 2 PM
2026-09-15 11:05	Email	Northside Cafe	PO 30455	Address	Back door, 14 Elm St	Loading dock, 20 Elm St	Maya, manager	Priya	No	No	Open	Waiting for the gate code
2026-09-15 13:30	Chat	Ridge Grocery	PO 30460	Cancel	6 cases mini peppers	Cancelled	Sam, buyer	Priya	Yes	Yes	Done
2026-09-15 15:20	Phone	Green Valley Market	PO 30418	Item swap	Honeycrisp apples	Gala apples, same quantity	Dana, receiving	Chris	Yes	No	Open	Second change on the same order today

What each column is for

Received: Date and time the change came in.
Source: Phone, Text, Email or Chat.
Customer: The customer or location.
Order: The PO or invoice number.
Change: Date, Quantity, Address, Item swap or Cancel.
Before: What the order said.
After: What it says now.
Requested by: Name and role of the person who asked.
Taken by: Who on your team took the change.
Confirmed: Yes once you have confirmed back to the customer.
Route updated: Yes once the route, pick list or driver has the change.
StatusCalculated: Done when both are Yes, otherwise Open.
Notes: Anything the driver or the next shift needs.

How to use it

1Write the change down while you are still on the call, one row per change.
2Fill Before and After in the customer’s words, not a summary.
3Confirm back to the customer and set Confirmed to Yes.
4Update the route or pick list, set Route updated to Yes, and filter Status to Open before the end of the day.

Where the spreadsheet stops helping

Changes come in while people are driving, picking or on another call, so they never get written down.
The route gets updated but the customer never hears back, or the other way round.
Two changes land on the same order in one day, and only one of them reaches the driver.

In Markhub

Let Markhub catch the change while you talk

1Talk it through in a Markhub call or chat, or post the customer’s text or email in their hub.
2Live Context picks out the change while you talk and drafts a to-do with the before and after.
3You confirm the to-do. It stays attached to the conversation it came from, so anyone can see who asked and when.

Start free

Start free. Live Context works in every call and chat in a hub, with no agent to set up.

Questions

What should a delivery change log include?

When the change came in, who asked, the order, what changed from and to, and whether both the customer and the route have it. The last two are what stop missed deliveries.

Why track Confirmed and Route updated separately?

Because they fail separately. A change can reach the driver without the customer ever hearing back, or be promised to the customer and never reach the route.

Should cancellations go in the log too?

Yes. The driver needs to know about a cancellation as much as about a new date.

Does it work in Google Sheets?

Yes. Upload the .xlsx file to Google Drive and open it with Google Sheets. The formulas and dropdowns carry over. The CSV has the same sample rows as plain values.

More templates

See how operations teams run this in Markhub