From Forms to Workflows: Eliminating Internal Email
Most internal email is a poorly-disguised form-and-workflow. Replace it with actual forms and workflows, and email volume drops 40%.
From Forms to Workflows: Eliminating Internal Email
Audit a knowledge worker's inbox for a week and you'll see the same patterns:
- “Can you approve this expense claim of KES 4,200?” → 5 emails over 3 days
- “Please find attached my leave request” → 3 emails, eventually approved
- “Need your sign-off on the supplier change” → 8 emails, two delegations, one re-send
Each of these is a poorly-disguised form + workflow. They use email because:
- Everyone has email
- Setting up a form-and-workflow feels heavyweight
- The receiver doesn't always know what's expected of them
The cost: ambient cognitive load, lost approvals, no audit trail, no SLA.
What replacing them looks like
Each pattern collapses into an eForm + workflow:
Expense claims
eForm: amount, category, receipt upload, business purpose. Workflow: line manager approval (auto-routed by submitter's department head). Conditional: claims under KES 5,000 auto-approved if submitter is in good standing.
Result: median expense-claim cycle goes from 3 days to 8 hours.
Leave requests
eForm: dates, leave type, handover notes. Workflow: line manager → HR review for compliance with leave balance. Conditional: medical leave routes to HR directly with confidentiality (line manager sees “absent for medical reasons” not the diagnosis).
Result: leave management out of email entirely.
Supplier change requests
eForm: existing supplier, proposed new supplier, justification. Workflow: Procurement Manager → Finance review (for credit impact) → CFO if value over threshold. Conditional: routine substitutions within an approved list bypass Finance.
Result: supplier changes documented, justified, and reversible.
The numbers
In customers who have rolled out eForms + workflows across the top 10 internal request types, we typically see:
- 30-40% drop in internal email volume
- Median request cycle time drops 60-75%
- Audit trail for every request (previously buried in inboxes)
- SLA visibility (previously: vibes)
What's hard
Two things:
Designing the right forms
A form with 30 fields is just as bad as an email thread. Forms should ask the minimum to enable a decision. If a 5-field form generates a question 30% of the time, add a 6th field — but never start at 30.
Convincing senior staff to use them
Junior staff adopt forms gladly — they finally know what to put in the email. Senior staff sometimes resist; “I'm too busy for a form.” The trick: make the form auto-populate from context (their department, their default cost centre, common values) so it takes 30 seconds, not 5 minutes.
What doesn't replace well
Some things shouldn't move to forms:
- True one-off communications (a question, a thank-you, a coordination DM)
- Conversations with external parties (they don't have your forms)
- Discussions that haven't crystallised into a request
Don't try to formalise everything. Formalise the repeated things.
Closing
Email isn't going away. The volume of unnecessary email can drop a lot. Most internal request flows belong as forms-and-workflows; only the conversational residue belongs in email. Sort once.