Mobile Data Collection Using CommCare Training Course

Participants can produce a build-ready specification for a CommCare data collection application.

• Stakeholder interviews structured around decisions, users, workflows and reporting needs
• Data collection specification covering forms, cases, users and outputs
• Process maps distinguishing registration, service delivery, referral and follow-up events
• Minimum dataset selection using indicator definitions and disaggregation requirements
• Field usability constraints documented for language, literacy, devices and connectivity
• Requirements traceability matrix linking indicators, questions, calculations and reports

Participants can design concise, field-ready questions and response options for mobile forms.

• Question wording techniques that reduce ambiguity, recall bias and interviewer variation
• Response formats selected for categorical, numeric, date and text data
• Standard answer lists designed with mutually exclusive response categories
• Required questions balanced against respondent burden and field workflow
• Mobile screen design using short labels, hints and logical sequencing
• Translation planning with source language, local terms and version control

Participants can create and organise functional CommCare forms using standard question types.

• Form Builder workspace, application menu and module structure orientation
• Text, numeric, date, single-select and multi-select question configuration
• Question labels, help text and default values for enumerator guidance
• Lookup tables used for controlled facilities, villages and service lists
• Form save settings and incomplete form recovery options
• Application menu ordering aligned with fieldworker task sequences

Participants can control question flow and prevent common data-entry errors.

• Skip logic configured through display conditions and relevance expressions
• Validation constraints applied to dates, ranges, identifiers and required combinations
• Calculation questions deriving ages, totals, scores and follow-up dates
• Conditional messages written to explain failed validation rules clearly
• Logic trees tested against expected respondent pathways and exceptions
• Hard stops and warning prompts chosen according to data-risk severity

Participants can build richer mobile forms for repeated observations and field evidence.

• Repeat groups configured for household members, commodities and service visits
• Group displays used to organise long forms into coherent sections
• Image, audio and signature capture configured with informed consent safeguards
• Barcode scanning applied to assets, vouchers and beneficiary documents
• Hidden values stored for metadata, calculations and workflow control
• Form completion timestamps and device metadata reviewed for supervision

Participants can design CommCare cases for tracking beneficiaries across multiple contacts.

• Case management concepts for longitudinal beneficiary and household records
• Case properties selected for identifiers, demographics, status and eligibility
• Registration forms configured to create new cases correctly
• Follow-up forms configured to load and update existing cases
• Case lifecycle states defined for active, closed, transferred and duplicate records
• Unique identifier design using programme codes and controlled registration rules

Participants can configure controlled case selection and multi-step programme workflows.

• Case search configured using beneficiary names, identifiers and locations
• Case lists designed with meaningful display fields for fieldworkers
• Eligibility criteria expressed through case properties and conditional form access
• Referral workflows linking originating services, receiving services and completion status
• Closed case handling prevents inappropriate follow-up data entry
• Duplicate prevention rules reviewed against realistic registration scenarios

Participants can configure user structures that reflect field operations and supervision lines.

• Mobile worker, web user and administrator roles distinguished
• User groups configured for teams, partners and programme units
• Location hierarchies structured by country, region, district and facility
• Role-based access controls matched to operational responsibilities
• Case sharing groups planned for team-based service delivery workflows
• User onboarding records include device assignment and training status

Participants can test CommCare applications systematically before field deployment.

• Test plan built from requirements, workflows, logic paths and risk areas
• Test cases cover valid entries, invalid entries and boundary values
• User acceptance testing records expected results, actual results and defects
• Android preview testing checks screen flow, language and offline behaviour
• Defect logs prioritise severity, ownership, retest status and release decisions
• Version naming conventions distinguish draft, pilot and production applications

Participants can prepare CommCare mobile applications for controlled field deployment.

• CommCare mobile installation, login and application restore procedures
• Application profiles configured for appropriate user groups and locations
• Offline submission queues monitored before and after synchronisation
• Device readiness checklist covers storage, battery, date and connectivity
• Mobile security settings address screen locks, updates and device loss
• Field support escalation paths define first-line and technical responsibilities

Participants can plan a pilot that validates workflows, usability and operational controls.

• Pilot objectives distinguish technical defects from workflow and training issues
• Enumerator briefing plan covers consent, device handling and form completion
• Pilot sampling selects representative users, locations and beneficiary scenarios
• Observation checklist captures delays, misunderstandings and workarounds during use
• Issue triage separates urgent defects from post-pilot enhancements
• Go-live criteria specify acceptable quality, support and readiness thresholds

Participants can establish routine checks for completeness, consistency and timeliness.

• Data quality dimensions assessed through completeness, accuracy, timeliness and consistency
• Routine Data Quality Assessment principles applied to CommCare submissions
• Completeness checks compare expected forms, submitted forms and missing records
• Outlier rules identify implausible values, durations and service volumes
• Duplicate checks compare identifiers, names, locations and registration dates
• Data correction protocol preserves audit trails and approved change authority

Participants can export CommCare data and prepare structured datasets for analysis.

• Form, case and user exports selected for specific reporting questions
• Export filters applied by date, location, user and application version
• Excel cleaning steps standardise dates, labels, codes and missing values
• Unique keys used to join form submissions with case datasets
• Repeat group exports reconciled with parent forms using identifiers
• Data dictionaries document variables, labels, values and transformation rules

Participants can specify reporting outputs that support programme decisions and donor requirements.

• Reporting questions linked to indicators, targets, disaggregations and decision owners
• Indicator calculations distinguish numerator, denominator, period and inclusion criteria
• CommCare reports configured for submission counts, case status and worker activity
• Data extracts structured for monthly reporting, donor templates and evaluations
• Reporting calendar assigns validation, analysis, approval and dissemination responsibilities
• Feedback loops return data findings to field teams and programme managers

Participants can incorporate proportionate protections for sensitive programme data in CommCare.

• Data minimisation applied to beneficiary registration and follow-up forms
• Informed consent scripts distinguish participation, data use and withdrawal options
• Sensitive data classification identifies protection, health and financial information
• Access matrices define who can view, edit, export and administer data
• Retention schedules specify archival, deletion and case closure decisions
• Safeguarding referral data separated from routine programme monitoring records

Participants can maintain CommCare applications without disrupting active field data collection.

• Change requests assessed for indicator, workflow, data and training implications
• Configuration change log records rationale, owner, version and approval
• Form version management protects continuity during active data collection
• Release procedures include backup, testing, communication and rollback decisions
• User access reviews identify inactive accounts and inappropriate permissions
• Application documentation maintained for forms, cases, reports and support contacts

Participants can assess practical options for connecting CommCare with programme information systems.

• Integration requirements distinguish data exchange, reporting and master-data needs
• API concepts explained through endpoints, authentication, requests and responses
• Unique identifiers planned for matching CommCare records with external systems
• DHIS2 reporting workflows assessed for aggregate indicator transfer requirements
• Data mapping table aligns source fields, target fields and transformation rules
• Integration risk assessment covers duplicates, timing, ownership and error handling

Participants can establish governance arrangements for sustained CommCare application ownership.

• Operating model defines application owner, technical administrator and data steward
• RACI matrix assigns build, approval, support and reporting responsibilities
• Support service levels classify incidents by urgency, impact and response time
• Training-of-trainers plan supports onboarding, refresher training and staff turnover
• Cost plan covers devices, connectivity, support and application maintenance
• Periodic review cycle evaluates relevance, data quality and user adoption

Participants can build, review and present a complete CommCare application with deployment and data quality documentation.

• Programme scenario converted into a complete CommCare application specification
• Mobile forms built with logic, validation, calculations and appropriate guidance
• Case workflow configured for registration, follow-up, referral and closure
• Users, groups and locations aligned with proposed field operating structure
• Test evidence, deployment plan and data quality protocol assembled
• Peer review assesses usability, data protection, reporting and maintenance readiness