Exception log week

What is Exception log week and how does it fit South African operations?

Exception log week is a single-page or single-card tool for tracking missed deliveries, customer handovers, or collection runs, without starting blame games. Designed for SMEs where the owner or senior lead still attends standups, it sits pinned near the kettle or on the ops board, always visible. We made this rhythm card for teams shifting real goods across Gauteng, Cape Town, Durban or Gqeberha, who can’t afford to lose hours to spreadsheets during load-shedding. Its job is to record misses each week, assign clear ownership, and prompt a useful review every Friday.

Who benefits, and who should look elsewhere?

Exception log week is for growing teams with regular freight on the move, but not a full ops department with ten layers of approvals. If your team moves parcels between small warehouses, florist shops, depots, or worksites, especially where power failures disrupt digital tools, a paper rhythm card keeps you steady. Using it makes sense for office, floor, bay or studio leads juggling multiple customer timelines. It may not suit very large organisations with mature ERP systems, or those needing deep audit trails for regulatory reasons. If your flow is fully automated or if you want tracking linked directly to your warehouse system, see other rhythm tools or look at moves for add-ons.

How Exception log week works on the floor

Print the card at the week’s start. Assign a clear owner, usually the ops lead, manager, or owner themselves. Pin it near the kettle or in the loading bay, where team members actually gather. Each day, anyone who spots a missed delivery or a late collection writes it down, with plain facts only. No blame, no decorating. On Friday, the owner calls a quick review (five to ten minutes), runs through the exceptions, and checks if there’s a pattern needing a fix. The owner then follows up as needed, sometimes through our contact form for advice or tweaks. Teams often pair this card with the Monday lane board or returns clear card for extra context.

A worked example: florist run with three misses

Take a small Johannesburg florist team delivering same-day bunches to Sandton, Rosebank and Maboneng. Monday: One bouquet delays when a driver can’t get through morning traffic. Write that on the card, noting the stop, date, and reason. Wednesday: Load-shedding kills the POS, so a collection promised for 15:00 gets pushed to 17:30, add that. Friday: The van’s back door sticks, slowing another handover. Add the note. At week’s end, the owner reads out the three misses, checks if the same route always has delays, and the team agrees to shift Sandton deliveries earlier to dodge morning jams. No finger-pointing, just facts and fixes.

What to prepare before sending your Exception log week

To get useful help via our contact form, have the marked-up card ready, with dates and locations noted. Jot down which suburb loop or move type (like same-day, fragile goods, or returns) is giving you trouble. If you’re running a special route, such as refrigerated goods up the N1 or inner-city collections during high load-shedding risk, note this in your message. Mention which other rhythm cards you use, if any.

Having these details ready helps us suggest tweaks, extra review questions, or a variant card, so you get a rhythm that matches your operation.

• Clear photo or scan of your filled card
• Highlight tricky routes or repeat exceptions
• Mention if you use Monday lane or returns cards
• Describe your main delivery or collection type
• Flag special issues (load-shedding, after-hours runs, fragile goods)

Common pitfalls and how to keep the card useful

Exception log week fails if no one actually owns the review time, or if the exceptions column becomes a list of complaints. Avoid letting blame creep in, stick to what happened, not who failed. Keep it visible (the kettle beats the inbox for daily reminders). If power cuts the week short, protect the core checklist lines, leave optional notes for calmer weeks. Don’t let the card vanish into a pile or a digital drive named Final_Final_v7. If it stops matching your flow, snap a photo and send us a message for a tailored variant. Use fragile tempo note or hub transfer card if your ops need more detail in certain lanes.