Telephone Verification for Village Teaching Visits
Record and corroborate volunteer teaching visits over ordinary voice calls while keeping uncertain attendance and duration claims honest.
Problem statement
For this exercise, assume a small NGO schedules volunteers to teach in villages and wants evidence that a scheduled visit happened and how long it lasted. Villages and the office have ordinary voice telephone service, but no Internet is available anywhere in the reporting or verification path.
Only calling is available for remote communication: do not depend on SMS, apps, GPS, IoT devices or biometric equipment.
Design a low-cost process and local office system for start and end reports, optional corroboration through registered adult village contacts, and staff review. The office may use an existing local computer and a paper fallback.
Keep the volunteer's claimed start/end times separate from the times the office receives calls. Explain what the evidence supports and what remains unknown: two calls, a caller number, a PIN or an agreeing contact cannot establish continuous presence or prove that teaching occurred.
A missed call must not become either a verified visit or proof of absence.
The illustrative workload and policies below are practice assumptions, not a recovered official interview answer. Consider redials, conflicting accounts and an office-computer restart. A recorded report needs a stable receipt; repeating a call must not silently create another visit or overwrite earlier evidence.
Do not collect pupil records or add Internet access to make the problem easier.
What to build
- Accept start and end reports for a scheduled teaching session through voice calls, record claimed and received times separately, and provide a stable receipt after durable recording.
- Let staff inspect original reports, late or missing phases, corroboration and disputes without treating a claim or a call receipt as conclusive attendance or teaching evidence.
- Support staff callbacks to pre-registered adult village contacts and preserve what each person actually reports, including uncertainty or disagreement.
- Reconcile redials, corrections and paper records after an office outage without duplicating sessions, losing acknowledged evidence on an ordinary restart, or silently replacing conflicting claims.
At scale
- Illustrative workload: 100 scheduled sessions per day across 20 villages, with one start and one end reporting phase per session and up to 20 completed audit callbacks on a normal day.
- One office operator works an 8-hour day. Target at most 60 seconds of connected call time per normal report or audit; enforce a 300 connected-call-minute daily budget across reports, audits, retries and exceptions. The nominal 220 minutes leaves 80 minutes for exceptions, not a guarantee that every attempt succeeds.
- No Internet in the critical path and no new specialist field devices. Reuse ordinary phones, an existing office computer and pre-numbered paper forms; a simple local implementation is sufficient.
- Survive an ordinary office-process or computer restart without losing an acknowledged local report. During an office-computer outage, accept explicitly identified paper receipts and reconcile them later; busy lines and exhausted call capacity can leave sessions pending for staff review.