How to create a workflow. On a sheet first, one step per row, then in software.
A workflow almost always lives in the head of the person who runs it, and stays there until they go on holiday. Here is the method to write it down, an Excel template with totals that calculate themselves, and a step-by-step example.
You create a workflow in six steps: choose a process, fix where it starts and where it ends, write one step per row, add rules and exceptions, measure the minutes, decide where a person approves. The sheet comes before any software.
There is a standard for drawing it, BPMN, published by the Object Management Group in version 2.0.2 in January 2014. To run it, tools such as Microsoft Power Automate turn it into an event that starts the flow and the actions that follow.
Below is the Excel template in Italian and English, with the eleven columns and the formulas for the totals, plus a completed example, to download without leaving an email address.
Written by: Mattia Esposito, AI and marketing consultant, founder of Itria AI. From Puglia, based in Turin since 2023, he works remotely in Italy and abroad. LinkedIn profile.
What a workflow is, and its five parts, is in the glossary entry on workflows; which process to tackle first is on the page about which process to automate first. This page is about building one.
The workflow template, to download
An Excel sheet with five questions about the process, fifteen rows for the steps and three totals that calculate themselves: minutes per run, minutes per week, hours per week. Alongside it, the completed example as a PDF: a fictitious print shop answering quote requests.

| File | Contents | Link |
|---|---|---|
| ItalianExcel, to fill in | The process, the steps across eleven columns and the totals with their formulas. | |
| EnglishExcel, to fill in | The same sheet in English. | |
| ExamplePDF, filled in, in Italian | Seven steps from quote request to order, with minutes, rules, who approves and what a system can prepare. | |
| ExamplePDF, in English | The same example, in English. |
How to create a workflow in six steps
Six steps, in order, and the first is the one most often skipped: choose a single process, with a clear start and end. “Sales” is not a process; “from quote request to confirmed order” is, because you know when it begins and when it is done.
| Step | What to do | In the sheet |
|---|---|---|
| 1. Choose the process | Just one, repeated often and done by hand today. | Process name and who owns it. |
| 2. Start and end | The event that starts it and the result that closes it. | Where it starts, where it ends. |
| 3. One step per row | In the order it really happens, not the order it should happen in. | Step, who does it, what comes in, what goes out, tool. |
| 4. Rules and exceptions | The conditions that decide the path and what happens when something stalls. | Rule or condition, if something goes wrong. |
| 5. The minutes | How long each step takes and how many times a week the process runs. | Minutes and runs per week; the totals calculate themselves. |
| 6. Who approves | Where a person decides and which steps a system can prepare. | The last two columns: yes, no, partly. |
Step three is done by watching, not remembering: follow the process for a few days and write down every action, including the ones nobody thinks of as a step, such as “I copy the address from the email into the business software”. Those are the ones that add up the minutes.
The eleven columns of the template, one by one
Each column answers a question that, left unanswered, stalls the process or makes it impossible to automate. The first five describe the step; the others say what it costs in time, under what rules, what can go wrong and where a person is needed.
| Column | The question it answers |
|---|---|
| N. | In what order does it happen? |
| Step | What gets done, with a verb: log, check, calculate, send. |
| Who does it | Which person or role, today. |
| What comes in | Which information or document the step starts from. |
| What goes out | What it hands to the next step. |
| Tool | Email, spreadsheet, business software, phone. |
| Minutes | How long it takes, on average, each time. |
| Rule or condition | What decides the path: an amount, a deadline, a missing detail. |
| If something goes wrong | The case that today gets sorted out by word of mouth. |
| Does a person approve? | Yes for anything that goes to a customer, involves money or decides something. |
| Can a system prepare it? | Yes, no or partly: the first filter for automation. |
A workflow example: from request to order
The completed example is a fictitious print shop that receives twenty-five quote requests a week and takes them through to an order in seven steps. Added up, the steps come to 41 minutes per request: with twenty-five requests the total is 1,025 minutes a week, or 17.1 hours. These are example estimates, labelled as such in the file.
The last two columns do the rest of the work. Five of the seven steps can be prepared by a system, fully or partly: logging the request, asking for missing details, sending the quote, sending the reminder, preparing the deposit invoice. Pricing and passing the job to production stay with the owner.
The seven-day reminder is the step that gets dropped most often when work piles up, and in the example it is written as a rule: send it only if the customer hasn’t replied. Written down like that, a rule can be handed to a program; spoken aloud, it can’t.
From sheet to diagram, and to software
To draw a workflow so that everyone reads it the same way, there is the BPMN notation, Business Process Model and Notation, from the Object Management Group. The current specification is version 2.0.2, published in January 2014: events, activities and branches each have their own symbol.
For a seven-step process, a diagram with shapes and arrows in Word or a drawing tool is enough, but it pays to follow the same conventions: a circle for the starting event, a rectangle for each step, a diamond where a rule splits the path. The sheet tells you what to draw.
The next step is running it. Microsoft describes Power Automate cloud flows as automated workflows that can be triggered by events, such as an email arriving or a specific time of day, and that carry out actions across several services. Those are the “where it starts” and “what goes out” columns of the sheet, translated.
Where AI fits into a workflow
In the steps that read, sort and prepare: an AI system reads the email, works out what it asks for, fetches the right data and drafts a reply, and a person approves. According to Istat, Enterprises and ICT 2025, 25.7% of businesses that use AI apply it to organising administrative processes, the second area after marketing and sales.
A classic automation follows fixed rules: if a form arrives, create a row. AI is useful where the rule isn’t enough, because the request is worded differently every time. Several steps lined up, which a system runs and pauses where a person is needed, are the work of an AI agent: the difference from an assistant you ask a question is on the page about AI agents and chatbots.
The line between what the system does alone and what a person approves is drawn in the sheet, column by column, before a single line of code is written. That way of working is called human in the loop.
Questions and answers
How do you create a workflow?
In six steps: choose a process, fix the event that starts it and the result that closes it, write one step per row with who does it, add rules and exceptions, measure the minutes and decide where a person approves.
The sheet comes before the software: a workflow that doesn’t fit in a table won’t fit in an automation tool either.
How do you create a workflow in Excel?
One row per step and one column per piece of information: who does it, what comes in, what goes out, the tool, the minutes, the rule, what happens if it goes wrong, who approves. At the bottom, a formula adds up the minutes and multiplies them by the runs per week.
The sheet on this page already has the eleven columns and the formulas for the totals.
What is an example of a workflow?
From quote request to confirmed order: log the request, ask for missing details, work out the price, send the quote, send a reminder after seven days, collect the deposit, pass the job to production.
In the completed example, with a fictitious company, it comes to seven steps and 41 minutes per request.
What is the difference between a workflow and an automation?
The workflow is the sequence of steps, with who does them and under what rules. An automation is a program that carries out some of those steps by itself, starting from an event.
First you write the workflow, then you decide which steps to automate and where a person stays in to approve.
Do you need software to create a workflow?
No. A spreadsheet, or a sheet of paper, is enough to create one. To draw it in a standard way there is the BPMN notation from the Object Management Group.
Software comes later, to run it: tools such as Microsoft Power Automate turn it into an event that starts the flow and the actions that follow.
Notes on sources
- Object Management Group, Business Process Model and Notation, version 2.0.2, status “formal”, publication date January 2014. Read on 8 November 2026.
- Microsoft Learn, Overview of cloud flows in Power Automate, paraphrased from the Italian page. Read on 8 November 2026.
- Istat, Imprese e ICT, 2025: areas of AI use among businesses with at least ten employees that use it.
- The template and the example are built by Itria. The company is fictitious and the example minutes are example estimates, not measurements.
The sheet shows which steps a system can do. Building it is the next job.
A completed sheet shows straight away where the hours go: the steps marked “yes” in the last column are the ones an AI agent can prepare, with a person approving before anything goes out. The piece that reads documents recognised the right type thirty times out of thirty and got 98.7% of fields right, in 6.3 seconds each: measured on a test bench on 4 September 2026, on a test system.