A missing contact route should create rural-support work, not erase an applicant
Keep the application visible while an authorized team confirms an alternative contact path.
A cleaner report can hide a person
A person needing rural support may not have the digital contact details an intake form expects. Deleting that row can make an administrative report cleaner while hiding the person with the greatest access burden. Truthound can check a minimal, authorized intake-support table. It cannot determine eligibility, economic vulnerability or whether someone will receive the project's benefits.
The rural-resilience project
ADB announced on October 26, 2026 a financing package for resilient agriculture and women's economic participation in Cambodia. The project covers disaster-vulnerable communes and services. These are intended program activities, not evidence that a particular application process requires a phone number or that any named applicant has been excluded.
Design a minimal contact record
For a proposed intake design, record application identity, agreed contact route, field-support owner and alternative-intake state. Collect only information the authorized process needs. The route may be in-person or another approved channel; it should not default to a requirement that everyone possess the same device or account.
Route a missing field to support
For the applicant support intake table prepared as a Polars DataFrame, Truthound Core Python SDK 3.3.4's NotNullValidator can flag missing entries in a field the intake owner has approved as necessary. That result should open a support task, not automatically close the application. A nonempty contact entry also needs appropriate verification. The check does not establish that a person is reachable or that an alternative route is accessible to them.
A preserved-record pandas check
pandas 3.1.1's isna offers a custom missingness check if the project defines empty strings and unknown states separately. Keep an existing tested mask when its output preserves the application and routes it to a responsible person. Neither pandas nor a framework validator should be used as an unreviewed eligibility rule.
Test two support situations
Try a synthetic application with no phone number but an agreed field-contact option. The process should preserve the record and identify the next authorized action. A second case may lack any confirmed route and require local follow-up. These are different support situations, not two reasons to remove a person from the count.
Review unresolved access before reporting
Review unresolved routes with the field team before reporting intake coverage. Keep the minimal record and a clear owner until the contact decision is resolved under the program's process. A support announcement becomes more accessible when its data preparation exposes a person's burden instead of making that burden disappear through row deletion.
Evidence
- Event checked
- Subject checked
- Modified
