178 templates · page 2 of 2
Project & Planning diagram templates
Gantt, timeline, kanban, mindmap, roadmap, journey.
Teaching Case — A Start Date That Contradicts Its Own Plan
The defect this engine was built to catch, and it is invisible in every tool that draws what it is told. `cut` states it must start on 15 September; its own predecessors do not release it until the 29th — ten working days later. Both sentences are in the same document, both look entirely reasonable, and the drawing of the wrong one is identical to the drawing of the right one. The engine names the contradiction and counts the days.
Gantt & critical pathTeaching Case — A Plan That Cannot Be Scheduled At All
Draft waits for review, review waits for rework, rework waits for draft. That is a loop, it has no schedule — there is no first task — and Mermaid will draw it anyway, in colour, with dates. Here nothing is drawn on a time axis at all, because no date exists to draw, and the engine names the loop in the order you trace it.
Gantt & critical pathTeaching Case — One Person, Two Tasks, Same Fortnight
Two bars drawn side by side look like two things happening in parallel, and they are — unless the same person is on both. Sam is booked at 200% for a fortnight here. The bars are the correct bars; the plan is still impossible. The engine sweeps every resource against its declared capacity and says who, when, and on what.
Gantt & critical pathTeaching Case — What "I Could Not Check That" Looks Like
The most important template here, and nothing in it is badly written: it is an ordinary plan in its first week, with one task nobody has estimated yet. Everything downstream of that task therefore has NO DATE. Rather than drawing bars anyway, the engine leaves those rows blank, says which task caused it, and reports the plan as not verified. That state — checked, and could not decide — is the one most tools never show anyone.
Gantt & critical pathConference Programme — Progress Against a Stated Today
A twelve-week event plan with percentage progress on each task, checked against a `today` the DOCUMENT states rather than a clock. That is deliberate: an engine with a clock renders a different figure tomorrow, which cannot be cached, diffed, thumbnailed or verified. Reports clean, with the progress on every bar consistent with the dates around it.
Gantt & critical pathClinical Trial — Elapsed-Day Waiting Periods
Regulatory clocks do not pause for the weekend. Every waiting period here is written in calendar days (`30cd`), and the engine converts each one to working days from wherever its predecessor actually lands — so a submission that finishes on a Friday waits the same thirty days as one that finishes on a Tuesday, and the bars differ accordingly. Reports clean.
Gantt & critical pathRelative Plan — Day Numbers, Because No Date Was Stated
A plan with no start date is still a plan: five days, then ten, then three. The engine schedules it, computes the critical path and the float, and draws the axis in DAY NUMBERS — because inventing a Monday would put a fabricated Tuesday under every bar and a fabricated weekend in the middle of one. There is deliberately no `calendar` line either: with no date there is no way to know which day is a Saturday, so declaring a working week here would declare something the engine cannot apply — and it says so if you do. Add `start 2026-03-02` and every bar becomes a date, on the week you then declare, without another edit.
Gantt & critical pathBaseline vs Actual — What Was Agreed, Under What Follows
Each bar carries a ghost underneath: the span that was agreed at kick-off. The bar above it is what the current durations and dependencies actually produce. A baseline is the one thing in this engine taken from the document rather than computed, because it is a historical claim and there is nothing to derive it from — everything above it is derived. Reports clean.
Gantt & critical pathThe Same Schedule as a Precedence Network
One line — `view network` — and the same document draws the activity-on-node network instead of the bars: a box per task carrying its own early start, duration, early finish, float, and what shortening it actually buys. Both views come from ONE schedule, so they cannot disagree; a network computed by a second pass would be two answers to one question. Reports clean.
Gantt & critical pathSix-Day Site Week — The Calendar Is Not An Assumption
The same durations under a Monday-to-Saturday working week, which is what a construction site runs. The working week is declared, not assumed, so "12 days" means one unambiguous thing and the engine says which — and the non-working days are shaded, so a bar that takes twelve days and spans fourteen is legible as such rather than mysterious. Reports clean.
Gantt & critical pathBusiness Model Canvas — Food Rescue Charity
Surplus-food charity whose beneficiaries and funders are different people, showing grant and corporate income against van and warehouse costs, with a deliberately empty partner block naming the supermarket relationships nobody has written down.
Business model canvasBusiness Model Canvas — Boutique Consultancy
Six-person data consultancy modelling 62 billable days a month against a small retained line, where the utilisation figure the whole model rests on is marked as a guess and the productised offer is still unpriced.
Business model canvasStory Map — Peer-to-Peer Marketplace MVP
Twenty cards and 146 points across four activities and four bands, where the first release covers discovery, listing and payment but leaves disputes entirely to release two — a 3-of-4 backbone span the map flags as a walking-skeleton gap.
User story mapStory Map — Outpatient Clinic Scheduling
Replacing three paper diaries with one booking screen, sliced into three waves; wave one books, moves and cancels but never runs a clinic, so the map flags the whole running-the-clinic activity as missing from the first band.
User story mapStory Map — Internal Developer Portal
Platform-team milestones along the service lifecycle — scaffold, ship, operate, comply — with bracketed estimates; the golden path gets an engineer to production before lunch but leaves every compliance control to the last milestone.
User story mapDecision Tree — Tender Strategy: Bid High, Bid Low or Walk Away
A contractor's bid decision with a downstream procurement choice: bidding high wins less often but rolls back to $447k against $264k for bidding low, and in both branches a fixed-price steelwork subcontract beats self-performing once overrun risk is priced in. Illustrative values.
Decision treeRisk Matrix — High-Rise Construction Project Risk Register
A principal contractor's register for a fictional 18-storey residential tower, with impacts banded by cost and programme: controls bring exposure from 89 to 52 (−42%), and the two risks left above the Medium appetite are a delayed Building Safety Regulator Gateway 2 approval (High 12) and façade subcontractor insolvency (High 8), both with treatment actions. Illustrative register.
Risk matrixRisk Matrix — Payments Platform Migration Cutover Register (4×4)
A cutover register for a fictional fintech moving 38 million payment records, on a 4×4 project matrix: controls move every risk down a band and cut exposure from 67 to 33 (−51%), leaving card-scheme certification as the one High risk above the Medium appetite, with a pre-certification test cycle as its treatment. Illustrative register.
Risk matrixPugh Matrix — E-bike Battery Mount Concepts
A weighted Pugh matrix screening four battery-mount concepts against the current down-tube rail, with one measured row — pack plus mount mass — compared with the datum's own value. The under-seat cassette leads with a weighted net of +0.40, better on four criteria and worse on one, and holds unless the weight on weight distribution more than doubles from 15% to 32%. Illustrative values.
Decision matrix (weighted / Pugh)Decision Matrix — School Heating Options Appraisal
An options appraisal for replacing a secondary school's heating, with like-for-like gas as the baseline and the trust's 120 tCO₂e carbon cap as a must-have that excludes both gas and the hybrid. A district heat connection ranks first at 3.69 of 5 — 0.49 above the gas baseline and 0.33 ahead of air-source heat pumps. Illustrative values.
Decision matrix (weighted / Pugh)Roadmap — Hardware Product Through EVT, DVT and PVT Gates
A stage-gated hardware roadmap for a fictional 22 kW wall-box EV charger, from engineering validation to mass production, with gate reviews as milestones on the band above the lanes: 16 items (3 done, 5 in progress, 7 planned, 1 at risk) and 4 milestones over six quarters, status date 10 Jun 2027. All 22 dependencies finish before their dependents start, including CE (LVD, EMC, RED) and UL 2594 testing after design validation, and the longest chain runs from the G2 concept freeze through EVT, DVT and the CE campaign to the retail launch. Illustrative roadmap.
RoadmapRoadmap — New Degree Programme From Validation to First Intake
A month-by-month roadmap for a fictional university launching a BSc (Hons) Data Science — 18 modules of 20 credits, 360 in all — from academic approval through the validation event to welcome week: 15 items (3 done, 2 in progress, 9 planned, 1 at risk) and 3 milestones across five lanes, status date 18 Jan 2027. All 19 dependencies finish before their dependents start; the longest chain, eight steps, runs from academic approval through learning outcomes, module specifications, the assessment strategy, the validation event and open days to first intake. Illustrative roadmap.
RoadmapTeaching Case — A Roadmap Whose Arrows Contradict Its Dates
A small product roadmap that looks plausible on a slide and is not, with each defect deliberately left in for the checker to find: the data-warehouse migration overruns into the quarter in which self-serve analytics is due to start (31 days of overlap), a pricing launch is dated 16 days before the billing rebuild it needs is finished, the mobile redesign was due to finish in April but is still in progress on the 20 May 2027 status date, and SSO is marked done though it is not due to start until July. 8 items in 3 lanes and 1 milestone. Illustrative roadmap.
RoadmapExam Revision Mind Map
Branch a subject into topics and subtopics to plan revision coverage.
MermaidSemester Study Plan (Timeline)
A term-long study cadence from foundations to finals.
MermaidResearch Project Plan (Gantt)
A four-phase research project timeline.
MermaidStudy Notes Outline (Markmap)
Turn lecture notes into an expandable outline mind map.
Markmap (Markdown)Product Roadmap (Timeline)
A quarter-by-quarter product roadmap.
MermaidWeekly Time Allocation (Pie)
Where the 168 hours of a week go — tune for your own schedule.
MermaidProduct Launch Plan (Gantt)
Build, test and launch phases with a go-live milestone.
MermaidMarketing Board (Kanban)
A marketing team's work board.
Kanban boardHouse Build (PERT)
Critical-path network for building a house.
PERT / CPM networkConference Planning (PERT)
Task network for organising a conference.
PERT / CPM networkKnockout Bracket (Tournament)
An eight-team single-elimination bracket.
Tournament bracketPersonal Tasks (Kanban)
A simple personal to-do board.
Kanban boardSoftware Release (PERT)
Task network from code freeze to production.
PERT / CPM networkEsports Playoffs (Tournament)
A four-team single-elimination playoff.
Tournament bracketProduct Roadmap (Timeline)
Release milestones across two phases.
Timeline (history)Project Delay (Fishbone)
Why a project is slipping its schedule.
Fishbone (Ishikawa)Product Backlog (Kanban)
A product team's delivery board.
Kanban boardFeature Delivery (PERT)
Network from discovery to launch.
PERT / CPM networkTennis Draw (Tournament)
An eight-player knockout draw.
Tournament bracketProject Phases (Timeline)
Discovery and delivery phases with milestones.
Timeline (history)Campaign Launch (PERT)
Task network for a marketing campaign.
PERT / CPM networkEditorial Calendar (Kanban)
Content moving from idea to published.
Kanban boardWedding Planning (PERT)
Task network leading to the wedding day.
PERT / CPM networkDSM — Aircraft Cabin Retrofit
Fourteen engineering and certification activities of a widebody cabin retrofit taken in the programme plan's own order, where five irreducible rework marks are quarantined into four iteration blocks.
Design structure matrixDSM — Marketing Authorisation Dossier
Sixteen authoring and review activities for a Common Technical Document submission in module order, partitioning into a safety-summary, clinical-overview, risk-plan and labelling loop plus a quality and bioequivalence pair.
Design structure matrixKanban — Investigations Desk
A newsroom investigations desk board from tip triage through legal read to publication, with a two-story WIP limit on writing and the FOI responses that stall in the waiting column.
Kanban boardPERT — Bridge Deck Replacement
Critical-path network for a weekend motorway bridge deck replacement, from possession handover through demolition and beam lift to trafficking, with the concrete cure dictating the float everywhere else.
PERT / CPM networkPERT — CubeSat Integration and Test
Assembly, integration and test network for a 6U CubeSat from structure fit-check to launch-provider delivery, with environmental testing and flight software freeze converging on the shipping milestone.
PERT / CPM networkTimeline — Sellafield Decommissioning Programme
Century-scale decommissioning programme for the legacy ponds and silos, separating retrievals milestones from site-wide end-state phases across a horizon no Gantt chart can hold.
Timeline (history)Excalidraw — Sprint Retrospective Board (Start / Stop / Continue)
A hand-drawn retrospective wall with three column headers and nine sticky notes for a software team's sprint review — what to start, stop and continue — and the dot-vote instruction underneath. Every note is a bound label inside its rectangle, so dragging a sticky in Excalidraw carries its text with it.
ExcalidrawProject Management — quarterly roadmap
Project-management vertical — a quarterly roadmap, drawn by gantt. Typed FlowScript for project management. Keywords: Gantt, roadmap, milestone, sprint, timeline.
FlowScriptProject Management — Release Delivery Pipeline
A release delivery pipeline: the plan on one side, and on the other the work items that actually travelled from committed to shipped. Typed FlowScript for project management. Keywords: Gantt, roadmap, milestone, sprint, timeline.
FlowScriptProject Management — research grant work plan
Two-year work plan for a funded research study as a Gantt chart: work packages with declared dependencies, the approvals that gate them, and the milestones a funder reports against. Typed FlowScript for project management. Keywords: Gantt, roadmap, milestone, sprint, timeline.
FlowScriptDigital twin handover assurance
Inspect parallel prerequisites and require model-data checks before operational acceptance. Typed FlowScript for project management. Keywords: Gantt, roadmap, milestone, sprint, timeline.
FlowScriptAI curriculum pilot and evaluation
Plan a reversible education pilot with explicit approval and evaluation milestones. Typed FlowScript for project management. Keywords: Gantt, roadmap, milestone, sprint, timeline.
FlowScriptProgressive platform migration
Use a staged migration with reconciliation before traffic change and retirement. Typed FlowScript for project management. Keywords: Gantt, roadmap, milestone, sprint, timeline.
FlowScriptCircular material recovery programme
Separate material characterisation, pilot recovery and receiver acceptance. Typed FlowScript for project management. Keywords: Gantt, roadmap, milestone, sprint, timeline.
FlowScriptReproducible research release
Make independent replication and discrepancy resolution visible before releasing research. Typed FlowScript for project management. Keywords: Gantt, roadmap, milestone, sprint, timeline.
FlowScriptEVM Performance Report — PV / EV / AC S-curve with CPI, SPI and EAC
Monthly earned value management report for a capital scheme: cumulative planned value, earned value and actual cost curves at the data date, with cost variance, schedule variance, CPI, SPI, TCPI and a CPI-based estimate at completion — the ANSI/EIA-748 figure a project controls manager files every period.
PlotBudget-to-Forecast Bridge — BAC £14.4m to EAC £16.0m by variance driver
Cost variance bridge for a monthly project review: the named drivers moving budget at completion to estimate at completion on a capital scheme, each priced, adding to the reported variance at completion.
Waterfall ChartQuantitative Schedule Risk Analysis — completion S-curve, P50 and P80
Cumulative probability curves from a Monte Carlo schedule risk analysis of a CPM network, pre- and post-mitigation, reading off the confidence in the deterministic finish date and the P50 and P80 dates used to set schedule contingency, as required by AACE RP 57R-09.
PlotRACI — IT change enablement, normal, emergency and failed changes
Responsibility assignment matrix for ITIL change enablement on a SOX-scoped production platform, covering RFC raising, risk classification, CAB and ECAB authorisation, implementation, back-out, post-implementation review and evidence retention for ITGC testing.
RACI matrixEngineering change control lifecycle
Distinguishes change authorization, implementation and verified acceptance. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.
MermaidAsset commissioning and defect closure
Preserves hold points and distinguishes physical installation from operational acceptance. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.
MermaidProject baseline, variations and actual costs
Keeps baseline versions, actual costs and authorized changes independently auditable. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.
MermaidAsset digital thread from requirements to operation
Traces requirements and acceptance evidence into operations and controlled configuration changes. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.
Graphviz (DOT)Scope change impact across cost, schedule and benefits
Links decision-making to baseline updates and implementation evidence, including bounded emergency work. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.
MermaidDesign freeze with constructability and operations review
Integrate design coordination, constructability and maintainability review before freezing a controlled baseline. Editable collaboration with role lanes, decisions and independent parallel checks. Illustrative policy and timing; adapt to local requirements.
BPMN 2.0Nonconformance correction with inspection evidence
Track a construction nonconformance from inspection through corrective work and reinspections while retaining an explicit unresolved closure route. Editable collaboration with role lanes, decisions and a correction and resubmission loop. Illustrative policy and timing; adapt to local requirements.
BPMN 2.0Asset handover dossier with operator reinspection
Verify a handover dossier and operator demonstrations; return incomplete components to the delivery team while preserving a controlled acceptance decision. Editable collaboration with role lanes, decisions and a correction and resubmission loop. Illustrative policy and timing; adapt to local requirements.
BPMN 2.0Design clarification request with overdue impact review
Bound a design clarification wait and route an overdue or inadequate response to a documented programme-impact decision. Editable collaboration with role lanes, decisions and an interrupting response timer. Illustrative policy and timing; adapt to local requirements.
BPMN 2.0Payment certificate query with assessment deadline
Resolve a query about measured work before certification, with explicit escalation where evidence arrives late or does not substantiate the claim. Editable collaboration with role lanes, decisions and an interrupting response timer. Illustrative policy and timing; adapt to local requirements.
BPMN 2.0Benefits realization attestation with overdue review
Request benefit-owner evidence for a reporting period, validate attribution and escalate missing evidence without counting unsupported benefits. Editable collaboration with role lanes, decisions and an interrupting response timer. Illustrative policy and timing; adapt to local requirements.
BPMN 2.0Shutdown work window with operator response deadline
Race operator approval of a shutdown window against expiry and validate isolation conditions before confirming the work. Editable collaboration with role lanes, decisions and a response-versus-expiry event race. Illustrative policy and timing; adapt to local requirements.
BPMN 2.0Maintenance isolation with controlled restoration
Prepare asset isolation, verify a safe work boundary and either authorize the maintenance package or restore controlled service. Actual isolation rules require local competent review. Editable collaboration with role lanes, decisions and explicit rollback activities. Illustrative policy and timing; adapt to local requirements.
BPMN 2.0