Ops Workflow Audit · Package 01 · Exception Tracker

Every exception lands in one owned queue, with a name on it and a clock running

The first implementation package after the audit. It installs the exception queue itself: all eight control-layer fields, the owner rules, the working statuses, and the resolution codes, built in the client's existing tracker or spreadsheet tools.

Why this package comes first

The queue is the spine of the control layer. Nothing else works without it.

The audit found 80-120 order exceptions per month scattered across inboxes, chat threads, and the 3PL portal. The dashboard, the cadence, the communication kit, and every safe automation all read from one place: this queue. Build it first, and every later package has a foundation. Skip it, and automation just moves the chaos faster.

80-120
example exception volume per month that the queue must absorb from day one
3-5m
target lookup time per exception, down from the 15-25 minutes of cross-system chasing found in the audit
1
shared queue. Every exception gets an owner, a status, and an SLA age in the same place
What gets built

A working queue in the tools the team already uses

No new platform. The queue is configured in the client's existing tracker or spreadsheet tools, so the team keeps its current logins and habits. Diazovate installs the eight fields from the future-state exhibit, wires the category-to-owner rules, defines the four working statuses (Open, Blocked, Customer update needed, Resolved), loads the resolution code set, and trains the team on triage. One week of post-go-live tuning is included, because the first week of real volume always surfaces edge cases.

Pricing: Scoped in the audit's implementation quote.
Field schema

The eight fields, exactly as designed in the future-state exhibit

Each field answers one operating question. Together they turn a scattered signal into a visible, owned, time-bound piece of work.

System signal Control layer Human owner Guardrail / escalation
Order IDThe shared key. Connects storefront, 3PL, CS, and inventory records to one exception row.
Exception categoryOne of five: inventory mismatch, 3PL delay, address, partial shipment, damage. Categories drive owner rules.
OwnerThe person or role accountable for the next action. Never blank. Assigned by rule, not by whoever noticed first.
SLA ageThe clock starts when risk is detected, not when the customer emails. Aging drives the daily review order.
Customer impactCustomer-safe status and urgency level. CS can answer before the customer asks, without exposing internal detail.
Next actionWhat happens next, by whom, by when. If this field is empty, the exception is not being worked.
Escalation thresholdFounder sees only high-dollar, aging, VIP, blocked, or repeat issues. Routine queue noise stays off the founder's desk.
Resolution codeThe final code on every closed exception. Feeds reporting, prevention work, and 3PL accountability.
Worked example

What the queue looks like on a normal Tuesday

Most exceptions are on track. One is aging and gets worked first in the daily review. One hit the VIP threshold and is the only row the founder sees today. That ratio is the point: the queue absorbs the volume so people can work the exceptions that matter.

On track Aging Blocked / threshold hit

Illustrative example rows

Exception IDOrderCategoryOwnerSLA ageCustomer-safe statusNext actionDue
EX-0141#40218Inventory mismatchOps Lead3h On track"Order confirmed, ship date unchanged."Confirm live count with 3PLToday 4:00pm
EX-0142#40226AddressCS Lead2h On track"Awaiting your address confirmation."Email customer to confirm unit numberTomorrow 10:00am
EX-0143#40231DamageCS Lead1h On track"Replacement on the way."Send replacement order, open 3PL claimToday 3:00pm
EX-0144#402373PL delayOps Lead6h On track"Slight delay, new ship date shared."Get committed ship date from 3PLToday 5:00pm
EX-0138#40194Partial shipmentOps Lead28h Aging"Remainder ships separately at no cost."Book remainder shipment; first item in today's daily reviewToday 12:00pm
EX-0136#401813PL delayOps LeadBlocked 5 business hrs VIP threshold hit"Your order has our full attention. Update by end of day."Escalated to founder per VIP rule (blocked more than 4 business hours); 3PL account call bookedToday 2:00pm
Owner rules

Ownership is assigned by rule, not by who saw it first

Illustrative rule set from the audit's future-state design

CategoryDefault owner roleSLA targetEscalation threshold
Inventory mismatchOps Lead, owns until root cause is clearFirst action same business dayHigh-dollar order (threshold set with the client); repeat issue if the same SKU appears 3+ times in a week
3PL delay3PL account owner, with Ops Lead oversightCustomer-safe status published same day; daily review after 24 hours openAging past 24 hours with customer impact; blocked
AddressCS Lead owns customer action, Ops Lead monitors agingCustomer contacted same business dayBlocked while waiting on external action
Partial shipmentOps Lead owns resolution, CS Lead owns communicationRemainder plan set within one business dayHigh-dollar order (threshold set with the client)
DamageCS Lead owns customer resolution, Ops Lead owns the 3PL claimReplacement or refund offered same business dayVIP: escalate if blocked more than 4 business hours
Resolution codes

Every closed exception carries exactly one code

  • INV-MISMATCH-3PL3PL stock count disagreed with the system of record.
  • INV-MISMATCH-INTERNALInternal inventory record was wrong at order time.
  • 3PL-DELAY-WAREHOUSEOrder sat past the agreed pick-and-pack window.
  • 3PL-DELAY-CARRIERCarrier missed the pickup or transit window.
  • ADDR-CUSTOMER-FIXCustomer corrected the address before ship.
  • PARTIAL-SHORT-PICK3PL shipped short against the order.
  • DMG-TRANSITItem damaged in transit.
  • DMG-PACKAGINGPackaging failure identified at the 3PL.
Codes turn one-off fixes into trend data. They feed the weekly readout, the prevention backlog, and the 3PL accountability conversation: when the same warehouse code repeats, the client walks into the vendor call with numbers, not anecdotes.
Package scope

Exactly where this package starts and stops

The boundary is deliberate. This package installs the queue and hands it to the team. Dashboards, cadence, communication templates, and automation are their own packages, each scoped in the audit's implementation quote.

Included

  • Queue configured in the client's existing tracker or spreadsheet tools
  • All eight control-layer fields
  • Category-to-owner rules wired in
  • Four working statuses: Open, Blocked, Customer update needed, Resolved
  • Resolution code set loaded
  • Team training on triage and ownership
  • One week of post-go-live tuning

Not included

  • Custom software platform build
  • New integrations beyond the agreed tools
  • AI-generated customer replies. The audit rated this "not first": customer messaging is not automated until source status is reliable

Client inputs

  • Approved category taxonomy and owner rules from the audit
  • Admin access to the tools the queue lives in
  • One decision owner for categories, owners, statuses, and escalation rules

Definition of done

Behavioral, not artifact-based. Every new exception lands in the queue with an owner and an SLA age within one business day of go-live, and the team triages the queue without Diazovate in the room. If the queue only works when Diazovate is watching, it is not done.

Pricing: Scoped in the audit's implementation quote.