The BA's process-mapping starter kit
Need a map now? Open a ready template below and fill in the emoji-marked boxes — free, no sign-up.
Building out the engagement? Download the RACI, SOP and requirements doc to go with it.
By Jack Finnegan · Updated 8 June 2026
Simple process map — single pool, no lanes
A blank template, how to make it yours, and a worked example.
Blank template — fill in the emoji-marked boxes
A blank single-pool process map template to copy and fill in. The emoji-marked placeholders show where to put your trigger, steps, decision and outcome — replace each one with your own wording.
How to make it yours
- Open the template in BA Copilot, then rename ▶️ Trigger to the event that kicks your process off (e.g. “Order received”).
- Rename ✏️ Step 1–3 to the real activities, in the order they happen — add or delete boxes as you go.
- Turn ❓ Decision? into the real yes/no question and relabel the two branches.
- Point 🔁 If no: redo at what should happen when the answer is no, then send it back to the step that repeats.
- Rename 🏁 Done to the real end state — that’s your first draft mapped.
Worked example — the same template filled in for raising a change request
The blank process map template above, filled in for a real process — raising a change request. It follows the same shape (trigger, steps, a decision and a rework loop) so you can see what a finished single-pool map looks like before you adapt the blank one.
Cross-functional collaboration — two pools with lanes
A blank template, how to make it yours, and a worked example.
Blank template — fill in the emoji-marked boxes
A blank cross-organisation collaboration template to copy and fill in. Pool A (your organisation) has two lanes; Pool B (a customer or supplier) has one. Solid arrows are the flow inside each pool; the dashed lines are messages passing between them. Replace every emoji-marked box with your own wording.
How to make it yours
- Rename the pools (👥 Your organisation, 🤝 Customer or supplier) to your two parties, and the lanes (🙋 Front line, 🛠️ Back office, ✉️ Their process) to the real roles.
- Replace each ✏️ box with a real activity, keeping it in the lane of whoever does it — drag boxes between lanes as ownership changes.
- Keep solid arrows inside a pool; use the dashed message flows only for things that pass between the parties (a request out, a reply back).
- Turn ❓ All good? into the real decision — 🏁 Done is the happy path, 🚫 Closed is the exception.
- Delete the parts you don’t need; BA Copilot keeps every arrow attached as you edit.
Worked example — the same collaboration filled in for handling a customer complaint
The blank collaboration template above, filled in for a real process — handling a customer complaint. Acme Ltd's Support team and Investigations lane work the complaint while the customer (the second pool) supplies details; the dashed message flows carry the request for details out and the details back, and the decision splits an upheld complaint from one that is explained and closed.
Download the kit
One zip with 3 document files and 4 maps (PNG + BPMN + SVG). Free to use and share — no sign-up.
Frequently asked questions
Why these five?
They are the artefacts a BA needs on almost every engagement. The single-pool process map and the collaboration map are the two formats you start with — a simple single-pool flow, then the cross-functional version with lanes and message flows once more than one team is involved. The RACI, SOP and requirements doc are the documents that hang off them. Having all five ready removes the blank-page tax.
How do I use the map templates?
Each map is a fill-in-the-blank skeleton. Open it in BA Copilot, then replace every emoji-marked box (▶️ trigger, ✏️ steps, ❓ decision, 🏁 / 🚫 ends) with your own wording. There is a short step-by-step guide under each map telling you exactly what to swap and how.
Is it free?
Yes, free to use and share. No sign-up required to download.
More free packs
Stop rebuilding the same five templates
Open the templates in BA Copilot and fill them in for your project — no blank page, no Visio licence.