Chart · gantt

Reporting platform plan, H1 2026

Six tasks across two quarters, grouped into three phases. The reporting API is the critical path: it runs two and a half months and every launch task waits on it.

Reporting platform plan, H1 2026 Illustrative plan, not a real project schedule. Six tasks with explicit start and end dates laid against a month-granularity calendar covering Q1 and Q2 of 2026, snapshot dated 1 March 2026. Foundations holds discovery and data audit, 1 January to 15 February, and schema migration, 1 February to 15 March. Build holds the ingestion service, 1 March to 30 April, the reporting API, 15 March to 31 May, and the console redesign, 15 April to 15 June. Launch holds the pilot rollout, 1 June to 30 June. The focal bar is the reporting API, the critical path: it is the longest task at two and a half months and the pilot rollout cannot start before it ends. Bar width means duration and nothing else; the pixel pitch per month is constant across the axis. A gantt has no value baseline, so none is declared. TASK Q1 2026 Q2 2026 JAN FEB MAR APR MAY JUN 1 MAR 2026 · SNAPSHOT FOUNDATIONS Discovery & data audit Schema migration BUILD Ingestion service Reporting API · critical path Console redesign LAUNCH Pilot rollout

Illustrative plan — the tasks and dates are invented to demonstrate the gantt grammar and describe no real project. Calendar granularity is one month, stated on the axis, and the pixel pitch per month is constant at 96 px across the whole span; no stretch of quiet calendar is compressed. Task names live in the left column so short bars stay readable, and start and end dates are read off the axis rather than printed in the bar. The today marker is drawn only because the snapshot date is declared alongside it. A gantt encodes duration by bar width against a calendar, not value against a scale, so data-baseline is not-applicable. Colour resolves through design-system tokens; where no project tokens are compiled the page falls back to the documented neutral palette declared in :root. Static, script-free, and offline.