When a student is hospitalized, missing, or in crisis, the institution reaches for its records — and discovers what "collected at enrollment, never confirmed since" actually means. The parent changed phones. The listed contact moved countries. The form said "uncle" with no language noted, and the uncle speaks no English.
Why emergency data decays
It is collected once, during enrollment, inside a stack of other paperwork — then treated as done. But contact details are perishable: phones change, families move, relationships shift. Nothing in the daily life of the institution touches the data again until the one moment it must work, which is the one moment it cannot be fixed. The gap is invisible by design — incomplete emergency data looks identical to complete emergency data until it is dialed.
What a real collection process looks like
Forms with structured, required fields — name, relationship, country, phone, email, language — so records cannot arrive half-complete. Confirmation dates, so staff know when each record was last verified rather than assuming. Scheduled re-confirmation at natural points: enrollment, re-enrollment, after each break. And access limited to those who need it, because families trust the institution with this data for one purpose.
Seven steps inside SumHubs
You don't have to start from a blank page.
Emergency contact collection is a free SumHubs template — configured with your fields and confirmation rhythm in an afternoon. Request a sample hub to review it.