Research question and scope

This protocol measures how often a courier pickup misses the booked cut-off. The unit is one pickup request that was assigned to a carrier for a specific day. A miss means the carrier did not collect the parcel within the confirmed window. The measure describes the dispatch promise and the carrier route, not the effort of the desk.

Set the scope to one warehouse, one carrier set, and a fixed period. Record the staffed hours, the service levels, and the time zone used for the cut-off. If the carrier changes a route during the period, split the sample at the change date. A different route creates a different expectation.

Keep the measure separate from a customer delivery score. A pickup can be on time and the delivery late, or the reverse. The purpose is to test the collection promise. Report the two measures separately so neither hides the other.

Population and unit of analysis

Define the population as every pickup request that entered the dispatch queue during the period. Include requests that were collected and requests that were missed. The unit is the request, not the parcel line. A single pickup with six parcels is one collection event.

Include requests that were cancelled before the carrier arrived, and report them separately from misses. A cancellation is not a carrier failure. Exclude requests that were never booked with a carrier. The boundary should be visible in the report.

Include requests that were booked after the cut-off and still collected. Mark them as late bookings but not misses. The distinction shows whether the desk recovered a late request. A rate that ignores late bookings will overstate the carrier's performance.

Definitions that make the measure reproducible

Define the cut-off as the time confirmed in writing for that carrier and service level. Define the pickup window as the period the carrier promised for arrival. Define a miss as no collection before the end of that window. Publish one example of an on-time and a missed pickup.

Define a late booking as a carrier confirmation recorded after the cut-off. Define an intake miss as a request that arrived after the desk's internal release time. The two are related but not identical. Record both timestamps so a reviewer can classify the case.

Decide how to treat a partial collection where some parcels were taken and others were left. Mark it as partial with the count collected and the reason. Do not count it as a full miss or a full success. The detail explains a customer promise that may still be at risk.

Sampling and data collection

Draw the sample from the dispatch queue and the carrier confirmation export for the full period. Record the export date, the filters, and the row count. Do not build the sample from missed-pickup emails alone. A sample built from complaints cannot produce a rate.

Capture the request identifier, the arrival time, the booking time, the carrier, the route, the confirmed window, the collection time, and the outcome. Add the customer promise and the order value where available. Store the export with the report. The timestamps are the core evidence.

Check a small overlap sample with a second reviewer. If the reviewers disagree about whether a collection was inside the window, the window definition is too vague. Rewrite the rule and retest before the full sample. Agreement matters more than sample size.

Record the time spent reconciling the carrier portal with the queue. A report that requires manual matching for every row will not be repeated. Note the fields that the carrier does not expose. The collection cost belongs beside the result.

Measuring missed pickups

Report the share of requests collected inside the window, the share collected late, and the share not collected. Show the counts behind each share. The three groups describe different failures and should not be collapsed into one rate. A single miss rate hides whether the problem is timing or collection.

Break the result down by carrier, route, day of week, and hour of booking. A single route with repeated misses may need a different cut-off. A carrier with failures across routes may need a service review. Compare only groups with similar volume and service level.

Report the median and longest delay for late collections. A pickup missed by twenty minutes is different from one missed by a day. The delay distribution shows whether the problem sits at the boundary or earlier in the route. Include the confirmed window in the report.

Limitations and next action

The measure cannot show a customer who arranged a private courier or a parcel that was handed over outside the booking. It also cannot show whether the carrier's scan was accurate. Treat the result as a measure of the dispatch promise. Note the routes and service levels that were not included.

Give the result to the dispatch owner and the carrier contact with one change to test. The change might be an earlier release time, a different route, or a revised booking form. Record the effective date and repeat the measure with the same definitions. A controlled change is easier to judge.

Review the boundary cases before changing the whole cut-off. A few requests received in the last minutes may explain a large share of the misses. Fix the intake rule first if that is the pattern. The goal is a promise the desk can keep, not a lower number by definition.