How to Brief a Studio So the First Draft Is Close

Most first drafts miss for the same reason: the brief described a deliverable instead of a decision. “We need a new website” leaves the studio guessing what the website is for, who has to approve it, and what is off the table.

A strong brief takes about an hour to write. It can remove entire rounds of revision. Here is what to put in it, and why each part matters.

Start with the outcome, not the deliverable

Say what should be different after the work ships. A deliverable is a thing. An outcome is a change in behavior, perception, or capability.

Compare two openings. “Redesign our product pages” gives a studio a surface to decorate. “Procurement teams abandon our product pages before they find the compliance documents, and we want them to find those documents in under a minute” gives the studio something to solve and something to test the draft against.

If you can’t state the outcome in two sentences, that is useful to know before the project starts. Settle it internally first.

Name who decides

Revision cycles usually stretch because feedback arrives from people the studio didn’t know existed. Put names and roles in the brief:

Who gives final approval? Who gives input but can’t veto? Who must be consulted for legal, security, or brand reasons? When in the process does each person see the work?

One more detail helps: tell the studio how your organization resolves disagreement. If two executives disagree about direction, the studio should know who breaks the tie before the draft goes out, not after.

Separate what’s fixed from what’s open

Every project has constraints. Problems start when they surface late. Sort them into two groups at the start.

Fixed: the launch window tied to an event, the platform your engineering team will maintain, the brand elements that cannot change, the accessibility standard you must meet, the budget ceiling.

Open: everything the studio is free to challenge, such as structure, naming, visual direction, and even the premise of the brief.

Be honest about the sorting. If the logo can’t change, say so plainly. If you have a preferred direction but would genuinely consider others, label it as a preference, not a requirement. A studio can only use the freedom you actually give it.

Say what you’ve already tried

Your history is some of the most valuable information in the brief. Include previous agencies’ directions, internal attempts, and anything that tested poorly, along with the reason it was dropped.

“We tried a bold, dark visual direction and leadership felt it didn’t fit our customers” saves a studio from proposing it again. “We tried it and it was fine, but not distinctive” tells them something different. The reason matters more than the result.

Include what worked, too. If one landing page outperformed the rest, show it and explain why you think it did.

Share references without asking for copies

References speed up alignment, but only when they come with a point of view. A bare link to a site you admire invites imitation, and imitation is rarely what you need.

For each reference, say which single quality you’re pointing at: the pacing, the restraint, the tone of the copy, the way navigation stays out of the way. Then say what you don’t want from it. Two or three references with notes are more useful than fifteen without.

Include one reference you dislike and say why. Studios often learn more from what you reject.

A one-page brief template

Copy this into a document and fill it in. If it runs past one page, you probably have two projects.

1. Project name and one-line summary. What are we making, in plain words?
2. Outcome. What should be different after this ships? How will you know? Limit it to two sentences.
3. Audience. Who is this for, and what do they need to do or understand?
4. Decision-makers. Final approver, contributors, required reviewers (legal, security, brand), and how ties are broken.
5. Fixed. Dates, budget ceiling, platforms, brand assets, compliance requirements, anything non-negotiable.
6. Open. What the studio is free to question or change.
7. Already tried. Past attempts, what happened, and why they were set aside.
8. References. Two or three, each with the one quality you’re pointing at and what to leave behind. Add one you dislike.
9. Schedule. Key dates, when each reviewer sees work, and how long your team needs to give feedback.
10. Open questions. What you haven’t figured out yet. Naming the gaps is better than hiding them.

Expect a conversation, not a handoff

A brief is a starting point. A good studio will read it and come back with questions, and some of those will challenge your assumptions. That is the brief doing its job.

The goal isn’t to remove every revision. It’s to make sure revisions refine a sound direction instead of correcting a misunderstanding. When the outcome, the deciders, the constraints, and the history are on the table from day one, the first draft has a real chance of being close.

If you’re preparing a brief for a project now, we’re glad to read a draft of it with you at artasce.com.