Say what needs to change
Start with the problem in plain words. A website brief might say that visitors can’t find the prices, or that the enquiry form is hard to use on a phone. That’s a more useful starting point than asking for something modern and professional.
Be clear about what is being made
List the pages, files or other deliverables you need, and say where they will be used. Separate the essentials from the things you’d like if time allows. Add an example when it explains a decision, such as how a menu should open on a small screen.
Agree how the work will be reviewed
Name the person who will collect feedback and describe what a finished version needs to do. Keep a short list of unanswered questions. A brief doesn’t have to cover every detail on day one, but it should give people enough common ground to start the right conversation.
