01
Instrument design
Structured instruments, not loose forms.
Build short checks or longer instruments with sections, validation, branching, and matrices.
LikertMultiSingleMatrixOpenNPSRankDateGeoFile+13Auto
01CollectEvidence arrives
Evidence arrives
with its context
intact.
Run structured forms, chat-style interviews, or voice collection from the same instrument. When fieldwork needs a CAPI layer, push to KoboToolbox or ODK Central, or export a validated XLSForm for SurveyCTO. Language, consent, skip logic, and respondent identity travel with every response from first contact.
heurista.i4di.org · study · collect
Collection workspace: multiple instruments, languages, consent, and release checks before launch.
What's inside Collect
Collection tools that preserve study structure.
Explore the tools for designing, localizing, and deploying a study while keeping consent, logic, and response records visible.
02
Response modes
Form, chat-style, or voice collection.
Choose the response mode that fits the study setting while keeping data in one study structure.
ChatVoiceForm
03
AI-assisted design
From brief to draft instrument.
Use AI to draft questions, sections, and response options from a research brief, then review before launch.
Midline Evaluation: WASH Nairobi.docx
Brief reviewed
Draft instrument outline ready for review
04
Logic & branching
Branching and validation.
Condition questions on prior answers, carry values forward, and validate responses with ranges or patterns.
05
Multi-language
Multilingual fieldwork support.
Manage study languages from one master instrument, with translations versioned and reviewable before launch.
ENFRESARSWPT中हिंTRRU+6
06
Consent management
Consent text, version-tracked.
Add consent screens, record accepted versions, and keep withdrawal paths documented in the study record.
07
Branding & theming
Your logo, colours, fonts.
Apply per-study visual settings so respondent-facing instruments match the organization or program identity.
Aa
08
Interview guardrails
Review follow-up behavior.
Check wording, consent flow, and follow-up prompts so collection stays aligned with the study protocol.
Follow-upsMax 2
ConsentLocked
TranscriptStored
09
CAPI interoperability
Use the field tool that fits the job.
Push to KoboToolbox or ODK Central by API, or export a validated XLSForm for SurveyCTO and other ODK-compatible systems.
Live pushKobo
Live pushODK Central
HandoffXLSForm
Inside Collect
The tools,in context.
heurista.ai · instrument design
Conversational records
Keep the session context available for review.
When a study uses chat-style or voice collection, transcripts and follow-up prompts stay available to the research team before analysis and reporting.
- Transcript linked to the session record
- Follow-up prompts visible for review
- Session notes available before coding
- Form, chat, and voice responses kept in one study context
SESSION 2014 · minute 07:42 Review
RESPONDENT
It got better, I think. The clinic is closer now.
HUE · follow-up
You said “better”. Could you give an example from the last month? What changed for you, specifically?
RESPONDENT
My son had a fever. Last year we would have walked four hours. Last Tuesday we got there in forty minutes.
REVIEW NOTE
Possible analysis note:
access → time-to-care. Researcher confirms during coding.Next stepCollected data moves
Collected data moves
into Analyze.
Responses, transcripts, and metadata remain connected to the study context so analysis can begin without reconstructing the evidence trail.
Continue →
Analyze
Next step
Plan collection around the study design.
Design instruments, set up consent, validate XLSForm handoff, and choose the collection path that fits your fieldwork.