The Doorstep Date: Planning December Deliveries From Arrival, Not Dispatch
Most organisations can produce, at short notice, a list of December deadlines: sign-off dates, submission windows, invoicing cut-offs, the day the finance team closes the ledger. Very few can produce the one date that decides whether any of it mattered — the day a physical item has to be in someone else's hands.
That gap is worth closing before the middle of December, because the moment a parcel, contract or component leaves the building, the plan changes character. Up to dispatch, you are managing effort. After dispatch, you are managing custody, tracking and exceptions — and in the final weeks of the year, the carrier networks you rely on are operating under different conditions from the ones you priced in during September.
The gap between dispatch and arrival
Internal deadline plans tend to measure the wrong event. A document that is 'sent' on 18 December has met an internal target and nothing else. It has not met a client's requirement, satisfied a contractual date, or reached a site before it closed. Dispatch is a transfer of custody; arrival is the outcome. Only one of those belongs on a plan that is meant to hold.
This distinction matters more in December than at any other point in the year. Seasonal volumes rise, guarantees are suspended or amended, and collection times move earlier. A parcel accepted on a published cut-off date is not promised to move that day; it is merely accepted. Treat the distinction literally.
Start with the receiving constraint
The first column of any December dispatch plan should not be 'date sent'. It should be 'date that must arrive', followed immediately by 'what has to be true at the other end for arrival to count'.
For each item, capture four things:
- The date and, where it matters, the time by which it must be received.
- The receiving location and whether anyone will be there. A client office that closes on 24 December may effectively have a 22 December deadline.
- Any signature, identity check or booked slot required on delivery.
- What the recipient will do with it — countersign, inspect, log, forward — and how long that takes.
A surprising number of December failures are not transport failures at all. They are receiving failures: a delivery attempted against a closed site, a signature required from someone on leave, a proof of delivery that arrives after the meeting it was meant to support.
Published cut-offs are ceilings, not targets
Royal Mail, Parcelforce and the main UK couriers publish seasonal last posting and dispatch dates each autumn. When the 2026 dates are confirmed, record them directly from each carrier rather than from a screenshot of an earlier year; services, surcharges and exceptions change.
Then apply the correct reading. A published cut-off is the latest date on which the carrier will accept an item for a given service. It is not a recommendation, and it is not a guarantee of movement. In practice, capacity on the final days is finite and the queue behind the cut-off is the longest of the year.
For anything that matters — a signed contract, a tender submission, a statutory notice, a replacement part holding up a site — the published date should sit in the plan as a limit you intend to stay well clear of.
Set internal dates a few working days ahead
This is where the plan becomes workable. For standard tracked services within the UK, an internal dispatch date two to three working days before the published cut-off is usually prudent. For signed-for, international or freight movements, allow more.
Working days, not calendar days. In 2026, Christmas Day falls on a Friday and Boxing Day on a Saturday, with the substitute bank holiday on Monday 28 December. A parcel dispatched on Friday 18 December may not move meaningfully until Monday 21. New Year's Day 2027 falls on a Friday, which extends the recovery period into the first week of January.
A simple rule helps: count backwards in working days, mark every non-working day explicitly, and never let a dispatch date fall on the last working day before a closure unless the item is genuinely low-risk.
Signature and proof-of-delivery dependencies
For some items, delivery is not the deadline; evidenced delivery is. Contracts, notices, examination scripts and regulated documents often need a signature, a timestamp or a retrievable proof of delivery.
Build a verification window into the plan. Decide in advance who checks tracking, at what point each day, and what triggers an escalation. A failed delivery attempt on 23 December is recoverable if someone notices on 23 December; it is not recoverable if the first check happens on 4 January.
Treat the proof of delivery as a deliverable in its own right. File it where the person who needs it can find it without asking, and note in the plan where it will be stored.
The one-page December dispatch worksheet
A single page is enough. Nine columns, completed for each item and reviewed weekly until dispatch:
- Item and reference.
- Must-arrive date, with time if relevant.
- Recipient, address and receiving constraint.
- Service level and whether a signature is required.
- Published carrier cut-off for that service.
- Internal dispatch date, set ahead of the cut-off.
- Owner for dispatch.
- Owner for tracking and proof of delivery.
- Escalation trigger and contact.
At the foot of the page, add two lines: the date by which a failed delivery must be escalated, and the name of the person authorised to arrange a courier upgrade or hand delivery. Those two lines convert a list into a decision-making instrument.
A countdown that survives contact with December
The purpose of this exercise is not to add process for its own sake. It is to move the centre of gravity of the plan from the outbox to the doorstep, where the actual commitment sits.
Done properly, 'before Christmas' stops being a phrase and becomes a sequence of dated decisions: this item leaves on the 15th, that one on the 17th, this one needs a signature and is tracked daily from the 18th. That is a deadline plan you can defend — and, more importantly, one that will still be true when the carrier's network is at its busiest.