Ops Workflow Audit · Exhibit 01 · Current-State

Where the workflow breaks before automation can help

The current-state exhibit from the Ops Workflow Audit: the evidence reviewed, the ownership failure, the business impact, and the exact stabilization logic inside the diagnostic package.

Executive finding

The client does not have an order-status problem first. It has an exception-control problem.

The 3PL can see fulfillment risk before the internal team can, but that information does not enter the operating rhythm until the customer escalates. Leadership is being used as the operating system: when ownership is unclear, the founder becomes the queue.

80-120
example monthly order exceptions requiring manual review
15-25m
example lookup time per exception across systems
20h+
example monthly labor lost to status chasing before fixes
Example discovery inputs

What this exhibit is based on

42 delayed-order samplesTrace from order creation through customer response.
5 stakeholder interviewsFounder, ops lead, CS lead, warehouse/3PL contact, finance/admin.
2 weeks Slack threadsManual escalation and status-chasing patterns.
System inventoryShopify, 3PL portal, shared spreadsheet, email, Slack.
Weekly reporting reviewManual metric assembly and disputed status sources.
Exception aging sampleWhere issues sit before a customer or founder notices.
Current-state swimlane

One inventory exception crosses six lanes before anyone owns it

The workflow is not failing because people are careless. It is failing because the system never converts a 3PL exception into a visible internal queue with owner, SLA, status, and escalation threshold.

System / data location Manual work Ownership gap Customer / escalation risk
Lane / Step
1 Order
2 Transfer
3 Exception
4 Hidden note
5 Blind spot
6 Customer asks
7 Slack chase
8 Manual lookup
9 Founder tag
10 Late update
Customer

Places order

Receives normal confirmation and expected ship window.

Asks for status

Customer discovers the delay before the team does.

Reactive service

Receives delayed answer

Trust damage has already happened.

Customer impact
Shopify

Order passes to fulfillment

Shopify shows order as open, not as operational risk.

Partial truth

Checked manually

Ops uses Shopify as one clue, not a source of truth.

Manual work
3PL portal

Inventory discrepancy appears

Available inventory does not match committed order demand.

Process break

Issue noted only here

3PL logs exception, but no internal alert is triggered.

Hidden queue

Portal rechecked

Ops searches notes after CS escalates.

Rework
Customer Service

No exception view

CS cannot see fulfillment holds until the customer asks.

Visibility gap

Receives customer email

CS now owns the customer anxiety without owning the answer.

Trust risk

Posts in Slack

Asks ops for status because no shared queue exists.

Manual handoff

Sends late update

Customer response depends on ad hoc recovery.

Delayed service
Ops Lead

Becomes investigator

Ops is pulled in after the workflow has already failed.

Owner unclear

Checks 3 systems

Compares Shopify, 3PL notes, and inventory spreadsheet.

15-25m lookup

No clear authority

Can diagnose the issue but lacks escalation rule or decision path.

Decision gap
Founder

Tagged for order-level issue

Leadership time substitutes for missing operating rules.

Escalation failure
Operational risk assessment

Failure points ranked by business impact and fix sequence

Failure point Customer impact Frequency Fix complexity Priority Recommended action
No unified exception queue 5 5 3 P1 Create shared exception tracker with owner, status, SLA clock, and customer-impact field.
No owner assignment 5 4 2 P1 Define owner by exception type before adding automation.
Manual cross-system lookup 3 5 3 P2 Standardize fields and reconcile Shopify, 3PL, and inventory spreadsheet into one view.
Founder escalation for routine exceptions 4 3 2 P2 Add threshold-based escalation so founder sees only high-dollar, aging, or VIP issues.
Late customer communication 5 4 2 P1 Create CS-visible statuses and approved templates for proactive updates.
How this exhibit feeds the rest of the package

From current-state map to paid roadmap

Next exhibit: Future-state workflow

Design the exception-control layer: shared queue, category, owner, SLA clock, CS-visible status, and escalation threshold.

Roadmap: 30-day stabilization

Sequence the fix: field definitions, owner model, daily cadence, dashboard, communication templates, then automation candidates.

Upsell: implementation support

Build the tracker, dashboard, SOPs, cadence, and lightweight automation after the diagnostic. No custom platform promise required.