Example brief used for this template
Hypothetical creation brief for this authored edition, not a historical prompt transcript. The sample answers describe the actual example rendered here.
- Purpose and audience
- A project board with owned work, clear status definitions, and actionable blockers.
- Working context
- This fictional studio snapshot covers four client workstreams at the Monday review. Status is manually maintained; the page represents one review point rather than a live project system.
- Example records
- Workstream: Café website · Status: In progress · Owner: Maya · Next move: Review the menu page
Workstream: Archive index · Status: Needs input · Owner: Leo · Next move: Request collection labels
Workstream: Workshop pack · Status: Ready for review · Owner: Sam · Next move: Run a participant walkthrough
Workstream: Support guide · Status: Complete · Owner: Robin · Next move: Confirm handover receipt
- Content decisions
- Needs attention: The archive index is blocked by missing labels. Leo should identify the content owner and agree a date for a usable sample. The workshop pack needs a reviewer, not more unrequested production work.
Status definitions: In progress means an owner is actively working on the next deliverable. Needs input means a named dependency prevents progress. Ready for review means the acceptance material is available. Complete means the agreed check has passed.
The next review: Update each row from its source record before the weekly meeting. Archive completed work after handover, and keep blocked items visible until the dependency is resolved.
- Format and interaction
- board layout; section navigation and expandable detail where useful; matching portrait document PDF.
- Sharing and provenance
- A hypothetical example informed by Claw Me’s small-team and Agent workflows. These are not Pete’s actual clients, finances, travel plans, research results, or commitments. Keep the real adaptation private until the owner chooses to share.