How to Monitor Enumerator Performance

Enumerator performance monitoring is the practice of reviewing each field interviewer's productivity, timing, and data quality while collection is running. The ODK audit log can record an enumerator identity when identify-user=true. Current DataSnap reports do not provide per-enumerator rankings or performance breakdowns.

Use DataSnap to review study-level activity and interview-level evidence, then compare relevant interview details with assignment or roster records when an individual follow-up is needed.

For the full fieldwork quality process, including form preparation and post-fieldwork documentation, see the ODK Field Data Quality Toolkit.

The goal is to catch problems on day one, not at endline. An enumerator whose results raise concern in week one can be reviewed and retrained if needed; waiting until fieldwork ends can make verification and corrective collection costly.

What enumerator metrics should you monitor?

Strong monitoring combines productivity, quality, assignment, and field-context evidence. The following are supervision metrics a team may calculate from its source and operational records; they are not all current DataSnap report sections.

Metric	What it measures	Watch for
Interviews completed	Daily output per enumerator	Results outside the planned workload
Median interview duration	Time spent per interview	Durations far below the team median
Answer-edit rate	Share of answers changed in source audit data	Results outside the form's expected correction pattern
GPS coverage	Spread of interview locations	Clustering at one point requires context and review
Time-of-day pattern	When interviews happen	Overnight or batched timestamps suggest backdating
Completion rate	Finished vs abandoned forms	High abandonment signals form or training issues

A useful supervision comparison is duration versus output. An interviewer with unusually high output and short durations is not automatically a top performer or a problem; the pattern warrants study-context review.

How to monitor enumerator performance with DataSnap

Step 1: Tag every interview with its enumerator

Enable identify-user=true in your XLSForm audit row so each submission carries the enumerator's ODK username:

type	name	parameters
audit	audit	track-changes=true identify-user=true location-priority=balanced location-min-interval=60 location-max-age=120

◀ ▶surveychoicessettings+

Without identify-user, you can see aggregate quality but cannot attribute it to individuals. For the full parameter reference, see ODK Audit Log: What It Tracks.

Step 2: Review performance in DataSnap

Export audit.csv from ODK Central and upload it to a DataSnap report. DataSnap renders the available study-level and interview-level evidence; it does not create an enumerator leaderboard.

For the public workflow and its review limits, see DataSnap reports. These comparisons are signals for human review, not automatic conclusions; interpret them against the form, field protocol, geography, and study context.

• Overview — total interviews, average and median duration, flagged interviews, and active days.
• Surveys per day — review interview volume over the collection period.
• Daily time-use heatmap — review when recorded interview activity occurred.
• Time by group or variable — summarize timing using an available report variable.
• Question friction, flagged interviews, and interview details — identify records that deserve contextual review.
• Survey concentration map — review recorded locations only when the source contains usable GPS evidence.

Turn monitoring into action

Monitoring only improves data if you close the loop with the field team:

1. Define review rules up front. Document plausible interview times, workloads, locations, and escalation steps for the study.
2. Review on a regular fieldwork cadence. Use the report's activity, time, question-friction, flag, and interview-detail sections to choose records for review.
3. Compare with operational records. Match relevant interview details to assignments and field context before contacting an enumerator.
4. Verify before acting. Back-check a sample, discuss context with supervisors, and document the evidence behind any retraining or corrective decision.

For the fraud-specific signals behind these checks, see How to Detect Curbstoning in Surveys.

Check my data quality free

Next: ODK Audit Log Explained →