TL;DR
- If a human still has to read, decide, or type something before the next step happens, the process is not automated. It's manual with a digital costume.
- Real automation removes humans from routine steps. It keeps them only at genuine decision points.
- There are three maturity levels: digital forms only, automated routing, and intelligent automation. Most clients start at Level 0 (email) and reach Level 2 or 3.
- The practical starting point: pick one process, map every step, mark each as a rule or a judgment. Rules get automated.
Here is a working definition that we use with every client before we start building anything:
If a human still has to read something, decide something, or type something before the next step happens, that process is not automated. It's manual with a digital costume.
Most organisations we work with believe they have automated processes. They have email notifications. They have digital forms. They have Excel trackers. When we sit down and map what actually happens, step by step, the humans are still in every handoff. The digital tools just made the paper slightly lighter.
This matters because the point of automation is not to use digital tools. It's to remove human bottlenecks from the parts of a process that don't need human judgment.
The Fake Automation Checklist
Check how many of these describe your current processes. If the answer is three or more, your "automation" is mostly theatre.
- An email is your trigger. An employee submits a form, and the next step is "an email gets sent to the approver." The approver has to read the email. That's a manual step. The sending of the email is automatic. Everything after it isn't.
- Your workflow is an Excel tracker that someone updates. "We track all requests in a spreadsheet" is not a workflow. It's a record-keeping tool that requires a human to keep it current. When the human forgets, the record is wrong.
- Approvals happen by replying to emails. Someone reads an email, decides to approve, and types "Approved" or "OK to proceed." That decision might be instant, but the action of reading and typing is a manual step sitting inside what could be an automated flow.
- Someone manually checks a form submission and types data into another system. A form submitted in SharePoint shouldn't require a human to copy the data into an accounting system or HR platform. That's a connector problem, not an automation problem — and it's solvable in hours, not weeks.
- You get a notification and then manually do the next thing. Notifications are not automation triggers for a human — they're the start of a manual process that should have been automated. Getting a Teams message saying "invoice arrived" and then opening the accounting system to enter it manually is not automated. It's just a faster way of hearing about manual work that needs doing.
Left: "automated" email workflow where humans remain at every step. Right: actual automation where humans only appear at the decision point.
The Difference: Human Judgment vs Human Action
This is the key distinction. Almost everything else follows from it.
Real automation removes humans from the routine steps — the carrying, the copying, the routing, the notifying — while keeping humans at the actual decision points.
An approval is a decision. Whether a request is a good use of budget, whether the timing works for the team, whether an exception should be made — these require human judgment. Automation doesn't replace that. It gets the request to the right human faster, with all the context they need, and removes every other step that didn't require a human in the first place.
But checking whether a submitted form has all required fields? That's not a decision. It's a rule. You can express it in logic: "if field X is empty, return an error." Power Automate does this. No human required.
Routing a request to the correct approver based on department and amount? Also not a decision. It's conditional logic. If department is Finance and amount is above £10,000, route to CFO. Below £10,000, route to Finance Manager. That's a rule. Automate it.
Sending a notification to the requestor when their request is approved? Not a decision. Not even close. A human doing this step is waste, pure and simple.
For every step in your process, ask: "Could I write a rule that describes exactly what to do in every situation?" If yes, it can be automated. If the answer is "it depends on context that can't be captured as a rule," keep the human. Most processes are 70-80% rules and 20-30% judgment. That 70-80% is where your time savings come from.
What Real Automation Looks Like in Power Automate
Here is a concrete example. A purchase approval flow. No black boxes.
Trigger: SPFx form submits to SharePoint list
An employee submits a purchase request via an SPFx form on the intranet. It lands in a SharePoint list. Power Automate triggers immediately. Zero humans involved in this step.
Condition: Amount threshold routing — no human touches this
If the amount is above £5,000, the flow branches to the Senior Manager approval path. Below £5,000, it goes to Line Manager. The approver's email is pulled automatically from Entra ID based on the requestor's reporting line. No hardcoded names. No human checking who should receive it.
Parallel branch: Finance notified simultaneously
For amounts above £2,000, a parallel branch runs at the same time as the approval request. Finance receives a notification with the request details. They don't approve — they're informed and can flag concerns. This runs in the background while the main approval is in progress. Zero added time to the process.
Teams Adaptive Card — the only human step
The approver receives a Teams card with the full request context: who, what, how much, why, and supporting documents linked. They click Approve or Reject. That's the human decision. One click.
SharePoint updated, requestor notified, audit log created
All three happen simultaneously, automatically, the instant the Teams card is actioned. Nobody copies anything. Nobody sends a follow-up email. Nobody files anything. The record is complete, accurate, and timestamped. Zero humans required.
From submission to final record update, the only human involvement is the approver clicking one button. Everything else — routing, notifying, validating, recording, escalating if needed — is handled by rules.
A real Power Automate purchase approval flow — humans appear only at the decision step. Everything else is automated logic.
The Three Levels of Automation Maturity
When we first meet a client, we assess where they are on this scale. It shapes the conversation about what we build and in what order.
Digital Forms
The paper has moved online. Forms exist in SharePoint or Microsoft Forms. But humans still route submissions, check them, and copy data between systems. This is where most "digitised" organisations actually sit. It looks like automation but most of the manual steps remain.
Automated Routing
Forms trigger workflows. Power Automate handles routing, notifications, and record-keeping automatically. Humans still make the actual decisions, but every step around those decisions is automated. This is achievable for most processes in 2 to 4 weeks of build time.
Intelligent Automation
Routine decisions are automated based on rules. Humans only handle exceptions — cases that fall outside the defined rules. Duplicate detection, balance checks, compliance validation, and low-value approvals all run without human involvement. This is where significant time savings compound.
Most of our clients arrive at Level 0 — email-based everything — and reach Level 2 or Level 3 by the end of their first project with us. Level 3 doesn't require AI or machine learning for most business processes. It requires clearly defined rules, which most organisations already have — they're just enforced by humans instead of code.
Where to Start
Pick one process. Any process that involves approval, routing, or data entry is a good candidate. Pick the highest-volume one, because the ROI compounds with transaction count.
Map every step. Write them down. Be brutal — "wait for response" is a step. "Check if the right person received it" is a step. "Reply to say it's approved" is a step.
Now mark each step with one of two labels:
- R (Rule): Could I write a sentence that describes exactly what to do in every situation? "If amount is over £5,000, route to Senior Manager." That's a rule. Automate it.
- J (Judgment): Does this require knowledge, context, or discretion that can't be fully captured in a sentence? "Decide whether this vendor is reliable." That's judgment. Keep the human.
In our experience, 70 to 80% of steps in typical business processes are Rules. That's your automation opportunity. The goal isn't to replace people — it's to stop having people manually carry information from desk to desk when a flow could do it in milliseconds.
Take any process that runs more than 50 times per month. Sit with the people who run it. Map every step, start to finish. Mark R or J on each one. Count the Rs. That's your business case for the first automation build. Bring us in for the build or bring us in to review your map — either works.
Key Takeaways
Automation means removing humans from routine steps, not removing humans from decisions. If a step can be expressed as a rule, it can be automated. If it requires judgment, keep the human.
Email notifications are not automation. An email is the start of a manual process. Real automation routes, validates, records, and notifies without any human involvement between trigger and outcome.
Level 3 automation doesn't require AI for most business processes. It requires clearly defined rules, a Power Automate flow, and an SPFx form as the entry point. Most organisations reach Level 2 or 3 within their first project.