Name the purpose
A brief is a decision tool, not a collection of persuasive language. It should explain the campaign’s purpose in terms that a new colleague can understand. Start with the cause, the audience and the reason this activity belongs in the wider plan.
Make the intended participant experience explicit. What should someone understand after the conversation? What choices are available? Where should a detailed question go? These decisions help a team respond consistently without relying on a rigid script.
Set the boundaries
Good preparation includes what the team should not do. Identify questions that require an authorised answer, information that should not be collected and circumstances that should end or pause a conversation. Boundaries support judgement rather than limiting it.
The operational section should cover practical ownership. Team members need to know who can resolve a question, how an issue is raised and where updated guidance will appear. A brief that names responsibilities is easier to use under pressure.
Keep it current
A brief should change when the team learns something important. Give updates a clear owner so colleagues do not work from competing versions. Explain the reason for a change as well as the new wording.
At review, ask which parts of the brief helped and which were missing. The next campaign should begin with the learning of the last one, not with a new document that forgets the experience behind it.