Dust off last year’s brief template and there is usually a blank space where a crucial question should sit: how far can AI go on this project, and does an AI-generated draft count as the finished deliverable? Leave that out of the design brief, and it has a habit of turning into a trust problem halfway through the job.
1. What Every Brief Is Missing Now
The fundamentals of a brief haven’t changed — goals, audience, constraints. What’s missing is a line item spelling out exactly how AI fits into the process: which stages, from research to rough sketches to final renders, are fair game for AI tools; roughly how much of the finished deliverable AI is allowed to generate; and who signs off on the result and answers for it. Settle that early and you close the gap between what a client expects and what the team actually hands over, before it becomes a dispute.
The old brief
Goals, audience, and the usual constraints — budget, timeline, materials, production method. None of that goes away in the AI era.
What the AI era adds
Which stages allow AI, how much of the output it can generate, who does final sign-off, and who owns the result.
2. Goals, Constraints, and Who Owns the Output
Getting the goals and constraints right
A brief’s job has never changed: define what you’re making, for whom, and inside what limits. Budget, timeline, and constraints around materials or production are the same fixed points they’ve always been, and they still deserve the same care. Adding an AI clause doesn’t rewrite that foundation — if anything, because AI speeds the work up, the goals and constraints need to be drawn even more precisely, or the direction of the project drifts before anyone notices.
Spelling out who owns AI-assisted work
Address copyright and ownership of anything AI touched at the brief stage, and the contract that follows becomes much easier to draft. This is also the moment to settle whether the client can use AI-generated images or copy freely, or only for a specific purpose — internal review, say, as opposed to a public campaign.
💡 Pro tip — You can lean on AI to draft the brief itself. Feed it the research you’ve already gathered and ask for a first pass at the goals and constraints — it beats staring at a blank page. But the calls that actually matter, priorities and tone, still need to come from you. If that research workflow isn’t set up yet, organizing design research with ChatGPT is worth reading, and if you want to think through where AI fits across the whole design system, bringing AI into a design system is a good next stop.
3. Why Briefs Suddenly Need an AI Clause
The design brief as a document grew out of advertising and agency work, where its job was to get scope and responsibility agreed with the client before anything got made. Spelling out the visible things — budget, timeline — was always its purpose, a way of heading off disputes down the line. Now that AI has a hand in actually producing the work, a question nobody used to bother asking — who made this — is back on the table. That’s the backdrop for why briefs need an AI clause at all.
The common misconception
Plenty of teams assume it’s enough to cover AI use in the contract. But a contract is the document you pull out after something has already gone wrong, while a brief is what aligns expectations before the project starts at all. Put the clause only in the contract and leave it out of the brief, and the people actually doing the work end up asking, over and over, mid-project, how far they’re allowed to take it.
💡 Pro tip — When you write the AI section of a brief, list not just what’s allowed but what isn’t — spell out the stages where AI is off-limits. That single addition closes most of the gap between how different people on the same team read the same clause.
In practice, it helps to keep a short table inside the brief itself, logging which AI tool was used for which deliverable and at what stage. If a question ever comes up later about where a particular image or line of copy came from, that one table is usually enough to settle it — whether it was an AI draft that a person redrew, or the AI output used as-is — without it turning into an argument.
4. Closing thoughts
Have you spelled out which stages allow AI and which don’t?
Is there a named person responsible for final sign-off on AI-assisted work?
Does ownership and usage of AI-generated output tie back to the contract?
Are the fundamentals — goals, audience, constraints — still fully filled in?
Does the brief include a record of which AI tools were used, and where?
For the basics of what belongs in a brief, Adobe’s own creative guide is a solid reference. But the core of it hasn’t changed: a design brief sets the direction for a project. Spell out where AI fits from the start, and you head off the argument about whether the finished work can be trusted before it ever has the chance to start.
Design Daily Life · Notes on design, daily