Capability template for operations and process improvement
Missed dock window recovery brief
The dispatch supervisor gets one brief when a truck misses its dock appointment and the reports disagree: each stated arrival time, the receiving cutoff, the appointment record and the questions that need a decision. It contacts no one and books nothing.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
When a truck misses its slot, three people usually say three different things. The driver gives one arrival time, the carrier's planner another, and the receiving office says what it will and will not take. Phone calls pile up and nobody is sure which statement is the newest or who said it.
This capability puts every stated arrival time on one page, in the order it was reported, each measured in minutes against the end of the appointment window and the receiving cutoff. It shows which source said what and how old each report now is, whether the latest times from different sources agree, and whether the cutoff the receiver quotes matches the one in the appointment record.
It also keeps three things apart that conversations blur. A late arrival counts as accepted only when the receiver said so; a driver passing on what the dock clerk said is shown as the driver's report. A possible fee is quoted from the record and never worked out. And the brief chooses nothing: it ends with the questions the facts raise, and the supervisor answers them.
Who starts the work, and when
A dispatch supervisor, or a dispatcher or dock coordinator on the supervisor's behalf, starts it when a truck has missed its appointment window and the reports differ. It can be run again when a new report comes in.
The supervisor confirms the facts and decides what happens next, including whether to ask for a changed appointment. The capability contacts no driver, carrier or receiver, books no slot, and changes no appointment.
What they supply
- The appointment record for the shipment: carrier, receiving site, date, window start and end, receiving cutoff, status and any fee terms.
- The reports received: for each, when it came in, who it came from, any arrival time or cutoff stated, whether the receiver was said to accept a late arrival, and what was said.
- Settings: the shipment reference, the date and time now, the supervisor's role, how far apart two arrival times may be and still agree, and how old a report may be before it is called stale.
Each file's column headers are checked first. If one does not match, the work stops and asks which column is which. It works from the notes and exports you supply and needs no connection to your transport or yard system.
What comes out
One brief in a fixed order: the appointment record, where things stand now, every stated arrival time, where the reports differ, the receiving cutoff, whether a late arrival is accepted, possible fees, data checks and a numbered list of questions for the supervisor. A section with nothing in it says "None."
Every minute count can be checked with a clock and the reports. Nothing is sent, booked or changed, and no recovery is chosen.
An invented example
Illustrative example with invented data. The site, the carrier, the shipment, the times and every statement below are invented. The site is an invented distribution depot, called the Depot here. The carrier is Carrier A. People are referred to by role. The dispatch supervisor asks for the brief at 14:20 on Tuesday 10 November 2026, after a truck has missed its appointment.
The inputs come first, in full, so the template can be run on them. The brief follows.
The inputs
1. Settings (typed by the dispatcher)
Shipment: S-4471
Site: the Depot
Now: 2026-11-10 14:20
Dispatch supervisor: not named, use the role
All other settings: use the defaults
2. Appointment record
shipment_ref,carrier,receiver_site,appointment_date,window_start,window_end,receiving_cutoff,appointment_status,fee_terms
S-4471,Carrier A,the Depot,2026-11-10,10:00,11:00,16:00,confirmed,Late-arrival charge may apply after window end. Amount not stated.
3. Reports
shipment_ref,reported_date,reported_time,source_role,stated_eta_date,stated_eta_time,stated_cutoff_time,receiver_accepts_late,statement
S-4471,2026-11-10,09:40,driver,2026-11-10,11:30,,,Traffic on the ring road. Expects 11:30.
S-4471,2026-11-10,11:05,dispatcher,2026-11-10,13:00,,,Driver called in about roadworks. Gave 13:00 as his estimate.
S-4471,2026-11-10,11:20,receiver,,,15:00,no,Nothing is received after 15:00 today. Has not agreed to a late slot.
S-4480,2026-11-10,12:10,dispatcher,2026-11-10,12:45,,,Other load. Running 20 minutes behind.
S-4471,2026-11-10,12:50,driver,2026-11-10,14:45,,yes,Says the dock clerk told him by phone they will take him.
S-4471,2026-11-10,13:30,carrier contact,2026-11-10,15:30,,,Last tracking ping 13:25 about 60 km from the Depot. Planner's ETA 15:30.
The brief
MISSED DOCK WINDOW RECOVERY BRIEF: S-4471, Carrier A
For: the dispatch supervisor. Prepared from: appointment record (1 row), reports (6 rows, 5 used), settings.
Column check: all headers matched.
Settings: now 2026-11-10 14:20; ETA tolerance 30 minutes; staleness limit 60 minutes. Defaults used: ETA tolerance, staleness limit.
Appointment record
Carrier A, the Depot, 2026-11-10: window 10:00 to 11:00, receiving cutoff 16:00, status confirmed. No change to the appointment is recorded here.
Position now
The window ended 200 minutes ago. The record cutoff of 16:00 is 100 minutes away. The cutoff the receiver stated, 15:00, is 40 minutes away.
Stated arrival times, in the order reported
09:40, driver: ETA 11:30. 30 minutes after the window ended; 270 minutes before the record cutoff. Said: "Traffic on the ring road. Expects 11:30." Earlier, replaced by the driver's report at 12:50.
11:05, dispatcher: ETA 13:00. 120 minutes after the window ended; 180 minutes before the record cutoff. Said: "Driver called in about roadworks. Gave 13:00 as his estimate." Latest from this source; reported 195 minutes ago, stale; the ETA passed 80 minutes ago.
12:50, driver: ETA 14:45. 225 minutes after the window ended; 75 minutes before the record cutoff. Said: "Says the dock clerk told him by phone they will take him." Latest from this source; reported 90 minutes ago, stale; the ETA is 25 minutes away.
13:30, carrier contact: ETA 15:30. 270 minutes after the window ended; 30 minutes before the record cutoff. Said: "Last tracking ping 13:25 about 60 km from the Depot. Planner's ETA 15:30." Latest from this source; reported 50 minutes ago; the ETA is 70 minutes away.
No arrival time: 11:20, receiver: "Nothing is received after 15:00 today. Has not agreed to a late slot."
Where the reports differ
Latest arrival times by source: dispatcher 13:00, driver 14:45, carrier contact 15:30. Earliest 13:00 (dispatcher), latest 15:30 (carrier contact), a spread of 150 minutes against a tolerance of 30: they differ.
Against the record cutoff of 16:00: dispatcher, driver and carrier contact are before or at it.
Against the stated cutoff of 15:00 (receiver): dispatcher and driver are before or at it; carrier contact is after it.
Receiving cutoff
Record: 16:00. Stated by the receiver at 11:20, 180 minutes ago: 15:00, which is 60 minutes earlier than the record. This brief does not say which applies.
Late arrival accepted?
Receiver, 11:20, 180 minutes ago: no. Driver, 12:50, 90 minutes ago: yes, reported by the driver and not confirmed by the receiver. The two conflict, and the later report does not settle it.
Possible fees
From the record: "Late-arrival charge may apply after window end. Amount not stated." No amount is worked out here.
Data checks
S-4480, dispatcher, 12:10: a report for another shipment; left out.
Questions needing a decision
1. Arrival time. The latest times differ by 150 minutes against a tolerance of 30: dispatcher 13:00 (passed 80 minutes ago, with no later report from that source), driver 14:45 (reported 90 minutes ago), carrier contact 15:30 (reported 50 minutes ago). Which arrival time is the working one, and does anyone need a fresh position first?
2. Cutoff. The record says 16:00; the receiver said 15:00 at 11:20, 60 minutes earlier. Which cutoff applies, and who confirms it with the receiver?
3. Late arrival. The receiver said it has not agreed to a late slot (11:20); the driver said the dock clerk would take the truck (12:50). Has the receiver accepted a late arrival, and who asks?
4. Appointment. Every latest arrival time falls after the window ended at 11:00, and the appointment is recorded as confirmed with no change. Is a changed appointment to be requested? Any request needs the supervisor's approval and the receiver's agreement; none has been made.
5. After the cutoff. The carrier contact's 15:30 is 30 minutes after the receiver's stated 15:00 cutoff, though before the record's 16:00. If the truck arrives after the cutoff that applies, who decides what happens to the load?
6. Fees. The record says a late-arrival charge may apply and gives no amount. Who owns the fee terms, and is anyone to check them before the truck arrives?
Draft for the dispatch supervisor's decision. Nothing has been sent, booked or changed, no one has been contacted, and no recovery has been chosen. Times are local to the Depot as of 2026-11-10 14:20.
Where it fits
- Operations and process improvement: a repeatable way to turn a scramble of calls into one set of facts.
- Supply chain and inventory: inbound loads that stock, production or customer orders are waiting on.
- Logistics and trade: carriers, dock appointments and receiving cutoffs are the daily material.
- Manufacturing: a late inbound load can hold up a production run that was scheduled around it.
- E-commerce and retail: inbound stock to a fulfilment site on a booked dock slot.
- Established businesses: when the cutoff and the fee terms live in people's heads and old emails.
- Growth and scaling: when there are more dock appointments than one supervisor can follow by phone.
It looks at one inbound truck and one missed slot. The review of orders that have not gone out is unshipped order review, the comparison of a supplier's promised and revised dates is supplier delivery date check, and the look at a carrier over time is carrier performance review.
What has to change for your company
- Your export or note layout, so the column check passes without a question.
- Your tolerance and staleness limit: how many minutes apart two arrival times may be and still agree, and how old a report may be before it is stale.
- Your roles: who the supervisor is, and who may ask a receiver for a changed appointment.
- Where your fee terms and cutoffs are recorded, so they are in the appointment record when the brief is run.
- Your AI product. It is written to run in ChatGPT, Claude, Copilot or Gemini from the files you supply. It sends nothing and never asks for a password or a login code.
What has been checked
Fully Powered AI wrote this capability template in its own words from its own map of the work, with no third-party text. It was editorially reviewed on 10 November 2026. It was tried once on its invented example in Claude on 10 November 2026, and the record is published with it. It has not yet been tested in a client environment.
Testing in your environment means running it on a missed appointment your supervisor remembers well, plus cases written in advance with their expected results: a renamed column, two sources giving arrival times far apart, a receiver cutoff that differs from the record, a driver saying the dock will accept the truck while the receiver says it has not agreed, a blank fee term. The supervisor checks every time and every minute count against the reports before anyone acts.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: