Advanced KoboToolbox Applications Training Course

Participants can structure maintainable XLSForms and control form versions through release cycles.

• XLSForm workbook structure: survey, choices, settings and external sheet roles
• Question types selected for categorical, numeric, text, geospatial and media data
• Names, labels, hints and appearances follow maintainable field naming conventions
• Settings define form identifier, version, default language and submission metadata
• XLSForm syntax checks prevent deployment failures and ambiguous field behavior
• Version control records changes, owners, test status and release dates

Participants can build reliable form logic that controls respondent pathways and validates entries.

• Relevance expressions implement branching with selected(), comparisons and boolean operators
• Required logic distinguishes mandatory responses from conditionally applicable questions
• Constraint expressions enforce ranges, dates, formats and cross-field consistency
• Constraint messages explain corrective action using respondent-safe language
• Calculation fields derive ages, durations, totals and indicator components
• Boolean precedence and blank-value handling prevent unintended form paths

Participants can model one-to-many data structures using repeat groups and linked identifiers.

• Repeat groups capture household members, commodities, facilities and event histories
• Nested repeats model distributions linked to sites, teams or beneficiaries
• Indexed-repeat functions retrieve selected values from repeated records
• repeat_count controls roster size while preserving enumerator verification
• Position(), count() and indexed-repeat() support repeat-level calculations and validations
• Child-record identifiers maintain parent-child relationships during export and analysis

Participants can connect forms to controlled reference datasets for accurate field selection and validation.

• External CSV files supply controlled beneficiary, facility and commodity reference lists
• search() appearance filters large lists using indexed external datasets
• Cascading selects apply choice_filter expressions for geographic and programme hierarchies
• Pulldata() retrieves reference attributes for validation and calculated labels
• List update procedures protect identifiers, encoding and lookup field integrity
• Offline lookup design balances device storage, update frequency and enumerator usability

Participants can prepare and test multilingual Kobo forms while preserving logic and meaning.

• Translation columns manage labels, hints, messages and choice text
• Default language settings control opening language and enumerator switching
• Language-neutral variable names preserve calculations across translated versions
• Terminology review checks technical terms, sensitive wording and local comprehension
• Right-to-left scripts, Unicode characters and font rendering receive device testing
• Translation change logs reconcile edits before controlled deployment

Participants can test advanced forms systematically and approve releases using documented evidence.

• Questionnaire review applies cognitive testing, field piloting and issue classification
• Test cases cover paths, constraints, calculations, repeats and language variants
• Boundary-value testing probes minimums, maximums, blanks and invalid formats
• Device test matrices compare Android versions, browsers and connectivity conditions
• Defect logs assign severity, owner, reproduction steps and resolution evidence
• Release criteria require signed form approval before production deployment

Participants can configure Kobo projects and manage safe form deployment across field teams.

• Project settings control data access, form visibility and submission permissions
• Collector account provisioning applies least-privilege roles and removal procedures
• Form lifecycle management separates draft, test, pilot and production assets
• Deployment checklists confirm server, devices, translations, reference files and contacts
• Versioned releases preserve submission continuity when forms require amendment
• Rollback plans define response actions for critical instrument defects

Participants can prepare Android devices and field protocols for dependable offline data collection.

• KoboCollect configuration sets server URLs, credentials, blank forms and updates
• Offline-first protocols schedule downloads, completed-form storage and synchronization windows
• Android permissions govern location, camera, storage and microphone capture
• Device readiness checks cover battery health, date settings and available storage
• Enumerator job aids standardize login, form refresh and submission confirmation
• Field support escalation records incident type, device identifier and resolution

Participants can configure location and evidence capture while managing associated protection risks.

• GPS questions capture points, accuracy, altitude and collection timestamps
• Geofencing rules compare submitted coordinates against assigned operational areas
• Photos, audio and signatures document service delivery and verification evidence
• Barcode and QR scanning reduce transcription errors for assets and vouchers
• Metadata review identifies enumerator patterns, duration anomalies and device irregularities
• Sensitive media protocols define consent, encryption, access and deletion schedules

Participants can monitor collection progress and direct corrective action using fieldwork evidence.

• Submission dashboards track targets, completion rates, timeliness and enumerator workloads
• Daily review routines classify missing, late, duplicate and suspect submissions
• Paradata analysis uses timestamps, duration, GPS and device metadata
• Quality flags prioritize follow-up using predefined thresholds and exception rules
• Supervisor feedback loops document corrections, retraining actions and closure dates
• Response-rate calculations distinguish eligible cases, refusals, ineligibility and noncontact

Participants can apply practical data-protection controls to KoboToolbox collection and sharing processes.

• Data minimisation removes fields not required for monitoring decisions
• Informed-consent scripts record purpose, voluntariness, risks and withdrawal options
• Personally identifiable information receives role-based access and retention controls
• Data protection impact assessments identify harms, safeguards and residual risks
• Secure sharing procedures apply encryption, access expiry and recipient agreements
• Incident response plans define containment, notification, investigation and remediation

Participants can create documented, analysis-ready datasets from KoboToolbox submission exports.

• Export structures distinguish wide submissions, repeat tables and attachment files
• Unique identifiers support deduplication, correction tracking and longitudinal matching
• Cleaning rules detect impossible values, inconsistent records and missing disaggregations
• Codebooks document variables, labels, values, derivations and data limitations
• Correction logs preserve original values, rationale, editor and timestamp
• Data quality reports summarize completeness, validity, consistency, timeliness and uniqueness

Participants can retrieve KoboToolbox data and metadata through controlled API requests.

• KoboToolbox API endpoints retrieve assets, submissions, files and project metadata
• Authentication tokens protect scripted access and require secure storage
• Query parameters filter submissions by date, status and modified records
• Pagination patterns retrieve large submission sets without incomplete extracts
• JSON response structures map fields, repeats and attachments for downstream processing
• API error handling records status codes, retries and failed requests

Participants can specify repeatable data-refresh workflows for routine monitoring and reporting.

• Scheduled exports produce controlled datasets for recurring indicator reporting
• Incremental extraction uses modification timestamps to reduce duplicate processing
• Data refresh specifications define source, frequency, owner and validation checks
• File naming conventions identify project, form version, date and status
• Automated quality alerts trigger when thresholds breach predefined tolerances
• Reproducible workflows separate raw, cleaned, analysis-ready and published datasets

Participants can prepare Kobo datasets for exchange with management information and reporting systems.

• Field names and identifiers align Kobo datasets with MIS data dictionaries
• Data exchange mappings reconcile Kobo choices with partner coding schemes
• DHIS2 import preparation structures aggregate indicators, periods and organisation units
• Humanitarian Exchange Language tags improve dataset discovery and reuse
• Interoperability specifications document keys, transformations, ownership and update schedules
• Master data governance prevents conflicting facility, location and beneficiary identifiers

Participants can convert Kobo data into credible indicator findings and decision-focused reports.

• Indicator calculation plans link numerator records, denominators and disaggregation rules
• Pivot tables summarize coverage, outputs and data-quality exceptions by location
• Disaggregation analysis tests sex, age, disability and geographic equity patterns
• Trend charts distinguish reporting changes from plausible programme performance shifts
• Confidence notes communicate denominator limits, missing data and interpretation cautions
• Decision briefs connect findings, actions, owners and review dates

Participants can select KoboToolbox architectures suited to common development and humanitarian monitoring cases.

• Cash and voucher monitoring forms reconcile distribution, redemption and complaints data
• Health facility assessments combine readiness scores, inventories and geolocated evidence
• Protection data collection applies safe wording, referral limits and access restrictions
• Education monitoring tracks attendance, materials, teacher support and infrastructure defects
• Rapid needs assessments prioritize essential questions under time and connectivity constraints
• Case selection matches Kobo architecture to programme risk and reporting needs

Participants can establish governance arrangements that support consistent KoboToolbox use across programmes.

• Standard operating procedures define form ownership, approvals, deployment and archival
• Data management plans assign stewardship, retention, access and disposal responsibilities
• Form catalogues record purpose, indicators, languages, versions and active status
• Change-control boards assess requested modifications against reporting and comparability impacts
• Training plans specify enumerator certification, refresher triggers and supervisor coaching
• Post-collection reviews convert recurring defects into form and process improvements

Participants can build, review and present a complete KoboToolbox monitoring solution for a defined operational case.

• Capstone brief selects a monitoring problem, users, indicators and operational constraints
• Requirements translate into an XLSForm specification, data-flow map and governance controls
• Complete Kobo form incorporates logic, repeats, validation, media and reference data
• Test evidence documents paths, edge cases, defects and release decisions
• Data management package defines exports, cleaning rules, access and reporting outputs
• Peer review assesses usability, data quality, protection and implementation feasibility
• Presentation defends design choices, field procedures and decision-use outputs