Operational process map template
By Kivrelune Studio

Operational process map
Document how work moves between people, systems and exceptions from trigger to completion.
Boundaries
Process: [name]. Starts when [event]. Ends when [observable result]. Inputs and origin: [items]. Customers of the output: [roles].
Trace the path
Step [number]: [role] uses [input] to produce [output]. Next handoff: [recipient and signal]. At decision [point], take route A if [condition], otherwise route B.
Control and change
Failure signal: [measure or complaint]. Recovery owner: [role]. Confirm the map against [recent real instance]. Last checked: [date], by [owner].
Using this template
Follow a recent instance of the process from the triggering event to the completed handoff and record who acted at each step. Walk the map with its participants to verify decision rules, exceptions and signals of failure.
Questions & answers
Looking for more help? Visit the Help center.
How should we depict a path that occurs only occasionally?
Place its trigger beside the relevant decision and identify the actor, action and re-entry point. Test the branch against a real past exception before publishing the map.
What is included in this template?
Boundaries · Trace the path · Control and change. Each section includes prompts you can adapt to your team.
How can the next shift use the finished document?
Leave a clear trigger, one person responsible for each action, and the signal that shows the work is done. Let a teammate try the instructions before you publish.
How do I use my own copy?
Choose “Start with this doc” to open an editable copy on this device. You can also copy the Markdown or download the file and use it in your own editor.

