Admin Untangled
Sample Workflow Autopsy

Customer order administration

An anonymised operational review of the journey from accepted customer order to service activation within a small UK telecoms consultancy.

01 · Executive summary

The process worked, but only through constant human attention.

The business had grown around a capable and highly involved team. Customer orders were being completed, but progress depended heavily on individual memory, inbox searches, handwritten notes, spreadsheets and repeated manual checks.

There was no single reliable view of what had been completed, what information was still missing, who needed to act next, which customer communications had been sent, or whether an order was genuinely ready to progress.

The order process was operationally functional but structurally fragile.
02 · Current process

What the workflow looked like

Information moved between email conversations, enquiry forms, spreadsheets, supplier systems, contract documents, payment records, informal notes and individual staff memory.
Customer enquiry received
Requirements discussed
Customer and company information collected
Products and quantities confirmed
Contract produced and sent
Payment information requested
Equipment or SIM cards allocated
Supplier order submitted
Activation requested
Customer updated
Order checked manually until complete
03 · Principal findings

Where the process was breaking down

The central issue was not effort. The team was compensating for a process that had developed gradually, with each new requirement added wherever it could fit.
Finding 01

No single source of truth

Customer information existed in several locations. Reviewing one order often required opening multiple systems and reconstructing what had happened.

Effect: extra checking, outdated information and difficult handovers.
Finding 02

Status labels did not describe the next action

Broad labels such as “in progress” or “awaiting customer” did not explain precisely what was outstanding.

Effect: each order had to be opened and interpreted before work could begin.
Finding 03

Progression depended on memory

Important checks and follow-ups happened because an experienced person knew they needed to happen.

Diagnosis: staff expertise had become part of the system architecture.
Finding 04

Information was repeatedly collected and checked

Details supplied early in the journey were sometimes requested again or compared manually across several documents.

Effect: slower completion, avoidable typing and customer frustration.
Finding 05

Exceptions were handled informally

Multi-line orders, missing porting information, partial activation and changed requirements were often managed through free-text notes or inbox conversations.

Effect: the hardest orders were also the least visible.
Finding 06

Communication was detached from progress

Emails were sent manually, but the order record did not always confirm what had been sent, when, or whether a response was required.

Effect: duplicate messages, missed follow-ups and inconsistent experience.
Finding 07

Completion was not precisely defined

An order could appear complete while one line, activation, supplier reference or confirmation remained unresolved.

Diagnosis: “complete” described an impression rather than a validated state.
04 · Root cause

The process had accumulated rather than been designed.

Every workaround was understandable on its own. Together, they created operational drag.

What had been added over time

Another spreadsheet column. Another email template. Another note. Another manual check. Another supplier login. Another reminder held in someone’s head.

What this created

A workflow that functioned, but only because experienced people continuously compensated for fragmented information and unclear progression rules.

05 · Risks

Operational exposure

The most serious risks were not dramatic system failures. They were repeated small failures that created delay, rework and customer uncertainty.
RiskLikelihoodOperational effect
Missing customer informationHighDelays and repeated contact
Incorrect order progressionMediumSupplier or fulfilment errors
Missed follow-upHighStalled orders
Poor handover visibilityHighDependence on key individuals
Incorrect equipment allocationMediumRework and customer disruption
Partial activation overlookedMediumBilling and service complaints
Inconsistent customer updatesHighReduced trust
Inaccurate reportingHighManagement decisions based on incomplete data
06 · Future workflow

A controlled process built around readiness

Each stage should have a clear entry condition, owner, required information, permitted actions, next stage, communication trigger and audit trail.
01New order
02Information required
03Ready for customer call
04Ready to prepare contract
05Contract sent
06Payment details required
07Ready for fulfilment
08Dispatched
09Activation requested
10Supplier order submitted
11Order confirmed
12Partially active
13Live
14Complete
07 · Recommendations

What should change first

The priority was not to automate everything immediately. It was to establish visibility, control and ownership before adding automation.
Priority 1

Create one operational record

Bring essential customer, product, order, contract, payment, fulfilment, activation and communication information into one reliable view.

Priority 2

Define stage-entry rules

An order should move forward only when the information required for the next stage has been verified.

Priority 3

Make outstanding actions visible

Show precisely what is missing: PAC required, contract unsigned, payment outstanding, SIM not allocated, supplier reference missing or activation incomplete.

Priority 4

Bring communication into the workflow

Record customer emails against operational events and make follow-up requirements visible.

Priority 5

Design explicitly for exceptions

Represent multi-line orders, partial activation, missing information and changed requirements structurally rather than relying on free text.

Priority 6

Create a reliable audit trail

Record what changed, who changed it, when it changed and the relevant reason or note.

08 · Implementation

A staged route from stabilisation to automation

Automation should follow process design, not replace it.

Phase 1 · Stabilise

  • Document the real workflow
  • Agree precise stages
  • Define mandatory information
  • Establish one master record
  • Standardise notes and ownership

Phase 2 · Control

  • Add stage validation
  • Surface missing information
  • Structure fulfilment and activation
  • Record customer communications
  • Add reminders for stalled actions

Phase 3 · Automate

  • Generate documents and emails
  • Connect supplier ordering
  • Import references and updates
  • Automate routine notifications
  • Create exception dashboards
09 · Expected impact

Less operational drag, more dependable delivery

The redesigned process would reduce dependency on memory while improving customer visibility and operational confidence.

Expected reduction

  • Time spent searching emails and files
  • Duplicated data entry
  • Repeated customer questions
  • Missed follow-ups
  • Dependency on individual memory
  • Manual order-status checking

Expected improvement

  • Clearer customer journey
  • More dependable reporting
  • Faster identification of blocked orders
  • Better handover continuity
  • Greater capacity without immediate headcount
  • A repeatable process able to support growth
10 · Final diagnosis

The business did not have a staff-effort problem.

It had a workflow visibility and control problem. The team was already supplying the intelligence, memory and checking that the process lacked.

The correct improvement was not to ask people to work more carefully. It was to move operational knowledge out of individual heads and into a process that could reliably guide the work.
Visit Admin Untangledhello@adminuntangled.co.uk