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
- Track recurring agreements with notice dates, owners, usage evidence, and decisions.
- Working context
- This fictional studio tracker shows four recurring services. Dates and amounts are illustrative; the real contract determines notice requirements and renewal behavior.
- Example records
- Service: Design software · Review by: 1 October · Renewal: 1 November · Owner: Maya
Service: Workspace agreement · Review by: 15 October · Renewal: 15 December · Owner: Robin
Service: Email service · Review by: 1 November · Renewal: 1 December · Owner: Sam
Service: Domain registration · Review by: 1 December · Renewal: 1 January · Owner: Leo
- Content decisions
- Start with the agreement: Record the actual notice period, renewal term, and cancellation route from the current contract. A reminder date should leave time to decide and complete the required process.
Review the usefulness: Ask whether the service is used, whether the plan fits, and whether any data needs to be exported before a change. Keep the current price and renewal quote separate.
Record the decision: Each owner marks renew, change, or end with a reason and evidence of the completed action. A planned cancellation is not a completed cancellation.
- Format and interaction
- register 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.