SurveyCTO Data Collection and Mapping Training Course

Participants can translate an indicator matrix into a structured SurveyCTO form specification.

• Indicator reference sheets converted into measurable survey variables
• Question wording aligned with recall periods and response categories
• Data dictionary fields: name, label, type, code and owner
• Unique identifiers designed for households, facilities and beneficiaries
• Skip logic documented before building the electronic instrument
• Consent, refusal and safeguarding questions positioned appropriately

Participants can construct valid XLSForm workbooks for SurveyCTO deployment.

• XLSForm workbook structure: survey, choices and settings worksheets
• Question types selected for categorical, numeric and text responses
• Field names created using stable machine-readable naming conventions
• Choice lists coded with durable values and clear labels
• Form settings configured for title, version and submission identity
• SurveyCTO form upload errors interpreted from validation messages

Participants can control respondent pathways and prevent invalid entries using XLSForm expressions.

• Relevant expressions route respondents through conditional question paths
• Constraint expressions enforce numeric ranges, dates and allowed combinations
• Required fields applied selectively to avoid forced inaccurate responses
• Selected() function controls follow-up questions after multiple selections
• Regex patterns validate phone numbers, codes and identifier formats
• Constraint messages written for clear enumerator correction prompts

Participants can use calculations and dynamic labels to reduce entry errors and interviewer burden.

• Calculate fields derive ages, totals and eligibility classifications
• Today(), now() and date arithmetic support monitoring schedules
• String functions standardise names, codes and concatenated identifiers
• Dynamic labels insert prior responses into interviewer prompts
• Coalesce() handles alternative values in calculation expressions
• Hidden calculations preserve derived fields without enumerator interaction

Participants can build repeatable household, beneficiary and facility roster sections.

• Field-list groups organise related questions on mobile screens
• Repeat groups capture household members, visits and distributed items
• Repeat counts set expected roster lengths from prior answers
• Indexed-repeat() retrieves values from previous repeat instances
• Nested repeats assessed against usability and data-export complexity
• Roster identifiers maintain links between parent and child records

Participants can configure accessible multi-language forms with consistent enumerator guidance.

• Language columns maintain parallel labels, hints and messages
• Translation glossaries standardise technical and programme terminology
• Enumerator hints distinguish administration instructions from respondent questions
• Media files add images, audio prompts and reference materials
• Language switching tested across Android devices and screen sizes
• Sensitive wording reviewed for neutrality, dignity and informed consent

Participants can test SurveyCTO forms systematically and approve controlled releases.

• Test cases cover normal, boundary, refusal and error paths
• Decision tables expose missing logic across eligibility combinations
• Preview mode checks labels, appearance and response sequence
• Android device tests confirm offline behaviour and media performance
• Bug logs record severity, owner, correction and retest status
• Release checklists authorise production deployment after sign-off

Participants can configure field accounts, devices and procedures for accountable data collection.

• Enumerator accounts assigned according to district, team and function
• Device registration controls approved phones and tablet access
• Server login procedures protect credentials during field deployment
• Assignment lists organise workloads for visits and follow-up
• Enumerator briefing packs cover consent, probing and escalation
• Daily synchronisation routines reduce delayed submission risks

Participants can configure case-based workflows for repeat visits and ongoing monitoring.

• Cases model households, facilities or individuals across repeated interactions
• Case properties store stable details for prefilled future forms
• Case updates record status changes, referrals and completed visits
• Workflow states distinguish pending, completed, rejected and escalated cases
• Case assignment rules distribute follow-up work among field teams
• Longitudinal identifiers prevent duplicate records across monitoring rounds

Participants can use server datasets to standardise selections and prefill verified information.

• Server datasets store reference lists for locations and beneficiaries
• CSV imports prepare clean keys, labels and lookup attributes
• Searchable select questions reduce scrolling through long lists
• Pulldata() retrieves verified values from linked reference datasets
• Dataset update procedures preserve identifiers and audit changes
• Lookup failures diagnosed through key matching and case sensitivity

Participants can configure automated controls that identify suspicious and incomplete submissions.

• Quality checks flag duplicate identifiers and improbable values
• Time stamps identify unusually short or long interview durations
• Audit logs record edits, location changes and form events
• Required photos and signatures applied only where justified
• Cross-field checks compare household size, ages and totals
• Quality flags prioritise supervisor review queues and callbacks

Participants can run a documented review process for submitted field records.

• Submission review queues sort records by risk and status
• Correction requests document errors without overwriting audit evidence
• Supervisor spot checks compare records against call-back findings
• Data cleaning logs record changes, reasons and approvers
• Missing-data codes distinguish refusal, unknown and not applicable
• Daily quality dashboards guide enumerator feedback and redeployment

Participants can select and capture appropriate spatial data types for programme monitoring.

• Geopoints capture site locations using latitude, longitude and accuracy
• Geotraces record routes for outreach, distribution and inspection
• Geoshapes define service areas, plots and infrastructure boundaries
• Coordinate reference systems explained through WGS 84 field collection
• Location accuracy thresholds set according to operational decision needs
• Field protocols address safety, privacy and restricted locations

Participants can configure SurveyCTO forms that support location-aware field decisions.

• Geopoint questions configured with accuracy and mandatory capture rules
• Map layers support enumerator orientation and site verification
• Location preloading compares reported sites against approved reference points
• Distance calculations flag submissions outside expected service areas
• Offline basemaps planned for remote collection areas and devices
• Spatial consent statements explain purpose, access and retention

Participants can export, inspect and prepare SurveyCTO spatial data for QGIS analysis.

• CSV and GeoJSON exports selected for downstream mapping requirements
• Coordinate fields inspected for order, precision and missing values
• QGIS layers loaded with correct geometry and CRS settings
• Attribute tables cleaned using filters, joins and field calculations
• Repeated records summarised before joining spatial parent records
• Export metadata documents source form, date and transformation steps

Participants can create decision-relevant spatial analyses from SurveyCTO monitoring data.

• Graduated symbols compare caseloads, coverage and service utilisation
• Categorised maps show verification status, risk class and referral outcome
• Buffer analysis examines access around facilities and distribution sites
• Spatial joins connect survey records with administrative boundaries
• Outlier locations investigated using accuracy values and field notes
• Map interpretation separates observed patterns from unsupported conclusions

Participants can produce clear, appropriately protected maps for operational reporting.

• Map layouts include title, legend, scale bar and source note
• Classification methods selected to avoid misleading visual comparisons
• Privacy-preserving aggregation protects sensitive respondent locations
• Inset maps locate project areas within administrative context
• Export settings produce readable PDF and image outputs
• Map review checks interpretation, labels and disclosure risks

Participants can apply data protection and ethical controls to SurveyCTO field operations.

• Data minimisation limits collection to justified programme information
• Informed consent records purpose, voluntariness and withdrawal options
• Access matrices define permissions for collection, review and export
• Retention schedules specify deletion, archival and handover decisions
• Pseudonymisation separates direct identifiers from analysis datasets
• Incident response procedures address lost devices and unauthorised access

Participants can build, review and present a complete SurveyCTO data collection and mapping deployment pack for a defined programme use case.

• Programme scenario converted into indicators, workflow and data requirements
• SurveyCTO form built with logic, repeats and quality controls
• Reference dataset and case workflow configured for field follow-up
• Geospatial questions and privacy controls integrated into collection protocol
• QGIS map output prepared from cleaned SurveyCTO submissions
• Deployment pack reviewed against testing, governance and reporting criteria