Emergency Contact & Sensitive-Info Collector: Current When It Actually Matters

The problem this kills

Emergency contacts have a cruel habit: they're perfectly current right up until the moment you need them, and badly out of date the instant you actually do. The number on file rings a phone that was disconnected two years ago. The "spouse" moved out last spring. The employee who could have told you about a severe allergy is the one person who can't speak right now. And the spreadsheet HR keeps "updating" was last touched when half these people were hired.

The usual fix is an email blast once a year asking everyone to "reply with any changes" — which most people ignore, which HR can't track, and which leaves sensitive medical details sitting in inboxes and reply-all threads. You don't need to live like this, and you don't need to be a developer to fix it.

What you'll build

A simple, secure internal web tool. You import your employee roster, pick a refresh cadence (say, every January), and launch a campaign. Each employee gets a private link to a short form: confirm the contacts already on file with one click ("nothing's changed"), or update name, relationship, phone, and a secondary contact. They can optionally opt in to share sensitive info like allergies or medical alerts — and only if your policy allows it, and only people you've explicitly authorized can ever see those fields.

HR gets a live completion dashboard: who's confirmed, who's updated, who hasn't responded. The tool auto-sends reminders to non-responders on the schedule you set. When an emergency happens, an authorized person pulls an access-controlled CSV with exactly the contacts they need — current, complete, and logged.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how you track employees today, exactly what your roster columns are named, what counts as a "contact" in your world, your headcount and peak onboarding spikes, who is allowed to see medical fields, and the messy edge cases (contractors, multi-site teams, employees with no email) — and then it tailors the data model, the form, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through the roster import, the secure self-service form, the one-click "no change" confirm, the campaign-and-reminder engine, the HR dashboard, the access-controlled export, and the audit trail — each step with a ready-to-copy prompt. There's also a fallback so you can build and run the whole thing today even with no HRIS integration.

The governance it includes (this is the point)

This is sensitive personal data, so it ships with the controls an HR team must have: login so only your team can use the admin side, row-level security so you only ever see your own organization's people, a complete audit trail of who viewed, exported, or changed what and when, and a hard human gate on the part that matters most — any change to who can view the sensitive medical fields requires explicit, signed-off configuration, and medical info is stored only if the employee opts in. The export is access-controlled and logged, so pulling someone's emergency contacts is always a deliberate, recorded action — never a quiet copy-paste. Duplicate guards keyed on employee ID mean each person has exactly one current contact set, never two competing versions.

Who it's for

HR and workplace-safety teams who've felt the specific dread of opening the emergency-contacts file in a real emergency and not trusting a single line of it. If you can describe how your roster is organized and who should be allowed to see medical details, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll have a working refresh campaign you can launch the same afternoon.