Still chasing approvals by email?
Inboxes are not workflow engines. Requests get lost, accountability vanishes, and customers wait longer than they should.
Why this breaks
- No one knows current state without reading a thread
- Delegations and out-of-office stall work silently
- Audit questions become archaeology in Sent items
- Customers ping “any update?” because internal status is opaque
What fixed looks like
Before: forward, reply, “see below,” screenshot attachments.
After: request ID, stage, owner, due date—email only nudges people to act.
What we change
- Process: defined stages, SLAs, and escalation—not infinite CC
- Integrations: forms, CRM, or ERP triggers into one queue
- Automation: reminders, routing by amount/type, audit log
- Controls: segregation of duties where it matters
Tools commonly involved: Microsoft 365, Power Automate, Teams, Slack, Notion, Airtable, Zapier, Make.
What we do not change: who has authority to approve—we make that authority visible and faster to exercise.
Security: role-based access, logged actions, no shared mailbox passwords for “convenience.”
FAQ
- Can we keep email notifications?
- Yes—email as a notification layer, not the system of record. Approvers click through to a single status view.
- What about exceptions and edge cases?
- We design an explicit exception path with an owner—so “reply-all chaos” is not the default escalation.
- Will managers resist another portal?
- We keep surfaces minimal—often Teams/Slack plus one list view—so approval takes fewer clicks than searching Outlook.
- How do you prevent rubber-stamping?
- Thresholds, required fields, and delegation rules so approvals mean something—not one-click yes on everything.
Selected work
Anonymized projects from real engagements—advisory judgment backed by implementation. No invented metrics; depth case studies come when clients approve outcomes.