JoripoOn most surveys, data quality is something you find out about later. Submissions come in, someone exports them, and a few days or weeks later a script flags the interviews that ran too short, the GPS points that landed in the wrong district, and the enumerator whose answers never vary.
By then the field team has moved on. The household is hours away, and the interview you wanted to redo has become a gap in your sample that nobody can fill.
The check has not changed, only the timing
High frequency checks are not new. Teams have run duration checks, GPS checks, productivity and straight-lining checks for years. What Joripo changes is when they run. The checks that look at a single interview run on every submission the moment it arrives, so a supervisor sees the flag while the enumerator is still in the area. The checks that compare enumerators or look across the whole dataset run whenever you choose, as often as you like.
That timing turns an after-the-fact audit into a field management tool. A flagged interview on the day it happens is a phone call you can still make.
What we check
Duration, GPS distance from the survey area, daily productivity, straight-lining, refusal and skip patterns, and back-checks, along with ported classics such as Benford's law, travel speed between interviews, and fuzzy duplicates. Every flag names the submission, the enumerator, and the reason it was raised, so a supervisor knows what to do next.