Source-to-report handoff
Teams can connect recruitment sources to interpretation outputs without leaking participant-level stories.
External Recruitment Integration
Connect external recruitment to your study.
Connect participant sourcing and completion records while preserving consent and access boundaries.
- Integrate external recruitment with clean governance boundaries
- Reconcile completion without exposing participant narratives
- Preserve source provenance for quality and audit review
See the experience
External sourcing with clear consent and handoffs.
Recruitment access controls
Keep responsibilities and access clear when several recruitment sources are used.
Multi-source coordination
Programs can coordinate panel, partner, and internal sourcing without collapsing boundaries.
How pricing works
Availability and pricing
ERI is a Project add-on for external recruitment.
- Priced as an add-on rather than included in lower bounded offers.
- Typically scoped from a base integration level upward.
- Used when source attribution and recruitment governance matter.
When not to add it
Skip ERI when internal sourcing, direct invitation, or continuity infrastructure is already enough for the work.
- Not needed when you already have the right participant reach.
- Not a promise of response volume or provider performance.
- Not the first step for bounded self-serve offers.
Why teams use ERI
Cleaner operational handoff
Keep recruiter operations and sensemaking operations aligned without overlap confusion.
- Clarify who owns sourcing versus interpretation
- Reduce handoff friction across teams
- Support reliable completion reconciliation
Better source accountability
Track source-level provenance so teams can review quality and comparability across recruitment sources.
- Maintain source and batch traceability
- Compare recruitment sources responsibly
- Support repeatable quality checks
Lower delivery risk
Use explicit data boundaries so integration remains defensible for legal, procurement, and ethics review.
- Reduce accidental over-collection
- Protect participant privacy boundaries
- Preserve audit-friendly records
Where it fits best
Market research firms and panel providers
Use it when: When client delivery requires a clear bridge from recruitment operations to governed interpretation.
Value: Improves delivery clarity without exposing participant narratives.
Public engagement and consultation teams
Use it when: When external sourcing supports broad participation and accountability requirements are high.
Value: Supports wider participation with better boundary control.
Enterprise multi-vendor programs
Use it when: When multiple recruitment sources must feed one decision process with traceable provenance.
Value: Creates a cleaner path for cross-source governance and review.
What this enables
What it can add
- A clearer sourcing and integration boundary model
- A more reliable completion and reconciliation flow
- Clear responsibilities when recruiting through external providers
How teams usually bring it in
- Decide whether outside recruitment is actually needed
- Agree the integration and completion checks first
- Bring ERI in once sourcing, handoff, and review boundaries are clear
Data boundary essentials
Allowed metadata
- Project-scoped source and batch tags
- Pseudonymous keys for reconciliation
- Categorical metadata needed for delivery quality checks
Not allowed
- Direct participant contact details stored inside ERI flows
- Free-text personal identifiers in operational metadata
- Recruiter browsing of participant stories or interpretation details