A flowchart is the simplest honest picture of a process: boxes for the things you do, arrows for the order you do them in, and a diamond wherever the path splits on a decision. This template gives you that skeleton already built — a clean seven-step flow that runs from Start / trigger through a single yes/no Decision point and back together to a clear End. It is deliberately generic, so it fits almost any procedure you need to map: an approval, an onboarding, a support triage, a release checklist, a returns process.
It is built for anyone who has to explain how something works to someone else — a team lead writing down a process that until now only lived in one person's head, an operations manager standardizing a workflow across a team, a founder documenting the first version of a repeatable task before they hand it off. If you have ever tried to describe a procedure in a wall of text and watched people's eyes glaze over, a flowchart is the fix. The shape carries the meaning.
What makes this version different from a picture you would draw in a slide deck is that every box here is a live card. You can rename it, assign an owner to it, attach a file to it, link it to other work, and — when you are ready — ask AI to extend the flow for you. The diagram is the starting point, not the finished artifact.
What's in this flowchart template
The template is seven cards connected by seven arrows, with one branch that splits and merges. Read left to right and top to bottom, it tells a complete little story.
Start / trigger. Every process begins with something that sets it off — a form is submitted, a ticket is opened, a date arrives, a customer asks. This first card is that trigger. Naming it well matters more than people expect: a vague start ("someone notices a problem") produces a vague process, while a specific trigger ("a refund request lands in the queue") makes everything downstream concrete.
Do the step. The first real action. In your version this becomes whatever the first concrete task is — verify the request, gather the inputs, run the check. It is the placeholder for "the work happens here."
Decision point. This is the diamond, and it is the heart of the template. A decision point asks a single yes-or-no question and sends the flow down one of two paths. This is the part most people leave out when they describe a process casually, and it is exactly where real work lives — the approval that can be granted or denied, the check that passes or fails, the case that is simple or needs escalation.
Path A and Path B. The two branches out of the decision. On the graph, the edge to Path A is labeled yes and the edge to Path B is labeled no — those labels are the whole reason a flowchart beats a checklist, because they make the condition explicit instead of implied. Path A is the happy path; Path B is what happens when the answer is no. In your real process these become, say, "approve and fulfill" versus "request more information," or "auto-resolve" versus "escalate to a human."
Merge. Both paths come back together here. This is a small but important idea: after a branch handles its two cases, the process often rejoins a common finish. Modeling the merge explicitly keeps the chart honest — it shows that both routes still have to complete the same closing steps rather than trailing off into nothing.
End. The process is done. A clear end state is what lets you say a case is truly closed, and it is the anchor you measure cycle time against — from trigger to end.
Every arrow in the template is a typed feeds relationship, which is FlowGraph's way of saying "this step flows into the next." That typing is not decoration: it is what lets the graph understand the order of your process, not just draw lines between boxes.
How to use it in FlowGraph
- Open the template. Click Open in FlowGraph to load the flowchart as a live, editable graph. Viewing, rearranging, and editing are free with no account — you can shape the whole thing before you decide to save anything.
- Edit the steps. Rename each box to your real process. Replace Do the step with your first concrete action, and keep going. Add cards where your process has more steps than the template's skeleton, and delete any you do not need. The layout stays clean as you go.
- Add a decision branch. The template already includes one yes/no split, but real processes usually have several. Split any step into two paths by drawing edges to two new cards, then merge them back together downstream. Label the edges with the actual condition — approved / rejected, in stock / backordered — so the chart reads as a decision, not a guess.
- Assign owners. Add the responsible person to each card so the flowchart answers the question every process review asks: whose job is this step? Now the diagram is not just how the work flows — it is who does it.
- Cross-link related work. Because each card is a real object, you can link a step to the document that governs it, the form it produces, or a card in another graph entirely. A flowchart step can point at the policy that defines it, so the "why" lives next to the "what."
- Ask AI to extend it. With your own AI key, describe the next stage in plain language — "add an escalation path when the approval is denied twice" — and the planner draws it for you to review. The AI proposes; you verify and decide. Nothing is written to your graph until you accept it, and every accepted change carries a receipt.
Why a living graph beats a static flowchart
A flowchart drawn in a slide or a whiteboard photo is a snapshot of what someone believed the process was on the day they drew it. It cannot be assigned, it cannot be linked to the real work, and the moment the process changes it starts lying to you. Most flowcharts in most companies are quietly wrong, and nobody notices until a new hire follows one off a cliff.
A living graph fixes that because every box is a real card, not a shape. You can assign an owner to a step, attach the actual template or form it uses, and link it to the ticket, the policy, or the downstream process it connects to. The relationships are the point — a process is nothing but steps in relationship to each other, and a graph models exactly that. When the process changes, you drag an edge and the chart is current again.
And because FlowGraph is governed and local-first, every edit is reversible and carries a receipt: who changed this step, when, and why. That means the flowchart doubles as a record of how your process has evolved, not just how it looks today. You can hand it to a new team member as a real training tool, ask AI to extend it into new cases with your own key, and keep it honest — all on top of a single, traceable write path. It opens with no account; you only sign up when you want to save it to a vault or plan with AI.
Frequently asked questions
What is a flowchart?
A flowchart is a diagram that lays out the steps of a process in the order they happen, using boxes for actions and diamonds for decisions, connected by arrows that show the flow. It turns a procedure that would take paragraphs to describe into a shape you can follow at a glance.
The reason flowcharts endure is that they make a process both easy to follow and easy to improve. Once the steps and decisions are visible, the redundant step, the missing branch, and the bottleneck all stand out — you can see the problem instead of arguing about it.
How is a FlowGraph flowchart different?
It is not a static picture. Each box is a live card you can assign an owner to, attach files to, and link to other work anywhere in your graph. The arrows are typed relationships the app actually understands, not just drawn lines, so the chart knows the order of your process.
On top of that, you can ask AI with your own key to extend the flow, and every change is governed — reversible and stamped with a receipt of who did what and when. The flowchart becomes a working document you run your process on, not a diagram you file away and forget.
Is the flowchart maker free?
Yes. Opening the template, editing the steps, adding branches, and viewing the whole flowchart are free with no account. You can build out your entire process before you ever create a login.
Signing up is the moment you want to save the chart to your own vault so it persists across sessions, or plan with AI to extend it. Everything up to that point is yours to explore for free — local-first, in your browser, no strings.