Who Do You Actually Need? Writing a Mission Brief Before Briefing Consultants

Most staffing problems are not sourcing problems. They are scoping problems that become visible late, when a capable person has been placed on a mission whose real need was never written down. The title says it plainly: before asking who is available, ask who you actually need. That question can only be answered by a document, the mission brief, and by the discipline of writing it before anyone is briefed, called or shortlisted.

This article sets out how to write that brief, how to translate it into a profile, where AI helps in finding and qualifying consultants and freelancers, and how to organise delivery when your bench mixes employees and independents.

Why the brief comes before the search

When a need appears, the natural reflex is to name a role: a project manager, a data engineer, a change lead. The role name feels precise, but it hides most of what matters. Two organisations asking for a project manager may mean a coordinator who tracks actions, a delivery lead who owns a schedule and a budget, or a senior figure who arbitrates between conflicting stakeholders. The label is identical; the expertise required is not.

Skipping the brief produces predictable consequences:

• Sourcing starts from a job title, so candidates are compared on keywords rather than on fit with the problem.
• Interviews drift into general impressions because nobody agreed on what good looks like.
• The consultant begins without a shared definition of done, and the first weeks are spent discovering the real scope.
• Changes of scope are negotiated verbally, then disputed at invoicing or at delivery.

A brief does not remove uncertainty. It makes the uncertainty explicit, so that it can be managed instead of discovered.

What a mission brief contains

A useful brief is short, typically two to four pages, and written for two readers: the person who will carry out the mission and the person who will decide whether to hire them. It should be possible to read it in a few minutes and to disagree with it precisely.

The problem, not the solution

Start with the situation that triggered the request, described in operational terms. A manufacturer running several sites might write: the sites report production incidents in different formats, so management cannot compare them or identify recurring causes. That sentence says more than "we need a quality systems consultant", because it defines the problem and leaves room for the expert to propose how to solve it.

If you already have a solution in mind, state it as a hypothesis, separately from the problem. Experienced consultants will test it; weaker ones will simply execute it. Knowing which you have is useful.

Objectives and what done looks like

List the outcomes expected, and for each one, how you will recognise it. Prefer observable deliverables and decisions over activities: a validated process map, a signed-off migration plan, a trained team operating autonomously. Avoid objectives that cannot be verified, such as "improve collaboration".

Distinguish what is required from what is desirable. When everything is a priority, the brief gives no guidance when trade-offs appear.

Scope boundaries

Say what is in, what is out, and what is undecided. Out-of-scope statements are as valuable as in-scope ones, because they prevent the silent expansion that turns a defined mission into an open-ended one. Mark undecided points as such and name who will decide them and by when.

Context and constraints

Cover the elements that shape how the work can be done:

• Stakeholders: who sponsors the mission, who is affected, who may resist.
• Existing assets: documentation, tools, data, previous attempts and why they stalled.
• Constraints: timeline anchors, regulatory obligations, security and confidentiality requirements, languages, locations, and whether work is on site or remote.
• Dependencies: decisions, access or people the mission relies on and that you do not fully control.

A consultant cannot compensate for a constraint they discover in week four. Writing them down also forces the client to confirm that access and decisions are actually available.

Governance and working rhythm

Name the sponsor, the day-to-day contact, the cadence of reviews, and the decision rights of the consultant. A person asked to deliver a result without authority to obtain the inputs it requires has been set up to fail. State how progress will be reported and how scope changes will be handled.

Commercial and legal framing

Without stating any figures in the brief itself if they are still under discussion, indicate the engagement model envisaged (time and materials, fixed scope, or outcome-based), the expected duration range, and any intellectual property, confidentiality or data protection requirements. Where the mission involves personal data, reference the applicable obligations, such as GDPR, so that candidates and their employers can assess their ability to comply.

From brief to profile: matching expertise to the real need

Once the brief exists, the profile is derived from it, not the other way round. This is the step where most mismatches are avoided.

Separate four things that job descriptions tend to blend:

1. Technical or domain expertise: what the person must know, for instance a given methodology, regulation, system or industry process.
2. Situational experience: whether they have operated in a context like yours, for example a multi-site environment, a regulated sector, or a team in conflict.
3. Level of autonomy and seniority: whether they need to be told what to do, propose what to do, or decide and answer for it.
4. Working style and interpersonal fit: the capacity to work with your stakeholders, in your language, with your pace of decision.

A useful exercise is to rank these for your mission. A short, well-defined technical task may need depth in the first and little of the fourth. A transformation involving reluctant teams reverses the weighting. Making the ranking explicit helps you resist the pull of a brilliant but misaligned candidate.

Choosing the form of expertise

Not every need calls for the same kind of resource. The brief should help you decide between several options:

The table is a starting point, not a rule. The relevant question is where the knowledge should live afterwards: if it must stay in your organisation, plan for transfer from the first day, whichever form you choose.

Where AI helps in sourcing and qualification

AI is useful at specific points in this process, and clarity about those points is what keeps it from becoming a liability.

What it does well

• Structuring the brief. Given rough notes, an assistant can propose a draft structure, flag missing sections, and highlight ambiguous statements such as undefined terms or objectives without a verification method. This is editing support, and the content remains yours.
• Translating the brief into search criteria. It can derive skills, experience patterns and adjacent profiles from the brief, including candidates whose job titles differ from the one you would have searched for.
• Processing volume. Reading large numbers of profiles, portfolios and past mission descriptions against criteria is tedious for humans and well suited to automation. It produces a first-pass ordering and the reasons behind it.
• Preparing qualification. It can draft interview questions tied to the brief, summarise a candidate's relevant experience, and surface inconsistencies worth probing.
• Administrative load. Scheduling, document collection, reference request templates and onboarding checklists can be largely automated.

What it should not decide

Judgment about people, credibility and fit has to remain with accountable humans. There are three reasons beyond principle.

First, outputs reflect the data and criteria they were given. If the brief is weak or the historical data embeds past bias, automated ranking will reproduce it efficiently. Second, much of what matters in a consultant, such as how they handle disagreement or admit uncertainty, appears in conversation, not on a profile. Third, regulation increasingly frames this area. Under the EU AI Act, systems used for recruitment and for selecting or evaluating people for work-related purposes are treated as high-risk, which brings obligations around transparency, human oversight and documentation.

Data protection rules also apply to the processing of candidate information. Organisations should verify with their legal advisers how these texts apply to their situation, and should be able to explain to a candidate how a shortlist was produced.

A workable principle: AI proposes and explains, a named person decides and records why. Keep the reasoning visible, so that a shortlist can be challenged and corrected.

Qualification practices that hold up

Whatever tools you use, qualification should test the brief, not the person's general reputation:

• Ask the candidate to restate the problem in their own words and to say what they would want to clarify. The quality of their questions is informative.
• Use a short, realistic scenario drawn from the mission rather than abstract exercises.
• Check references for the specific type of situation, not for general satisfaction.
• Make explicit what was assumed about availability, location, language and tooling.
• Where several people interview, align beforehand on the criteria and gather assessments independently before discussing.

Onboarding: the first days decide the mission

A mission that was well scoped and well staffed can still fail in its first weeks if the person is not equipped to start. Onboarding an external expert is a short, intense version of onboarding an employee, with fewer chances to correct course.

Prepare, before the start date:

• Access to systems, documents and people, tested in advance rather than promised.
• A first-week plan that includes introductions to the stakeholders named in the brief.
• A single point of contact who can unblock quickly.
• Confidentiality, security and data handling rules, communicated and acknowledged.
• The brief itself, updated with whatever changed between selection and start.

In the first week, review the brief together. The consultant will have questions, and some will reveal that the written scope and the understood scope differ. Treat this as the purpose of the exercise, not as a sign that something went wrong. Agree any adjustment in writing, and confirm the first checkpoint date.

Quality of delivery

Quality is easiest to manage when it is defined before work starts and observed continuously, not assessed at the end.

• Acceptance criteria are drawn directly from the brief's definition of done. Reviewers know what they will be asked to approve and when.
• Intermediate deliverables make progress visible and reduce the risk of a late surprise. For an uncertain mission, the first deliverable can be a refined plan.
• Regular reviews with the sponsor test whether the original problem is still the right one. Context changes, and a faithful delivery of an outdated need is still a failure.
• Documentation and transfer are part of the mission, not an optional extra. Decide who will maintain what is produced, and make that person a participant, not a recipient.
• Closure includes a short review of what worked, what did not, and what should change in the next brief. This is where organisational learning actually happens.

The same standards apply whether the person is an employee, an independent or a member of a firm's team. Applying them equally is also what makes mixed teams function.

Organising around a mixed bench

Most organisations now deliver through a combination of employees, independents and external firms. The model works when its rules are explicit, and fails when each category is managed by habit.

For clients

• Maintain a clear view of who is working on what, under which contract, with which access. Visibility across categories is a governance and security matter, not only a staffing one.
• Keep decision rights with your own people. External experts advise, produce and execute within a defined mandate, but accountability for outcomes stays internal.
• Plan knowledge retention deliberately. Where independents hold unique knowledge, require documentation and handover as contract terms.
• Be aware of legal boundaries between genuine independent work and situations that resemble employment, which are treated differently depending on jurisdiction. Seek legal advice for your context.

For consulting firms

• A firm combining salaried staff with a network of independents has to maintain consistent quality standards across both. The client buys a result, and does not distinguish between categories of contributor.
• Qualification, onboarding and delivery review should follow the same method for everyone, with differences handled in contracts and not in rigour.
• Matching should draw on a structured, current view of skills and availability, which is precisely where automated assistance saves time, provided people validate the final match.
• Be transparent with clients about who will actually do the work and how continuity will be ensured if someone becomes unavailable.

Shared practices

Whether you are on the client or the provider side, a few habits make the model sustainable: a common brief template, a shared definition of done, a consistent onboarding checklist, and a lightweight record of lessons learned after each mission. None of these is sophisticated. Their value comes from being applied every time.

Practical next steps and questions to ask

Before briefing anyone, work through the following.

Steps

1. Write the problem in two or three sentences, without naming a solution or a role.
2. List the outcomes expected and how each will be verified.
3. State scope boundaries, including what is explicitly out and what remains undecided.
4. Identify constraints, dependencies and the access the mission requires, and confirm they are available.
5. Rank expertise, situational experience, autonomy and working style for this specific mission.
6. Decide which form of resource fits the need and where knowledge should remain afterwards.
7. If using AI in sourcing, define the criteria yourself, keep the reasoning visible, and name the person who will make and record the decision.
8. Prepare onboarding before the shortlist is final, so that the start is not delayed by access and introductions.
9. Schedule review points and a closing review at the outset.

Questions to ask yourself

• If the consultant started tomorrow, could they explain the problem back to me accurately?
• What would make me say, in a month, that this mission has succeeded or failed?
• Which of my requirements are essential, and which am I using as a filter out of habit?
• Who in my organisation will own the result once the external person leaves?
• Can I explain to a candidate how they were assessed, and to a regulator how automated tools were used?
• What decisions does this person need to be able to take, and have I given them the authority to do so?

Questions to ask candidates and providers

• How do you understand the problem, and what would you want to verify first?
• What have you done in a comparable situation, and what would you do differently now?
• What do you need from us in the first two weeks to be effective?
• How will you document and transfer what you produce?
• What would lead you to tell us that the scope should change?

A brief will not guarantee a good mission, but its absence almost guarantees a confused one. Time spent writing it is time recovered in every later step: sourcing, qualification, onboarding and delivery.

Going further with Stratelya

Talent OS, currently in Early Access, is designed around this sequence: a structured mission brief first, then AI-assisted sourcing and qualification across employees and independents, with people keeping the final decision. It is meant to support the discipline described here, not replace it.

Explore Talent OS, currently in Early Access, or book a 30-minute diagnostic call.