What this is
What is a delivery appointment record?
What is a delivery appointment record?
It is the record that books an inbound delivery into a dock slot and then captures whether reality matched the booking — arrival time, vehicle type, paperwork, load, and who caused any delay. It exists so that a late or unbooked arrival is a fact on a form rather than a disagreement in the yard.
What does 'arrived within the slot' actually mean?
It means the vehicle presented at the dock inside the window defined by Slot Booked For and Slot Length Minutes, not simply that it turned up on the right day. A vehicle that arrives four hours early or ninety minutes late has still missed its slot, because the labour and dock capacity were planned around the booked window, not the vehicle's own schedule.
What is detention, and when does it become chargeable?
Detention is the vehicle standing at site beyond the agreed free time, captured here as Minutes Beyond Free Time. Whether that time is chargeable is a commercial question, not an automatic one: it depends on who caused the delay and what the carrier contract's free-time terms say. Marking Detention Chargeable without that reasoning behind it produces a number nobody can defend.
Scope
When is a delivery appointment record required?
This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later, and disputes that can't be reconstructed from either one.
Use this template when
- A supplier or carrier has requested a dock slot and it needs to exist in the system before the vehicle sets off
- A vehicle has arrived, or is about to, and its actual timings, paperwork and load need checking against what was booked
- Turnaround needs a cause attached — dock, labour, equipment, or a party at fault — so a delay isn't just a number
- Detention time is being considered for a charge and needs a record that can stand up to the carrier disputing it
- A linked record needs this one to exist first: it feeds Receiving Inspection and Carrier Service Failure
Do not use it for
- Receiving Inspection Record, which checks an inbound delivery against the purchase order and the specification before it is accepted into stock.
- Over Short and Damaged Report, which records a discrepancy between what was ordered, what the paperwork says and what physically arrived.
- Container and Trailer Seal Check, which verifies the seal number against the paperwork and records its condition before the doors are opened.
- Container Devanning Record, which covers what happens once the vehicle is at the dock and unloading is under way, not whether it got there on time.
- Anything outside KnowLogistics, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 9001 cl.8.4 requirements does this satisfy?
ISO 9001 cl.8.4 covers control of externally provided processes, products and services; a carrier delivering to your dock is exactly that, and the clauses below map onto the fields that make the control real rather than nominal.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.4.1 | Confirm the carrier is an approved external provider before a slot is booked against them. | Header |
| ISO 9001 cl.8.4.3 | Capture what was communicated to the carrier — booking source, slot time and slot length — at the point the appointment is made. | Header |
| ISO 9001 cl.8.5.1 | Verify the arriving vehicle, its paperwork and its load against what was actually booked before unloading proceeds. | Arrival |
| ISO 9001 cl.7.1.3 | Record that the dock, labour and equipment needed to receive the load were actually available on arrival. | Turnaround |
| ISO 9001 cl.8.7.1 | Attribute any delay to a cause — an internal failure or the carrier's — rather than leaving the gap unexplained. | Turnaround |
| ISO 9001 cl.8.5.2 | Link the appointment to the receiving record and, where detention applies, the detention log, so the chain stays traceable. | Outcome |
| ISO 9001 cl.9.1.3 | Roll turnaround minutes and score percent into a result band that can be trended across sites and carriers. | Outcome |
What it does not cover
- A booking with no slot time entered, which means Arrived Within The Slot can only be answered by guesswork.
- A Detention Chargeable of Yes with no Detention Log ID, which leaves a cost claim with nothing behind it if the carrier disputes it.
- A Result Band of Pass sitting next to a low Completeness Percent, which reports a clean score on a form nobody actually finished.
- Delay Caused By Us and Delay Caused By The Carrier both marked No for the same late arrival, which means the turnaround gap has no owner at all.
- An Action Required of No next to a Fail result, which closes the record without raising the corrective action the failure should trigger.
Global
Delivery Appointment Record requirements by country
A delivery appointment sits inside the carrier's contract and driver hours-of-service law as much as inside your own SOP, so the same late arrival can carry a different consequence depending on the vehicle's origin.
FMCSA hours-of-service rules (49 CFR Part 395)
Detention time at your dock eats directly into a driver's legally limited on-duty clock.
A late or over-length appointment can force the carrier's driver into a compliance violation, which is exactly the argument carriers use to dispute a detention charge you thought was straightforward.
Regulation (EC) No 561/2006 on driving and working time
Driver hours are regulated the same way, so an overrun slot has the same knock-on effect on carrier compliance.
Where the load also crosses a border, the CMR Convention governs the carrier's liability for the goods themselves — separate from whether your dock caused the delay.
Carrier service agreement free-time and detention terms
Unlike hours-of-service, whether detention is chargeable at all is set by the contract with that carrier, not a regulation.
Detention Chargeable is a judgement against a specific agreement, which is why the record needs a Detention Log ID behind it rather than the tick-box alone.
How to complete it
How to complete a delivery appointment record, step by step
Filling in every field correctly still leaves four judgement calls that decide whether the record holds up when someone disputes it later.
Dock unavailable, labour short, and the carrier itself late — Delay Caused By Us and Delay Caused By The Carrier aren't mutually exclusive in reality, but the form records a single attribution each. Someone has to decide which cause gets recorded when more than one genuinely applied, and that needs a rule, not a mood.
Entering Detention Chargeable at goods-in, before the commercial conversation with the carrier has happened, turns the tick-box into evidence rather than a verdict. Treating it as a verdict and closing the record removes the carrier's chance to contest it before money changes hands.
Temperature Declared Where Required and Vehicle Type As Declared both carry an N/A option, and N/A items leave the denominator entirely rather than counting against the score. That's correct when the field genuinely doesn't apply, and a quiet way to protect a score when it does.
Result Band has three states, and Caution sits below Pass without automatically forcing Action Required to Yes. Whether Caution gets raised as an action or just logged is a threshold call that decides whether a drifting carrier is caught before it becomes a Fail.
What auditors find
Most common delivery appointment record findings
Six patterns that show up when this record is reviewed against its own fields, not against a generic checklist.
| Finding | Clause | What fixes it |
|---|---|---|
| Slot Booked For is entered after Actual Arrival, so Arrived Within The Slot is answered retrospectively rather than checked against a pre-existing booking. | ISO 9001 cl.8.4.3 | Require the slot time to be captured when the booking is taken, before the appointment can be marked Planned. |
| Delay Caused By Us and Delay Caused By The Carrier are both marked No against a turnaround that clearly overran, with no note reconciling the gap. | ISO 9001 cl.8.7.1 | Block submission when Turnaround Minutes exceeds a threshold unless one delay-cause field is marked Yes. |
| Detention Chargeable is marked Yes with the Detention Log ID field left blank. | ISO 9001 cl.8.5.2 | Make Detention Log ID conditionally required whenever Detention Chargeable is Yes, matching how CAPA ID is gated on Action Required. |
| Result Band shows Pass on a record where Completeness Percent is well under full, since the score is calculated only on fields actually answered. | ISO 9001 cl.9.1.3 | Display Completeness Percent alongside Result Band wherever the score is reported, so a partial form can't present as a clean pass. |
| Vendor ID is entered by hand rather than pulled through from the FDN-005 link, and occasionally doesn't match the Carrier selected. | ISO 9001 cl.8.4.1 | Auto-populate Vendor ID from the linked FDN-005 record once Carrier is selected, and lock manual entry. |
| Action Required is marked No on records where Result Band is Fail. | ISO 9001 cl.8.7.1 | Force Action Required to Yes whenever Result Band is Fail, rather than leaving it an independent call. |
Case in point
Case in point: the phone booking that wasn't
A carrier calls ahead to move a delivery forward a day. Nobody enters it as an appointment — it's a diary note, then not even that. The vehicle arrives to find two portal-booked deliveries already occupying the dock. Goods-in has a choice: mark Arrived Within The Slot as No against a booking never properly logged, or fudge it to avoid an argument neither side can win from the paperwork that exists.
Once Booking Source became required and phone-booked slots had to be entered within a fixed window of the call, the scenario resolved differently: the record showed a Standing slot changed by phone, a timestamp for when that happened, and a genuine dock conflict rather than a dispute over whose memory of the call was right.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- LOG-001
- Archetype
- Record
- Record ID
- APPT-2026-000
- Scoring
- On time arrival
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 9001 cl.8.4
- Links
- Feeds Receiving Inspection and Carrier Service Failure
- Tags
- Inbound, Dock, Scheduling
- Sections
- 4
- Fields
- 49
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 5
Header
15 fieldsAppointment ID*
Auto sequence. Format APPT-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Carrier*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Booking Source*
Portal, email, phone or standing slot. Phone bookings are the ones that vanish.
Purchase Order Reference
Booked In Advance*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Slot Booked For*
Slot Length Minutes*
Dock Assigned
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
The Booking Is The Problem, Not The Dock
Receiving chaos is almost always a booking that was never made, was made for the wrong duration, or was made and then ignored. None of that is visible while bookings live in an inbox.
Arrival
6 fieldsArrived Within The Slot*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Arrived Without A Booking*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Vehicle Type As Declared*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Driver Had Correct Paperwork*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Load Matched The Booking*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Temperature Declared Where Required*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Turnaround
6 fieldsUnloading Started On Time*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Dock Available On Arrival*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Labour Available*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Equipment Available*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Delay Caused By Us*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Delay Caused By The Carrier*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Outcome
22 fieldsActual Arrival
Unloading Started
Vehicle Released
Turnaround Minutes
Minutes Beyond Free Time
Detention Chargeable*
- Yes0 pts
- No2 pts
- N/Aexcluded from denominator
Receiving Record ID
Links to LOG-002 Receipt ID
Detention Log ID
Links to LOG-026 Log ID
Carrier Informed Of The Failure*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Items Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Goods In*
Signature*
Warehouse Manager*
Second Signature*
LOG-001 · record IDs look like APPT-2026-000 · Feeds Receiving Inspection and Carrier Service Failure
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping the booking current before the vehicle arrives, and holding the delay-attribution and detention evidence together afterwards, is the work that actually slips.
Holds the appointment against the dock schedule, flags a booking with no slot time before the vehicle is due, and keeps Detention Log ID and Receiving Record ID linked once the delivery closes out.
Cross-checks the Carrier and Vendor ID against its own approved-carrier and vehicle records, so a mismatch between what was booked and what turned up gets caught rather than just logged.
Rolls Score Percent and Result Band across sites and carriers into one trend, and surfaces a Caution pattern before it becomes a Fail that nobody raised as an action.
Coordinates the crew across the linked records, chases the delay-attribution and detention fields that got left blank, and holds every write for your approval before it touches a live record.
This template lives in KnowLogistics — supply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.
Glossary
Delivery Appointment Record definitions and key terms
- Detention
- Time a vehicle stands at the dock beyond the agreed free time, tracked here as Minutes Beyond Free Time. Detention is a duration; whether it converts into a charge is a separate, contractual question.
- Free time
- The period a carrier's vehicle can occupy a dock before detention charges can apply, set by the carrier agreement rather than by this record. The record measures against it; it doesn't define it.
- Turnaround
- The elapsed time from a vehicle's actual arrival to its release, captured in Turnaround Minutes. It's a measure of dock and labour performance, not of whether the appointment itself was honoured.
- Standing slot
- A recurring booking held open for a carrier that delivers on a fixed schedule, one of the four Booking Source options. It removes the need to rebook every trip, but also removes the prompt to actively confirm each one.
- OTIF
- On Time In Full — a standard logistics measure combining timeliness and completeness of a delivery. This record supplies the timeliness half directly; completeness is judged by the linked Receiving Inspection Record.
FAQ
Frequently asked questions about delivery appointment record
Does a slot need to be booked before a vehicle can be logged as arriving?+
Not technically — Arrived Without A Booking exists because it happens. But the record is designed around the booking existing first: Slot Booked For and Booking Source are meant to be entered when the appointment is made, with Arrival fields completed once the vehicle turns up.
What happens if a carrier arrives without ever booking a slot?+
Arrived Without A Booking is marked Yes, which scores against the record. Whether the vehicle is turned away or squeezed into the schedule is an operational decision the record documents rather than makes, but an unbooked arrival should still generate a Turnaround entry if received.
Why does the record need two separate sign-offs?+
Goods In captures the operator who worked the delivery, and Warehouse Manager with a second signature provides the review layer that catches a Fail or Caution before it's treated as closed. Splitting them stops one person booking, receiving and signing off the same appointment unchecked.
Does marking a field N/A hurt the score?+
No — N/A items leave the denominator entirely rather than scoring as a failure, which makes Score Percent comparable between deliveries where, say, temperature declaration genuinely doesn't apply. It's also worth checking N/A for pattern abuse on any one carrier or site.
What happens once Action Required is set to Yes?+
Priority, CAPA ID and Action Owner all become visible, and the help text is explicit: raise the action record first, then enter its reference here. This record doesn't run the corrective action, it points to where that action lives.
Can this record be used to build a carrier scorecard?+
It's one input, not the whole thing. Score Percent and Result Band trend a single carrier's on-time and turnaround performance over repeated appointments, but a full scorecard also needs the Receiving Inspection Record and Over Short and Damaged Report for quality and accuracy.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Inbound and Receiving
Vendor and Contractor Register
Holds every supplier, contractor and service provider you work with, including their status and approval level
Receiving Inspection Record
Checks an inbound delivery against the purchase order and the specification before it is accepted into stock
Over Short and Damaged Report
Records a discrepancy between what was ordered, what the paperwork says and what physically arrived
Container and Trailer Seal Check
Verifies the seal number against the paperwork and records its condition before the doors are opened
Container Devanning Record
Records the unloading of a shipping container, covering condition, contamination, count and the conditions inside
Inbound Quality Gate
Holds a receipt until the checks that must happen before it enters usable stock are complete
More in Inbound
Receiving Inspection Record
Checks an inbound delivery against the purchase order and the specification before it is accepted into stock
Over Short and Damaged Report
Records a discrepancy between what was ordered, what the paperwork says and what physically arrived
Container and Trailer Seal Check
Verifies the seal number against the paperwork and records its condition before the doors are opened
Container Devanning Record
Records the unloading of a shipping container, covering condition, contamination, count and the conditions inside
Inbound Quality Gate
Holds a receipt until the checks that must happen before it enters usable stock are complete
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 cl.8.4 — Control of externally provided processes, products and services
- ISO 9001:2015 cl.8.5.1 and cl.8.5.2 — Control of production and service provision; identification and traceability
- 49 CFR Part 395 — FMCSA hours-of-service regulations (United States)
- Regulation (EC) No 561/2006 — driving and working time rules (European Union)
- CMR Convention — Convention on the Contract for the International Carriage of Goods by Road
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.