Small business outsourcing workflow guide
Build a delivery route exception log for a small-business assistant
A delivery route exception log that helps a small-business assistant capture the stop, notify the customer, and keep the remedy separate from the routing decision.

Key takeaways
- Write the exception triggers and the driver authority limits before the first report.
- Record the stop, promised window, evidence, and time in one entry with a single owner.
- Notify the customer before the window closes and stop when the delivery is settled.
- Keep routing decisions, customer remedies, and carrier claims as separate dated records.
Define what counts as a route exception
A route exception log starts with a written list of events that count as exceptions. Include a missed stop, a refused delivery, an address problem, a vehicle breakdown, and a delay that pushes the arrival past the promised window. State which events the driver may resolve alone and which must go to the dispatcher. Write each trigger in one sentence and post it where the assistant works. The log should not depend on how frustrated the caller sounds.
Decide what the log is for before adding columns. It may support customer notices, driver coaching, carrier claims, or all three, but each purpose needs different evidence. Record the purpose at the top of the log so a later reader understands the entries. Keep the promised delivery window beside the exception so lateness can be measured. A log without a purpose becomes a list of complaints with no owner.
Capture the stop, the evidence, and the time
Capture the route, the stop number, the customer, the promised window, and the time the exception was reported. Record the driver, the vehicle, and the reason code from the approved list. Attach the photo, scan, or message that supports the report when one exists. Note the weather or traffic event only when a source confirms it. The entry should be complete before the assistant contacts the customer.
Give every exception one owner even when the driver and the dispatcher both act. Record the first action taken and the time it happened. If the stop was moved to another route, link the new route and the new window. If the parcel returned to the depot, record the depot and the hold date. The assistant should be able to answer where the parcel is without calling three people.
Tell the customer before the window closes
Tell the customer as soon as the exception is confirmed and the next step is known. State what happened, what the new window is, and what the customer should do if the new window fails. Do not blame the driver or the customer in the message. Use the customer's preferred channel and keep a copy with the entry. A notice sent before the facts are checked creates a second problem.
Set a contact cadence for exceptions that stay open past the day. Send one update when the parcel reaches the depot and one when it returns to the route. Stop the messages when the delivery is complete or the customer chooses a pickup. Record each message and the reply. A missed promise turns a routing problem into a service complaint.
Separate the driver decision from the customer remedy
Keep the driver's operational decision separate from the customer remedy. A dispatcher may reroute a stop, while only the owner may waive a fee or send a replacement. Record who approved each remedy and the policy that allowed it. Do not mark the route exception closed just because the customer received a credit. The two records answer different questions.
When a carrier is involved, record the claim or ticket number and the carrier's deadline. Compare the carrier response with the customer remedy so the owner can see the net cost. If the carrier denies the claim, keep the denial and the appeal date. Do not erase the original exception when a later delivery succeeds. The history is what makes the next decision faster.
Review exceptions by route and cause
Review exceptions every week by route, driver, and reason code. Look for one street, one building, or one time of day that produces repeat failures. Check whether the customer notice went out before the promised window closed. Record the pattern and the person who received it. A weekly review keeps a small routing problem from becoming a monthly cost.
Compare the exception rate with the volume on each route so a busy route is not punished for its size. Ask drivers which instruction was unclear and record the answer. Change one part of the route or the notice text at a time. Keep the old reason codes with the date they were retired. The next review should start from the same definitions.
Sources and next steps
- Federal Trade Commission, mail, internet, or telephone order merchandise rule
- U.S. Small Business Administration, manage your business
- Federal Trade Commission, advertising and marketing guidance
- U.S. Government Accountability Office, internal control standards
Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.
Related guides
Set a customer waitlist promotion routine for an assistant-run shop
A waitlist promotion routine that helps an assistant-run shop offer open stock in a fair order, record each outcome, and keep the list honest.
Write a vendor rebate credit tracker for a small-business assistant
A vendor rebate credit tracker that helps a small-business assistant claim on time, match the credit note, and keep short pays visible.