Door-to-Door or Field Sweep¶
Workflow — instantiates Exhaustive Population Mapping
Sends people to physically walk every zone and verify units on the ground, catching the ones administrative records never held.
A Door-to-Door or Field Sweep is the workflow of last resort against invisibility: it puts a person physically in front of every location and lets direct observation be the source of truth, rather than trusting any register to already contain the units. Its defining premise is that the units most likely to be missed are precisely the ones no record holds — the unlisted, the informal, the newly built, the deliberately hidden — and the only way to enumerate them is to go there. It treats field presence itself as an enumeration frame: what the enumerator sees on the ground gets added to the map, whether or not any database predicted it. It is not the plan that carves the territory into zones and not the audit that re-checks a finished count; it is the labor that walks the ground the first time and confirms each unit by having stood in front of it.
Example¶
A water utility must locate every lead service line before it can certify a neighborhood remediated, because a single missed lead line leaves a household exposed and the "we replaced them" claim false. The problem is that the utility's pipe-material records are a century of partial, inconsistent paperwork — plenty of service lines are marked "unknown," and some connections appear in no record at all. So crews run a field sweep: working zone by assigned zone, they visit each property, inspect the line where it enters the building, and — where the record is ambiguous — dig a small "potholing" excavation at the curb stop to see the metal directly.
The sweep's yield is exactly the units the records missed. On one block, three homes that the database showed as "no service connection" turn out to be occupied houses on a shared lateral; on another, a line filed as "copper" is lead under the paint. Each is verified by eye and metal, not by trusting a field, and added to the enumeration. The workflow does not decide the block's boundaries — that came from the zone map — and does not estimate how many lines it might still have missed; it simply guarantees that every address in its zone was physically reached and each pipe personally confirmed.
How it works¶
- Observation is the frame. The enumerator's own sighting is a legitimate source of units, independent of any register, so off-record units enter the map for the first time.
- Walk the zone to exhaustion. Every location in the assigned area is visited, not sampled — the sweep's promise is coverage of the ground, address by address.
- Verify by physical presence. A unit is confirmed by being seen, measured, or dug up — not by a record asserting it exists.
- Resolve non-response, don't skip it. A no-answer door is a scheduled callback or a proxy check, because a skipped location is an uncounted unit, not a rounding error.
Tuning parameters¶
- Callback depth — how many revisits a non-responding location earns before proxy or last-resort methods. More callbacks reduce undercount but raise cost sharply.
- Verification intensity — eyeball, instrument reading, or invasive confirmation (potholing, entry). Deeper verification catches misclassification but slows the sweep.
- Crew density vs. schedule — more enumerators finish faster but strain quality control; fewer stretch the timeline and staleness.
- Off-record discovery mandate — whether crews are instructed to log only expected units or to actively hunt for unlisted ones. The latter finds hidden units but lengthens each visit.
When it helps, and when it misleads¶
The sweep is the right tool whenever the population's hardest units live outside every record and the decision cannot tolerate missing them — hazard location, exposure notification, service eligibility. It is the only mechanism here that creates new units from the world rather than reshuffling ones already listed, which makes it the backbone of genuine completeness.
Its failure modes are human and expensive. Curbstoning — enumerators fabricating visits they never made — silently reintroduces the undercount the sweep was meant to erase, which is why field work without independent verification is untrustworthy.[n1] Sweeps also decay under deadline pressure into skipped callbacks and guessed classifications, and their cost tempts teams to sample "just the uncertain ones," quietly collapsing the exhaustive sweep back into the survey it was supposed to replace. The guarding discipline is to subject the field work itself to independent re-checks and to treat every skipped location as an open undercount, not a closed one.
How it implements the components¶
A Door-to-Door or Field Sweep fills the go-find-and-confirm slice — the physical labor of first-pass discovery:
enumeration_frame_inventory— treats direct field observation as a source frame in its own right, adding units that appear in no register.coverage_sweep_plan— executes the exhaustive pass, visiting every location in the assigned zone rather than a sample of them.field_verification_protocol— confirms each unit by physical presence and inspection, not by trusting a record's claim.
It walks the zones but does not draw them — the population_boundary_statement and its geographic tiling belong to Census Protocol and Enumeration Area Map — and it discovers units on a first pass but does not re-check a completed count for error; testing the completeness_evidence_record by re-verifying finished entries is the audit run by its fellow field-verification user Enumeration Quality Backcheck.
Related¶
- Instantiates: Exhaustive Population Mapping — the sweep is the field labor that discovers the off-record units completeness depends on.
- Consumes: Enumeration Area Map supplies the zones and search paths the sweep walks.
- Sibling mechanisms: Census Protocol · Enumeration Area Map · Master Unit Index · Capture-Recapture Check · Administrative Record Linkage · Duplicate Resolution Queue · Coverage Gap Heatmap · Late-Unit Inclusion Window · Enumeration Quality Backcheck
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: The bounded sweep exhaustively inspects each location and produces a ground-truth finding about units that exist, including those absent from administrative records.
Nearest alternative: Protocol, Workflow & Routine — Walking zones and resolving nonresponse follow a procedure, but the operative output is verified population coverage rather than completion of the steps as such.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Statistics & Experimental Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Specialized
Rationale: Census and survey methodology cohered exhaustive field enumeration, mapped coverage, enumerator assignments, and independent backchecks against omission and curbstoning.
Related originating lineages:
- Public Administration & Policy — Population censuses and service registries institutionalized door-to-door enumeration, zone assignment, and follow-up at scale.
Review resolution: Census methodology and public administration jointly cohered exhaustive field enumeration; ethnographic field presence is analogous but not a co-origin of exhaustive coverage sweeps.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The sweep and Enumeration Quality Backcheck both put a field_verification_protocol to work, but at opposite ends of the pipeline: the sweep verifies units into the enumeration for the first time, while the backcheck re-verifies units already in it to measure how well the sweep did. First-pass discovery versus second-pass audit — never the same visit.
[n1] Curbstoning is the field-enumeration fraud of fabricating responses — filling in forms "from the curb" without actually visiting — named in survey and census methodology. It is the reason exhaustive field work is not self-certifying: without an independent backcheck, a sweep can look complete while quietly omitting the very units it was sent to find. ↩