What does "out for delivery" mean?
Out for delivery means a parcel has been loaded onto a delivery vehicle at the depot that serves the destination address, and that a driver is working the round it belongs to that day. The status is produced by a load scan taken before the vehicle leaves the building, not by the driver approaching the address, which is why it can appear long before anything arrives. On an average United States Postal Service route the address is one of roughly 721 delivery points the vehicle covers. It is a custody event with a strong same-day expectation attached, not a delivery commitment.
The load scan that sets the status
The status comes from a scan taken at the delivery depot as the parcel is loaded onto the round vehicle, and on most postal operators it is one of only 2 scans a parcel is guaranteed to receive. The parcel reaches that depot on an overnight or early trunk movement, is sorted to a route, and is loaded in stop order. The scan records the moment it joins the route, and nothing about how far it is from the address.
That distinction is the whole reason the status behaves the way it does. A parcel scanned onto a route is physically at the depot at the moment of the scan, which for most addresses is further away than it was an hour earlier at the inbound dock. The status describes custody transfer to a driver, and custody transfers happen at the depot.
Route scale is what turns that one scan into a full day of waiting. The Postal Service served 170.4 million delivery points across 236,347 delivery routes in fiscal year 2025, an average of about 721 delivery points per route (USPS Postal Facts, Size and Scope). One vehicle works that sequence in a fixed order, so the same scan means a short wait for the first address on the list and a full shift for the last.
Some operators scan an entire cage or route consignment in a single pass rather than item by item. Where that happens, dozens of parcels share one timestamp to the second, which is a reliable sign that the time shown is a loading time rather than a departure time.
Where the status sits in the scan sequence
A domestic parcel can complete its whole journey with as few as 2 recorded scans, and out for delivery is one of them. Everything between acceptance and the depot is optional detail that varies by operator and by how many sorting centres the item passes through. The two ends of the sequence are the ones every tracked service records.
| Event | Physical trigger | Where the scan happens | Typical timing |
|---|---|---|---|
| Item accepted or posted | Sender hands the item over and the barcode is activated | Counter, drop-off point or collection vehicle | Once, at handover |
| In transit or departed facility | The item moves between sorting centres | Hub conveyors and dock scanners | 0 to several times, once per leg |
| Arrived at delivery depot | The item reaches the office that serves the address | Inbound dock of the final depot | Once, usually overnight |
| Out for delivery | The item is loaded onto the round vehicle | Delivery unit, before the vehicle departs | Once per delivery day attempted |
| Delivered | The item is handed over or left in the agreed place | Handheld device at the address | Same working day as the load scan |
| Delivery attempt made | The driver reached the address and could not complete | Handheld device at the address | Same working day, retry the next business day |
| Available for pickup | The item is taken to a retail counter or locker | Retail office on the vehicle's return | Same day or the following morning |
Only 2 events in that list are recorded at the address itself, the delivery and the attempt. Every other event is recorded inside a building. Canada Post publishes the paired status Delivery Attempt Made / Rescheduled for delivery next business day, which is the standard shape of the outcome when the driver reaches the address but cannot complete the stop.
How long the status normally lasts
The status is built to resolve inside a single working day, and the interval between the load scan and the outcome scan is the length of the route worked up to that address. An address near the front of a 721-point sequence clears within the first part of the shift. An address near the end clears at the close of it, on the same service and the same vehicle.
No operator publishes a per-stop interval, so any figure at the hour level is an estimate rather than a commitment. The estimate that holds across operators is that the status resolves on the working day it appeared, or produces an attempt event on that day. The clock window the round is worked inside is a separate question, covered on the usual delivery hours.
The status carrying over into a second working day with no new event is the real anomaly. Two consecutive working days on the same line, with no attempt scan and no delivery scan between them, means the parcel almost certainly did not travel on the vehicle the scan assigned it to.
The same parcel can also collect the status more than once. A parcel loaded, returned to the depot undelivered and loaded again the next morning produces a second load scan, and a well-behaved tracking page shows both.
Why the tracking page freezes on it all day
Most operators record no scan at all between loading the vehicle and completing the delivery, so a page frozen on this status for 8 hours is normal behaviour rather than a fault. Canada Post states the scan pattern plainly.
"Typically, we scan a package when it's first mailed and again when it goes out for delivery."
Canada Post, Why is my tracking status not updating?, accessed July 2026 (Canada Post, Tracking status not updating).
There is no mid-route scan to record. A driver scans at the address, not between addresses, so the record holds nothing to publish until the stop is worked.
The whole route was scanned in one batch. Where a depot scans a cage rather than individual items, the timestamp is the loading time for every parcel in it, and nothing in the data distinguishes the first stop from the last.
The vehicle has not left. The scan is taken before departure, so a parcel can hold the status while still sitting on a dock inside the depot.
The outcome scan failed or was taken late. Handheld devices upload in batches, and a delivery worked in a poor signal area can post its scan hours after it happened.
The number being watched is not the number being scanned. Marketplace order pages and consolidator references often carry their own identifier, and the symptoms of that mismatch are set out in a tracking number that is not found or shows the wrong shipment.
What the status does not promise
No operator attaches a refund or a guarantee to the out-for-delivery scan, because the only time commitments that carry money are properties of the service bought rather than of a scan event. The scan is an operational record generated by the depot, and its accuracy has been audited. The United States Postal Service Office of Inspector General reviewed 500 packages pulled from facilities across 25 states and found the messaging wrong in most of them.
"Messages for 318 of 500 packages (64 percent) did not accurately reflect the location, time, and/or date." Of those, "messages for 163 packages indicated 'Out for Delivery' when they were still at the post office."
USPS Office of Inspector General, Package Tracking Messaging, report 22-159-R23, 11 May 2023 (USPS OIG, Package Tracking Messaging).
Three things the status is routinely read as saying, and does not say: that the parcel is near the address, that the vehicle has departed, and that the parcel is physically on that vehicle. It says a scan was taken against a route. Everything else is inference.
What it does say is strong enough to be useful. An outcome event that day is the designed behaviour, and on a normal day it is what happens. The status is a high-probability signal, not a contract.
This scan is the cut-off for changing the delivery
The out-for-delivery scan is the point at which redirection and delivery-change requests stop being accepted, which makes it the last moment a recipient has any influence over where the parcel goes that day. Australia Post, which labels the same event onboard for delivery, states the boundary exactly.
"You can request to have your parcel redirected once your parcel leaves the sender right up until it's onboard for delivery."
Australia Post, Parcels in transit, accessed July 2026 (Australia Post, Parcels in transit).
The mechanism behind the cut-off is physical rather than administrative. A redirection instruction has to reach the depot while the depot still holds the parcel; once the item has joined the stop sequence of one of the 236,347 routes running that day, there is nothing at the depot to act on. The instruction has nowhere to land.
Anything set in advance still applies, because it travels with the record rather than being requested against it. Safe-place preferences, signature waivers and nominated neighbours are all evaluated by the driver at the stop. What can no longer be changed is which round the parcel is on and which address it is going to.
Operator and marketplace wording for the same event
The same depot load scan is published under at least 2 different labels across the major operators, and the difference is wording rather than mechanism. Canada Post and the Postal Service both display out for delivery. Australia Post displays onboard for delivery for the identical event. FedEx, UPS, DHL, Royal Mail and Evri each publish their own string for the stage; the underlying event in every case is the scan that assigns the parcel to a round.
Address type changes what happens after the scan more than the wording does. The Postal Service served 157.8 million residential addresses and 12.6 million business addresses in fiscal year 2025, and the same status string covers both, even though a closed reception desk ends the working day for a business stop while a residential stop stays workable for hours longer.
Marketplace order pages add a second layer. AliExpress, Shein, Temu and Amazon do not run the final leg for most orders in Europe and North America; a local carrier does, and the marketplace mirrors whatever that carrier reports, often with a delay and often in its own vocabulary. A parcel showing out for delivery on the carrier page and shipped on the marketplace page is one parcel with two publishers, not two shipments.
Consolidated cross-border items behave the same way. The seller's own tracking stops updating when the item leaves the outbound network, and the destination operator's record starts when it enters the domestic one, which is where this status eventually appears.
When the day ends and nothing has arrived
A round that ends without a delivery produces 1 of 2 outcomes, and only one of them is a problem. An attempt event, a notice or a card means the driver reached the address, the process moved forward, and the parcel is now in a defined aftermath: retry, pickup point or return. That sequence is covered on what happens if delivery fails.
The day closing with no new event at all is the case worth acting on. It usually means the parcel was scanned to a route it did not travel on, was missorted at the depot, or was left behind when the vehicle filled. The normal correction is automatic: the parcel is loaded the following working day and the status appears a second time.
Waiting 1 further working day before contacting anyone is what almost every operator asks for, because the second load scan resolves most of these cases without intervention. Beyond that, the thresholds are formal. The Postal Service accepts a Missing Mail search request 7 days from the mailing date (USPS, Missing Mail).
Who to contact depends on who holds the contract. The recipient of a marketplace or retailer order has no contract with the carrier, and the seller is the party that can open a claim; a shipper who booked the carriage directly raises it with the carrier. Approaching the wrong party is the most common reason a genuine failure sits unresolved for a week.
What it gets confused with
The nearest neighbour is in transit, which covers every movement between facilities and can persist for several days, while this status covers a single working day and a single vehicle. The other confusions are with events that look like progress and are not, and with the retail counter as an endpoint: a diverted parcel ends up at a staffed location, and the Postal Service alone operates 30,972 of them.
| Status | What it actually records | How it differs |
|---|---|---|
| In transit | Movement between facilities, or nothing new since the last hub scan | Can last days, and no vehicle is assigned to the address. See what in transit means |
| Onboard for delivery | The same depot load scan, under Australia Post wording | Identical event, different published string |
| Arriving today or expected today | A forecast produced by the operator's estimate, not a scan | Can show before any load scan exists |
| Delivery attempt made | The driver reached the address and could not complete | An outcome event, not a stage, and it ends the delivery day |
| Available for pickup or notice left | The parcel was taken to a counter, locker or access point | The parcel is stationary again and a retention clock starts |
| Out of delivery | Not a status any operator publishes | A misreading of the same string, not a separate event |
The practical reading is to treat the full scan history as the record and the last line as a headline. A load scan followed by an outcome scan on the same day is a completed story. A load scan with nothing after it by the following morning is the point at which the next load scan, rather than a phone call, is the thing to watch for.