Start with the current state
Describe prototype status, completed tests, intended markets and the proposed launch window. Separate confirmed facts from assumptions. A planned feature is not the same as one the current unit can demonstrate. Mark the difference clearly so later assets do not quietly turn a future goal into a present-tense claim.
Put proof beside the value
Choose a small set of benefits to explain first. Attach a demo, test record or user question to each. If a portable device promises fewer things to carry, for example, show the full working kit rather than only the lightest part. The evidence tells the creative team what it can film and write.
Include limits and prohibited claims
List budget bounds, available samples, asset rights, known compatibility limits and certification questions. State what must not be claimed, such as an unconfirmed delivery date or an unfair comparison. Name the approver and when feedback is available. These details help the team far more than another list of brand adjectives.
Maintain one version of the brief
Assign an owner and record changes, dates and affected assets. When a meeting reaches a new decision, update the brief rather than leaving it in chat. Use the first review to identify missing proof, assign who will supply it and agree when a decision can be made. End with tasks, not just discussion.
Put this into practice
- Separate current facts, plans and untested assumptions.
- Pair key claims with evidence and explicit limits.
- Name the version owner and next decision point.
