What a good brief actually contains
A few years back, a shop owner asked me to "build a website, nothing fancy, just like my competitor's." I built something close to the competitor's site. He hated it. It turned out the competitor's site was exactly the thing he was trying to get away from: too busy, too loud, aimed at a younger crowd than the one he wanted. He'd told me what to make. He hadn't told me what he was trying to fix. That gap cost both of us a fortnight.
I think about that job whenever someone asks me how to write a brief. Most briefs I receive are either three sentences long or eleven pages of detail nobody will read. Both versions skip the part that matters most: why you're doing this at all. So here's what I'd want to know if you handed me a project, and why each piece changes the work.
Start with the problem, not the thing you want built
The single most useful sentence in any brief is the one that names the problem. Not "I need a new website." That's a solution you've already picked. I want "people call to ask questions the site should answer, and I'm losing an hour a day to the phone." Now I know what success looks like. That might be a redesign, or three good pages and a better FAQ, or it might turn out you don't need me at all.
When the problem is missing, you get what my shop owner got: a competent version of the wrong thing. The contractor builds exactly what you asked for, you're unhappy, and nobody can point to where it went sideways. It went sideways at the very beginning, when the request was a deliverable instead of a problem.
He'd told me what to make. He hadn't told me what he was trying to fix.
Say who it's for
A site for booking contractors and a site for selling handmade soap can look identical in a brief that only lists pages, and they are two different jobs. The audience decides almost everything downstream: the tone, how much explaining the copy does, whether the design leans trustworthy or playful, how fast it has to load for someone reading on a phone in a parking lot.
Be specific here. "Small business owners" tells me very little. "Café owners in their fifties who've never run online ordering and are nervous about it" tells me how to write every button label. If you're not sure who the audience is, that's worth knowing too, because it means the first piece of work is figuring that out, and it should be priced as such.
Define what success looks like
This is the question that separates a brief from a wish list. How will you know this worked? More bookings? Fewer support emails? A site you're not embarrassed to hand someone a card for? All of those are valid. They just point at different work.
The trap is leaving success undefined, because then it defaults to "I'll know it when I see it," and that's not a target anyone can hit on purpose. I've watched projects go three rounds of revisions on the colour of a heading because nobody agreed on what the page was supposed to achieve. Name the outcome and a lot of those arguments never start.
Be honest about constraints and what's already decided
Budget, timeline, and the difference between must-have and nice-to-have. People hide the budget because they think naming it means paying it. The opposite is true. If you tell me you have $4,000, I'll design the best $4,000 project I can. If you don't, I'll guess, and either I overbuild and scare you off or I underbuild and you wonder why it feels thin.
Timeline matters the same way. "Before the spring season" is a real constraint that shapes scope.
And the must-have versus nice-to-have split is the most quietly valuable thing in any brief. When the deadline tightens or the money runs short, that list is what we cut from, and it's far less painful to draw that line while everyone's calm than during the last week.
If you've committed to a brand colour, a platform, a host, a name, a logo you love, say so. These are fences, and I'd rather know where they are before I start than after I've designed something that climbs right over one.
The flip side is just as useful: tell me what's genuinely open. "We're attached to the logo but everything else is up for grabs" lets me bring real ideas instead of tiptoeing. Briefs that pretend everything is open when three things are locked produce a lot of polite, wasted work.
You don't need a project manager or a template to do this. Open a blank note and answer five things in plain sentences: the problem you're solving, who it's for, what success looks like, what the budget and deadline are, and what's already decided. Half a page is plenty. If you can't answer one of them yet, write "not sure yet" and leave it. That honest gap tells whoever you hire exactly where the work really begins, and it's often the most valuable line on the page.