What Is a Workflow? Meaning, Examples and Workflow vs Process
By the SystemaFlow team · Updated November 2026 · Share this
A client emails a question on Tuesday. One person forwards it, another replies from their own inbox, a third adds it to the tracker, and on Friday the client chases. Ask the team "what's our workflow for client requests?" and you'll hear three different answers.
A workflow is the route one piece of work takes from start to finish: what starts it, the tasks in order, who does each one and where it passes from one person to the next. A client request, a purchase approval and a new starter's first day each have one, whether or not anyone has written it down.
Below: what a workflow is made of, everyday examples, how a workflow differs from a process, a quick quiz and a way to map one in under an hour.
What is a workflow?
Think of the work as something that moves: a request, a document or a decision travelling from one desk to the next until it's done. The workflow is the path it takes. It has six parts:
| Part | What it answers | Example: client request |
|---|---|---|
| Trigger | What starts it? | An email arrives at the shared inbox |
| Tasks | What gets done, in order? | Log it, assign it, answer it, follow up, close it |
| People | Who does each task? | Office manager logs and assigns; account manager answers |
| Handovers | Where does it pass from one person to the next? | Office manager to account manager |
| Decisions | Where does it branch? | Is it inside the agreed scope or a change request? |
| End point | When is it finished? | Client has an answer, and the request is closed in the tracker |
Every business is full of workflows, and they exist whether or not anybody designed them. The ones nobody designed are usually the ones that go wrong, because the handovers happen by habit. That's what invisible workflows are about.
A workflow can be entirely manual, partly automated or almost entirely automated. Automation changes who does a task (a tool rather than a person), but the route still has to be decided first.
Workflow examples
These are typical workflows in a small service business. Notice that each has a clear start and a clear finish.
| Workflow | Starts when | Main tasks | Finished when |
|---|---|---|---|
| Client enquiry | An enquiry arrives | Log, qualify, reply, book a call, send a proposal or decline | The enquiry is won, declined or closed |
| Purchase approval | Someone needs to buy something over a set amount | Request, check budget, approve or refuse, order, record | The item is ordered and recorded, or the request is refused |
| Supplier invoice | An invoice arrives | Check against the order, approve, add to the payment run, pay, file | The invoice is paid and filed |
| New starter set-up | An offer is accepted | Order kit, create accounts, book first-week sessions, send welcome | Day one starts with everything ready |
| Blog post | An idea is approved | Draft, review, edit, publish, share | The post is live and shared |
| Holiday request | Someone asks for time off | Check cover, approve, record, tell the team | It's in the calendar and cover is agreed |
Each of these has handovers, and the handovers are where work tends to stall. A request sits in someone's inbox because they didn't know it was theirs.
Workflow vs process: what's the difference?
People use the two words as if they mean the same thing, and in everyday conversation that does little harm. When you're deciding what to write down or fix, a distinction helps. There's no single official definition of either, so here's how we use them, which matches how they're commonly used.
| Process | Workflow | |
|---|---|---|
| What it is | The whole way the business gets a result, with its purpose, rules and measures | The route one item of work takes through tasks and people |
| Scope | Wide. Can span several teams and include several workflows | Narrower. One path from trigger to end point |
| Main question | What are we trying to achieve, and how do we do it? | What happens next, and who does it? |
| Example | Paying suppliers: approval limits, payment runs, records, who signs off | One supplier invoice going from inbox to paid and filed |
| What you do with it | Design it, own it, measure it | Map it, hand it over, automate parts of it |
A simple way to hold it: the process is the "what and why", and the workflow is the "route". Paying suppliers is a process. Inside it sit workflows for approving invoices, setting up a new supplier and handling a disputed bill.
The difference matters for one practical reason. When something keeps going wrong, a fix to the workflow (who it goes to next, and when) is often small. A fix to the process (the rules or the purpose) is bigger and needs the owner. Knowing which one you're looking at stops you rewriting everything to fix one handover.
There's a third word that matters more than either, which is a system: the workflow plus the owner, trigger, handovers and review that keep it running without anyone chasing. That's covered in process vs system. And where the written steps fit, as a procedure or SOP, is in what is an SOP.
Task, workflow or process?
Three words, eight typical examples. Pick the best fit for each, then see our answer.
Task, workflow or process?
Check the purchase order number on an invoice
One action, done by one person. It's a step inside a workflow.
A supplier invoice goes from the inbox to approval, into the payment run and is filed
One item of work moving through several tasks and people, with a start and a finish.
How the business pays suppliers: approval limits, weekly payment runs, records and who signs off
The whole way of getting a result, with rules. Several workflows sit inside it.
A client enquiry is logged, qualified, answered and either booked in or declined
A route from trigger to end point, with a handover and a decision.
Send the welcome email to a new starter
A single action inside the new starter workflow.
How we win new clients, from first enquiry to signed contract, including pricing rules and who approves discounts
It covers the purpose, rules and several workflows: enquiries, proposals and contracts.
A holiday request is checked for cover, approved, recorded and shared with the team
One request moving through several people to a clear finish.
Book the meeting room for a client call
One action. On its own it doesn't take work from start to finish.
0 of 8 answered.
How to map a workflow
You don't need special software or a workshop. A sheet of paper, the people who do the work and about an hour is enough. Pick a workflow that keeps causing questions or delays.
- Pick one item of work. "A client request", not "client service". Follow one real example from last week.
- Name the trigger and the end point. What starts it, and how would anyone know it's finished?
- List the tasks in order, with who does each one. Write what actually happened, not what should have. Ask the people who did it.
- Mark every handover. Each time the work changes hands, note how the next person found out it was theirs.
- Mark the waits. Where did the work sit untouched, and for how long? That's usually where the delay is.
- Fix one handover first. Name who it goes to next, and how they're told. Then write the steps down so the next person can follow them.
Here's a layout you can copy. One line per task.
WORKFLOW: [name, e.g. Answer a Client Request] Starts when: [trigger] Finished when: [end point] Owner: [one person who keeps it working] # Task Who Handed to How they know Typical wait 1 [ ] [ ] [ ] [ ] [ ] 2 [ ] [ ] [ ] [ ] [ ] 3 [ ] [ ] [ ] [ ] [ ] Decisions (where it branches): [e.g. in scope? yes: answer. no: change request] Where it usually stalls: [ ] One change to try: [ ] Check on: [date]
Once a workflow is mapped, the next steps follow. Write the steps as an SOP if several people do it. If it's not clear who decides at each stage, a RACI chart sorts that out. If you're not sure which workflow to map first, what to systemise first helps you choose.
Workflow software or a written workflow?
Workflow tools, from the task features in ClickUp or Notion to automation services, are good at running a route once it's agreed: moving a card, assigning the next person, sending a reminder. They work best when the route is already clear. Put an unclear workflow into a tool and you get the same confusion, faster.
So decide the route first, in a document, with the people who do the work. Then put it in whichever tool you already use. If a step is repetitive and costing real time, the cost of manual processes shows how to weigh up automating it.
Workflows that are mapped, owned and reviewed, and joined to each other, are what people mean by a business operating system. SystemaFlow™ systems are done-for-you templates in Word and PDF for exactly that, and they're not software: they work alongside the tools you have.
Want the full version?
To map your workflows properly, the Workflow Mapping and Optimisation pack in the Systems for Scale Core Vault has the Process Mapping Canvas, the Current vs Ideal Workflow Map, the Bottleneck Finder Sheet and the Workflow Handoff Protocol, each with a guide and a filled-in example. For a lighter start, the Workflow Signal Scanner is in the Scale Starter Kit Mini Vault.
See what's in the Systems for Scale Vault →Or get all 352 systems, and every one we add later, with Masterworks: $999, paid once.
Was this helpful?
Frequently asked questions
- What is a workflow in simple terms?
- The route one piece of work takes from the moment it starts to the moment it's finished: the tasks in order, who does each one and where it passes from one person to the next.
- What is the difference between a workflow and a process?
- The words overlap and many people use them as one. In practice, a process is the whole way the business gets a result, with its rules and purpose, and may include several workflows. A workflow is the route one item of work takes through tasks and people, which makes it the part you map, hand over and automate.
- What are the parts of a workflow?
- A trigger that starts it, the tasks in order, the person or role for each task, the handovers between people, any decisions or approvals, and an end point that says when it's finished.
- What is an example of a workflow?
- A client enquiry arrives, is logged, assigned to someone, answered within a set time, followed up and either turned into a job or closed. Others include approving a purchase, publishing a blog post and setting up a new starter's accounts.
- Do I need workflow software?
- Not to start. Decide the route first, on paper or in a document. Workflow tools are good at running and automating a route once it's agreed, and the one you already use for tasks may do the job.
- Is a workflow the same as an SOP?
- No. The workflow is the route the work takes. An SOP is the written instructions for doing it, step by step, so anyone trained can follow the route the same way.
