Write a Client Brief That Prevents Avoidable Rework

Describe the reader's immediate task

Begin with the person who will use the finished work and what they need to do. For a workshop handout, that might be finding materials, following three activities and taking notes. This is more actionable than make it engaging. Ask where they will read it, whether it will be printed, what prior knowledge they have and what information must remain available afterward. Write one primary purpose. If the brief contains several competing audiences, discuss whether they need separate versions before the layout becomes crowded.

Separate supplied facts from new work

Make an input table with item, owner, status and due date. The organiser might own approved teaching notes, location details and a logo file; you might own formatting and a plain-language edit. Mark missing or unapproved facts explicitly. Do not fill a gap with a plausible date or a guessed claim. If research, copywriting or image sourcing is additional work, name it. An input list prevents a modest formatting task from silently becoming a much larger content-development assignment.

Define the package at file level

Write quantities, dimensions where relevant, language, file formats and use. Example: one English handout, maximum four pages, A4 PDF for printing plus an editable document; no separate slide deck. Ask whether a US Letter version is also needed instead of assuming it is interchangeable. Describe what the editable file requires to open and whether fonts or linked assets are included. The definition should let another person count the deliverables without interpreting expressions such as a full content package.

Use references to discuss decisions

Invite two or three reference examples and ask what the client likes about each. They may mean spacing or information order rather than the entire visual style. Record the preference in ordinary words: large headings, restrained colour, readable labels and plenty of note space. Do not promise to copy another creator's layout, photography or text. The Copyright Office explains that copyright protects expression rather than ideas; in practice, your brief should describe the problem to solve and the design qualities to explore, using original execution.

Set the review route

Choose one person to consolidate comments, even if several colleagues will review. Identify when factual content is approved, when the first draft is due and how feedback will arrive. Ask reviewers to cite a page or section and explain the issue. Example: page two must show the earlier arrival time because doors open before the session. A single feedback document is easier to action than scattered emails and annotated screenshots with conflicting edits. Record what happens when a needed approval arrives late.

End with an unresolved-questions box

A brief can be useful before every answer is known, provided uncertainty is visible. Add questions such as whether printing will be single-sided, which photograph is cleared, or who confirms accessibility needs. Give each question an owner and a decision date. Send a concise recap and ask the designated approver to confirm the working version. Save it under a dated name. Later changes can then refer to a known baseline instead of relying on everyone remembering the same conversation differently.

Your working checklist

Checkmarks stay in this browser when storage is available. They do not submit a form or complete a booking.

• A blank brief document
• Client-supplied source files
• A reference list with written preferences
• A dated decision and questions log

Put it into practice

1. Ask about the reader, use context and single most important outcome. Draft the purpose in one sentence and confirm that it describes a practical task.
2. Inventory the inputs, mark their approval status and list the finished files. Assign an owner to every missing item rather than making assumptions during production.
3. Agree the reviewer, feedback format and milestone dates. Capture dependencies such as approved text or licensed images before committing to a production schedule.
4. Send the brief as a dated working version with open questions highlighted. Update it when a meaningful decision changes and keep the original baseline for reference.

Common questions