Research operations workshop / 5 MIN READ
Check the recruiter’s handoff before the first session
Translate the research need into verifiable recruitment instructions and acceptance checks.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A recruiting supplier can fill a calendar while still delivering the wrong experience mix. The research team must review how criteria became questions and how exceptions will be handled.
What you will leave with: A supplier handoff checklist covering screening, participant communications and replacement decisions.
Use this when
- An external recruiter supplies participants.
- The team discovers screening mismatches only after interviews start.
This is not a guide to excluding people by stereotypes or a claim that a recruited qualitative sample represents a population.
Describe qualifying experience in observable terms
GOV.UK recommends a written recruitment brief and checking the agency’s resulting screener. The important operational step is to inspect the translation between the two.
Specify relevant recent activities rather than relying only on job titles. “Has personally approved a supplier invoice” identifies experience more clearly than “finance decision-maker.” Separate essential criteria from useful variety, and explain why each matters to the research question. Do not collect private details simply because the recruiter has a standard field for them. State what evidence of experience is reasonable without demanding confidential documents.
Read the screener as a participant would
Check the order and wording of questions for clues that reveal the desired answer. An obvious product pitch can encourage people to present themselves as ideal users. Ask how the supplier verifies ambiguous responses and what it does when someone is unsure.
Review automatic exclusions, quotas and definitions against your brief. A default agency rule may remove relevant people without anyone noticing. Run through contrasting fictional profiles and see where each lands. Record any changes in one approved version so the recruiter does not mix instructions from an email thread, call and old attachment.
Agree the operational boundary
Document who sends invitations, provides session information, handles incentives and answers participant questions. Specify what contact data is shared, by which route and for how long it is needed. Participants should not receive conflicting instructions from the recruiter and research team.
Agree a mismatch procedure before sessions start. A researcher should be able to pause and contact the supplier without accusing the participant of dishonesty. Distinguish an administrative error, an ambiguous criterion and a genuinely unsuitable session. Decide replacement terms with the supplier, but do not make participants absorb the cost of a confusing brief or broken technology.
Accept a handoff, not just a list of names
Request a privacy-conscious roster showing the criteria needed to prepare each session, the status of participant communications and any unresolved exceptions. Review it early enough to correct issues. Avoid asking for complete screening transcripts when a minimal summary will do.
After the first session, compare the actual experience with the intended criteria and tell the supplier about any systematic ambiguity. Keep changes explicit so later participants are not silently recruited under a different definition. At closure, reconcile fulfillment, outstanding participant queries and the approved handling of recruitment records.
Make the reasoning concrete.
A fictional industrial software company asks for people who “manage maintenance.” The supplier recruits senior managers who approve budgets but never use work-order systems.
Accept the job-title match
Opening: Proceed with the planned operator workflow sessions.
Hypothesis: The roster resembles the original brief.
Risk: Participants cannot speak to the hands-on task the study concerns.
Repair the criterion
Opening: Specify direct responsibility for creating or closing work orders and review the revised screener.
Hypothesis: Observable experience better matches the session task.
Risk: The schedule may need adjustment, and budget approvers belong in a different study.
The team takes responsibility for its ambiguous brief, agrees revised criteria and keeps any useful budget-governance questions separate from the operator sessions.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Essential experience
What has the participant actually done that makes the session relevant?
Translation
How does each screener question implement the brief?
Exception
What happens when experience is ambiguous or a mismatch appears?
Data boundary
Which minimal roster details does the research team need?
Acceptance
Who confirms the handoff before the session begins?
Watch for the wrong conclusion.
- Using broad job titles as proof of task experience.
- Assuming the supplier’s standard exclusions fit every study.
- Blaming participants for ambiguity in the recruitment brief.
Your next action
Review one supplier screener against its brief and flag a question that could recruit the wrong experience despite a plausible answer.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- GOV.UK Service Manual: Write a recruitment brief →Primary government research guidance · Supports: A written agency brief and review of its screener help align recruitment with study requirements; the supplier controls are original analysis.