Research question and scope
This protocol measures how often a lost-parcel tracer packet lacks a usable carrier scan reference. The unit is one tracer case opened for one parcel. A usable reference includes the tracking number, the last scan time and location, and the carrier case identifier. The measure describes packet readiness, not whether the carrier finds the parcel.
Set the scope to one client, one carrier mix, and a fixed period. Record the tracer template and the carrier requirements in force. If the carrier changed its portal or required fields during the period, split the sample at the effective date. A different requirement creates a different denominator.
Keep the measure separate from the customer outcome. A complete packet can still end in a lost-parcel refund, and an incomplete packet can still be resolved by a helpful carrier agent. The purpose is to test the desk's evidence, not the carrier's decision. Report the outcome separately.
State the decision the result will support before collection begins. The client may use it to add a scan export, change the tracer template, or move the carrier case opening earlier. Write the intended action beside the scope. A measure with no decision becomes a monthly count.
Population and unit of analysis
Define the population as every tracer case opened during the period. Include cases opened by the desk, the warehouse, and the customer service team. The unit is the tracer case, not the parcel or the customer. A parcel with two tracer cases is two units when each case has its own packet.
Exclude cases closed before any packet was assembled, such as a wrong tracking number corrected at intake. Record the excluded count and the reason. A case that never became a tracer is not a tracer packet. Report the exclusion so the reader can judge the mix.
Include cases opened through any carrier channel, including phone, portal, and email. Record the channel and the role that opened the case. Leaving out a phone channel hides a common source of missing references. State the inclusion rule before drawing the sample.
Decide how to treat a tracer that was reopened after a carrier response. Score the original packet first, then note the reopened packet separately. Record the reopen time and the new evidence. A reopened case is still evidence of the first packet's quality.
Definitions that make the measure reproducible
Define a complete tracer packet as one with the order identifier, tracking number, ship date, full scan history, recipient address, and carrier case reference. Define a partial packet as one missing one or two items. Define a failed packet as one missing three or more items or missing the carrier submission. Give one example of each before sampling.
Define a usable scan reference as a dated event with a location and a status, not a bare tracking number. A tracking number with no movement is a different fact from a parcel with no scan at all. Record both. The reviewer should not have to infer the difference.
Define the carrier case reference by the identifier the carrier returns after submission. A queue ticket or an internal case number is not a carrier reference. Record the source and the time. The distinction matters when the desk tries to escalate.
Define a slow response separately from a missing record. A packet can be complete and still wait past the carrier's deadline. Record the submission date and the response date. The report should show both readiness and cycle time.
Sampling and data collection
Draw the sample from the tracer log for the full period. Record the export date, the carrier filter, and the row count. Do not build the sample from cases the client escalated or from parcels that were eventually found. A selected sample cannot show the everyday packet.
Capture the case identifier, the order, the carrier, the queue, the opener role, the submission time, the scan fields, and the carrier reference. Add the template version and any reopen. Store the packet copy with the report. The packet and the template are the core evidence.
Check a small overlap sample with a second reviewer. If the reviewers disagree about whether a status page counts as a scan history, the definition is too vague. Rewrite the definition and retest before the full sample. Agreement matters more than sample size.
Record the time spent reading each packet and the number of systems opened. A measure that requires a carrier portal login for every case will not be repeated. Note whether the desk can export the scan history. Collection cost belongs beside the result.
Measuring tracer completeness
Report the share of packets that are complete, partial, and failed. Show the counts behind each share. The three groups describe different levels of readiness and should not be collapsed. A single completeness rate hides the packet that missed only the scan location.
Break the result down by carrier, queue, and opener role. A carrier with a different portal may produce more missing references. Compare only groups with the same template version. A rate without the group size is hard to interpret.
Report the most common missing item and the second most common. A missing scan history may point to an export, while a missing carrier reference may point to a submission step. Record one example of each. The pattern should lead to one fix.
Report the median time from case open to carrier submission. A high completeness rate with a slow submission still leaves the customer waiting. Record the internal cutoff and the actual time. Readiness without speed is only half the process.
Limitations and next action
The measure cannot show whether the carrier could have found the parcel with a better packet. It also cannot show a missing scan that the carrier never recorded. Treat the result as adherence to the tracer checklist. Note the carriers and channels that were not included.
Give the result to the logistics lead and the client contact with one change to test. The change might be an automatic scan export, a required carrier reference field, or an earlier case opening. Choose one change and assign it to a named owner. Record the effective date and repeat the measure with the same definitions.
Review the boundary cases before adding a field. A parcel may be too new for a meaningful scan history. Fix the waiting rule before treating that case as a failure. The goal is a tracer the carrier can act on, not a longer form.
Schedule the next measurement for the same week in the following month. Keep the carrier and queue filters unchanged so the comparison is fair. Record any template change in the note. A trend built from different requirements is not a trend.
