ODK and KoboToolbox for Monitoring and Evaluation Training Course

Participants can select appropriate ODK and KoboToolbox components for a field-data workflow.

• ODK ecosystem components: Collect, Central, XLSForm, and Enketo
• KoboToolbox project structure, assets, permissions, and deployment settings
• KoboCollect and ODK Collect mobile application capabilities
• Offline-first data collection for low-connectivity field locations
• Server-hosted versus cloud-hosted project administration considerations
• Form lifecycle from design through retirement and archival

Participants can translate indicators and information needs into well-structured mobile questions.

• Indicator-to-question mapping using a structured data collection matrix
• Question wording that reduces ambiguity, recall bias, and interviewer influence
• Response formats matched to categorical, numeric, date, and text data
• Disaggregation fields for sex, age, disability, location, and vulnerability
• Recall periods specified consistently within monitoring and survey questions
• Enumerator guidance notes separated from respondent-facing question labels

Participants can build a basic XLSForm using survey, choices and settings worksheets.

• XLSForm workbook structure: survey, choices, and settings worksheets
• Question types including select_one, select_multiple, integer, decimal, and date
• Choice lists coded with stable names and readable labels
• Form settings for title, form_id, version, and default language
• Required fields configured without forcing inappropriate respondent disclosure
• Column naming conventions supporting analysis, integration, and version control

Participants can create and publish a basic monitoring form in KoboToolbox.

• KoboToolbox form builder compared with XLSForm import workflows
• Projects created with descriptive titles, ownership, and access permissions
• Monitoring questions arranged into logical sections and respondent flows
• Form preview used to inspect labels, response options, and instructions
• Draft forms deployed only after structured design review
• Test submissions reviewed through KoboToolbox table and report views

Participants can configure conditional questions that present only relevant fields.

• Relevant expressions controlling question display through response conditions
• Skip patterns designed from respondent pathways and eligibility criteria
• Boolean operators: and, or, equals, not equals, and selected
• Grouped questions hidden when preceding screening conditions fail
• Eligibility screening documented separately from programme participation decisions
• Logic paths tested for positive, negative, and missing-response scenarios

Participants can prevent common entry errors through field-level validation rules.

• Constraint expressions limiting numeric values to plausible measurement ranges
• Date validation preventing future dates and inconsistent reporting periods
• Regular expressions checking telephone numbers, codes, and identity formats
• Constraint messages written as specific instructions for enumerators
• Requiredness rules distinguished from legitimate non-response options
• Range checks aligned with indicator definitions and operational thresholds

Participants can create calculated fields that support validation and monitoring analysis.

• Calculate fields generating age from date of birth
• Arithmetic expressions deriving household totals, scores, and percentages
• Today() and now() functions for time-stamped collection records
• Conditional calculations responding to selected eligibility and service categories
• Hidden fields used for metadata, case identifiers, and programme codes
• Derived indicators checked against manual calculations before deployment

Participants can model households, service contacts and repeated observations using groups and repeats.

• Groups organising questions into clear thematic and operational sections
• Field-list appearance presenting short interviewer-led question sequences
• Repeat groups capturing multiple household members or service visits
• Repeat counts controlled through prior numeric responses where appropriate
• Parent-child identifiers linking repeated records to primary submissions
• Nested repeat risks assessed before designing complex relational data structures

Participants can prepare multilingual forms that support accessible and consistent field administration.

• Language columns created for translated labels, hints, and messages
• Translation control using source-language identifiers and review logs
• Plain-language wording adapted for respondent comprehension and literacy
• Audio prompts considered for low-literacy and disability-inclusive collection
• Select choices checked for culturally appropriate and mutually exclusive labels
• Enumerators instructed on language selection and translated consent scripts

Participants can configure geographic, media and metadata fields proportionately and safely.

• Geopoint questions capturing latitude, longitude, altitude, and accuracy
• GPS accuracy thresholds considered before accepting location records
• Photo, audio, and file attachments governed by consent requirements
• Start, end, deviceid, and username metadata interpreted carefully
• Sensitive location data protected through access restrictions and retention rules
• Media collection justified against monitoring value and safeguarding risk

Participants can execute a structured test process before releasing a mobile form.

• Test cases covering eligibility, skip logic, constraints, repeats, and calculations
• Boundary-value testing for minimum, maximum, and invalid numeric entries
• User acceptance testing with enumerators using realistic respondent pathways
• Defect logs recording issue description, severity, owner, and resolution
• Version numbers updated after approved design changes
• Deployment readiness checklists confirming content, logic, permissions, and devices

Participants can prepare practical procedures for enumerators using mobile forms.

• Enumerator standard operating procedures for devices, forms, and submissions
• Informed consent scripts covering purpose, voluntariness, and data handling
• Device setup procedures for KoboCollect and ODK Collect
• Form download, offline completion, editing, and submission workflows
• Daily synchronisation routines for teams operating with intermittent connectivity
• Escalation routes for safeguarding concerns, technical faults, and suspected fraud

Participants can manage users, permissions, projects and form versions responsibly.

• Role-based access controls for project managers, enumerators, and analysts
• ODK Central app users, web users, and project permissions
• KoboToolbox sharing settings for collaborators and external data access
• Form versioning procedures protecting active field collection from disruption
• Submission editing policies aligned with audit and data-quality requirements
• Project archiving procedures preserving forms, exports, metadata, and documentation

Participants can identify and document data-quality issues in exported mobile datasets.

• KoboToolbox table views used for rapid submission review
• Export formats: XLSX, CSV, ZIP, and repeat-group tables
• Duplicate detection using unique identifiers, timestamps, and respondent details
• Completeness checks for required indicators and disaggregation fields
• Outlier review using range rules, logical consistency, and spot checks
• Data cleaning logs documenting corrections, exclusions, and outstanding queries

Participants can prepare mobile data for routine monitoring analysis and reporting.

• Analysis-ready datasets structured around indicators, periods, and disaggregation
• Codebooks documenting variable names, labels, values, and derived fields
• Data dictionaries maintained alongside approved form versions
• Indicator calculations reconciled with numerator, denominator, and target definitions
• Pivot tables summarising service delivery, coverage, and respondent feedback
• Reporting schedules linking field submission deadlines to management decisions

Participants can apply proportionate security and protection controls to mobile monitoring data.

• Data minimisation applied when selecting respondent identifiers and sensitive variables
• Personally identifiable information separated from analysis and reporting datasets
• Retention schedules defining deletion, archival, and access review requirements
• Device security controls including screen locks, updates, and secure storage
• Data breach procedures covering containment, notification, and incident records
• Risk assessments addressing harm from disclosure, loss, and unauthorised access

Participants can adapt mobile form design to common development and humanitarian monitoring requirements.

• Post-distribution monitoring forms measuring receipt, use, satisfaction, and protection concerns
• Beneficiary registration fields designed for verification and duplicate prevention
• Service supervision checklists recording standards, observations, and corrective actions
• Rapid needs assessments structured around household priorities and severity indicators
• Community feedback mechanisms recording complaints, referrals, and response status
• Partner monitoring forms aligning evidence requirements with grant reporting obligations

Participants can produce a practical plan for deploying and maintaining a mobile data collection system.

• Deployment plans defining scope, locations, dates, roles, and submission targets
• Enumerator allocation plans based on workload, language, and travel constraints
• Communication protocols for version releases, technical support, and field updates
• Data-quality monitoring dashboards specifying review frequency and responsible staff
• Contingency arrangements for connectivity failures, damaged devices, and incomplete submissions
• Handover documentation covering form ownership, administration, and maintenance procedures

Participants can build, review and present a complete mobile monitoring form package for a defined programme requirement.

• Programme scenario translated into indicators, respondent groups, and data requirements
• XLSForm built with sections, relevance logic, constraints, calculations, and repeats
• KoboToolbox or ODK project configured with appropriate user permissions
• Test submissions reviewed against predefined completeness and consistency criteria
• Deployment package assembled with consent text, enumerator guidance, and quality controls
• Peer review presentation explaining design choices, risks, and implementation decisions