Outlier Science
How a Research Consulting Engagement Works
A useful engagement begins with a clear question and ends with work the client can understand and use. The process below explains how an assignment can be scoped, reviewed and handed over, with responsibilities agreed before substantive work begins.
On this page 8 sections
FROM THE FIRST QUESTION TO HANDOVER
A clear process. Shared decisions.
The phases below connect to the full process guidance. Scope and responsibilities are agreed for each engagement.
Brief
Clarify the research objective and the information needed to assess the assignment.
Scope & prepare
Agree the activities, outputs, responsibilities and materials before substantive work.
Review & adapt
Use review points to make decisions and agree changes before adding work.
Hand over
Bring together the agreed outputs and explain how they can be used.
01
Describe the objective and the current stage
Start with the problem you need to solve or the decision you need to make. For an institution, explain the unit or function involved and the change you are considering. For a researcher, describe the question, study stage and type of material available.
The initial form asks for your name, email and message. An institution or organisation name is optional. You can mention a relevant deadline in the message, but there is no need to provide a complete technical specification.
An inquiry requests a discussion. It does not confirm a meeting, reserve capacity or create an obligation to purchase. Detailed files are not required at this stage.
02
Establish suitability and information needs
The scoping discussion should clarify the intended output, the expertise required and the information needed to assess the work. It can also identify whether the task is well defined or whether a diagnostic stage is necessary.
For example, a request for statistical analysis may first require a review of variable definitions and the study design. An institutional request to improve research reporting may need a data-quality review before a dashboard specification can be produced.
Where specialist or external input is required, the proposal should explain the role and any dependency. Data access, confidentiality, permissions and potential conflicts should be addressed before restricted material is shared.
This stage should also identify work outside the proposed scope. The client needs to know whether a recommendation, practical implementation or both are being considered.
03
Agree a written scope
The scope should define the objective, included activities, client inputs, deliverables and the evidence used to assess completion. It should also state the fee basis, timing assumptions and relevant third-party costs.
Review arrangements need similar clarity. Agree what the client will review, when feedback is expected and which revisions are included. A request to clarify an agreed output differs from introducing a new dataset, research question or institution-wide requirement.
For institutional engagements, identify an internal sponsor and the people authorised to approve scope, access and changes. Purchase orders, procurement steps or framework arrangements must be resolved before work is committed, where required.
For researcher assignments, clarify authorship or acknowledgement expectations, institution-specific limits and responsibility for final scholarly decisions. The written scope should reflect the actual work, not a vague promise of end-to-end support.
04
Prepare the project inputs
The client supplies the agreed material and confirms the necessary rights and permissions. Complete, well-described inputs make it easier to distinguish the task itself from additional preparation.
A research audit may need publication exports, organisational definitions and interviews. An analysis assignment may need a data dictionary, protocol and documented exclusions. A manuscript review may need the target journal instructions and a complete version of the manuscript.
The project should identify a working version of each file and a route for resolving questions. If important material is missing or changes during the assignment, the implications for scope and timing need to be discussed.
Sensitive information should be transferred only through an agreed, suitable route. Read the confidentiality guidance before providing unpublished research or participant-related material.
05
Review progress at meaningful points
Review points should support decisions rather than create reporting for its own sake. They can confirm an analysis plan, a set of institutional priorities, a draft procedure or a proposed equipment specification before more work depends on it.
For a longer programme, a concise progress record can show completed outputs, decisions required, dependencies and agreed changes. It should distinguish work delivered from outcomes that will be observed later.
Feedback is most useful when it is consolidated by the appropriate client lead. Conflicting instructions from several people can change the scope or delay a decision. The proposal should identify how those differences are resolved.
If the evidence changes the original plan, the next step should be explicit. A study may need a different analysis, or an institutional intervention may depend on a resource that is not available. The work should adapt through an agreed decision.
06
Manage changes before adding work
A change request should explain what has changed, why it matters and the implications for deliverables, responsibilities, timing and fees. The authorised parties then decide whether to proceed.
Illustrative example: an editing assignment covers one complete manuscript and an agreed revision round. If the author adds a new study and substantially rewrites the results, the revised material may require a new scope. The original agreement should not leave either party uncertain about that boundary.
For institutional work, a change may involve additional departments, more consultation or implementation beyond the initial recommendation. Recording the decision helps preserve a clear account of what the engagement includes.
07
Deliver and hand over the work
The handover should include the agreed outputs, an explanation of their use and any material limitations. It should identify items requiring client approval and the responsibilities that continue after delivery.
An analysis handover may include results, code where agreed and interpretation notes. An institutional handover may include procedures, an action plan and a measurement specification. A laboratory handover may identify confirmed requirements and unresolved technical dependencies.
Completion of the consulting work does not mean a journal has accepted a paper, a funder has awarded a grant or an institution has implemented every recommendation. Those outcomes should be tracked separately from delivery.
08
Choose the right form of engagement
A diagnostic audit, scoped project, workshop, programme or ongoing support arrangement can each suit a different need. The most useful choice depends on how well the problem is understood and how much connected work is required.
Tell us the objective and what would make the engagement useful to you. The next step is to turn that into a specific, reviewable proposal.