Small-business outsourcing research

How often do assistant-run shops miss a supplier delivery-date update?

A protocol for measuring delivery-date changes that never reach the order record, the customer message, or the inventory plan.

How often do assistant-run shops miss a supplier delivery-date update?

Research question and scope

This protocol asks how often a supplier delivery-date change fails to reach the people and records that depend on it. The unit is one purchase order with a supplier-confirmed delivery date that changed during the window. The study measures whether the change reached the order record, the customer message, and the inventory plan. It does not judge whether the supplier was right to change the date.

Set the scope to one shop, one supplier group, and one ordering system. Record the channels through which a supplier can send a change, such as email, portal, phone, or a delivery note. If the shop changes its ordering system during the window, analyze the cohorts separately. A new portal can reduce missed updates without any change in the assistant's routine.

Define the population as every purchase order with at least one confirmed date change during the window. Include orders that were cancelled after the change, because the cancellation may depend on the new date. Exclude orders that never had a confirmed date, and state that exclusion. Test the definition on three recent orders before collection begins.

Definitions that make the measure reproducible

Define the change time as the moment the supplier sent the new date, not the moment the assistant read it. Define recorded as the point when the order record shows the new date and the source of the change. Define communicated as the point when the customer who depends on the order received the new date. Define planned as the point when the inventory or fulfilment plan reflects the new date.

A change that reaches the order record but not the customer is not a full update. A change that reaches the customer but not the inventory plan can still cause a stock-out. Record each destination separately so the result shows where the break occurred. Do not collapse the three into one pass or fail.

Record the supplier, the order value, the original date, the new date, and the number of days moved. A one-day slip and a three-week slip have different consequences. Add whether the order was for stock, a customer, or internal use. The required evidence differs by order type, so state the list beside each type.

Evidence standard and data dictionary

For each order, capture the supplier message, the order number, the old date, the new date, and the date the message arrived. Record the time the order record was updated and the person who updated it. Add the time the customer was told and the time the inventory plan changed. Keep the supplier message with the record so the source can be checked.

Record whether the supplier sent the change proactively or only after the assistant asked. A proactive change is a different signal from one discovered during a chase. Note the channel and whether the message was addressed to the right person. A change sent to a shared inbox with no owner is easy to miss.

A second reviewer should be able to rebuild the timeline from the record without reading every email. If they cannot find the old date, the dictionary is incomplete. Test the record on three orders before scaling the collection. Record the result of that test and any field that had to be added.

Sampling and collection

Draw the sample from the purchase-order log, not from a list of late deliveries. A late-delivery list overrepresents the misses and hides the changes that were handled well. Record the export date, the filters, and the number of orders excluded. If the population is large, use a fixed interval across the window.

Collect the supplier message as it existed at the time, not after a later cleanup. If the record was updated days later, note the update date and analyze the original delay separately. Do not infer a supplier change from a delivery note that arrived after the fact. Record the collection date separately from the change date.

Record the assistant's shift and the supplier's contact hours. A change that arrives after the assistant leaves may wait for reasons unrelated to the routine. Add the shop's holiday calendar and the supplier's time zone. These fields help separate a missed update from a coverage gap.

Analysis and reporting

Report the number of orders, the share recorded, the share communicated, and the share planned. Show the counts by supplier, order type, and channel. Present the median time from the supplier message to each destination. Use the same denominator for every rate and show orders with incomplete times.

Inspect the orders where the change reached one destination but not the others. A break between the record and the customer message may point to a missing template. A break between the customer message and the inventory plan may point to a handoff gap. Describe the case without naming the assistant or the customer.

A useful additional view is the number of times the assistant had to ask the supplier for the date. A high count may mean the supplier messages are unclear or the order record lacks a field. Show the count beside the missed-update rate. That view separates a supplier communication problem from an assistant follow-up problem.

Limits of the evidence

The record cannot show whether the customer changed plans because of the new date or for another reason. It can show only the messages, the updates, and the timing. A fast update is not proof of good service, and a slow one is not proof of neglect. The protocol also cannot capture a date change agreed in a phone call that was never logged.

A shop with a small number of orders cannot support a stable rate. Describe the orders and the size of the slips instead of ranking the supplier. If one supplier dominates the sample, report that concentration. A general rate would hide a single relationship problem.

A change that is recorded but entered in the wrong field is still a miss for the reader. Add a short check for the date format and the field used. Record the correction and the time it took. That evidence points to a form or training problem rather than a reminder problem.

Give the result to the owner, the assistant, and the supplier contact and ask for one observable change. The change might be a required date field in the order record, a supplier template, a daily date check, or a customer message template. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions after the change.

If recording improved but communication did not, the bottleneck may have moved to the customer message. If communication improved but planning did not, the inventory handoff may need a named owner. Report the stages together before declaring a success. Close the review when the owner accepts the finding and the next cohort is scheduled.

Record whether the order record has a dedicated delivery-date field or only a note in the description. A note is easy to overwrite and hard to report on. If the system lacks a field, state that limitation in the scope. The missing field may explain more misses than the assistant\'s routine.

Ask the supplier whether they sent the change to the named contact or to a general inbox. A general inbox can be read by several people and still leave nobody responsible. Record the recipient and the channel. That detail separates a supplier habit from a shop process.

Ask the assistant which supplier message was hardest to interpret. A concrete example is more useful than a general complaint. Add the example to the supplier template or the order guide. The next measurement should test whether the same confusion recurred. Record the date the supplier confirmed the new date so a later reviewer can check the update path. Add the name of the person who received the confirmation, because an unowned inbox is a common hiding place for a date change.

Sources

Frequently asked questions

Does a favorable sample prove the routine caused the result?

No. The design is observational and supports a bounded operating decision, not a universal causal claim.

What should an owner review first?

Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.

Related research