Published 2026-07-17 · Updated 2026-07-17 · Adrieluxe Team

The Vague Project Brief: A Triage Playbook

A vague brief doesn't call for a full interrogation or an automatic decline — it calls for a five-minute triage. Re-read the brief once against four checks (does it name an outcome, a budget, a reason for the timeline, and the actual decision-maker), ask only the ones still missing, and sort the answer into one of three buckets: quick clarify, needs a scoping call, or not worth pursuing. The goal isn't to demand a perfect brief — most people writing one have never done it before — it's to spend five minutes now instead of finding out the gaps existed three weeks into the project.

TL;DR

Run every vague brief through four checks — Scope Clarity, Budget Alignment, Timeline Pressure, Stakeholder Position — each with one specific question if the brief doesn't already answer it. Zero or one gap: reply with the missing question and move to a proposal. Two or three gaps: propose a short call instead of an email back-and-forth. Three-plus gaps where a direct question gets deflected or ignored: that's your answer — not the vagueness itself, but what happened when you asked about it directly.

Why a vague brief is a triage problem, not a yes/no decision

The instinct with a vague brief is to either decline on sight or fire back a long list of questions that reads like a proposal before there's even a project. Both waste the same thing: time, on a brief you haven't actually assessed yet. Unclear requirements aren't a minor annoyance either — PMI's research on requirements management found 37% of organizations cite inaccurate requirements as the primary reason projects fail, with nearly half of unsuccessful projects tracing back to requirements gaps. That's the cost of skipping triage and starting anyway. The fix isn't more questions up front — it's the right four, asked once.

A vague brief isn't a red flag by itself. What the client does when you ask one direct, specific question about it — that's the actual signal.

The 5-minute triage: four checks, one question each

These are the same four vectors that determine whether a project is worth taking at all — Scope Clarity, Budget Alignment, Timeline Pressure, Stakeholder Position. Run them as a quick read of the brief you already have before you send anything back.

Scope Clarity

Is there a stated outcome, or just a task list?

Check the brief for: Read the brief once for a goal, not a deliverable. "Build me a website" is a task list. "Get more people to book a consultation from the site" is an outcome — even if it's short.

If missing, ask: "What should be different for you once this is done?"

Good answer: A specific change they're trying to cause — more signups, fewer support tickets, a rebrand ahead of a launch.

Bad answer: A restated task list ("I just need the website built") or no answer at all.

Budget Alignment

Is there a number, even a rough one?

Check the brief for: Look for any figure — a range, a "we've budgeted around," a comparison to a past project's cost. Absence of a number isn't automatically bad; absence of an answer when you ask for one is.

If missing, ask: "What's the budget range you're working with for this?"

Good answer: A number or range, even a wide one — "somewhere between $3–8k depending on scope" is a real answer.

Bad answer: "It depends on the proposal" or "send me your rates" repeated after you've already asked once.

Timeline Pressure

Is there a reason behind the deadline, or just urgency?

Check the brief for: Note whether the brief names an external reason for the date — a launch, an event, a compliance deadline — or just states one.

If missing, ask: "Is there a specific date this needs to be live by, and what's driving that date?"

Good answer: A named, checkable reason: a product launch, a trade show, a contract renewal.

Bad answer: "As soon as possible" with no reason, or a reason that shifts when you ask a follow-up.

Stakeholder Position

Are you talking to the person who approves the work?

Check the brief for: Check whether the brief is signed by, or the conversation is with, someone who can say yes without checking with anyone else.

If missing, ask: "Besides you, is there anyone else who needs to sign off before we start?"

Good answer: "It's just me" or a named second approver mentioned upfront, unprompted.

Bad answer: "I'll need to run this by my team/partner/boss" with no name attached, especially if it comes up more than once.

Sorting the answers into three buckets

Count how many of the four checks the brief left unclear once you've read it. That count — and how the client responds when you ask — decides which of three moves comes next.

Quick clarify

0–1 of the four checks came back unclear

Send the one or two missing questions in your reply and move straight to a proposal once they answer. Most first-time-brief-writers land here — they just hadn't been asked before.

Needs a scoping call

2–3 checks came back unclear

Too many gaps to resolve over email without it turning into an interrogation. Propose a short call instead of a written back-and-forth — it's faster for both sides and lets you read tone, which email can't give you.

Not worth pursuing

3+ checks unclear AND a direct, specific question goes unanswered or gets deflected

The triage isn't punishing vagueness — it's testing whether a direct question gets a direct answer. A brief that's vague on everything but resolves fast once you ask is a "quick clarify." A brief that stays vague after a specific, polite question is a different problem entirely.

What to actually send back

Ask only the questions the triage flagged as missing — not all four by default. Naming the gap in the brief, not the client's effort, keeps the reply from reading like a complaint: "Thanks for the brief — before I put a proposal together, two quick things: what's driving the launch date, and is there anyone besides you who'll need to sign off?" is specific, short, and answerable in one reply. A client who answers both promptly has resolved the gap. One who goes quiet or answers a different question than the one you asked has told you something the original brief couldn't.

Frequently asked questions

No — most vague briefs are fixable with one or two questions, and declining on sight throws away work that would've been fine once clarified. The triage exists precisely so you don't have to guess: it sorts a brief into "quick clarify," "needs a real scoping call," or "not worth pursuing" in about five minutes, so decline is a decision you make on evidence, not a reflex you use to avoid reading closely.

Re-run the same triage on the reply. A client who names a budget number and a decision-maker but stays vague on scope has moved from "not worth pursuing" to "needs a scoping call" — that's real progress, not a stall. A client who answers the easy questions (timeline, who's involved) but goes quiet on budget specifically is a different pattern worth noting on its own; a named number is usually the highest-leverage single answer to get.

The triage runs on you re-reading the brief you already have — it doesn't require sending all four questions to the client. Most briefs already answer two or three of the four checks; you're only asking the ones still missing after your own read, which in practice is usually one or two questions, not four.

The red-flags list is what to notice while reading a brief. This triage is what to do about it — a repeatable five-minute routine that runs on every brief, vague or not, and ends in one of three concrete next actions instead of a list of concerns to sit with.

No. Most people writing their first project brief have never written one before — nobody taught them what a freelancer or agency actually needs to know. A vague brief from someone who answers your clarifying questions promptly and specifically is a client who just needed help structuring their ask, which is a normal, fixable gap. The signal isn't the vagueness itself; it's what happens after you ask.

Skip writing the questions yourself.

The free Discovery Question Generator takes a project type and returns the specific questions to ask before you quote — grounded in the same four checks this triage runs on, in under a minute, no signup required.

Generate discovery questions