Basic flowchart template

Basic flowchart template: handle an incoming request

A worked example to adapt. Rename steps, add branches and owners to match how your team actually works.

flowchart TD
  s(["Start"])
  in[/"Receive request"/]
  chk["Check the request details"]
  d1{"Is anything missing?"}
  ask["Ask for the missing details"]
  d2{"Can we do it?"}
  no["Explain why and suggest an option"]
  do["Do the work"]
  rec["Record the outcome"]
  e(["End"])
  s --> in
  in --> chk
  chk --> d1
  d1 -->|Yes| ask
  ask --> chk
  d1 -->|No| d2
  d2 -->|Yes| do
  d2 -->|No| no
  no --> rec
  do --> rec
  rec --> e

About this basic flowchart template

Most flowcharts need only a handful of symbols. This template uses each of them once so you can see how they connect: an oval to start and end, a parallelogram for something that comes in, rectangles for actions, diamonds for yes/no questions, and a document shape for a record that gets written.

The example handles an incoming request, which is a shape almost every team has: a ticket, an order, a form, an access request. Keep the structure and rename the boxes, or use it as a reference while you draw your own.

Step by step

1. Start and input. One start oval, then the input that triggers the process. Name the real trigger, such as "Customer submits form".
2. Process steps. Each rectangle is one action written as a verb and an object. Split a box if it hides two actions done by different people.
3. Decisions. Each diamond asks one yes/no question and has exactly two labeled exits.
4. Loops. "Is anything missing?" loops back to the check, which shows rework honestly instead of hiding it.
5. Records and end. The document shape marks what gets written down; every path finishes at an end oval.

How to make it in flow-chart.io

1. Start from the example. Edit the text in the generator box above so it names your own trigger, steps and checks, then press Generate. The free preview needs no sign-up.
2. Add the branches. Add the decision points that matter for you, for example "is it urgent?" or "over the approval limit?". Each decision becomes a diamond with labeled outcomes.
3. Assign owners. Save the diagram to the editor (free account) and rename steps to show who does what: who receives, who checks and who does the work.
4. Share or export. Share a read-only view link: people with the link can view the diagram but not edit it. Downloads as PNG, SVG or PDF are part of Flow Pro (see pricing).

Tips

• Write every process box as verb plus object ("Check details", not "Details").
• Label both exits of every diamond so nobody has to guess which way is yes.
• If the chart gets wider than a page, move a section into its own flowchart and link to it.
• Use the flowchart symbols guide when you need a shape this template does not include.

Frequently asked questions

What symbols does a basic flowchart need?

Usually five: an oval for start and end, a rectangle for each step, a diamond for each yes/no decision, a parallelogram for inputs or outputs, and arrows to show the order. Add a document or database shape only when a record matters to the reader.

Can I use this flowchart template for free?

Yes. You can edit the prompt on this page and generate a free editable preview without signing up. A free account saves one diagram and shares it as a read-only link; downloads (PNG, SVG, PDF, PowerPoint, Mermaid, JSON) are part of Flow Pro.

Is there a Word or PowerPoint version?

Flow Pro exports PowerPoint and PDF, which you can place in a slide deck or a document. The Mermaid source below also renders in any Markdown tool that supports Mermaid.

How do I add more branches?

Add another diamond with its own yes/no question, then connect each exit to the next step. In the editor you can also describe the change in words, for example "add an urgent path that skips the queue".

Related