Emergency Contact Form Template
The form you hope to never open, holding two emergency contacts and the medical notes that matter, collected once and kept current.
Two minutes now, peace of mind later. We open this only in a genuine emergency, and only the people who would be calling ever see it.
Optional: allergies, conditions, medications. Shared only in a genuine emergency.
Nobody thinks about the emergency contact sheet until the day it is the only thing that matters: a collapse on a job site, an allergic reaction at the office, a missing colleague after a storm. On that day, the gap between a current phone number and a stale one is measured in hours of panic. This form exists to make that day boring, someone opens the record, calls the right person, and coordinates help in minutes.
The thinking behind each field. The employee's own name is phrased "as it appears in our records" because in a genuine emergency someone unfamiliar may be doing the lookup, and nickname mismatches cost time right when time is scarce. Two contacts are the professional standard for one blunt reason: primary contacts travel, sleep through calls, and share office hours with the employee. The relationship dropdown tells the caller who they are about to speak to, which changes how the conversation has to begin. The backup-channel field treats a single phone number as the single point of failure it is. The medical-notes field is optional, purpose-labeled, and free-form: allergies, conditions, and medications can be lifesaving context for responders, and only volunteered information belongs here, never demanded.
What paramedics don't need. Blood type, insurance policy numbers, physician details, and next-of-kin legalities all stay off it. Paramedics do not rely on a self-reported blood type, and the rest turns a two-minute safety net into a medical questionnaire people postpone forever. A postponed safety form protects nobody.
Who keeps one on file. Every employer should. Beyond them come field crews, schools collecting staff contacts, volunteer event teams, and sports clubs. Construction and logistics companies pair it with onboarding, and offices run it as an annual refresh campaign.
Retrieval is the hard part. Collection is the easy half, and this form earns its existence in the ninety seconds after something happens. Decide now how the record gets reached if the form owner is unreachable (many teams keep a current printed export in the site's emergency binder for that exact gap), and run one drill a year: pick a name, find the row, dial the primary number. Drills surface the fixable failures early, a number saved without its country code, a primary and secondary who share one household, and second-contact fields left blank by half the roster.
Keep it current. The refresh is the feature. Stale contacts are worse than none, because they end the search. Re-send the link every January, leave duplicate prevention off so a resubmission supersedes the old record, and sort the responses table by date to see who has not updated. Treat access with respect, since this is a form where fewer eyes is better, so skip the webhook, keep notifications minimal, and let the responses dashboard be the single sealed envelope you hope stays sealed.
Frequently asked questions
How often should employees update this?
Once a year at minimum, plus after life changes like moves, splits, or new partners. Resubmitting the form takes two minutes and the newest response wins.
Is the medical information required?
No, and it should stay optional. The field states its purpose and its audience: volunteered context helps responders, while demanded disclosure only lowers completion.
Who can see these responses?
Only the form owner's account. Keep that owner senior enough, and share details internally only during a genuine emergency.
Can we preload it for our whole team?
Send everyone the same link, and each person submits their own record. The responses table becomes your emergency roster, exportable to CSV for the safety binder.