Skip to main content
Plan this 45-minute session around two weeks after the analytics walkthrough, once you have used the findings. Bring the delivered report or deck, the original research decision, stakeholder feedback and an idea or questionnaire for the next study. Review open actions from coding, launch and analytics.

Plan the review

Use specific examples from upload, coding, collaboration, testing, launch and analysis. Separate product issues from research-design or sample limitations. Give each unresolved issue an owner and a next update.
Check the actual content permissions and remaining expiry before sharing.

Check the actual content permissions and remaining expiry before sharing.

Before you start

Bring the delivered files, final sample, fieldwork notes, and access list after findings have been shared.

Review the sample

Compare the planned and achieved sample. Focus on the subgroups that appeared in the final conclusions, including any that were not central in the original plan. Ask:
  • Did each reported subgroup have a sufficient unweighted base?
  • Did screening produce the intended audience?
  • Did quotas fill as planned, and where did they constrain collection?
  • Did weighting correct a known imbalance without excessive variance?
  • Which completed responses were excluded, and why?
Save the final bases and weighting source with the project record.

Review the questionnaire

Use response distributions, open-text answers, abandonment points, and participant feedback to identify improvements. Note questions that:
  • Were interpreted inconsistently
  • Produced options with little or no use
  • Needed an option that was missing
  • Repeated information already collected
  • Appeared too early or too late
  • Created avoidable routing complexity
  • Were difficult to answer on mobile or with media
Do not edit a completed study as a template without preserving the final fielded version. Create the next study separately and apply the documented changes there.

Review the analysis claims

Take the main statements from the report or deck and trace each one to its chart or source answers. Confirm that:
  • Wording matches the population and sample actually studied
  • Differences are supported by the base and, where relevant, significance tests
  • Weighting is disclosed where it affects interpretation
  • Open-text examples represent a theme rather than an isolated response
  • Recommendations are clearly separated from measured findings
If analysis was refreshed after new responses, check the charts in your story folders, slides and exports too; a plan run does not change them.

Review access and delivery

Revisit the sharing and comments introduced during coding. Organization account types and study/folder access are distinct: Researcher or Collaborator membership alone does not grant access to existing studies. Confirm that workspace membership and study access match current responsibilities. Disable guest links that are no longer needed, extend only those still in use, and check what each active link exposes. Open an active guest link in a private window to verify enabled tabs, result depth, expiry and commenting where available. Store the appropriate final deliverables:
  • PowerPoint for an editable presentation
  • Excel for numeric charts and crosstabs
  • Response-level Excel only where access to participant data is justified

Start the next study with a change log

Create a short list with three headings: Keep, Change, and Investigate. Use it during the next brief and test cycle. This makes the completed study a practical input to the next one instead of relying on memory. Then drive the next setup yourself while Customer Success observes. With a questionnaire ready, open New study → Recreate a questionnaire and explain how you will review, share, check coverage and test. Without a source file yet, locate that route and identify the materials and steps you need. Explain your launch checks and when provider redirects need attention. Record any gap and agree a focused follow-up; independence is only confirmed once demonstrated.

Confirm the support path

Open FIN AI in the in-product support chat yourself. Use the same conversation for product questions and help from the team, and say when you remain blocked. Confirm specifically agreed follow-ups without assuming a standing series of extra calls or a fixed response time.

Check the result

Feedback and Keep, Change, and Investigate decisions are recorded. Deliverables and access have been checked; remaining actions have owners. Record whether independent setup was demonstrated or still needs checking. Finish onboarding when the agreed outcomes are complete, with unresolved support or product issues still owned. Review personal-data retention, outstanding rewards and copies of exported data as part of the handover. Confirm which guest links and campaign access remain needed.