# One-page project brief

Project name, version, and date: [name / version / date]
Owner: [person responsible]
Decision-maker or reviewer: [person / role]

## Person and problem
Who, in what situation: [specific person and context]
Task they need to complete: [task]
Current difficulty: [problem, not a preselected feature]
Evidence and source links: [dated findings / private source pointers]
Assumptions: [not yet established]
Unknowns that could change the approach: [unknown / owner / check date]

## Complete promise
After this delivery, the person can: [one useful action]
In scope: [minimum complete contents or behaviour]
Out of scope for this version: [explicit exclusions]
Accessibility and assisted alternatives: [needs / formats / gaps to resolve]

## Delivery and care
Available time and resources: [confirmed / unknown]
Dependencies and permissions: [requirements / owner]
Review date: [date]
Readiness checks: [accuracy / functional checks / required review]
Maintenance and correction route: [owner / update trigger / contact]
Privacy and safety boundary: [what is not collected / required review]

## Decision gate
Next decision: [continue / change / stop / investigate]
Evidence needed for that decision: [method and limits]
Separate pilot plan, if needed: [link / version]
Claims this delivery does not establish: [outcomes / prevalence / causation]
Revision record: [date / what changed / reason]

A working brief, not a contract or professional approval. Do not publish private source material or unresolved sensitive details.

---

Blank template by Daniel Ziedins (https://www.danielziedins.com).
Read the guide: https://www.agent-six33.com/journal/how-to-write-a-one-page-project-brief
Template library: https://www.agent-six33.com/field-kit
Guide updated: 2026-10-18

Public blank prompts only. No private journal notes or tool drafts are included. Keep completed copies and participant details private.
