A graphic design brief is a short document, written before the work starts, that states the problem a piece of visual work has to solve, the exact files it needs to produce, and the brand rules it follows. Write those three things down and a designer can start without a kickoff call. Skip them and the first draft comes back wrong in ways nobody can point to, because nobody agreed on what "right" meant.
Most briefs for graphic work fail on the visual half specifically. The deadline is clear and the deliverable list says "social assets" instead of four images at 1080x1350. The brand direction is "clean and modern" instead of a hex value and a type scale. Three rounds later, someone finally says the logo cannot sit on a busy background, which was true the whole time and written nowhere.
Below are six steps for writing a graphic design brief, what makes the visual sections specific instead of vague, and how to write the same brief so it works as a prompt for an AI tool.
Key Takeaways
- A graphic design brief needs an exact deliverable list (file type, dimensions, and count), not a category like "social assets."
- Visual direction works as a constraint, not an adjective: a hex value and a contrast ratio settle what "modern and clean" cannot.
- Name one approver and a number of revision rounds in the brief itself, before any design work starts.
- The brand half of a brief (colors, logo rules, type) is the part most teams keep retyping. Link to a current source instead.
- TrueKeep serves that brand half to Claude, ChatGPT, and Cursor through an MCP connection, so a brief pasted into a chat window carries the same rules a designer would get.
What a graphic design brief covers
A graphic design brief is narrower than a general creative brief. It is written for visual output specifically: a logo, a set of social graphics, a packaging mockup, a slide deck, a print ad. It states the problem, the audience, the files that get produced, the brand rules those files follow, and how the result gets judged.
It is not a layout spec. A brief that says "put the headline top left in 48 point type" has made the design decision for the designer. A brief that says "the offer needs to be readable in three seconds on a phone, in a feed full of other ads" has handed over a problem worth solving. The Design Council's Double Diamond treats defining a problem as a separate stage from developing its answer, and a graphic design brief is where the first stage ends.
This post focuses on the visual half: the deliverable list, the color and type constraints, the reference images. For the other sections a full brief needs, such as the approval line and the budget, see the design brief template.
Step 1: Write the problem before the request
Start with what is wrong now and what should be true once the work ships. "Our last product launch used three different badge styles across channels, and none matched the one in the brand guide" is a problem. "We need a new badge" is a request with no problem attached, and a request with no problem gets judged on taste instead of on whether it worked.
Step 2: Name the audience and the one action they take
State who sees the work, where they see it, and the single thing they do next. "Existing subscribers, in an email, on a phone, who tap through to the product page" tells a designer more than "our customers." A graphic made for a billboard and a graphic made for an Instagram story solve different problems even when the message is identical.
Step 3: List deliverables as exact files, not categories
This is where most graphic design briefs go soft. Replace the category with the file:
- Weak: "Social assets for the launch."
- Specific: "Four Instagram carousel images, 1080x1350 PNG, one 15-second Reel at 1080x1920 with captions burned in, source file included."
Every deliverable gets a format, a dimension, and a count. If a source file matters later, say so now; asking for it after the designer has closed the project costs a second round that the brief could have prevented.
Step 4: Replace visual adjectives with constraints
"Modern," "clean," and "premium" describe a feeling and leave the decision to a feedback round, when changing it is expensive. A constraint settles the same question in writing, before anyone has looked at a draft:
Primary color stays at #1B3A5C, never shown tinted below 80 percent. No new typefaces; use the existing type scale. Body text meets the WCAG 2.2 contrast minimum of 4.5:1 against every background it appears on.
Add one reference image that worked and one that did not, with a line on why each. "Not this: last quarter's banner, three fonts, no clear first read" saves an argument about taste that an adjective never would have settled.
Writing it this way costs more up front. Someone has to pick the hex value and the contrast ratio before the brief goes out, instead of leaving it for the first round of feedback. That cost is smaller than the one it prevents: a designer who built the wrong thing because "clean" meant something different to each person in the room.
Step 5: Point the brand section at one current source
The brand section of a graphic design brief is close to identical across every brief a team writes: the same hex values, the same logo rules, each one retyped from a slightly different copy of the guidelines. It is also the section most likely to be wrong. Swap out a logo variant in June and three briefs drafted in May are still pointing new work at the old file.
Link to a current source instead of pasting the values in. TrueKeep's portal holds a brand's strategy, guide, assets, and components in one place, with colors rendered as swatches and logos at presentation quality, so a designer working from the brief copies the value instead of asking someone for it.
Step 6: Name one approver and the number of rounds
Without a named approver, feedback comes from whoever happens to see the file first: a manager, a colleague passing the desk, someone in a Slack thread. Write one name, a number of revision rounds, and the date feedback is due. One line, and the project has a clear end instead of an open invitation for notes.
Write the graphic design brief for an AI tool too
A graphic design brief gets pasted into a chat window as often as it gets sent to a designer now. Someone asks Claude for three headline layouts, or asks ChatGPT to draft the carousel copy, and drops the brief in above the prompt. Whatever the brief leaves out, the model fills in on its own, the same way an unbriefed designer would guess.
The parts that work for an AI tool are the same parts that work for a new designer: named files, exact dimensions, a stated contrast ratio, a list of colors and words the brand avoids. The parts that fail are the ones that assume shared context, like "keep it on-brand."
The brand half does not have to live in the prompt at all. TrueKeep connects a portal to Claude, ChatGPT, or Cursor once through an MCP connection, built on the Model Context Protocol, an open standard for giving AI tools access to a source of information. A downloadable brand kit skill carries the same rules directly into Claude. The AI connection guide covers the setup, and a final pass checks the output against the brand before it ships. What goes in the prompt is then only the project half: the problem, the audience, the deliverables, the constraints.
FAQ
What should a graphic design brief include? The problem, the audience, an exact list of deliverables with file formats and dimensions, the brand rules the work follows, the constraints, how success gets judged, and who approves it.
How is a graphic design brief different from a creative brief? The terms overlap, and many teams use one document for both. Where they are separated, a creative brief covers the message and the campaign idea, and a graphic design brief covers what actually gets produced: the files, the dimensions, and the visual rules they follow.
How specific should the deliverables section be? Specific enough to check against the finished files. "Four images, 1080x1350, PNG" can be verified. "Social assets" cannot.
Who writes the graphic design brief? Whoever is commissioning the work writes the first version, and the designer reviews it before work starts. A brief the designer has not questioned is often hiding an assumption about scope or deadline.
How do I write a graphic design brief for an AI tool? The same way, minus anything that assumes shared context. Give named files, exact dimensions, and the brand's colors and banned words rather than "on-brand." TrueKeep connects a brand portal to Claude, ChatGPT, or Cursor through an MCP connection, so that half comes with the tool instead of the prompt.
What makes a graphic design brief fail? No named problem, no named approver, and visual direction written as adjectives instead of constraints. Each one turns the review into an argument about taste, and that kind of argument has no natural end.
Start with the problem, not the file list
A graphic design brief works when the problem comes before the request, the deliverables list exact files instead of categories, and the visual direction reads as a constraint a designer can check against rather than a feeling to interpret. Name one approver and a number of rounds before the work starts.
The brand section is the part most teams keep retyping instead of linking. Put it in one portal a team and their AI tools can both read, and get started with TrueKeep.