How to reply to a consulting brief
Begin with the decision the client needs to make, not a diagnosis of a problem you have not investigated. Explain a relevant method you can support with experience, then ask which evidence and people are available. A consulting introduction should make your proposed inquiry understandable without pretending that the recommendation is already settled.
An invented process-review assignment
The scenario below is fictional. Its replies demonstrate differences in scoping an engagement; they do not describe a real client or a successful proposal.
Brief: “Our service team says requests are delayed between intake and assignment. Managers disagree about whether the problem is staffing or the handover process. We want an outside review and a recommendation before choosing a new workflow.”
Weak reply: “Your process needs automation. I can transform the workflow and eliminate the delays. I will create a strategy presentation and recommend the best software.”
Example reply:
The review needs to distinguish a staffing constraint from a handover problem before the team chooses a workflow. I can describe a comparable investigation and the evidence I used, without sharing former clients’ records. I would first map how requests are received, assigned and returned for clarification, then compare that account with available records and staff interviews. Which decision must the review support, and who can authorise access to the people and request history? I’d propose an assessment with unresolved assumptions and options made explicit, rather than recommend a system before understanding the constraint.
Adapt the experience claim to your actual role. If you supported an assessment rather than led it, say so. Describe what you examined and what you contributed. A confidential engagement can be discussed through its method and limits without identifying the organisation or revealing internal findings.
Locate the decision and its owner
The same request history could support a staffing discussion, a revised intake form or a change in assignment rules. Ask what decision is pending and what alternatives the sponsor is willing to consider. Otherwise you could produce a detailed assessment that answers a different question from the one the team needs resolved.
Find out who will receive the findings and who has authority to act. Managers can describe their departments while disagreeing about the wider process. Agree how those differences will appear in the assessment. Making disagreement visible is useful; treating the sponsor’s preferred explanation as a finding is not an investigation.
Match the account to observable evidence
Request the available intake records, assignment history and descriptions of exceptions. Ask whether the recorded timestamps actually represent the events the team wants to compare. A delay in entering a record can look like a delay in doing the work. Establish what can be checked before building an explanation around the system’s labels.
Interviews can reveal work that never enters the formal record, such as clarification through a separate channel. Ask how you will examine those accounts without collecting unrelated information. Mark gaps and conflicting explanations in your working notes. If important records are unavailable, state how that limits the assessment rather than filling the gap with a plausible story.
Choose an output people can act on
A process map can expose ownership gaps; a decision paper can compare alternatives; a workshop can help the team examine conflicting assumptions. Ask how the sponsor expects to use the result. A presentation may accompany the work, but its format should not determine the investigation.
For each recommendation, distinguish the supporting observation from the proposed action. Name the dependency, responsible role and unresolved assumption. If a small trial would help test an idea, explain the observation it should collect. Do not describe the proposed trial as proof that the change will succeed or quietly expand the assignment into running it.
Separate the review from implementation
Agree whether your responsibility ends with findings or includes training, configuration and follow-up. The people who operate the process must be involved in a change that affects their work. Access for review does not itself give you authority to alter the system. Establish who approves operational changes before offering to make them.
Use the consulting hub to locate assignments, then check the actual responsibilities. Finish your opening reply with the evidence or sponsor decision needed to scope the inquiry, rather than an unsupported promise about the organisation’s future performance.