How to Create a Business Process Flowchart (Step-by-Step)

Most business process flowcharts fail for the same reason: someone starts by opening a diagramming tool instead of a blank page. If you sit down and try to lay out shapes and arrows before you've written down the actual steps in plain language, you end up redrawing the whole thing twice. Here's how to create a flowchart for a business process the way I do it with clients — starting with words, not shapes.

Step 1: List every step before you draw anything

Open a blank doc, not a diagramming tool, and write the process as plain sentences in order. For a client onboarding process this might look like:

1. Client signs contract.
2. Sales notifies onboarding team.
3. Onboarding specialist schedules kickoff call.
4. Client fills out intake form.
5. Specialist reviews intake form for completeness.
6. If incomplete, specialist follows up with client.
7. If complete, specialist creates project workspace.
8. Kickoff call happens.
9. Process ends when first deliverable is scheduled.

This list is 90% of the actual thinking work. The diagram is just a translation of it.

Step 2: Mark every decision point

Read back through your list and circle anywhere the next step depends on a condition. In the example above, step 6 is a decision: "is the intake form complete?" Decisions are the places flowcharts add real value over a bullet list, because they show branching that's hard to read in prose.

A useful test: if you can't phrase the branch point as a yes/no or multiple-choice question, it's probably not a decision — it might just be a missing step you haven't written down yet.

Step 3: Choose your symbols

Standard flowchart notation, which traces back to work formalized by ANSI and later incorporated into broader process notation standards, uses a small, consistent symbol set:

• Oval — start or end point. Every flowchart needs exactly one start.
• Rectangle — a single action or step.
• Diamond — a decision, always with at least two labeled exits (e.g. "Yes" / "No").
• Arrow — direction of flow.
• Parallelogram (optional) — input or output, like a form or a document.

You don't need more than this for the vast majority of business processes. Teams that reach for BPMN's full OMG specification usually only need it once they're modeling processes for formal compliance or automation handoff — for internal team clarity, the basic five shapes cover it. For a deeper reference on symbol meaning, see our flowchart symbols guide.

Step 4: Draw the happy path first

Lay out the no-exceptions, everything-goes-right version of the process left to right or top to bottom, one arrow at a time. Resist the urge to add every edge case as you go — you'll tangle the layout and have to redo it. Get the main line clean first.

Step 5: Add exception and error branches

Now add the decision paths you identified in step 2. Each branch needs a clear resolution — either it loops back into the main flow, or it reaches its own end point. A branch that trails off with no arrow leaving it is the most common error I see in client-drawn flowcharts.

Step 6: Assign owners

Add who does each step, either as a label on the box or by converting the diagram into a swimlane layout if the process crosses more than two roles. This step alone catches a huge share of real process problems, because it's often the first time anyone has written down who is actually responsible for a handoff.

Step 7: Validate with the person who does the work

Show the draft to whoever executes this process weekly, not just their manager. In my experience, the manager's mental model and the frontline reality diverge in at least one meaningful way almost every time — an extra approval step that got added informally, a shortcut that's become the real default. Fix the diagram to match reality, or explicitly flag it as the process you want them to switch to going forward.

Comparison table: manual vs. tool-assisted flowcharting

Step 8: Publish it somewhere it'll actually get used

A flowchart that lives only in the file you drew it in doesn't help anyone. Put it where the team already looks — a shared workspace, a pinned doc, or attached to the client or project record it describes. Set a reminder to review it in 90 days; processes drift, and an outdated flowchart is worse than no flowchart because people trust it.

Once you've got the habit down, a single business process flowchart takes 20 to 30 minutes to draft and another 15 to validate. The upfront listing step is what makes that speed possible — skip it, and you'll spend twice as long fighting the diagram itself.