Process flow chart maker
Document how work actually gets done: the steps, the approvals, the waits. Type the process, tag documents, systems and delays, and export a clean process map for your SOP or improvement workshop.
How to write steps
- One step per line. Lines connect top to bottom.
- End a line with
?to make a decision. Indent the answers under it:yes: Ship it,no: Refund. - Indent more lines under an answer to continue that branch.
-> Step namejumps back to an earlier step (a loop).no -> Step nameworks inside a decision.Start,End,DoneorStopbecome rounded start/end shapes.- Shape tags:
[input][output][doc][db][sub][manual][delay]. lane: Saleson its own line puts the next steps in a swimlane.- Or paste Mermaid code starting with
flowchart TD. It’s detected automatically.
Mermaid code for this chart
flowchart TD
n1(["Start"])
n2@{ shape: doc, label: "Purchase request submitted" }
n3{"Under the budget limit?"}
n4["Team lead approves"]
n5@{ shape: delay, label: "Wait for director approval (2 days)" }
n6{"Director approves?"}
n7[/"Notify requester"/]
n8(["End"])
n9["Procurement gets three quotes"]
n10@{ shape: delay, label: "Wait for quotes (3 days)" }
n11["Place purchase order"]
n12[("Record in finance system")]
n13[/"Confirm to requester"/]
n1 --> n2
n2 --> n3
n3 -->|"yes"| n4
n3 -->|"no"| n5
n5 --> n6
n6 -->|"no"| n7
n7 --> n8
n4 --> n9
n6 -->|"yes"| n9
n9 --> n10
n10 --> n11
n11 --> n12
n12 --> n13
n13 --> n8How to map a process
- Pick one process with a clear trigger and outcome, e.g. “purchase request received” to “order confirmed”.
- Walk it with the people who do it. Map how it really works today, not how the policy says it works.
- Write each step as verb + object. “Approve request”, “Send quote”.
- Mark decisions, documents, systems and waits with
?,[doc],[db]and[delay]. - Add owners with
lane:lines if several teams are involved. That makes it a swimlane diagram. - Look for waste: long delays, loops that send work back, and approvals that rarely say no.
Flowchart shapes for process maps
| Shape | Type | Use for |
|---|---|---|
| Rectangle | Approve request | Work being done |
| Diamond | Over budget? | Approvals, checks |
| Document | [doc] Invoice | Forms, reports |
| Cylinder | [db] ERP | Systems of record |
| D-shape | [delay] Wait 2 days | Queues and waiting |
| Double-sided box | [sub] Credit check | A process mapped elsewhere |
Need a starting point? The order fulfilment, expense approval and onboarding templates are all process flow charts.
Questions people ask
What is a process flow chart?
A process flow chart shows the steps of a business or production process in order, including decisions, hand-offs and waiting times. It’s used to document how work is done and to find where it can be improved.
What is the difference between a process map and a flowchart?
In practice the terms overlap. “Process map” is the Lean / Six Sigma name and usually implies extra detail such as owners (swimlanes), inputs, outputs and times; a flowchart is the general drawing technique behind it.
Is a workflow diagram the same thing?
Mostly. A workflow diagram tends to show how tasks and approvals move between people or software, which is why they often use swimlanes. You can draw either with this tool.
What about BPMN?
BPMN 2.0 is a formal notation with around a hundred element types, used when diagrams are executed by workflow engines. FlowBuilder deliberately sticks to classic flowchart shapes, which cover what most teams need for documentation and training.
How do I show waiting time?
Use a delay step: [delay] Wait for approval (2 days). Writing the typical duration in the label turns your chart into a quick value-stream view.