How to Write a Clear Consulting Project Brief
A practical framework for writing a consulting brief that helps consultants understand the problem and propose a clearer scope, timeline and price.
A useful brief does not need to be long, but it should explain why the project exists and what needs to change. That information helps a consultant propose a realistic approach and reduces expectation gaps and changes after work begins.
1. Start with concise background
Describe your business, size, stage and why help is needed now. You do not need to disclose trade secrets in an initial brief; provide enough context to understand the nature of the problem.
For example: “We are a B2B services company. Our sales team grew from three to ten people in a year, but opportunity management and reporting did not evolve with that growth.” This is more useful than “we need a sales consultant.”
2. Describe the problem without prescribing the solution
Explain the symptoms, impact and available evidence. Avoid assuming a tool or solution before diagnosis unless the engagement is specifically to implement a decision already made.
Instead of “we need to install a specific system,” write: “Some opportunities are not followed up and there is no shared view of the pipeline. We need an assessment of the process and requirements, followed by a suitable recommendation.”
3. Define deliverables and acceptance criteria
A deliverable is something you can review or use: a diagnostic report, financial model, market-entry plan, operating procedure, workshop, or requirements design. “Improve performance” is an objective, not a defined deliverable.
State the expected format, level of detail, language and intended audience. If you do not yet know what is needed, request a short discovery phase that ends with a proposed scope.
- Name and format of each deliverable
- Draft and final dates
- Who approves the work
- What is out of scope
4. State timing, budget and constraints
Explain whether a deadline is linked to a decision, launch or regulatory requirement. Distinguish a necessary deadline from a preferred one because it affects approach, price and consultant availability.
A budget range helps shape a realistic proposal. If you cannot provide a number, clarify whether you expect a diagnostic session, a short project or extended implementation. Include constraints on access to data, teams or systems.
5. Review the brief before sending it
Ask someone outside the project to read the brief. If they can explain the problem, desired outcome and expected consultant contribution, the brief is probably clear enough to start a conversation.
Do not try to close every detail before speaking with an expert. The brief should attract the right consultant and begin a structured discussion; final details can be agreed in the proposal or statement of work.
FREQUENTLY ASKED QUESTIONS
Questions related to this guide
How long should a project brief be?+
Half a page to two pages is usually enough for an initial conversation if it covers context, problem, outcome, deliverables, timing and constraints. Complex projects may need separate attachments.
Should I disclose the budget?+
A budget range helps avoid unsuitable proposals and allows the approach to match available resources. You can state an approximate range or investment level rather than a final number.
What if I do not know the required deliverables?+
Request a diagnostic session or short discovery phase. Its output should define the problem, priorities, options and a proposed scope for the next phase.