Corporate workflow · worked example

One purchase request, two very different journeys

The same event — a staff member needs to buy something — traced through the way most companies handle it today, and through a workflow system built around how the team already works.

Before The email-and-WhatsApp way

Every hop depends on a person remembering. The request has no number, no owner, and no clock — and the only record of the decision is a conversation in a corridor.

  1. WhatsApp photo“boss, can I buy this?”
  2. Forwarded emailnow it’s someone’s problem
  3. Sits in an inboxunder 40 other emails2–3 days
  4. Verbal “OK”in the corridor, no record
  5. Invoice landsfinance is surprised
  6. “any update?” — chased by hand, again
  7. Month-end auditwho approved this? nobody can say
Fig 1 — the manual journey: three hand-offs with no owner, a chase loop that runs on memory, and an audit trail that ends in a shrug.
After One workflow system

The same request rides a single rail. Routing, chasing, paperwork, and the audit record are the system’s job — people only make the decision.

  1. no reply in 48 h → system nudges
  2. Request form2 min on a phone, quote attached
  3. Auto-route<$5k manager · ≥$5k +directorrules
  4. One-tap approveapprove / reject, with a commenthours
  5. PO generatednumbered, emailed to supplierinstant
  6. Invoice matchedpayment scheduled
  7. audit trail — every step timestamped, searchable at month-end
Fig 2 — the built workflow: the identical five decisions, but routing, chasing, and the record are automatic. People only appear where judgement is needed.
3 days3 hours
typical approval turnaround
“any update?”auto-nudge
chasing becomes the system's job
corridor OKaudit trail
every decision timestamped, with a name on it
Map Your Workflow Tell us how approvals work in your company today — we'll sketch the system that replaces the chasing.