Aglet

Verify Recruitment Coverage Before Using Findings

Verification asks whether a study recruited the people needed for its stated question. Review the sample against inclusion goals, task experience, and access arrangements. A study can be useful with a narrow scope, but its conclusions should match that scope precisely.

Check whether the outcome improved

  1. Set coverage checks

    List required contexts, user stages, access needs, and service roles. Define what counts as covered and what must be reported as missing. Include a check for self-selection or familiarity when those factors could change behavior.

  2. Review the actual sample

    Map every participant to the relevant context and record whether the session confirmed it. Compare intended and observed coverage, including people who dropped out or could not complete the planned task. Preserve deviations from the recruitment plan.

  3. Approve the evidence boundary

    State which questions the sample can answer and which require more recruitment. Record adaptations and limitations in the findings brief. Choose a follow-up owner when a missing group could change the recommendation.

What to carry forward

The verification record should show coverage checks, actual contexts, access support, deviations, and the evidence boundary. Use findings only for the population and questions the sample supports. Keep a recruitment follow-up when a missing context could reverse the decision.

Technical background: GOV.UK user research guidance.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow