Start with the decision the brief needs to support
A client project brief is a short, shared description of what the work is meant to achieve and how the project will proceed. It is not a polished pitch or a substitute for a contract. Its job is to help both sides make consistent decisions once creative work begins. When a request changes or feedback conflicts, the brief gives everyone a point of reference.
Before writing, ask what the client wants to be different when the project is complete. “We need a new website” names an output; “Visitors should be able to understand our services and request a consultation” describes a purpose. Both belong in the brief, but the purpose helps guide choices about content, design, and priorities. If the client has several goals, ask which one matters most. A short list in priority order is more useful than a long list where everything is equally important.
Gather context before proposing a solution
Use an initial conversation or a simple questionnaire to learn who the work is for and where it will appear. Ask about the intended audience, what that audience needs to know or do, and any existing materials the project should build on. For a visual identity, those materials might include current logos and examples of where the identity will be used. For an editorial project, they might include a content outline, style guidance, and an established publishing process.
Ask what has prompted the project now and what has or has not worked in the past. This can reveal constraints without treating the client’s first suggested solution as the only possible one. If they request a particular style, for example, ask what they hope that style will communicate. Record the answer in plain language rather than replacing it with vague terms such as “modern” or “premium.”
Separate facts from assumptions as you take notes. If the client has not decided who will supply copy or approve the final work, mark those items as open questions. A brief should make uncertainty visible so it can be resolved, not quietly turn a guess into an agreement.
Define the work and its boundaries
List the deliverables in terms a non-specialist can recognize: for example, a homepage design, two supporting page layouts, and export-ready image assets. Include relevant formats, sizes, or platforms if they are known. Then state what is not included when a reasonable reader might otherwise expect it, such as copywriting, photography, development, or ongoing updates. Clear boundaries make it easier to discuss additions later without treating every new request as a misunderstanding.
The brief should also identify practical dependencies. Who will provide source files, brand assets, product details, or access to a publishing system? When does the creative work depend on receiving them? Note any accessibility, technical, or brand requirements the client already knows about. Avoid promising a level of performance or a specific outcome that the creative work alone cannot guarantee.
Keep scope proportional to the project. A small illustration may need only a few sentences about use, dimensions, and approvals. A multi-page site will need more detail. The aim is not to fill every possible field; it is to capture the information that would change what you make or how you make it.
Agree on feedback and approvals
Creative projects can stall when feedback arrives from several people at different times. Name the person who will collect feedback and the person who can approve the work, if those are different roles. Specify how feedback will be shared, what each review stage covers, and how many rounds of revision are planned. A review of the overall direction should happen before time is spent refining small details.
Include a working timeline with key handoffs rather than only a final deadline. Dates may need to change if required materials or decisions arrive late, so describe the dependencies alongside the milestones. If a date is tentative, label it as tentative. This gives both sides a clearer way to discuss schedule changes.
It helps to say what useful feedback looks like. A comment such as “make it pop” is difficult to act on; a note that a call to action is getting lost beside other elements points to a problem that can be addressed. Invite the client to describe what is not working and why, while leaving room for the creative professional to propose the fix.
Turn your notes into a brief both sides can use
After the conversation, draft the brief in a format the client can read quickly. A practical order is: project purpose, audience, priorities, deliverables, requirements, exclusions, materials and responsibilities, timeline, and feedback process. Use short sentences and concrete terms. The document should be detailed enough to guide the work but easy enough to revisit during a meeting.
Send the draft to the client and ask them to confirm it or correct what you have misunderstood before production begins. Pay particular attention to unresolved decisions and statements that sound precise but are open to interpretation. Once agreed, keep the brief accessible and update it when both sides decide to change the plan. That small habit turns the brief from an administrative document into a useful tool throughout the project.
