A discovery brief prepares both sides to explore a project without presenting assumptions as an agreed scope. Record the problem described, relevant context, existing evidence and the questions that could change your recommendation. End with the decision the conversation needs to support and the information you do not need to collect.
Start with the reason for the conversation
Write one sentence explaining why someone contacted you now. A triggering event, such as a new service launch or a difficult handover, is more useful than a broad ambition to improve everything. Attribute the statement to its source and date. If it came from an initial message, preserve its meaning without treating it as a diagnosis you have independently confirmed.
Add the people affected and the task that currently causes difficulty. Keep this separate from the service you sell. A consultant who offers documentation may discover that unclear approval authority, rather than missing instructions, is causing delays. The brief should leave room for that finding. Its purpose is to make the first conversation more informed, not to preselect a paid engagement.
Separate evidence, assumptions and questions
Use three short labels in your working document: reported information, supporting material and open questions. A report that staff often ask the same question belongs under reported information until you have reviewed appropriate examples. A redacted instruction sheet can be supporting material. Whether it reflects current practice remains an open question. This distinction protects the conversation from confident but unsupported conclusions.
Choose questions according to the decisions they affect. Ask who owns the process if ownership determines access or approval. Ask about a deadline if it changes feasibility. Leave detailed personal histories and unrelated company information out. Invite the client to bring a safe sample rather than a complete archive. Decide who can see the brief, particularly when several prospective collaborators are involved.
Make preparation proportionate and revisable
Limit the first brief to material you can reasonably review before the meeting. A useful working structure includes the trigger, affected task, known constraints, available examples and three priority uncertainties. Mark the document as preparation rather than an approved project specification. A long, polished document can accidentally suggest that decisions have already been made, especially when it includes proposed deliverables and commercial language.
Share a short agenda that explains what you hope to understand and what the meeting will not settle. Ask whether any important perspective is missing, and offer a written route for someone who cannot attend. After the conversation, revise the brief with corrections and a dated summary. Retain unresolved questions visibly so the next proposal does not silently convert guesses into commitments.
Before sending the agenda, check each requested input against the meeting objective. If you need to choose a review approach, one representative document and the name of its owner may be enough. Put optional background in a separate list. This prevents preparation from becoming unpaid analysis of a large archive and lets the client understand what to bring first.
Fictional example: preparing for an onboarding discussion
In this fictional scenario, a service writer receives a message saying that new volunteers struggle with an onboarding guide. The request asks for a rewrite before a training event. The writer creates a brief with the reported issue, the event date and a link to a redacted copy of the current guide. She does not describe the guide as the proven cause of the difficulty.
Her three priority questions concern the tasks volunteers must complete, who answers questions during onboarding and which instructions changed recently. She requests an anonymized example of a confusing step instead of volunteer records. The meeting objective becomes deciding whether to revise instructions, clarify support responsibilities or investigate both. The output is a prepared discussion document with an owner and revision date; there is no agreed rewrite, claimed improvement or fabricated client result.
A checklist for your next step
- Record the triggering event.
- Label evidence and assumptions separately.
- Prioritize questions that change a decision.
- Request a safe sample.
- Date the revised brief.
Common questions
Should the brief include a proposed price?
Include commercial boundaries only when useful to preparation. A discovery brief should not make an unscoped estimate appear to be an agreed offer.
Can I prepare it without client documents?
Yes. Record the initial message accurately and identify missing evidence. Avoid filling gaps with invented operational detail.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.