A vague client inquiry can leave a new freelancer feeling they must recommend a solution or send an estimate immediately. But “refresh our website” may describe a deliverable label—not the problem, context, or change the client has in mind. Before scoping, capture what was actually said and identify the missing detail most likely to change your next step.
Why a request is not yet a scope
A client’s first message is a useful clue, not a complete scope. “Refresh” could mean revising copy, adjusting a few visuals, improving a booking path, or something else. Choosing one interpretation too early can turn an assumption into a commitment.
Project and service-design guidance distinguishes a stated need from a proposed solution and recommends surfacing assumptions before detailing requirements. Those are useful design principles for freelance intake—not evidence that a script guarantees a business result. See PMI’s discussion of clear project requirements, Nielsen Norman Group’s discovery guidance, and the GOV.UK Service Manual on learning user needs.
How to clarify a vague freelance client inquiry before scoping
Use a short evidence-first pass instead of sending a long questionnaire.
- Preserve the client’s wording. Copy the exact request when possible. If you are summarizing from memory, label it as a paraphrase. Keep “refresh the website” separate from your interpretation, such as “full redesign.”
- Separate known, assumed, and unknown. A known item is supported by what the client said or another identified source. An assumption may be plausible but still needs checking. An unknown is simply information you do not have. “Spring booking period is approaching” may be stated context; “the site is losing bookings” is not a fact unless the client said so.
- Choose the decision-bearing unknown. Ask whether the answer could change the work, its boundaries, the fit of the next step, or what you should do next. If not, record it and let it wait. You do not need to resolve every open detail at once.
- Ask one neutral question. Avoid wording that smuggles in a solution: “Do you need a complete redesign?” Instead, ask about the context or desired change: “What prompted the refresh now, and what would you like visitors to be able to do more easily?”
- Record the next step honestly. If the key information is unavailable, write “clarify before scoping.” A tidy note is not the same as a quote-ready scope.
A six-field inquiry snapshot
Use this lightweight template for a first pass:
- What I heard: the exact request, or a labeled paraphrase.
- Why now / context: the stated trigger and source, or “not yet known.”
- Change sought: a tentative hypothesis, clearly marked as unconfirmed.
- Known / assumed / unknown: each detail sorted by evidence status.
- Scope-sensitive unknown: the missing answer most likely to change the next decision.
- Next move: one neutral question, or “clarify before scoping.”
For the website example, the request and timing cue may be known; the pages involved, current difficulty, and intended visitor action may remain unknown. “They need a redesign to increase bookings” adds a solution and an outcome that have not been confirmed. A careful snapshot preserves the request and leaves the gaps visible.
This snapshot is a planning aid—not a proposal, contract, diagnosis, or pricing recommendation. It does not guarantee less rework, client conversion, or project success. Its narrower purpose is to make the available evidence and the next question easier to see before you define the work.
When to move forward—and when to clarify first
Before passing the note along, check that the request has not been rewritten as a solution; facts, assumptions, and unknowns are visibly distinct; context is supported or marked unknown; the next question connects to a consequential uncertainty; and the note contains no price, promise, or deliverable commitment. Repair unsupported lines before moving on.
If the checks pass, you have an honest intake snapshot—not a quote-ready scope. If a consequential unknown remains, carry it forward with the question attached. The next stage can use that record to frame the client’s problem and intended change while keeping the original evidence separate from the hypothesis.
A short, honest note is a better starting point than a confident answer built on missing information. Treat the request as a clue, not the scope.