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

Is This Scope Too Vague? A 5-Criteria Scoring Method

A project's scope is too vague to quote when it scores low across most of five checkable criteria: named deliverables, explicit exclusions, acceptance criteria, a reference point, and priority order. Score each 1 (missing), 3 (partial), or 5 (clear) from the brief alone, sum the five scores out of 25, and the total tells you what to do next — quote it as-is, ask 1-2 targeted questions, or propose a paid scoping phase before committing to a number. The point isn't a perfect score; it's knowing exactly which one or two gaps are actually open instead of treating the whole brief as uniformly unclear.

TL;DR

Score a brief 1/3/5 on each of five criteria — Named Deliverables, Explicit Exclusions, Acceptance Criteria, Reference Point, Priority Order — for a total out of 25. 20-25: quote as-is. 12-19: ask the 1-2 questions tied to whichever criteria scored low. 0-11: the gap is too large for a written back-and-forth — propose a paid scoping phase before pricing it.

Why "does this feel vague" isn't a repeatable method

A gut sense of vagueness is real, but it doesn't tell you which specific gap to close, and it's inconsistent brief to brief — the same person can read the same brief differently on a busy day versus a slow one. That inconsistency has a cost: PMI's research on requirements management found 37% of organizations cite inaccurate requirements as the primary reason projects fail, and IAG Consulting's Business Analysis Benchmark separately found that poor requirements definition consumes more than one dollar in three of total project budget. A checkable score, run the same way every time, catches what a feeling misses — and tells you exactly what's missing instead of just that something is.

"Vague" isn't one problem. It's up to five different missing pieces, and they need five different questions.

The 5 criteria, scored 1 / 3 / 5

Score each from the brief as it stands today — 1 if the brief is silent on it, 3 if it's partially there, 5 if it's clearly answered. Use 2 or 4 for anything that falls between the anchors below.

Named Deliverables

Are the actual outputs specific, not just a task category?

Score 1: A task list with no outputs named ("build me a website")

Score 3: A general deliverable named, no format or detail

Score 5: Specific deliverables with format and quantity ("12-page website, 4 core templates, mobile + desktop")

Explicit Exclusions

Does the brief say what's NOT included, not just what is?

Score 1: Nothing stated as out of scope anywhere

Score 3: One exclusion mentioned in passing

Score 5: A stated list of what's explicitly not included

Acceptance Criteria

Is there a checkable definition of "done"?

Score 1: No way to know when it's finished

Score 3: A vague success statement ("looks professional," "feels modern")

Score 5: A specific, checkable definition of done ("passes these 3 test scenarios")

Reference Point

Is there something concrete to calibrate against?

Score 1: No comparable example given anywhere

Score 3: A vague comparison ("something modern and clean")

Score 5: A specific named example, competitor, or existing asset to match

Priority Order

Does the brief distinguish must-have from nice-to-have?

Score 1: Everything implied as equally required

Score 3: A rough priority mentioned once, not applied consistently

Score 5: Deliverables explicitly split into must-have and nice-to-have

What the total score means

Add the five scores together for a total out of 25, then match it to one of three actions.

20–25

Clear enough to quote as-is

All five criteria are mostly answered. Write the proposal from what's already in the brief — re-confirming everything with the client at this point adds friction without adding information.

12–19

Ask 1-2 targeted questions before quoting

One or two criteria are genuinely open. Identify which specific ones scored low and ask only those — not a generic "can you clarify the brief" that reopens everything.

0–11

Not scoped enough to price with a fixed number

Most criteria are open. A written back-and-forth won't close a gap this size efficiently — propose a short paid scoping phase or a call specifically to build the scope document together before quoting.

A worked example

Brief: "We need a new website for our consulting firm, similar to [a named competitor's site]. Should include a homepage, an about page, and a contact form. We're not looking for a blog or anything fancy — just clean and professional."

Named Deliverables: 5 — homepage, about page, contact form are specific, named pages. Explicit Exclusions: 5 — "not a blog or anything fancy" states what's out. Acceptance Criteria: 1 — "clean and professional" isn't checkable. Reference Point: 5 — a named competitor site to match. Priority Order: 3 —three pages are listed with no stated priority among them, but the scope is small enough that this matters less. Total: 19 — solidly in the "ask 1-2 questions" band, and the score tells you exactly which one to ask: what does "clean and professional" mean, checkably, for this specific client.

Frequently asked questions

No — a low score means the scope isn't defined yet, not that the project is bad. Most low scores are fixable: ask the 1-2 highest-value questions (see the related question bank below), or propose a short paid scoping phase before quoting a fixed price. A low score becomes a decline-level concern only if the client resists defining scope at all after you've asked directly.

Yes — all five criteria are checkable from the written brief alone. A first call or reply can raise the score (the client names deliverables or an example when asked), but you don't need one to run the method the first time.

That's normal and useful information on its own: it tells you exactly which one or two questions to ask, rather than treating the whole brief as uniformly vague. A brief that's a 5 on Named Deliverables and a 1 on Explicit Exclusions needs one specific question ("what's not included"), not a full re-scoping conversation.

The matrix scores Scope Clarity as one line among four broader qualification vectors (scope, budget, timeline, stakeholder) — useful for a fast overall read. This method is a deep drill-down on scope specifically, five separate criteria instead of one, for when scope is the part of the brief you're actually unsure about.

No method guarantees that — a clearly scoped brief today can still expand once work starts. What a high score tells you is that the starting point is solid: deliverables, exclusions, and a definition of done are all in writing, which is exactly what makes a later addition visibly outside scope instead of an ambiguous gray area.

Get the full risk picture, not just scope.

Scope is one of four vectors that decide whether a client is worth taking. The free Client Risk Analyzer scores all four — scope, budget, timeline, stakeholder — from a pasted brief in under a minute, no signup required.

Analyze a brief free