Data Quality Safeguards in Panel Recruitment¶

Recruiting real respondents from outside your existing audience raises a fair concern: how do you know the people answering your survey are engaged, real respondents, rather than someone clicking through as fast as possible to collect a reward? Panel Recruitment has safeguards at two different points - before a participant ever reaches your survey, and while your wave is actually running.

Before a Respondent Reaches Your Survey¶

Every participant in the panel goes through the panel's own vetting process - dozens of quality checks - before they're even eligible to be recruited into any study, including yours. This isn't something you configure per wave; it's a baseline the panel applies to its whole participant pool, so you're not starting from an unvetted general population every time you launch.

Your own screening criteria add a second layer on top of that baseline - narrowing who's eligible for your specific study based on whatever combination of age, country, employment status, or other criteria your research actually needs, from 300+ available filters.

While a Wave Is Running¶

Automatic protection against unusually high drop-off. If an unusually high share of respondents start your survey and don't finish it, the wave pauses itself automatically, rather than continuing to recruit against whatever's causing the problem. This is a protective measure, not a judgment on your survey - it's often worth checking for something specific (a broken question, a screening mismatch, a survey that's running longer than expected) when it triggers, but the pause itself happens without you needing to be watching in real time.

Payment tied to genuine outcomes, not just participation. You're only charged for a submission that reaches approved or screened-out status - someone who starts and never finishes isn't charged at all, which removes any incentive structure that would reward incomplete or abandoned attempts.

Your Own Recourse If Something Still Looks Wrong¶

Data quality safeguards reduce how often a problem happens; they don't guarantee it never will. If a specific submission still looks suspect once it's in - a suspiciously fast completion time, answers that don't hang together, anything that reads as low-effort rather than genuine - there's no in-app way to reject it yourself, but you can file a report directly from the wave, flagged as suspected low-quality submissions, and platform staff follow up with the panel provider on your behalf.

What This Doesn't Replace¶

None of this is a substitute for your own survey design choices that affect data quality - attention-check questions, reasonable completion-time expectations built into your reward pricing, and a survey that isn't so long it invites rushing are still worth building in yourself, the same way they would be for any survey regardless of where the respondents come from.

FAQ¶

Can I add my own attention-check questions to a panel-recruited survey?
Yes - a Panel Recruitment wave runs against the same survey you'd build for anyone else, so any question type, including an attention check, works exactly the same way it would for any other respondent.

What happens to a submission flagged as suspected low-quality once I report it?
Platform staff review it with the panel provider directly - there's no in-app self-service resolution, by design, since individual submission review happens through the provider's own process rather than a second layer inside Opionate.

Does a high-return-rate pause affect submissions already collected before it triggered?
No - a pause only affects new recruitment going forward. Submissions already completed or in progress at the time it triggers are unaffected and still resolved normally.

See our Panel Recruitment FAQ for more on reporting a specific issue with a wave.