What it means
A customer requests delivery between 09:00 and 11:00, but sales confirms the date without confirming the dock window, and this measure shows how long the specific slot remains unconfirmed after a defined request. Distinguish a requested window from a promised one, since a customer calendar preference does not become a seller commitment until transport and receiving capacity are checked.
Microsoft describes order promising that calculates ship and receipt dates using lead time, stock and transport inputs, but a calculated day does not by itself secure an hourly delivery appointment. Define the start event, whether customer window request, order acceptance or booking invitation, using the milestone that creates a need for a response, and define the endpoint as a confirmed time window acknowledged by the required parties: customer receiving site, carrier and seller if applicable.
Include time zone, local date and daylight-saving change when sites differ, because a window sent as 9 to 11 with no zone can be ambiguous across regions, and a date crossing midnight can create a wrong-day promise. Keep one authoritative local-time booking and make conversions explicit.
Check loading cut-off, transit and customs clearance so the transport plan supports arrival before the window closes, record the appointment number and location for sites with dock appointments, and confirm the window per load when several loads form one order. For temperature-sensitive or staffed unloading, check equipment and personnel availability, because a time slot the site cannot receive is not useful.
If the requested window is unavailable, respond with grounded alternatives rather than silently accepting a later slot, and when the carrier proposes a different ETA, update the confirmed plan with the customer before the original window is missed. Keep the initial request and later revisions, because resetting the clock when the customer asks again hides the earlier unconfirmed period, and if an order is on credit or quality hold, state that the window is conditional.
If the destination changes, reconfirm travel and site constraints, and for customer pickup identify who books the window and what counts as confirmation. Preserve the exact words of any customer commitment in the order record, since a calendar invite to a carrier may not match what the customer was told.
Distinguish confirmation lag from on-time delivery, since a slot can be confirmed quickly and still missed by a delayed truck, and use a denominator of orders or loads with requested delivery windows, excluding flexible deliveries. Show unconfirmed windows near their cut-off and high-percentile lag, not only the average, and classify delays by inventory readiness, transport capacity, customer dock, missing contact and internal handoff.
Audit selected windows from request through appointment confirmation, carrier instruction and final receipt; the metric's value is a real appointment everyone can execute, not a fast automated reply.
In practice
Real-world examples.
Example
A customer requests Tuesday 09:00-11:00. The dock and carrier confirm at 14:00 Monday, with the request time retained for the lag. The report records the lag from the original request, not from the last email.
Example
Sales promises an hourly slot before transport is booked. The status stays unconfirmed until the necessary booking is secured. The customer is told the slot is requested, not yet confirmed.
Example
A customer moves the destination across town. The old dock appointment is cancelled and a new window confirmed. The revised lag is measured from the date of the change, and the earlier appointment is kept in the record.
Formula
Calculation
Lag = final required window confirmation timestamp - original qualifying window request timestamp. Show open requests near cut-off separately.
Worked example: five orders in a week have confirmation lags of 2, 4, 6, 6.5 and 30 hours. The median is 6 hours, but the mean is (2 + 4 + 6 + 6.5 + 30) / 5 = 48.5 / 5 = 9.7 hours, pulled up by one order whose dock contact could not be reached. Reporting the median alone would hide that order, so the 30-hour case is shown separately with its cause.Case study
Seen in the real world.
This fictional case follows Brookstone Kitchens. A customer requested an early delivery slot for an installation, but the carrier booked afternoon unloading without checking the customer dock. Sales found the conflict and arranged a different truck before confirmation.
The case is invented and does not describe a real delivery. Brookstone then added a rule that no window is marked confirmed until the carrier booking and the customer dock appointment both exist. Over the next month the median lag rose slightly, from 4 to 5 hours, but the number of rebooked deliveries fell, which the team judged a better trade.
Watch out
Common mistakes.
- Treating a delivery date calculation as an hourly dock confirmation.
- Promising a window before the carrier and customer receiving site agree.
- Resetting the lag clock when a customer follows up.
Questions
People also ask.
Is a quick confirmation proof of on-time arrival?
No. Arrival performance is a separate measure.
What if the requested slot is impossible?
Offer grounded alternatives and record the window the customer accepts.
Does every sale need a delivery window?
No. Include only orders where a specific slot is requested or required.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related