Enumerator Training Checklist for Field Surveys
Good enumerator training covers five blocks: device and app skills, question-by-question form practice, consent and ethics protocol, data quality procedures including GPS capture, and supervised mock interviews with a certification gate. Two to three days is the realistic minimum for a substantive questionnaire — and the cheapest data quality investment you will make.
Every hour spent training costs less than the same hour spent re-collecting bad data. Here is the checklist we recommend for ODK-based fieldwork.
Use the ODK Collect offline workflow checklist to rehearse the device-to-server path before the team starts fieldwork.
Block 1: Devices and ODK Collect
- Every enumerator can charge, unlock, and manage storage on their assigned device.
- ODK Collect is configured on each device by scanning the project QR code — done together, in the room.
- Everyone has downloaded the form, completed a practice submission, and watched it reach the server.
- Offline behavior is demonstrated: airplane mode on, interview completed, sync on reconnect — so nobody panics in the field.
- Common failure drills: what to do when submissions won't send, the battery dies mid-interview, or the form needs updating.
Block 2: The questionnaire, question by question
- Walk the entire form aloud, including every skip path — enumerators must know why questions appear and disappear.
- Explain each constraint and its error message so a rejected answer doesn't become a guessing game (constraint examples help here).
- Standardize probing: what counts as "don't know", how to handle refusals, how to record "other".
- Translate ambiguous terms into local-language phrasings as a group, and write the agreed phrasings down.
Block 3: Consent and ethics
- Informed consent is rehearsed verbatim until it sounds natural, not recited.
- Refusal handling is explicit: a refusal is recorded and respected, never argued with.
- Confidentiality rules cover the device too: no screenshots, no showing screens to bystanders, screen lock mandatory.
Block 4: Data quality procedures
- GPS capture protocol: where to stand, how to capture an accurate point, and never capturing from inside a vehicle.
- Interview pacing expectations: rushing flags an interview for review.
- The monitoring briefing. Tell enumerators, plainly, that the audit log records timing, GPS, and answer changes for every interview, and that supervisors review per-enumerator dashboards daily.
The monitoring briefing is the highest-leverage item on this page. Most curbstoning is opportunistic — enumerators who know that duration and GPS are checked daily rarely attempt it. Deterrence is cheaper than detection.
Block 5: Mock interviews and certification
- Paired role-play: every enumerator completes at least three full mock interviews as interviewer.
- A field pilot with real (non-sample) respondents, reviewed the same day.
- A certification gate: a written or practical test that each enumerator must pass before receiving a field assignment. Re-train, don't wave through.
- Review the pilot data together in DataSnap — durations, GPS spread, error rates — so the team sees exactly what supervisors will see during fieldwork.
After training: the first week is part of training
Certification doesn't end the training; the first field week does. Review every enumerator's duration, GPS, and submission patterns daily for the first week, and call same-day about anomalies — early correction is coaching, late correction is data loss.
The bottom line
Train on the form, rehearse the ethics, drill the failure modes, and tell the team exactly how they will be monitored. A certification gate plus a daily-review first week catches nearly every problem while it is still fixable.
Check my data quality freeNext: The survey data quality checklist →
Frequently Asked Questions
How long should enumerator training take?
Two to three days minimum for a substantive questionnaire: one day on devices and the form, one on ethics and data quality procedures, and one on mock interviews and certification. Complex or sensitive surveys justify a full week plus a supervised pilot.
What should enumerator training cover?
Five blocks: device and ODK Collect skills, question-by-question form practice including skip logic and constraints, informed consent protocol, data quality procedures like GPS capture, and supervised mock interviews ending in a certification test before field assignment.
How do you prevent enumerator fraud?
Deterrence plus detection: tell enumerators during training that the audit log records timing, GPS, and answer changes for every interview, then actually review per-enumerator dashboards daily. Opportunistic curbstoning drops sharply when monitoring is known and visible.
Should enumerators be certified before fieldwork?
Yes. A pass-or-retrain certification gate — a practical test after mock interviews — is the single best predictor of field data quality. Enumerators who cannot complete a clean practice interview will not produce clean real interviews under field pressure.
What is a mock interview in survey training?
A full practice interview conducted in pairs during training, with one trainee as interviewer and one as respondent, using the real form on the real device. Each enumerator should complete at least three before a field pilot with non-sample respondents.
What should supervisors monitor in the first week of fieldwork?
Interview durations, GPS locations, and submissions per enumerator per day, reviewed the same day. The first week functions as an extension of training: anomalies caught early are coaching opportunities, while anomalies found late are usually lost data.
No Credit Card Required
Build the form first. Add hosting when you need it.
Start free with LooprAI, then deploy a managed ODK Central server or run DataSnap checks when your project is ready.
Automation handles the mechanical work.
Researchers decide what the evidence means.