Create a Mobile Data Collection Protocol

You are a senior MEAL specialist with extensive experience managing digital data collection operations in low-resource and field environments. Your task is to create a comprehensive Mobile Data Collection Protocol for a program. **Context:** - Program name: the program conducting data collection - Number of data collectors: the team size - Devices: the type and number of devices available - Data collection platform: the software platform being used - Connectivity conditions: the typical network availability in field sites - Data collection duration: the planned data collection period - Number of active forms: how many different forms are in use - Server setup: the data server configuration **Deliverables:** **1. Device Management** - Device inventory register template (device ID, IMEI, assigned enumerator, condition, accessories) - Device configuration checklist: - Android version requirements and security updates - Required apps (data collection app, file manager, GPS test app) - Settings: screen timeout, location services, storage management, battery optimization disabled for data app - Security: screen lock, encryption, remote wipe capability - Device issuance and return procedures - Maintenance schedule (charging, cleaning, storage case requirements) - Lost or damaged device protocol (reporting, replacement, data recovery) **2. Form Deployment and Version Control** - Form naming convention - Form deployment workflow: author, review, test, approve, deploy - Version update procedure: how enumerators receive updated forms - Rollback procedure if a deployed form contains errors - Form retirement process when data collection ends **3. Data Submission and Syncing Protocol** - Submission workflow: - Step-by-step instructions for submitting completed forms - Auto-send settings configuration (when connectivity is available) - Manual submission procedure - Submission confirmation verification (how to check submissions reached the server) - Syncing schedule: recommended sync frequency (at minimum, daily) - Connectivity troubleshooting: what to do when submissions fail - Offline data management: - Maximum offline storage duration before mandatory sync (recommend 48-hour maximum) - Backup procedure for finalized but unsubmitted forms - What to do if device storage is full **4. Data Quality Checks** - Real-time checks (built into forms): validation rules, constraints, skip logic - Daily checks by team supervisors: - Submission count vs. target tracking - GPS coordinate verification (submissions from expected locations) - Interview duration checks (flag interviews shorter than minimum threshold) - Duplicate detection - Completeness rates by enumerator - Weekly checks by MEAL team: - Cross-form consistency - Outlier analysis - Enumerator performance comparison - Response pattern analysis (detecting straight-lining or fabrication) Present the daily check as a supervisor checklist template. **5. Data Security and Privacy** - Encryption requirements (at rest and in transit) - Access controls: who can view, edit, or export data on the server - Device-level protections (no data stored after submission, app-level passwords) - Enumerator data handling rules (no screenshots, no sharing forms, no personal devices) - Incident response: what to do if a device with unsubmitted data is lost or stolen **6. Troubleshooting Guide** Provide a quick-reference troubleshooting table: | Problem | Likely Cause | Solution | Escalation | |---|---|---|---| Cover at least 8 common field issues: app crashes, GPS not working, form won't load, submission stuck, device frozen, storage full, battery draining fast, language display issues. **7. Roles and Responsibilities** | Role | Responsibilities | Frequency | |---|---|---| Include: Enumerator, Team Supervisor, MEAL Officer, IT Support, Data Manager. Align with OCHA and UNHCR digital data collection guidelines.