Describe the problem
Explain what is difficult today and who experiences it. “We lose track of enquiries after the first email” gives a project a clearer starting point than a list of desired tools. Include an example of the current process if you can.
Name the result you want
Describe what should be different when the work is finished. A website brief might focus on making services easier to understand. An automation brief might focus on getting each new enquiry into one review queue. Pick a result you can check.
Share the practical constraints
Include the deadline, budget range, existing systems, and people who need to approve the work. If a date depends on an event or launch, say so. Identify anything that must remain in place, such as a booking system or an established visual identity.
Collect the material you already have
Gather your current website, brand files, copy, and relevant examples. Explain what you like about a reference. Share only material you have permission to use, and keep private customer information out of an initial brief.
Leave room for questions
A brief does not need to solve every design or technical decision. It should make the problem, desired outcome, and constraints clear enough to discuss. End with the open questions so they become part of the scope instead of surprises later.