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
- Welcome a client with owners, access requests, milestones, and a first-week checklist.
- Working context
- Common Room’s fictional café project begins with one decision maker and a shared brief. This guide explains what the client supplies, what the studio prepares, and when the first review happens.
- Example records
- When: Before kickoff · Client prepares: Brand files and menu copy · Studio prepares: Shared document index
When: Day one · Client prepares: Business goals and constraints · Studio prepares: Kickoff notes
When: Day three · Client prepares: Feedback on content outline · Studio prepares: First page structure
When: Day five · Client prepares: One consolidated response · Studio prepares: Confirmed project plan
- Content decisions
- Working agreement: Use one review thread for each deliverable and identify the person who consolidates feedback. Urgent issues go to the project lead; a new idea goes into the scope discussion before work begins.
Access without confusion: List the systems required and the minimum role needed in each. The client grants access through the system’s own invitation process. Keep passwords and recovery codes out of this guide.
Ready for the first review: The kickoff is complete when the goal, the five-page scope, the content owner, and the first review date are understood by both sides. Missing inputs become named actions rather than hidden assumptions.
- Format and interaction
- dossier 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.