printable · A4 portrait · v0.1.0
Project Status One-Pager
Scorecard-style project status on one A4: KPI tiles (budget, timeline, scope, issues), workstream table with RAG status and % complete, milestone list, top risks and a highlighted decisions-needed panel. Built for steering committees.
Paste the prompt into Claude (or any agent that can fetch URLs) with your content — you get back a finished, self-contained HTML file.
Live preview — the example content ships with the template and is replaced by your content.
What an agent may change — and what content you should have ready. Everything outside these slots is fixed by design.
Slots
| Slot | Type | Req. | Example |
|---|---|---|---|
doc-title |
text | yes | Status — Warehouse Move — 14 Aug 2026 |
project-title |
text | yes | Warehouse Move — Almere DC2 |
owner |
text | yes | Bram Verlaan — project lead |
status-date |
text | yes | 14 Aug 2026 · update #7 |
overall-status |
text | yes | On track |
risks |
html | no | <ul><li>WMS vendor capacity — buffer exhausted…</li></ul> |
asks |
html | no | <p>Approve € 18k contingency…</p> |
footer-note |
text | no | Steering committee distribution · next update 21 Aug |
Repeat: kpi (2–4×)
Scorecard tiles across the top. 4 gives a balanced row.
| Slot | Type | Req. | Example |
|---|---|---|---|
kpi-label |
text | yes | Budget used |
kpi-value |
text | yes | € 412k |
kpi-sub |
text | no | of € 550k (75%) |
Repeat: stream (1–8×)
One row per workstream.
| Slot | Type | Req. | Example |
|---|---|---|---|
stream-name |
text | yes | Racking & fit-out |
stream-rag |
text | yes | On track |
stream-pct |
text | yes | 80% |
stream-note |
text | yes | Aisles 1–12 installed; certification booked for 28 Aug. |
Repeat: milestone (2–8×)
Key dates, chronological.
| Slot | Type | Req. | Example |
|---|---|---|---|
milestone-name |
text | yes | Racking certified |
milestone-due |
text | yes | 28 Aug |
milestone-status |
text | yes | On track |
Optional blocks
risks— Top-risks panel (max 3 bullets, each with a mitigation).asks— Highlighted decisions-needed panel — the reason a steering committee reads this. Remove only if there is truly nothing to decide.
The authoritative fill instructions from manifest.json — the only place a template may instruct an agent (why).
ONE page, always (remove the data-example tiles and rows — they are preview content only). overall-status and every stream-rag/milestone-status must use exactly the fixed vocabulary (On track / At risk / Off track / Done / Planned) — no synonyms, no emoji. The overall status must be consistent with the table: if any workstream is Off track, overall cannot be On track; if you adjust it, keep the user's stated status unless it contradicts their own data, in which case flag the inconsistency to them. Compute percentages only from user-provided data; never invent budget or scope numbers. KPI tiles: value big and bare, context in kpi-sub ('of € 550k (75%)'). Risks max 3, each as risk — impact; mitigation. The asks panel is the point of the document: make each ask specific (amount, deadline, decision forum). Milestones chronological.
Published versions are immutable: /t/project-status@{version}/ never changes once live. /t/project-status/ always points at the latest.