outsource
The third round of revisions is where the cost of a missing brief becomes visible. The work gets returned with comments that are not about execution at all. The tone is wrong, the audience turns out to be different from the one assumed, a competitor is mentioned that nobody named at kickoff. Nothing in that feedback is unreasonable. It is simply arriving after the draft instead of before it, and every hour spent absorbing it is unbilled.
A creative brief template is often treated as paperwork that delays the start. It does the opposite when it is built correctly, because its real job is not documentation. It is to force a set of decisions out of the client while those decisions are still cheap to make.
Most downloadable templates are questionnaires. They ask about brand values, tone of voice, competitors and target demographics, and they get filled in with answers that are true and useless: the audience is "small business owners aged 25 to 55", the tone is "professional but approachable", the goal is "increase brand awareness".
None of those answers can be wrong, which is exactly the problem. An answer that cannot be wrong cannot settle an argument later. When the first draft comes back marked as too corporate, "professional but approachable" offers no way to resolve it, so the resolution becomes taste, and taste rounds are unbounded.
A brief that functions has a different test for every field: could this field have been answered differently, and would a different answer have changed the work? If not, the field is decoration.
That test changes what gets asked. Instead of tone of voice, the brief asks for two existing pieces the client considers close to right and one they consider close to wrong, with a sentence on why. Instead of a demographic, it asks what the reader currently believes and what they should believe after seeing the work. Instead of a goal, it asks what will be measured and by when. Each of these has answers that exclude other answers, which is what makes them usable when feedback arrives.
The brief is also where scope lives. A brief without deliverable counts, formats and revision rounds is not a brief, it is a mood board with headings.
Ten fields cover most client work. The table below pairs each one with the kind of answer that will not survive contact with feedback, and the kind that will.
| Field | Weak answer | Usable answer |
|---|---|---|
| Business problem | Increase brand awareness | Renewal rate dropped after the pricing change and customers say they did not know what they were paying for |
| Single objective | Drive engagement | Get existing customers to open the plan comparison page |
| Audience | Small business owners | Current customers on the oldest plan who have not logged in for 60 days |
| Current belief | Not asked | This product is the cheap option and probably has limits |
| Desired belief | Not asked | The plan already covers what is needed, and the upgrade is optional |
| Deliverables | A campaign | Three email versions, one landing page, four banner sizes, source files included |
| Mandatories | Follow brand guidelines | Logo top left, legal line on every asset, the word free is not permitted |
| What is out of scope | Not asked | No photography, no video, no translation |
| Approver | The team | One named person, with a second named as backup |
| Deadline and rounds | ASAP | First draft on a fixed date, two rounds of revision included, third round billed |
Two of these are worth defending when a client resists them.
A single objective. Clients frequently want a deliverable that also does two other jobs. The brief should accept only one objective and list the others as secondary, explicitly ranked. Work that serves three equal goals serves none of them, and at review time each stakeholder judges it against their own goal.
What is out of scope. This is the field most often left off the template and the one that saves the most money. A written line saying that photography is not included prevents the conversation where photography was assumed to be included, and that conversation always happens after the draft.
The brief is usually written by whoever will manage the work, not by the client and not by the person doing the creative work.
Clients cannot write it alone because a brief is a translation. The client knows the business situation in detail and has no reason to know which of those details will change a design decision. A form sent over for the client to complete comes back with the boxes filled and the decisions still open. A short conversation, transcribed into the brief by the person who knows what the work needs, produces a usable document in less time than the form takes to chase.
The person doing the creative work should not write it either, for a plainer reason. A brief written by the maker tends to describe the solution already imagined, which removes the one useful function of the document: being something the work can be measured against by someone other than its author.
Approval is the field that quietly decides whether the project ends on time. One named approver, with one named backup, and no committee. When approval is collective, feedback arrives as a list of individually reasonable comments that contradict each other, and the maker is left to arbitrate between the client's own stakeholders. The brief should state who resolves conflicting internal feedback before it is sent on.
Getting a signature, even an email that says approved, changes behaviour on both sides. It marks the point where scope was agreed, which is what makes a third round of revisions a billable conversation rather than an awkward one.
A signed brief that nobody opens again is only slightly better than no brief. Three failures are common.
The brief lives in an attachment. It was emailed at kickoff, and six weeks later the current version is in somebody's downloads folder. When feedback contradicts the brief, nobody can produce the brief quickly enough for it to matter, so the contradiction stands.
The brief is not updated when scope legitimately changes. Scope changing is normal. The problem is changing it in a thread. Where a client adds a fourth banner size in a chat message and the work proceeds, there is now a gap between the agreed deliverables and the actual deliverables, and it will be discovered at invoicing.
The brief is separated from the tasks. Execution happens against a task list, and the brief sits in a different tool from that list. Anything that requires both to be open at once eventually gets done with only one open.
A fourth failure is less obvious. The brief records the objective but not how the objective will be checked, so at delivery there is no agreed way to say whether the work did its job. If the brief states that success is measured by opens on a comparison page over two weeks, then the review after delivery is about the number. If it states only that the work should increase engagement, the review after delivery is about whether the client likes it, which is the same conversation the brief was written to avoid.
All three of the storage failures are structural rather than matters of discipline, and they respond to being fixed structurally. Keeping the brief as the description of the top card of the project, with each deliverable as its own card beneath it, means the brief is one click from the work rather than in a separate system. Where a project tool holds a rich description field, checklists and comments on the same card, the brief, the deliverable list and the approval trail end up in the same place, and the range of board types matters here mostly because the deliverable list and the schedule need to read from the same cards.
Templates from large agencies assume a structure that a five person team does not have, and copying them wholesale adds work without adding clarity.
| Aspect | Agency brief | Small team brief |
|---|---|---|
| Length | Several pages, often with a separate strategy deck | One page, readable in two minutes |
| Written by | Account or strategy lead | Whoever manages the project |
| Audience research | Commissioned or drawn from existing research | Whatever the client already knows, written down honestly |
| Sign off | Client marketing lead plus internal creative director | One named client approver |
| Revision policy | Defined in a master services agreement | Stated in the brief itself |
The one thing worth borrowing from the agency version is the discipline around the objective and the mandatories. The one thing worth leaving behind is length. A brief that takes an afternoon to produce will not be produced for a two week project, and a brief that does not exist protects nobody.
For recurring clients, a standing brief plus a short job brief works better than rewriting everything each time. The standing brief holds the parts that do not change: brand mandatories, file formats, who approves, how revisions are counted, where source files are delivered. The job brief holds the objective, the audience, the deliverables and the dates. Second and third projects for the same client then start in fifteen minutes instead of an hour.
The practical setup for a small team is unglamorous. One card per project holds the brief in its description. Each deliverable is a card with the format, the size and the due date. Mandatories become a checklist on the deliverable cards rather than a paragraph nobody rereads. Client feedback goes in the comments of the card it concerns, not in a chat channel, so that the history of a decision sits next to the thing that was decided.
Two habits make the difference. The brief gets a version note at the top whenever scope changes, with the date and what changed, so there is never ambiguity about which version was agreed. And revision rounds get counted visibly, as a checklist or a field on the card, because a round that is not counted is a round that is not billed.
None of this requires a specialised tool. It requires that the brief, the task list and the schedule are not in three separate places, and what the plans include is worth checking against how many people actually need to be in the tool, since clients usually need to see rather than edit.
Take the next project and add two fields to whatever brief is currently in use: what is out of scope, and the name of the single person who approves. Those two answers resolve most of the disputes that surface after the first draft. Then put the brief where the tasks are rather than in an email attachment, and if the tasks and the schedule are currently in different places, Pinateca can hold the brief, the deliverable cards and the dates on one board.
For a small team, one page that can be read in two minutes. Length is not a measure of quality here, and a long brief is less likely to be reread when feedback arrives. Agency briefs run longer because they are also internal strategy documents, which is a different job from the one a small team needs done.
Sending a blank template to a client usually returns filled boxes and unresolved decisions, because the client has no reason to know which details change a design decision. A short conversation, written up by whoever manages the project and then sent back for approval, produces a more useful document and takes less calendar time than chasing a form.
A creative brief defines what the work has to achieve and for whom: the objective, the audience, the belief to change, the mandatories. A project brief defines how the work will be delivered: the schedule, the responsibilities, the budget and the milestones. Small teams often merge them into one document, which works as long as the objective and the out of scope list do not get lost among the logistics.
Update the brief rather than the thread. Add a dated note at the top saying what changed and who agreed to it, adjust the deliverable list, and state whether the change affects the deadline or the revision count. A scope change agreed in a chat message and never written into the brief is the change that gets argued about at invoicing.