Emergency Contact & Call-Tree Manager
Build an internal tool that keeps your emergency contact list and call-tree current, nags people to confirm their details on a schedule, and runs test notifications so you find dead numbers before a real event does.
A live, login-protected tool where you import contacts and your call-tree, send scheduled "confirm your details" requests, run test notifications that record who acknowledged, approve the active version, and export the current tree and test results as CSV.
Before you start
- A free Vercel account
- A free Supabase account
- A free Resend account (with a sending domain or the test sender)
- Your current contact/roles list and call-tree as a CSV or Google Sheet
The problem this kills
Your emergency contact list looks fine right up until the moment you need it. Then you discover the cell number on the sheet belonged to someone who left eight months ago, the night-shift lead's "alternate" is a disconnected line, and nobody is sure whether the call-tree spreadsheet in the shared drive is the one that's actually current.
Continuity and EHS teams live with this. The list rots quietly between drills. People change phones, change roles, change sites. The spreadsheet gets copied, edited, and re-copied until there are five versions and no clear owner. And the only way you ever find out it's broken is during the event itself - which is the worst possible time.
This tool keeps the list honest. It asks everyone to confirm their details on a schedule, it actually test-fires the tree and records who acknowledged, and it flags the dead numbers and silent contacts so you can fix them while it's calm.
What you'll build
A small, login-protected web app that:
- Imports your contact/roles list and your call-tree structure (who calls whom) from a CSV or Google Sheet.
- Keeps an alternate contact for every person, so there's always a backup path.
- Sends scheduled "please confirm your details are current" emails via Resend, and tracks who confirmed, who updated, and who never replied.
- Runs a test notification down the tree and records who acknowledged - so you get a real reach rate, not a hopeful guess.
- Flags unconfirmed, bounced, and never-acknowledged contacts so you know exactly where the tree is weak.
- Routes every contact change and every tree edit through the continuity manager for approval before it becomes the active version used in a real event.
- Exports the current call-tree and the latest test results as clean CSVs.
What's inside the Implementation Plan
The plan is a complete, paste-and-go runbook for an AI coding agent (Claude Code). You don't write code - you paste the plan, answer a few questions, and the agent builds the tool with you.
- It opens by interviewing you about your business. This is the part that makes it yours and not a generic template. Before it builds anything, the agent asks how your call-tree is structured today, what systems and spreadsheets you keep contacts in, how you name roles and sites, your typical and peak group sizes, who's allowed to approve the active version, and the messy exceptions (shift coverage, contractors, multi-site people). Then it reads a short tailored spec back to you and waits for your thumbs-up.
- A clear definition of done so you know when you're finished.
- Step-by-step build instructions, each ending with a ready-to-paste prompt.
- A simple architecture diagram so you can see how the pieces fit.
- A "No API yet?" fallback that runs the whole thing off a CSV/Google Sheet import and a clean CSV export - so it's fully buildable today, with no integration to your existing system.
- A verification checklist to prove the tree actually reaches people.
The governance it includes (this is the point)
This isn't a toy. The plan bakes in the controls a continuity program needs:
- Login so only your team can use the tool.
- Row-level security so each organization only ever sees its own contacts and tree.
- A complete audit trail - who changed which contact or tree edge, and when.
- A human approval gate - the AI and your people draft updates, but nothing becomes the active emergency version until the continuity manager reviews and approves it.
- Duplicate guards - person-id is the dedupe key, so the same person can't be imported or processed twice.
Who it's for
Business continuity and EHS teams who own the emergency notification list and the call-tree - the people who get blamed when the tree doesn't reach someone, and who'd much rather find the dead numbers during a quiet Tuesday test than during a real incident.
You don't need to be technical. If you can fill in a spreadsheet and answer questions about how your team works, you can build this.
You've got this - paste the first prompt and let the agent interview you.