A good brief describes the outcome, not the method. Eight things have to be in it: the goal, the audience, the scope, what you actually receive, in what format, by what date, for what money, and how you will decide it is done. Get those in writing and a freelancer nails the task on the first try. Leave them out and you get endless revisions, a "but we agreed on this" argument, and a burned budget.
The failure starts with one line in the brief
A client writes: "Need a logo. Modern, something with punch." The designer sends three options. "Not it." Three more. "Not it." On round four it turns out the company makes industrial pumps for boiler rooms, and the client had German engineering severity in his head the whole time. Two weeks gone, and both sides are sure the other one is at fault.
No freelancer reads minds. They read text. Anything missing gets filled in from their own taste and experience. That is not sabotage, that is physics.
Every word you leave out of the brief, the freelancer writes for you. Free of charge — and not the way you wanted.
What to put in the brief: eight required blocks
Whether you are ordering a 20-dollar banner or a 3,000-dollar CRM integration, the structure is the same. Only the depth changes.
- Goal. Not "we need a landing page", but "the landing page has to collect requests for air-conditioner installs; right now leads come from Instagram and there is no landing page at all".
- Audience. Who reads, looks at, buys this. Age, situation, how deep they are in the topic. "Cafe owners, 30–45, no design background, decide in two minutes."
- Scope. How many screens, words, options, hours, integrations. Boundaries are half the brief.
- Deliverables. What lands in your hands: files, source files, access, documentation.
- Format and technical requirements. A Figma file plus 2x PNGs; text in Google Docs with comments; code in a repo with a README and run instructions.
- Deadline. A date, not "asap". Anything over a week needs checkpoints.
- Budget or a range. Staying quiet about money is not a negotiating trick — it is a filter that screens out exactly the strong freelancers, because they will not play guessing games.
- Acceptance criteria. How you both know it is finished. More on this below — the most underrated block of all.
Then a ninth, optional but hugely accelerating one: references. Three to five "I like this" examples and one or two "definitely not this" — always with a note on what exactly you like. "I like this work" is useless. "I like that the headline reads from three metres away" is already a technical requirement.
Describe the result, not the method
The most common mistake experienced clients make is not too few details — it is the wrong ones. Someone paying for expertise starts dictating: "build the header with flexbox", "use Montserrat", "put the word innovative in the first paragraph".
Compare two versions of the same task:
- Method: "Write 700 words, add five subheads, use the phrase buy windows online eight times."
- Result: "The text has to convince someone comparing three companies to send us the enquiry. The key argument is one-day installation and a five-year warranty. Length is your call, but it should read in four to five minutes."
The first version guarantees exactly what you asked for and nothing more. The second buys the freelancer's brain instead of their hands. If you hired a specialist and then scripted every step, you overpaid — someone half the price could have followed your instructions.
The exception is hard constraints that genuinely exist: a brand book, the project's stack, platform rules, a legacy integration. That is not dictating method, that is input data, and it belongs in the brief from the start.
How detailed is too detailed
There is a simple test. Hand your brief to someone outside the project and ask: "What needs to be done, and how do we know it is finished?" If they answer with no follow-up questions, you are done. If they ask three questions, write those answers in.
Overkill looks like twelve pages where nine are company history and values, with zero actual requirements. Or the opposite: a pixel-by-pixel script for something a designer would have solved better on their own.
A working rule of thumb: a simple task takes 5–10 sentences, an average one takes a page, complex development takes 3–5 pages plus attachments. If you are writing page ten for a landing page, you are not briefing — you are postponing the start.
Design, copy and development: how briefs differ
A design brief
References and constraints decide everything here. Must-haves: where the artwork will live (web, print, stories), sizes, brand colours and fonts, what cannot be touched, and how many revision rounds the price covers. Spell out source files — without them you get a picture nobody can ever edit.
A copywriting brief
Audience, job of the text and raw material decide it. Say what action the reader should take and hand over real facts — numbers, timelines, guarantees, differences from competitors. With no raw material the writer produces filler, and that is on you. Name the tone: "like a colleague explaining it", not "business style".
A development brief
Scenarios and edge cases decide it. Write user stories: "user enters a phone number, gets a code, logs in". Separately, describe what happens when things go wrong: wrong code, failed payment, a 200 MB upload. Plus the environment: versions, hosting, access, repo ownership.
Acceptance criteria: your shield against endless revisions
This is the one block that turns "I don't like it" into a concrete conversation. Make every criterion checkable:
- "The page opens on an iPhone SE with no horizontal scroll."
- "No praise adjectives in the text unless a number backs them up."
- "The form pushes data to the Telegram bot; the email arrives within 30 seconds."
- "Two revision rounds are included; the third onwards costs 20% of the fee."
Always write that last one down. Revisions are not the enemy; revisions with no end are. And keep the agreement inside the platform: a safe deal only protects you when the subject of the deal is defined — which is what the brief is.
A brief skeleton you can copy
Take this frame and fill it in your own words — fifteen minutes of work:
- The task in one sentence. "Landing page for an accounting course for sole traders."
- Why. "Goal: 30 enquiries a month from Facebook traffic."
- For whom. "Sole traders, 25–40, afraid of fines, allergic to jargon."
- Scope. "Hero screen plus five blocks plus a form. Copy is mine."
- What I get. "Figma file, 360 and 1440 layouts, all source files."
- What already exists. "Logo, palette, photos at this link. Texts in the doc."
- References. "Like 1, 2, 3 for the whitespace and big type. Dislike 4 — cluttered."
- Deadline. "Hero by the 5th, full layout by the 12th."
- Budget. "250–350 dollars, paid through the safe deal."
- Acceptance. "Done when all blocks are built, responsive works, sources handed over. Two revision rounds included."
And if you hate writing briefs by hand, do not. 24freelance.pro has a free brief and spec generator: you answer questions about your task and get back a structured, ready-to-send brief — all that is left is to proofread it. It asks about format, deadline and acceptance criteria on its own, which is exactly what clients forget most often.
Then post your project together with the brief — the proposals will be specific instead of "hi, ready to start". Want to read the market first? Browse open freelance projects to see how others phrase tasks, or go straight to the freelancer catalog and invite specific people.
In short
A brief is not bureaucracy — it is the cheapest way to buy the right result on the first attempt. Half an hour on the document saves two weeks of revisions. Describe the goal and the outcome, leave the method to the freelancer, lock down format, deadline, money and acceptance criteria, and most conflicts disappear before work even starts. The rest comes down to picking the right person: that is covered in how a client finds a reliable freelancer.
Build yours in fifteen minutes with the free brief generator and publish the project — the first replies usually land within an hour.
