Founder notes
How to Document Business Workflows Before You Automate Them
Walk through a real job with the people who do it. Capture handoffs and exceptions, then use those examples to test the new system.
By Hassan Jamal, Co-founder and Lead Engineer
PublishedStart with somebody doing a real job. Ask them to walk you through a recent order, show where they got the details and explain what had to happen before they could hand it to the next person. Do this with each team that touches the order, including the person who gets the call when things go wrong.
What did we learn by sitting down with the team?
At Panda Patches, I led the engineering work on a system that replaced spreadsheet processes. I spoke with sales agents, production staff and the people who digitize artwork and create mockups. Each group knew a part of the order journey. Seeing those steps together helped us decide what information to carry through the order and when to tell the next person it was ready.
Panda Patches is owned by my PandaCodeGen co-founder, Imran Raza Ladhani. I described this part of the work in Tech Magazine when it asked how teams prevent critical knowledge gaps. See the founder-affiliated Panda Patches project.
What should go in a workflow note?
| Record | Example to test |
|---|---|
| Starting event | Customer confirms the artwork and order details. |
| Information needed | The approved file, order reference and any special instructions. |
| Owner and next step | Production receives the job and confirms it can begin. |
| Exception | If the file is missing or a change comes in, send the job back for review with a clear owner. |
| Evidence it worked | Staff can tell which file was approved and see the current status. |
Keep the first note short enough for someone to correct on a call. Give it an owner who can update it when the real process changes. Mark which facts came from the order and which were guessed. Where two teams describe the same step differently, show them the same case and agree what should happen.
How do you check the workflow before making it live?
Pick a standard case and two exceptions, such as a file arriving late or a customer changing a confirmed order. Have the teams run each case and explain what they expected to happen next. Check who can update a status, whether a message goes to the intended person and how someone can recover a mistake. Use sample records for the walkthrough if the real ones contain private information.
At handover, ask somebody who missed the meeting to do one task using the guide. If they have to call the developer, record where they got stuck and update the guide or the screen. A short, tested handoff gives new staff a place to start.
For the question of when the current tools are worth replacing, read the rebuild decision guide.
Common questions
Who should help document a workflow?
How do you tell if a workflow is ready to automate?
Related Articles
When Should You Rebuild an Aging Business System?
Follow one order through your team. Use repeated handoffs, mistakes and support costs to decide what to repair, connect or rebuild.
Should You Build or Buy Software in 2026? A Cost Framework
Compare SaaS with custom software using current quotes, migration, maintenance, security, adoption, operating risk, and scenario-based break-even.
Can You Export Your Website? What 8 Platforms Let You Take
What Wix, Squarespace, Webflow, Shopify, WooCommerce, GoHighLevel and WordPress let you export, from their own help pages, and what to save before you cancel.
PandaCodeGen offers website and application development. Recommendations here reflect our delivery approach; the proposal for your project defines its scope. How we use evidence.