CommCare for Development Programmes Training Course

Participants can configure a CommCare project for appropriate mobile and web-based use.

• Android device requirements, CommCare Mobile installation, and secure application access
• Project settings controlling languages, time zones, defaults, and data retention
• Application profiles matched to device type, language, and deployment channel
• Mobile menu structure designed around frontline worker task sequences
• Demo users distinguish web administration from mobile field workflows
• Synchronization mechanics explain server copies, local records, and conflict resolution

Participants can design usable mobile forms that capture valid programme data.

• Form Builder question types selected for valid field data capture
• XLSForm columns map labels, relevance, constraints, and calculations
• Question wording follows cognitive interviewing principles and local terminology
• Choice lists use stable codes, labels, and controlled vocabulary
• Required fields distinguish mandatory service data from optional observations
• Form sections reduce respondent burden through logical grouping and sequencing

Participants can configure form logic that guides users and prevents invalid submissions.

• Skip logic directs users through eligibility, referrals, and follow-up pathways
• Relevance expressions control question display using prior answers and case values
• Validation constraints prevent impossible dates, ranges, and incompatible responses
• Calculation questions derive age, gestation, scores, and visit schedules
• Default values populate worker identifiers, locations, and encounter timestamps
• Error messages give actionable correction prompts without exposing sensitive information

Participants can configure case structures for clients, households, referrals, and service episodes.

• Case types model clients, households, facilities, referrals, and service episodes
• Case properties store persistent attributes required at later encounters
• Case lifecycle rules define opening, updating, closing, and reopening conditions
• Parent-child cases connect households with individual members and visits
• Case sharing groups support supervised handovers while controlling visibility
• Duplicate prevention uses search, matching fields, and registration safeguards

Participants can build end-to-end workflows for enrolment, service delivery, referrals, and follow-up.

• Registration workflows capture consent, identity, eligibility, and baseline information
• Service delivery forms schedule visits from protocol-specific completion criteria
• Referral workflows record destination, completion status, and feedback loops
• Follow-up lists prioritize overdue cases using calculated visit dates
• Closed-loop workflows connect screening, referral, treatment, and outcome records
• Protocol exceptions document missed appointments, refusals, and escalations

Participants can structure complex forms using repeats, subforms, filters, and lookup tables.

• Repeat groups capture multiple services, commodities, or household members
• Subforms separate complex assessments from short routine encounter forms
• Repeat counts validate expected observations against roster or visit rules
• Dynamic choice filters restrict lists using location, eligibility, or caseload
• Lookup tables maintain standard protocols, commodity lists, and referral directories
• Form normalization avoids repeated data elements and conflicting enumerations

Participants can improve form usability for diverse field users and local contexts.

• Multimedia prompts support counselling, job aids, and protocol adherence
• Language profiles manage translated labels, audio, and culturally appropriate terms
• Plain-language design reduces interpretation errors among low-literacy user groups
• Accessibility checks address font size, contrast, audio, and touch targets
• Device testing confirms media performance under constrained storage and bandwidth
• Translation review reconciles programmatic meaning, local usage, and data codes

Participants can establish user access structures that support operations and protect sensitive data.

• CommCare user roles separate administration, supervision, data entry, and analysis
• Mobile workers assigned to locations using programme hierarchy and caseloads
• User groups control shared cases, reporting access, and peer handovers
• Least-privilege access matrix documents permissions for each operational role
• Account lifecycle procedures cover creation, transfer, deactivation, and audit
• Supervisor workflows review caseloads without unrestricted personal data access

Participants can prepare CommCare applications for reliable use in low-connectivity field settings.

• Offline-first workflows account for interrupted connectivity and delayed synchronization
• Device enrolment checklist records ownership, security settings, and support contacts
• Mobile updates follow version control, backup, and rollback procedures
• Sync monitoring identifies stale devices, transmission failures, and unresolved conflicts
• Field support triage separates account, form, device, and connectivity incidents
• Deployment calendar coordinates releases with service continuity and supervision schedules

Participants can align CommCare questions and case data with valid M&E indicator definitions.

• Indicator reference sheets define numerator, denominator, source, frequency, and owner
• Results frameworks connect activities, outputs, outcomes, and reporting questions
• Disaggregation plan specifies sex, age, location, disability, and cohort fields
• Data dictionary aligns indicator terms, question codes, formats, and allowable values
• Collection frequency balances decision needs, respondent burden, and data latency
• Unique identifiers support longitudinal monitoring while minimizing identifiable data

Participants can apply systematic data-quality controls to mobile collection and reporting processes.

• Routine Data Quality Assessment dimensions assess accuracy, completeness, timeliness, integrity
• Range checks flag improbable values using programmatic thresholds and distributions
• Consistency checks compare related answers, repeated visits, and reported totals
• Missing-data rules distinguish nonresponse, not-applicable, unknown, and system failure
• Audit trails support correction review, accountability, and documented data changes
• Supervisory verification samples source records against submitted mobile forms

Participants can specify reports and dashboards that support operational and management decisions.

• CommCare reports filter cases, users, locations, dates, and completion status
• Report specifications translate management questions into fields, filters, and aggregations
• Case list reports identify defaulters, high-risk clients, and pending referrals
• Aggregate reports calculate service volumes, coverage proxies, and workload measures
• Dashboard wireframes prioritize exceptions, trends, targets, and action owners
• Reporting calendar aligns refresh cycles with management and donor deadlines

Participants can prepare structured CommCare exports for repeatable M&E analysis and reporting.

• Data exports select de-identified fields, date ranges, and analytic formats
• Excel Power Query cleans CommCare exports using repeatable transformation steps
• Codebooks preserve variable labels, response codes, and derivation rules
• Long-format repeat data reshaped for service counts and longitudinal analysis
• Pivot tables summarize disaggregated results by location, cadre, and period
• Reconciliation log records extraction dates, filters, transformations, and exceptions

Participants can assess and specify data exchange requirements with external programme systems.

• Interoperability assessment maps source systems, identifiers, exchange frequency, and ownership
• DHIS2 aggregate reporting mapped from CommCare indicators and approved disaggregations
• API concepts distinguish authentication, endpoints, payloads, and scheduled transfers
• FHIR resources considered for patient data exchange where national standards apply
• Master-data rules reconcile facility codes, locations, users, and organisation names
• Integration controls document validation, error handling, retries, and reconciliation

Participants can apply data protection and safeguarding controls to CommCare application designs.

• Data minimisation limits collection to information required for stated purposes
• Informed consent scripts explain collection, use, sharing, and withdrawal choices
• Data protection impact assessment identifies risks, controls, and residual exposure
• Sensitive case access restricted through roles, sharing groups, and retention rules
• Safeguarding escalation workflows protect survivors and prevent harmful disclosures
• Incident response plan assigns containment, notification, investigation, and recovery actions

Participants can test CommCare applications and manage release decisions before field deployment.

• Requirements traceability matrix links user stories, forms, indicators, and tests
• Test cases cover normal, boundary, exception, offline, and synchronization conditions
• User acceptance criteria define expected workflow results before release approval
• Defect log records severity, reproducibility, owner, resolution, and retest status
• Pilot feedback separates usability issues from configuration and training gaps
• Release sign-off confirms programme, M&E, technical, and safeguarding approval

Participants can plan adoption support for CommCare users, supervisors, and administrators.

• Training needs analysis segments administrators, supervisors, and frontline workers
• Role-based job aids document mobile tasks, escalation routes, and troubleshooting
• Training-of-trainers plan sets facilitation standards, observation, and refreshers
• Pilot rollout monitors adoption, completion, error rates, and support demand
• Help desk workflow categorizes incidents, service levels, and resolution ownership
• Change communications explain workflow changes, data responsibilities, and support channels

Participants can establish governance arrangements for maintaining and improving CommCare applications.

• Product backlog prioritizes enhancements using value, risk, effort, and dependency
• Application governance board reviews change requests, releases, and data impacts
• Service-level measures track uptime, synchronization, support response, and closure
• Monthly performance review converts dashboard findings into accountable actions
• Configuration documentation records versions, decisions, owners, and approval dates
• Exit and continuity plan protects records, access, devices, and operational knowledge

Participants can build, peer-review, and present a deployable CommCare application package for a defined programme.

• Programme brief converted into workflow map, indicator matrix, and application scope
• Configured forms demonstrate case management, validations, calculations, and follow-up
• Security matrix assigns roles, locations, case sharing, and access restrictions
• Data-quality plan specifies checks, supervision, correction, and reporting cadence
• Deployment plan covers testing, training, support, rollout, and governance
• Peer review assesses usability, data protection, indicator fit, and release readiness
• Final presentation defends design choices against programme and operational requirements