On this page
- Start with the decision, not the topic
- Frame the question precisely
- Scope, exclusions and depth
- Sources to use and avoid
- Specify the output format with an example
- Agree checkpoints, not just a deadline
- How quality will be checked
- Common briefing mistakes
- Protecting confidential research
- Building a long-term research relationship
- A brief template you can reuse
- ✓Start the brief with the decision the research will inform, not the topic.
- ✓Define scope, sources, depth and what is out of bounds before work starts.
- ✓Specify the output format and a worked example so the deliverable is usable without rework.
- ✓Agree checkpoints and quality checks, and give feedback after every delivery.
The short answer: A good research brief states the decision the work will support, the precise question, the scope and exclusions, the sources to use and avoid, the depth and time budget, the output format with an example, the deadline and checkpoints, and how quality will be checked. Briefs written this way get decision-ready output from external researchers on the first pass instead of the third. Teams that use research outsourcing regularly keep a brief template and improve it after each project.
Start with the decision, not the topic
The most common reason outsourced research disappoints is that the brief describes a topic, not a decision. “Research the European payments market” could produce a hundred pages that answer nothing. “We are deciding whether to enter Germany or the Netherlands first with our payment product; compare the two on market size, competition, regulation and partner options” produces something useful.
Writing the decision first forces clarity about what matters. It also lets the research team make sensible choices when they find something unexpected, because they know what the work is for. Every brief should open with one or two sentences on the decision and who will make it.
Frame the question precisely
After the decision, state the research question or questions as precisely as possible. Good questions are specific, answerable and limited in number. Break large questions into sub-questions, and say which are essential and which are nice to have. If there are hypotheses the team already holds, share them and ask the researchers to test them rather than ignore them.
Define key terms. “Mid-sized company” or “active user” can mean different things to different people. A short definitions section prevents researchers from building their work on different assumptions from yours.
Scope, exclusions and depth
State what is in scope: geographies, time periods, segments, competitors and product categories. State what is out of scope just as clearly, because researchers will otherwise follow interesting leads. Set the depth: a quick scan of published sources is very different from a detailed analysis with primary interviews.
Give a time or effort budget. Research expands to fill available time, and a budget helps the team prioritize. If some questions deserve more effort than others, say so.
Sources to use and avoid
Tell researchers which sources you trust and which you do not. Many organizations have paid databases, industry reports or internal data that researchers should use, and sources they consider unreliable. Specify whether primary research, such as expert calls, customer interviews or surveys, is allowed and who approves it.
Ask for every claim to be sourced, with links or references, and for estimates to be clearly marked as estimates with their method shown. Source discipline is what makes research defensible when it reaches decision-makers. See information services and data operations for how data teams document sources at scale.
Specify the output format with an example
Describe exactly what you want back: a one-page summary with recommendations, a comparison table, a slide deck, a spreadsheet model, a memo with appendices. Better still, share an example of a past deliverable you liked, or a blank template. Format decides whether the output can be used immediately or needs rework.
Ask for an executive summary that answers the decision question directly, followed by supporting evidence. Busy decision-makers read the first page; everything else exists to support it.
Agree checkpoints, not just a deadline
For anything longer than a few days, agree an early checkpoint where the researchers share their approach, initial sources and any problems with scope. A short call at this stage prevents a week of work in the wrong direction. A second checkpoint with draft findings lets you redirect before the final deliverable.
Name one person on your side who answers questions quickly. Research stalls when questions sit unanswered.
How quality will be checked
Say how you will judge the work: accuracy of sourced facts, logic of the analysis, clarity of recommendations and fit to format. Ask the research team to run their own checks before delivery, such as a second analyst reviewing sources and calculations.
After delivery, give specific feedback: what was useful, what was missing and what to do differently next time. Feedback compounds; a team that receives it after every project gets better quickly. See data analytics for reporting and analysis programs that use the same discipline.
Common briefing mistakes
The most common mistakes are asking for everything at once, leaving the decision unstated, not defining terms, failing to mention sources the team already has and not saying how the output will be used. Another is changing the question halfway through without updating the brief, which leaves researchers working toward a target that has moved.
A brief is a living document during the project. When scope or priorities change, update it, date the change and tell the team. Keeping the brief current is how both sides stay aligned.
Protecting confidential research
Research often touches sensitive plans: market entry, acquisitions, pricing and product strategy. Briefs should say what can be shared with researchers, how confidential documents will be provided and whether the client’s name may be used in primary research. Expert calls and surveys need rules on what researchers may disclose about the purpose.
External teams should work under confidentiality agreements, with access limited to people on the project. See the confidentiality questions clients ask professional firms for the controls clients expect.
Building a long-term research relationship
Teams that use the same researchers over many projects build shared context: the client’s industry, preferred sources, writing style and decision patterns. Each brief gets shorter and each delivery better. Keeping a short project log of what worked and what did not makes that knowledge durable even when individuals change.
A brief template you can reuse
A reusable template covers: the decision and decision-maker, research questions in priority order, definitions, scope and exclusions, depth and time budget, sources to use and avoid, primary research rules, output format and example, deadline and checkpoints, quality checks and the contact for questions. Filling it in takes an hour and saves days.
Our research outsourcing page explains how vetted Philippine research teams work from briefs like this for consultancies, investors and corporate strategy teams, and the confidentiality questions clients ask professional firms covers how sensitive research is protected.
Frequently asked questions
What should a research brief include?
The decision the research supports, precise questions, definitions, scope and exclusions, depth and budget, sources, output format, deadline, checkpoints and quality checks.
Why does outsourced research often miss the mark?
Usually because the brief describes a topic instead of a decision, leaves scope open or does not specify the output format.
Should researchers use primary research?
Only if the brief allows it and the method, such as expert calls or surveys, is approved in advance.
How long should a research brief be?
Often one to two pages is enough when it covers the decision, questions, scope, sources, format and checks clearly.
