How to spot a bad brief before you accept the project

How to Spot a Bad Brief Before You Accept the Project

The email looked normal. Five hundred words on cloud security, due Friday, rate acceptable. Forty-five minutes later, after three follow-up questions, it became clear the client wanted five hundred words that somehow covered compliance frameworks, vendor comparison, implementation timelines, and a case study they'd forgotten to mention.

Learning to identify bad content brief freelance projects before you accept them is the skill that determines whether your week involves writing or firefighting. The brief itself tells you almost everything — if you know what to look for in the first read.

The Brief That Isn't Actually a Brief

Some briefs are just topic requests wearing a brief's clothing. They say what to write about but nothing about why, for whom, or what success looks like. "Write an article about email marketing" is not a brief. It's a starting point for a conversation that should have happened before the email was sent.

The red flags content brief readers miss most often:

No audience specified. "Our readers" isn't an audience — it's a placeholder. If the client can't describe who reads their content, they haven't thought through why this piece exists.

No goal beyond "more content." Every article should do something: rank for a term, move readers toward a product, answer a question support keeps getting. If the brief doesn't mention what the piece is supposed to accomplish, you'll write something that accomplishes nothing.

Links to competitors but no links to their own site. This usually means they want you to reverse-engineer a voice and product understanding from scratch. That's research work, and it should be priced as such.

When Requirements Keep Multiplying

The initial brief said six hundred words. The reply to your first question added "also include a comparison table." Your follow-up about the table prompted "and maybe a FAQ section at the end." By the time you've agreed on scope, you're writing a fifteen-hundred-word piece at the six-hundred-word rate.

Scope creep during the brief stage is one of the clearest bad client brief signs. If requirements are expanding before the project starts, they'll keep expanding after. The same person who adds a comparison table in the second email will request "just a few tweaks" that turn into a rewrite.

Watch for unclear requirements that sound specific but aren't. "Make it engaging" tells you nothing. "Include industry statistics" without sources tells you you're doing the research. "Match our brand voice" without any voice documentation tells you they'll know it when they see it — and they haven't seen it yet.

The Revision Round Trap

Every brief should specify revision rounds. Two is standard. Unlimited is a warning sign. But the real content brief problems show up in how they describe the revision process.

"We'll need a few rounds to get it right" means they don't know what right looks like. They're planning to figure it out using your drafts as the experiment. That's a different service than writing to a clear brief — and a more expensive one.

"Our team will review" without specifying who on the team has final say means you'll be reconciling contradictory feedback from people who haven't talked to each other. One person wants it shorter, one wants more detail, and you're supposed to thread a needle that doesn't exist.

Some clients genuinely need help figuring out their content direction. That's fine — but it's consulting work, not article writing. The price and timeline should reflect it.

What the Brief Reveals About Client Communication

How someone writes a brief is how they'll communicate throughout the project. Vague briefs come from vague communicators. Briefs that contradict themselves come from clients who haven't aligned internally. Briefs that arrive at 11 PM with a morning deadline come from people whose emergencies will become your emergencies.

The freelance project red flags worth tracking:

Response time asymmetry. They take three days to answer your question, then expect the draft in twenty-four hours. This pattern doesn't improve after you've accepted.

Excessive enthusiasm with minimal substance. Lots of exclamation points and phrases like "this is going to be great" but no actual direction. Enthusiasm without clarity is how revision hell starts.

References to previous writers that "didn't work out" without specifics. Sometimes writers don't work out. But if every previous writer failed and they can't explain why, the brief isn't the only problem.

Project Qualification Before You Quote

The goal isn't to avoid every imperfect client. It's to know what you're walking into before you name a price. A brief with gaps is workable if the rate accounts for the extra work. A client who can't articulate what they want is manageable if there's budget for a discovery phase.

What makes a brief bad isn't incompleteness — it's incompleteness that the client doesn't recognize or isn't willing to address. The brief that says "I know this is rough, here's the context we have, let me know what else you need" is a different animal than the one that presents a paragraph as if it were a complete set of instructions.

Before quoting, run through what a brief actually needs to include. If major elements are missing, ask for them. The response tells you everything: clients who take the question seriously become good clients. Clients who brush it off stay exactly as they started.

Sometimes the fastest way to surface brief problems is to show what a well-researched piece actually looks like. BrandDraft AI reads the client's website first, then generates a draft using their actual product names and terminology — which immediately reveals whether the client's brief matches what their business actually says about itself. The gap between the brief and the website is often where the real requirements are hiding.

The Question That Filters Everything

After reading a brief, ask yourself: could another competent writer produce the same piece from this document? If two writers would interpret this brief completely differently, the brief is incomplete. Whatever you write will be wrong — not because of your skills, but because success was never defined clearly enough to hit.

This is why writers keep missing briefs that clients thought were clear. The client pictured something specific. The brief didn't capture it. The writer delivered exactly what was requested and nothing that was wanted.

A bad brief costs more in revision time than the project pays. Learning to spot one in the first email is how you stop trading hours for frustration and start taking projects that actually work.