How does data get from an enumerator in the field into the Portal?
Enumerators collect on the app, which works offline and stores responses on the device, then syncs them when a connection is available. In the Portal the responses arrive as drafts or pending items you can review, approve or reject before they count as final.
Understanding this path matters because it is where most field problems live. A response that "disappeared" is usually unsynced on a device, and data that looks wrong in a dashboard is often pending rather than approved. Knowing the sequence, and who is responsible at each point, is what makes a data collection operation manageable at scale rather than a series of individual mysteries.
How to do it
Have enumerators log in to the app and sync so their deployments and site data are on the device.
Collect responses in the field, working offline where there is no connection.
Sync when a connection is available, and confirm the response count on the device drops to zero pending.
Review the incoming responses in the Portal, where approvers can accept, reject or send them back.
Fix systematic problems in the survey design rather than correcting the same mistake response by response.
Work from approved data in your dashboards so drafts do not distort the figures.