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
- Tell a project story through constraints, decisions, evidence, and the finished result.
- Working context
- This fictional case study follows a small studio preparing a client handover. The work focused on making the next owner’s responsibilities visible, rather than redesigning every document.
- Example records
- Stage: Before · Decision: Map the handover gaps · Evidence to collect: Questions from the receiving team
Stage: During · Decision: Use one document index · Evidence to collect: Observed lookup tasks
Stage: After · Decision: Name a review owner · Evidence to collect: A completed maintenance check
- Content decisions
- The original difficulty: The client received useful files but could not tell which ones were current. Several links referred to earlier drafts, and no single page explained who would update the website after launch.
What changed: The studio created an index with a purpose, owner, and status for each deliverable. A short maintenance routine sat beside the index. Old drafts stayed in an archive rather than appearing as equal alternatives.
What the example can show: The sample result is an organized handover with explicit responsibilities. A real case study should add verified before-and-after evidence, permission to name the client, and any limitations in the evaluation.
- Format and interaction
- casebook 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.