CommCare for Field Data Management Training Course

Participants can plan a CommCare application structure suited to a defined field workflow.

• CommCare HQ projects organise applications, users, locations and reporting assets
• Application modules group forms around worker tasks and programme processes
• Form menus reflect registration, follow-up, referral and closure workflows
• Offline Android use shapes form length, media choices and synchronization routines
• Project naming conventions support version control and multi-team administration
• Application scoping documents capture users, devices, languages and reporting needs

Participants can specify clear, measurable and ethically appropriate digital questions.

• Question wording follows indicator definitions and respondent-friendly language principles
• Response types match nominal, ordinal, interval and open-text data requirements
• Recall periods reduce ambiguity in household, service and outcome questions
• Disaggregation fields capture sex, age, disability and location consistently
• Informed consent questions record voluntary participation and data-use permissions
• Question matrices identify labels, hints, response options and validation requirements

Participants can build functional CommCare forms using the form builder.

• CommCare form builder creates questions, groups and sectioned mobile screens
• Display text uses concise labels, hints and translated field guidance
• Question properties set required responses, defaults and help text
• Choice lists standardise administrative areas, services and programme classifications
• Field order follows interview flow and reduces enumerator screen switching
• Save settings connect completed forms to selected case-management processes

Participants can create and import structured CommCare forms using XLSForm.

• XLSForm survey sheets define question types, names, labels and constraints
• Choices sheets manage reusable select lists and cascading response options
• Settings sheets specify form identifiers, versions and default languages
• Relevant expressions control conditional questions using XPath logic
• Constraint messages explain invalid values without exposing technical expressions
• Import checks identify unsupported question types and spreadsheet formatting errors

Participants can configure logic and controls that prevent common field-data errors.

• Skip logic presents questions only when prior answers require them
• Validation constraints prevent impossible dates, ages and numeric values
• Calculated values derive totals, eligibility scores and visit schedules
• Required fields distinguish essential monitoring data from optional narrative detail
• Repeat groups capture multiple household members, services or referrals
• Logic testing uses boundary values, missing values and conflicting responses

Participants can configure multilingual and usable forms for diverse field teams.

• Language tables maintain consistent translations for labels, hints and choices
• Plain-language prompts reduce interviewer interpretation and respondent confusion
• Audio prompts support low-literacy interviews and standardised question delivery
• Image capture requirements balance verification needs with privacy risks
• Date formats, calendars and units match local field conventions
• Mobile screen layouts minimise scrolling, typing and repeated data entry

Participants can configure cases to track people, households or service entities over time.

• Cases store longitudinal records beyond individual submitted form responses
• Case types distinguish households, clients, facilities and community groups
• Registration forms open cases using unique identifiers and core properties
• Follow-up forms update status, service history and scheduled actions
• Case lists help workers find assigned records during repeat visits
• Case closure rules prevent inactive records from appearing in routine workflows

Participants can model programme relationships and referrals using case properties.

• Case properties store stable attributes, current status and programme eligibility
• Parent-child cases link households with members, children or service episodes
• Referral workflows record destination, acceptance, completion and follow-up outcomes
• Conditional case updates protect verified records from accidental overwriting
• Duplicate detection compares identifiers, locations and demographic matching fields
• Case-property dictionaries document ownership, source forms and update rules

Participants can administer field users and access controls for a CommCare project.

• Mobile worker accounts assign unique logins to individual field personnel
• Location hierarchies organise teams by country, district, facility and community
• User roles restrict application settings, reports and data-management actions
• Case sharing settings determine which workers can view programme records
• Account deactivation protects data when staff leave or change roles
• User administration logs support supervision, accountability and access reviews

Participants can apply practical privacy and safeguarding controls to field data systems.

• Data minimisation limits collection to information required for programme decisions
• Consent workflows distinguish service provision from optional research participation
• Sensitive data classification identifies protection, health and identity information
• Role-based access limits visibility of sensitive records and reports
• Device security includes passcodes, screen locks and controlled user accounts
• Data-retention schedules define review, archival and secure deletion decisions

Participants can prepare CommCare data for routine monitoring and external analysis.

• Form exports provide submission-level records for cleaning and indicator calculation
• Case exports provide current longitudinal records for caseload management
• Export filters limit extracts by date, location, form and user
• Data dictionaries define variables, formats, labels and allowable values
• Unique identifiers link submissions, cases, workers and reporting periods
• Reporting calendars align data extraction with monthly programme review cycles

Participants can establish data-quality checks for routine CommCare field operations.

• Data-quality dimensions assess completeness, timeliness, consistency, accuracy and uniqueness
• Daily supervisor checks identify missing forms, unusual values and inactive workers
• Range checks compare submitted values against expected operational thresholds
• Cross-field checks detect contradictions between household, service and outcome responses
• Verification protocols compare digital records with source documents and observations
• Correction logs record issue source, action owner and closure evidence

Participants can test CommCare applications systematically before field deployment.

• Test scripts cover normal paths, exception paths and boundary conditions
• Test cases verify question logic, calculations, case updates and permissions
• Android testing checks offline completion, synchronization and menu behaviour
• Defect logs record reproduction steps, priority, owner and resolution status
• User-acceptance criteria confirm workflow fit, clarity and reporting readiness
• Regression testing confirms revisions have not damaged functioning components

Participants can prepare a controlled rollout plan for a CommCare application.

• Deployment plans sequence configuration freeze, training, piloting and phased rollout
• Enumerator training covers login, form completion, synchronization and error reporting
• Pilot protocols define sample sites, observation methods and revision decisions
• Device inventories track custody, operating status and replacement requirements
• Support escalation routes technical, workflow and data-quality issues appropriately
• Change logs document application revisions, approval dates and release notes

Participants can maintain CommCare applications without disrupting active field operations.

• Version numbering distinguishes draft, pilot, production and retired application releases
• Form edits assess effects on exports, calculations and historic submissions
• Case-property changes require migration planning and revised documentation
• Release checklists confirm testing, approvals, communications and rollback arrangements
• Archive procedures preserve superseded forms and supporting implementation records
• Maintenance calendars schedule access reviews, export checks and system housekeeping

Participants can plan controlled data exchanges between CommCare and reporting systems.

• Integration mapping identifies source fields, destination systems and transfer frequency
• DHIS2 reporting requirements shape indicator aggregation and disaggregation fields
• CSV export workflows support controlled transfer to approved analysis environments
• Data transformation rules document recoding, aggregation and missing-value treatment
• Reconciliation checks compare CommCare totals with programme and reporting records
• Interface ownership assigns responsibility for extracts, reviews and issue resolution

Participants can use CommCare data to identify field delivery and caseload issues.

• Submission timeliness identifies delayed reporting by location, worker and period
• Caseload summaries show active cases, overdue follow-ups and closure patterns
• Service completion rates reveal drop-off points within programme workflows
• Disaggregation tables compare reach by sex, age, location and vulnerability
• Outlier review distinguishes genuine programme changes from data-entry errors
• Management action logs connect findings to owners, deadlines and follow-up evidence

Participants can adapt CommCare design choices to common programme delivery scenarios.

• Cash assistance registration captures eligibility, identity checks and payment status
• Community health workflows schedule visits, referrals and treatment adherence follow-up
• Protection case management applies restricted access and sensitive-data controls
• Education monitoring tracks attendance, learning materials and school-level needs
• Livelihoods programmes monitor participant support, production milestones and market referrals
• Rapid assessments balance timely field collection with minimum data requirements

Participants can build, review and present a complete CommCare application package for a defined programme workflow.

• Programme brief defines users, indicators, cases, forms and reporting decisions
• Application build configures registration, follow-up, validation and case updates
• Indicator mapping demonstrates traceability from result definition to exported field
• Test evidence records defects, corrections and user-acceptance decisions
• Deployment plan specifies training, support, governance and data-quality routines
• Peer review assesses usability, privacy controls, workflow fit and reporting readiness