near real‐time monitoring, field teams uploaded interviews onto the project’s Survey Solutions server at the end of each day. An automated pipeline of Stata code downloaded and processed the data, creating a detailed monitoring dashboard in Microsoft Excel, which headquarters reviewed daily. The dashboard tracked the number of submissions meeting the quality standards to be considered acceptable (see section 3.3 for these standards), interview duration, and unit non‐response rates separately by EA, enumerator, team, and strata. It further assessed item non‐response by listing the number of household members, proportion of missing values, ‘No’, and ‘Don’t know’ or ‘Refused to respond’ entries in all modules and several other key questions, which would trigger follow‐up questions. Unusually high proportions of missing values, ‘No’, ‘Don’t know’, or ‘Refused to respond’ entries indicated possible enumerator shirking, as this behavior would reduce enumerators’ workload. For example, entering that a household self‐identifies as displaced would trigger an entire module on displacement. Enumerators returning low‐quality or displaying suspicious behavior received warnings and follow‐up training. If the issues could not be resolved in this way, enumerators were replaced by reserve enumerators from their team. Overall, however, enumerator performance was high, requiring few replacements, while the unit non‐response rate was very low at 0.16 percent among urban, rural, and IDP households, and 0.50 percent among nomadic households.

# 3.3. Submissions quality standards

Each enumerator submission was subject to a set of minimum standards to ensure data quality. Interviews were classified as valid or invalid based on the criteria listed in the following.

- _Valid EAs_ . If the EA was not part of the final sample (i.e. it was replaced), the interview was classified as invalid and thus excluded from the final data set.

- _Valid EBs._ If the EB was not part of the final sample (i.e. it was replaced), the interview was excluded.

- _Duration._ If the duration of the interview did not exceed the minimum threshold of 30 minutes, the interview was excluded.

- _Location._ If the interview did not have GPS coordinates associated with it, the interview was considered invalid. If the GPS coordinates fell outside buffer zone of a 50m+accuracy of GPS (based on the minimum latitude‐longitude formula + 50m buffer) around the EA, the interview was excluded.

- _Follow up visits_ . If the interview was not conducted in the first visit, the interview for the first visit must be valid except for the minimum duration, and both records must contain matching GPS positions (with a 10m + precision maximum distance), otherwise the interview completed in the follow‐up visit was excluded.

- _Replacement interview_ . If the interview was from a replaced household, the record of the original household must be valid except for the minimum duration and the reason for no interview must also be valid, otherwise the interview was excluded.

Beyond these criteria, the Survey Solutions CAPI platform allowed to ‘reject’ submissions on a case‐by‐ case basis and send them back to enumerators to correct whenever headquarters found problems with a submission.

16