What to Put in a Simple Client Brief

When a client asks for “a short guide,” you might picture a two-page handout while they expect a designed booklet. Put the deliverable, format, reviewer, and due date on one page before either of you starts work. That brief gives you something to check when the feedback arrives.

A practical example

Before work begins, send the client the page you would want to find if you had to take over the job halfway through. Here is a sample for a small writing project.

Job: A two-page guide that helps first-time workshop leaders set up the room without calling the organizer.

Delivery: One editable document, written from the organizer’s room plan and checklist. One round of consolidated comments. Design, translation, and printing are outside this job.

Timing: The organizer sends the approved room plan on Monday. The writer sends a draft on Thursday. The organizer returns one set of comments by the following Tuesday; final copy follows on Friday.

Approval and fee: The event lead approves the wording. The agreed fee is $480; payment timing is in the accepted quote. The writer will ask for approval before taking on additional work.

Still open: Which entrance is available before 8 a.m.? The organizer will confirm before the draft is due.

Notice what the open question does. The writer can start, but nobody is authorized to invent a door number. If the answer is essential before work can begin, move it out of “still open” and make it a start condition.

Ask the client to correct the brief, especially who can sign off and who collects feedback. Keep the agreed version with the quote. If the deliverable changes, date the revision and confirm any new cost or deadline in writing; don’t quietly overwrite the original agreement.

Capture the desired outcome

Start with the outcome. Ask the client what should be true once the project is finished. Perhaps a new landing page should explain the service in under a minute, or an onboarding guide should reduce the number of support questions. Write the outcome in one or two sentences, using plain language. A clear outcome gives every later decision a test: does this choice help us reach the goal?

If the client names several goals, ask which one matters most. A project with one priority is easier to scope and easier to finish well.

Describe the audience and context

Add a short section about who the work is for and how it will be used. Note the intended readers or users, where the material will appear, and any constraints you already know about, such as brand guidelines, existing files, or a platform the client uses. Context prevents wasted effort. A design that looks excellent in isolation may fail if it does not fit the client’s website or the people who will read it.

Define the deliverables

List each item you will deliver, with its format and the number of revision rounds included. For example, “one blog article of about 1,000 words, delivered as a document, with two rounds of revisions” is specific enough to check. Avoid vague items such as “support” or “content.” If a deliverable depends on the client providing something, name that dependency and its due date.

State the exclusions

Exclusions are as important as deliverables. Say what is not included, such as hosting, translation, photography, social media posting, or updates after launch. Clear exclusions prevent later disagreement about whether a request was part of the original agreement. You can phrase them politely: “Publishing and scheduling are not included in this project, but I can provide a separate quote if you want them.”

Set a timeline with checkpoints

Add the main dates for the project, including the start, the review points, and the final delivery. Mention what happens if feedback arrives late. Many delays come from slow approvals rather than from slow production. A timeline that names checkpoints makes it easier for the client to see when they need to respond, and it gives you a clear basis for discussing schedule changes.

Agree on sign-off

Decide who approves each stage and how approval is given. A simple rule works well: approval is confirmed in writing by the named contact, and work moves forward after that confirmation. If the client wants several people involved, ask who has the final decision. An unclear approval process is one of the most common causes of repeated revisions.

Record the budget and payment terms

Include the agreed price, the payment schedule, and what happens if the scope changes. You do not need to write full legal terms in the brief. A reference to your quote or contract is enough. The purpose is to keep the commercial basics visible alongside the creative or technical goals, so that both parties can see the full picture in one place.

Keep the brief short

A brief that runs to ten pages will not be read. Aim for one page, with clear headings and short sentences. Use bullets for deliverables and exclusions, and put the most important decisions near the top. A short document is easier to review, easier to update, and more likely to be used during the project.