Skip to content
flowss
Start freeChecking your session
Gantt & critical path templates

The 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 pathProject & PlanningGantt & critical path syntax docs
Template previewGantt & critical path
Data platform migration — precedence network with critical path9 tasks; from 2026-02-02 to 2026-03-27, 40 working days; 9 on the critical path; every check ran and found nothing.Data platform migrationMo 2 Feb 2026 → Fr 27 Mar 2026 · 40 working days · 54 calendar days2 critical paths through 9 tasks — shortening one of them alone buys nothingshorten first: pipe (up to 14d) · audit (up to 8d) · dry (up to 5d)FF02-028d02-11Audit current warehouseno floatshorten → 8d02-1210d02-25Target data modelno floatshorten → nothing02-124d02-17Pick the loaderno floatshorten → nothing02-186d02-25Landing zoneno floatshorten → nothing02-2614d03-17Build pipelinesno floatshorten → 14d03-068d03-17Reconciliation testsno floatshorten → nothing03-185d03-24Dry runno floatshorten → 5d03-253d03-27Cut overno floatshorten → 3d03-27◆03-27Legacy offno float8 columns do not fit at this width, so the network is drawn at 68% — every task is here, smallercritical — zero floatnear-criticalhas floatdrives its successorno datesEvery check ran, and none of them found anything.·Mo 2 Feb 2026 to Fr 27 Mar 2026 — 40 working days across 54 calendar days, on a Mo–Fr week·2 distinct critical paths run through 9 tasks — a task on only ONE of them can be shortened without moving the finish date at all·to finish sooner, shorten `pipe` by up to 14 working days (the whole task); `audit` by up to 8 working days (the whole task); `dry` by up to 5 working days (the whole task). Anything beyond those figuresmoves nothing — the gain from taking δ days off a task is min(δ, the figure above), and it is zero for every critical task not listed here.

Make it your own.

title "Data platform migration"
view network
start 2026-02-02
calendar mon-fri

section "Assess"
  task audit "Audit current warehouse" 8d
  task model "Target data model" 10d after audit
  task pick  "Pick the loader" 4d after audit

section "Build"
  task land  "Landing zone" 6d after pick
  task pipe  "Build pipelines" 14d after model, land
  task qa    "Reconciliation tests" 8d after ff:pipe

section "Cut over"
  task dry   "Dry run" 5d after qa
  task cut   "Cut over" 3d after dry
  milestone done "Legacy off" after cut