SurveyCTO for Research Projects Training Course

Participants can convert a questionnaire specification into a structured mobile form plan.

• Questionnaire matrices defining variables, responses, skips and validation requirements
• Unique identifiers specified for households, respondents, facilities and visits
• Indicator reference sheets linked to questionnaire variables and disaggregation fields
• Response options reviewed for mutual exclusivity and analytic usefulness
• Sensitive questions sequenced using privacy, consent and respondent-burden principles
• Form plan documents sections, groups, repeats and required metadata

Participants can create valid XLSForm workbooks for basic SurveyCTO questionnaires.

• XLSForm workbook structure using survey, choices and settings sheets
• Question types selected for text, integers, decimals, dates and select lists
• Variable names created using stable, analysis-friendly naming conventions
• Choice lists organised for reusable coded response categories
• Required fields configured without forcing inappropriate respondent answers
• Form titles, identifiers and version labels maintained in settings

Participants can configure branching logic that presents only applicable questions to respondents.

• Relevant expressions control questions based on previous responses
• Skip patterns modelled from questionnaire decision rules and eligibility criteria
• Boolean operators combine conditions using and, or and not
• Selected functions test multiple-choice responses within select_multiple questions
• Nested conditions simplified through intermediate calculate fields
• Branching paths tested against positive, negative and exceptional cases

Participants can prevent common entry errors through constraints, calculations and tailored prompts.

• Constraint expressions enforce valid ranges, dates and response combinations
• Constraint messages explain corrections in clear enumerator-facing language
• Calculate fields derive ages, totals, ratios and eligibility classifications
• Relevance and constraints distinguished to avoid hidden invalid records
• Soft warnings configured for unusual values requiring enumerator confirmation
• Validation rules aligned with the analysis plan and indicator definitions

Participants can model repeated respondents, household members and service records using repeats.

• Field-list groups arrange short related questions on one screen
• Repeat groups capture household rosters, visits and multiple observations
• Repeat counts driven by entered totals or selected service categories
• Indexed repeat references retrieve previous answers for checks
• Roster questions structured to support later analysis and reporting
• Group labels and hints improve enumerator orientation during interviews

Participants can prepare multilingual forms that support consistent administration across language groups.

• Translation columns added for labels, hints, messages and choices
• Language codes configured using standardised locale naming conventions
• Source text controlled through approved questionnaire version management
• Back-translation checks identify conceptual errors in translated survey items
• Enumerator instructions separated from respondent-facing question wording
• Readability reviewed for device screens, literacy levels and interview pace

Participants can select and configure appropriate SurveyCTO question types for field evidence.

• Image, audio and signature fields configured with justified collection purposes
• GPS questions set for accuracy thresholds and location-capture conditions
• Barcode scanning supports asset tracking, vouchers and case identifiers
• File attachments managed for supporting documents and verification evidence
• Select_one and select_multiple choices distinguished for valid coding
• Media collection assessed against consent, safeguarding and storage requirements

Participants can configure a controlled SurveyCTO Server environment for a research project.

• Server interface used to upload, publish and retire form versions
• User accounts assigned according to enumerator, supervisor and administrator roles
• Server groups organise users, forms and project-level permissions
• Form access controlled through publication settings and user assignments
• Dataset permissions separated from raw submission access where required
• Administrative audit trails reviewed for account and configuration changes

Participants can configure case-based workflows using preloaded datasets and controlled updates.

• Preloaded datasets prepare sampled cases, identifiers and contact details
• Unique keys link form submissions to assigned respondent records
• Dataset lookups retrieve household details and prior interview information
• Case assignments restrict enumerator access to authorised respondent lists
• Follow-up status fields support callbacks, revisits and completion tracking
• Dataset updates planned to prevent conflicting fieldwork records

Participants can test, document and approve forms before field deployment.

• Test cases cover eligibility, skip paths, constraints and repeat loops
• Happy-path and edge-case submissions identify configuration defects
• Device testing checks screen layout, language display and offline behaviour
• Bug logs record severity, reproduction steps, ownership and resolution
• Version numbers distinguish draft, pilot, approved and production forms
• Release approval criteria confirm questionnaire, translations and protocol alignment

Participants can prepare practical enumerator procedures for secure and consistent data collection.

• Enumerator briefing plans cover protocol, consent, devices and escalation routes
• Standard operating procedures define interview opening, saving and submission steps
• Device allocation registers record custody, return and incident reporting
• Consent scripts align respondent information with approved research procedures
• Refusal, distress and safeguarding referrals follow defined escalation protocols
• Offline submission procedures address connectivity failures and delayed synchronisation

Participants can apply practical safeguards for respondent privacy, consent and sensitive data.

• Data minimisation removes unnecessary personally identifiable information from forms
• Informed consent records purpose, voluntary participation and withdrawal rights
• Role-based access limits exposure to sensitive respondent information
• Device passcodes and screen locks protect data during fieldwork
• Encryption options assessed for stored submissions and exported files
• Retention schedules specify deletion, archiving and controlled data handover

Participants can monitor progress, productivity and potential fieldwork irregularities using SurveyCTO data.

• Submission timestamps measure interview duration, workloads and reporting delays
• GPS coordinates reviewed against assigned locations and plausible travel patterns
• Enumerator productivity dashboards compare completed, pending and rejected submissions
• Paradata flags identify unusually rapid, repetitive or incomplete interviews
• Daily supervisor reviews prioritise exceptions requiring timely follow-up
• Fieldwork trackers combine sample status, contact attempts and outcomes

Participants can establish systematic procedures for detecting, correcting and documenting data-quality issues.

• Quality rules identify missing values, duplicates and logical inconsistencies
• Supervisor checks distinguish correction requests from protocol deviations
• Verification calls sampled using documented risk-based selection criteria
• Correction workflows preserve original submissions and change accountability
• Discrepancy logs record issue type, action, owner and closure date
• Quality thresholds trigger retraining, intensified review or fieldwork suspension

Participants can review submissions and produce documented exports for analysis teams.

• Submission tables filtered by date, user, status and form version
• Saved views support recurring checks by supervisors and data managers
• CSV, Excel and Stata exports selected for downstream analysis needs
• Wide and long data structures interpreted for repeat-group exports
• Export folders separate raw, reviewed and analysis-ready data versions
• Data dictionaries document variable names, labels, codes and derived fields

Participants can prepare a transparent handover package for data cleaning and statistical analysis.

• Cleaning specifications translate quality rules into reproducible data actions
• Identifier checks reconcile sample frames, submissions and repeat interviews
• Missing-data codes distinguished from blank, refused and not-applicable values
• Outlier review combines automated flags with contextual verification evidence
• Change logs document transformations, corrections and unresolved data limitations
• Analysis handover packages include exports, dictionaries and fieldwork metadata

Participants can assess appropriate options for connecting SurveyCTO data with project reporting workflows.

• SurveyCTO API concepts distinguish retrieval, authentication and scheduled data transfers
• Webhook events support notifications after completed form submissions
• Google Sheets connections assessed for controlled operational reporting use
• Power BI workflows plan refreshes from governed exported datasets
• Integration requirements document fields, timing, ownership and failure handling
• Manual exports retained as contingency for interrupted automated processes

Participants can establish governance arrangements that keep SurveyCTO projects usable beyond initial deployment.

• RACI matrices assign accountability for forms, data, devices and approvals
• Change-control procedures manage questionnaire amendments during active fieldwork
• Project repositories store forms, protocols, translations and release records
• Form libraries identify reusable modules for future programme instruments
• Post-fieldwork reviews capture defects, lessons and template improvements
• Support plans define escalation paths, service ownership and maintenance responsibilities

Participants can build, review and present a complete SurveyCTO deployment pack for a defined research project.

• Project brief defines research questions, respondents, sampling and fieldwork constraints
• Complete XLSForm incorporates logic, constraints, repeats and multilingual content
• Server configuration assigns forms, users, permissions and preloaded cases
• Testing evidence documents resolved defects and approved release decisions
• Quality-control plan specifies monitoring indicators, review rules and correction workflows
• Capstone presentation defends deployment choices, risks and implementation recommendations