How to map one workflow before you automate it
Every Monday, your volunteer coordinator copies sign-ups from a form into a spreadsheet, then emails reminders one by one. Someone says, "We should automate this." Maybe. But if you automate a messy process, you just get the mess faster. This guide shows you how to map the work first, in one meeting, with a free canvas you can fill in right here.
Before you automate any nonprofit workflow, map it. Write down where it starts and ends, every step, who does it, which tool they use and what information they touch. Mark where people retype information, wait on someone else, or handle personal details. Fix the obvious problems first. Then automate only the boring, repeatable steps, and keep a person in charge of every decision about a person.
- 1Why map before you automate
- 2The five parts of a map
- 3Map it in one meeting
- 4A worked example
- 5The free canvas
- 6What comes after the map
Why map before you automate
Three reasons, and all three come up again and again with nonprofits.
- You'll automate the wrong thing. The work people describe in a meeting is rarely the work they actually do. A map shows the real steps, including the workarounds nobody wrote down.
- You'll know where personal information goes. Volunteer forms, client intake and donor lists all carry personal details. Canada's federal privacy impact assessment template asks organizations to describe each step in the flow of personal information (Government of Canada). It's a good habit for nonprofits too.
- You'll keep a person where it matters. Automated tools make mistakes. In a 2025 test of AI helpers by safety institutes from several countries, including Canada, even the best result handled only about 57% of tasks safely (AI Security Institute). A map shows exactly where a person needs to say yes.
The five parts of a map
A useful map answers five questions. That's it.
1Where does it start and end?
Name the trigger ("a new volunteer fills in the form") and the finish line ("the volunteer shows up to their first shift"). Fuzzy edges make a map impossible to automate.
2What are the steps?
List every step in order: who does it, which tool they use, and what information they touch. Include the small ones, like "copy the email address into the spreadsheet."
3Where does work wait?
Mark every handoff, approval and "waiting to hear back." That's where most time disappears.
4What are the exceptions?
What happens when someone signs up twice, or needs a police check, or speaks French? Write down the cases that don't fit the normal path. Automation struggles with these, so a person usually keeps them.
5Where does personal information go?
Trace each piece of personal information from the moment you collect it to wherever it ends up. If it lands in someone's personal email or a free tool you haven't approved, fix that before anything else.
Map it in one meeting
You need the person who does the work, one other colleague, and a whiteboard or the canvas below.
- Watch it happen. Ask the person who does the work to walk through one real example, from start to finish, with their actual screens. Don't map the policy. Map what they do.
- Write every step. One line per step: who, which tool, what information. Count how long the whole thing takes, and how often it happens.
- Mark it up. Put a mark next to every step where someone retypes information, copies and pastes, waits, sends a reminder, or touches personal details.
- Fix the obvious first. Before you automate anything, remove steps that don't need to exist. Often the biggest win is deleting a step, not automating it.
A worked example: volunteer sign-ups
Here's what a map looks like for a fictional nonprofit, Harbor Community Hub. It's a teaching example, not a real organization.
| # | Step | Who | Tool | Marks |
|---|---|---|---|---|
| 1 | Volunteer fills in the sign-up form | Volunteer | Online form | PERSONAL INFO |
| 2 | Copy each sign-up into the volunteer spreadsheet | Coordinator | Spreadsheet | RETYPEDPERSONAL INFO |
| 3 | Check if a police check is needed | Coordinator | Policy doc | PERSON DECIDES |
| 4 | Email a welcome and orientation date | Coordinator | Personal email | COPY-PASTEWRONG PLACE |
| 5 | Wait for the volunteer to confirm | Volunteer | WAITING | |
| 6 | Send a reminder the day before | Coordinator | REMINDER |
Fictional example. Time today: about 3 hours a week.
What the map shows: step 2 can be automated (the form can send sign-ups straight to the spreadsheet), step 4 needs to move out of a personal email account, and step 6 is a simple scheduled reminder. Step 3 stays with a person, because it's a decision about a person.
The free Workflow Mapping Canvas
Fill it in during your meeting. Load the example to see how it works. Nothing you type is saved or sent anywhere. When you're done, print it or save it as a PDF.
Tip: tick the marks under each step. Steps marked Retyped, Copy-paste or Reminder are usually the best ones to automate.
What to automate, and what to keep
- Copying form entries into a list or database
- Reminders and confirmations
- Status updates ("received," "scheduled")
- Moving files to the right folder
- A first draft for a person to check
- Decisions about who gets help, a role or money
- Anything sensitive, like safety or health concerns
- Exceptions and complaints
- Anything sent to the public without a check
Before you switch anything on, write down three things: who owns the automation, how to turn it off, and how you'll know if it stops working. Then measure the time it takes after a month, and compare it with your map.
What comes after the map
A map is step one. We think about it as a ladder, and you only climb when the step you're on is working.
Many nonprofits stop at step 2 or 3 for a while, and that's fine. Connected, tidy information saves time on its own, and it's what makes automation and AI work later. Not sure where you are? Try our readiness self-check.
Sources worth your time
- Government of Canada · Treasury BoardPrivacy impact assessment template →
Shows how to describe each step in the flow of personal information. Built for government, useful for anyone.
- Innovation, Science and Economic Development Canada · 2025Implementation guide for managers of AI systems →
A voluntary guide covering owners, records and off switches for any automated system.
- Canadian Centre for Cyber SecurityTop 10 AI security actions →
Includes keeping a person in the loop with clear controls over what automated tools can do.
- Nimara · free guideIs your nonprofit ready for AI? →
A 12-question self-check across rules, data, systems and people.
Questions people ask
What is a workflow map?
A simple written picture of how one piece of work gets done: where it starts and ends, each step, who does it, which tool they use and what information they touch. It can be a table, a whiteboard or our free canvas.
Which workflow should we map first?
Pick one that happens often, follows the same steps each time, and annoys the people who do it. Volunteer sign-ups, event registrations and intake forms are common first choices.
Do we need special software to map a workflow?
No. A whiteboard, a spreadsheet or our free canvas is enough. The value is in watching the real work and writing it down, not in the tool.
What's the difference between automation and AI?
Automation follows fixed rules, like "when a form comes in, add it to the spreadsheet." AI makes a guess, like drafting a reply. Start with automation for repeatable steps, and add AI later, with a person checking its work.
Should we automate everything we can?
No. Automate the boring, repeatable steps. Keep decisions about people, sensitive situations and exceptions with a person, and make sure every automation has an owner and an off switch.
How do we know if automating it worked?
Write down how long the work takes before you start. Check again after a month. If it's not saving time, or it's causing new mistakes, change it or switch it off.
Want help with the map, or what comes next?
We help nonprofits map one workflow, connect the tools they already use, and automate the boring parts, with a person in charge of every decision about a person. Now, or when you're ready.
Book a Call →See Connected Systems
Starting on your own? Write your AI rules first, then map one workflow with the canvas above.
Map it. Fix it. Then automate it.
Updated October 2026. All examples are fictional. This guide is general information. Written with AI assistance. Reviewed by a person.
