Flowchart vocabulary, a seven-step DrawFig workflow, templates, design rules, research examples, and TikZ export.
Flowcharts that survive peer review — a practical guide
Published: 2026-03-12
Category: Tutorial
Reading time: ~18 min
This English article condenses the longer Chinese guide on the same topic. Switch to Chinese via
?lang=zh on
/blog/2026-03-12-flowchart-guide.html for the original wording.
Introduction
Flowcharts explain control flow: who does what, in which order, with which branches. In grants, papers, SOPs, and IRB packets, a
clean flowchart beats a wall of prose.
DrawFig (draw.io heritage) gives you snapping connectors, reusable templates, and
TikZ when you need LaTeX-native output.
1 — Vocabulary
| Shape |
Meaning |
| Terminator (stadium) |
Start / end |
| Rectangle |
Process / action |
| Diamond |
Decision |
| Parallelogram |
Input / output |
| Cylinder |
Data store |
| Document |
Report / artefact |
Rules of thumb
- One entry point, clearly marked exits
- Decision diamonds must expose
every branch (even error paths)
- Keep labels verb-first (“Validate token”)
2 — Seven-step professional workflow
- Draft on paper — list steps + decisions before touching the mouse.
- Pick orientation — usually top-down for procedures, left-right for pipelines.
- Drop skeleton nodes — no colours yet, just topology.
- Connect with orthogonal edges — fewer crossings than freehand diagonals.
- Align & distribute — use the built-in arrange tools every few minutes.
- Apply palette — two neutrals + one accent colour for print safety.
- Review with a reader — someone unfamiliar should trace the chart in <60s.
3 — Five templates you will reuse
- Linear process — onboarding, sample prep.
- Branch + merge — CI/CD style gates.
- Loop — retry until success / max attempts.
- Swimlanes — multi-role handoffs (PI / student / core facility).
- Exception path — highlight red dashed edges for failure handling.
Save each as a
.drawio starter in your team drive.
4 — Ten design rules
- ≤12 nodes per canvas for slides; split if larger.
- Consistent font (e.g. 10–11 pt sans) across the deck.
- Align baselines of parallel boxes.
- Avoid crossing rivers — reorder columns before adding jumps.
- Annotate decisions with Yes/No or condition text on both exits.
- Number optional only when the doc references “Step 3”.
- Legend if colour carries meaning.
- Margins — leave ≥24 px breathing room around the bounding box for export cropping.
- Accessible contrast — test print in greyscale.
- Version diagrams like code (
flow_v3.drawio + Git tag).
5 — Three research-flavoured stories
Grant methods flow
Show recruitment → consent → assay → QC → analysis with IRB decision diamond.
Lab SOP
Depict centrifuge speeds, timers, and stop conditions with warning glyphs.
Data pipeline
Ingest → clean → feature store → training → evaluation, with feedback loops for drift monitoring.
Each story exports to
PDF for appendices and
TikZ for LaTeX methods sections.
6 — TikZ export specifics
- Finish layout first — TikZ output respects coordinates.
- Export → TikZ → choose snippet mode inside your
methods.tex.
- Add libraries (
arrows.meta, positioning, …) as instructed by the export header.
- If line breaks differ, tweak
node distance once in LaTeX rather than re-dragging everything.
7 — FAQ snapshot
Q: Swimlanes in DrawFig?
A: Use horizontal containers or tables; group roles with background rectangles.
Q: BPMN vs simple flowchart?
A: BPMN adds events/gateways — only adopt if your audience expects that notation.
Q: Animations?
A: Not in-editor; export frames or use Beamer overlays.
8 — Learning resources
9 — Action checklist
- [ ] Pick one messy slide deck flow and redraw in DrawFig
- [ ] Export TikZ snippet into a dummy
article.tex
- [ ] Share
.drawio source with co-authors via Git
Start drawing: https://drawfig.com/editor.html
DrawFig Team — updated 2026-03-12