What a algorithmic flowchart is
A flowchart traces a process step by step, branching at each decision into yes and no paths. It turns "how do we handle this?" from tribal knowledge into something a new starter can follow on their first day.
When to use one
- Documenting a support, triage or escalation procedure
- Finding the branch where a process quietly loops or dead-ends
- Agreeing on how something works before automating it
The data format
Branching: id, type, text, next1(YES), next2(NO). Types: start/process/io/decision/end.
Paste rows like this — copy the example straight into the builder to see it render:
n1, start, Receive ticket, n2 n2, process, Triage severity, n3 n3, decision, Critical?, n4, n5 n4, process, Page the on-call engineer immediately, n6 n5, process, Add to the normal support queue, n6 n6, end, Close ticket
How to make one
- Paste your data into the Studio, or upload a CSV or XLSX file.
- Set your colours — by hand, from pasted brand hex codes, or extracted from your logo.
- Generate and export as PNG or SVG for your deck or report.
One thing people get wrong. Every decision needs both branches drawn. Unhandled no-paths are exactly where real cases fall through the cracks.
Why it runs in your browser
Charts are parsed and drawn entirely on your own device. No rows, files or logos are uploaded, so a algorithmic flowchart built from confidential project or process data never touches a server. You can verify it: open your browser's network tab while you generate one.