Critical Incident Notification Tracker

New Critical Alert

Log a critical incident and alert a group within the required time frame. The clock runs from the exact incident time to the moment you send it.

Incident

Property / Site *

Resolver Reference # *

Incident Type (MAJOR classification) *

Exact Time Incident Occurred *

Date and time to the minute. This is the clock start.

Exact Location

Location Zone *

Floor / Level

Specific Location *

Status (tap)

Current Status *

Emergency Services

Injuries

Tenant Impact

Notification

Target Group *

Template

Narrative *

Facts only — no interpretation (Reporting Voice Standard). Most detail is captured by the taps above; keep this brief.

Settings

Your profile and alert preferences.

My Profile

Your contact details and what you see.

Name

Phone

Home Site

See other sites' alerts

Off = only your home site. On = the whole portfolio.

Alerts

Audible + on-screen alert when a critical alert lands, or when your alert gets a reply.

Audible alert

System — Supabase Connection ADMIN

Enter your project URL and anon key to sync across all users. Leave blank to run local-only (this device).

Project URL

Anon Key

Poll interval (seconds)

Table setup: download schema SQL

System — Data ADMIN

Local cache utilities.

About

v1.0.2 — 2026-07-10 — Added an optional Building Property Manager (name · email · phone) to each site, shown on the alert card and in the ledger so leadership can reach the site PM. Added the Brookfield Place towers (200L, 225L, 200V, 250V, 300V); removed the generic BFP site.

v1.0.1 — 2026-07-09 — Added a “How this tool works” page (reachable from the login screen and Settings). Made the form section headers distinct (gold marker + underline). Renamed the action button to “Send Critical Alert.”

v1.0.0 — 2026-07-09 — Production build. Real Supabase Auth (email + password) with Row-Level Security enforcing every role rule server-side. Config (project URL, anon key, poll interval) loads from config.js. Polling pauses when the tab is hidden and catches up on return, to keep bandwidth minimal. Runs in on-device Preview/Demo mode when no config is present.

v0.9.4 — 2026-07-09 — Redesigned the Received alert card for readability. Replaced the cramped three-column top with a clean vertical stack: compact header (RES · ref · elapsed), full-width incident type as the title, and tighter meta with a compressed "Occurred → Fired" time line. No more squeezed, over-wrapping text.

v0.9.3 — 2026-07-09 — Corrected role separation. Executives (Bill, his peers, Brookfield) receive and respond only — they cannot originate alerts. Senders (Property Managers / Security Directors) and admin originate alerts, see the ones they've sent, and append updates.

v0.9.2 — 2026-07-09 — Send is now available to everyone (including executives), so any user can originate a critical alert, see the alerts they've sent in Received, and append updates to them.

v0.9.1 — 2026-07-09 — Login quick-select set to four demo profiles: Admin, Property Manager, Bill Wikstrom, and Brookfield Execs. Added a Brookfield executive to the demo roster.

v0.9.0 — 2026-07-09 — Received Alerts now has search (across ref, incident type, location, site, sender, status, and facts) and a time-window filter — All time, last 24 hours, 3 days, 7 days, or 30 days — with a live count of matches.

v0.8.0 — 2026-07-09 — Replaced the incident types with the true critical-incident taxonomy (fatality, SIF, fire/smoke, active shooter, gunfire, bomb threat / suspicious package, hazmat, workplace violence, elevator entrapment, evacuation, etc.). Admin can now edit every dropdown — Incident Types, Location Zones, Status, Emergency Services, Injuries, Tenant Impact, and Leadership Directives — from Admin → Lists (add, remove, reorder, reset), applied instantly across the form.

v0.7.0 — 2026-07-09 — Senders can now append timestamped updates to their own alert (never erased) — optional status change plus an update note, which alerts leadership and stays on the thread. Settings split: every user has a profile (phone, email, alert sound, and a "see other sites" opt-in); the Supabase/system settings are admin-only. Visibility is now site-scoped — users see their home site by default and can opt in to the whole portfolio. All updates and responses stay attached to the alert with timestamps, visible to execs.

v0.6.1 — 2026-07-09 — Renamed to Critical Incident Notification Tracker.

v0.6.0 — 2026-07-09 — Dropdown-first form to cut typing: Location Zone and structured Status taps (Current status, Emergency services, Injuries, Tenant impact) — the narrative is now one short field a template pre-fills. Added the two-way closed loop: recipients confirm receipt AND send a recorded directive back to the PM (Notify FDNY, Escalate, Call me, etc.), which alerts the PM and is logged to the incident. Responses appear on the feed thread, in the ledger record, and in CSV/JSON export.

v0.4.0 — 2026-07-09 — Re-scoped to an Allied Universal portfolio-wide tool. Added a Site / Property dimension across the whole system: every alert is tagged to a site, every user has a home site, portfolio-level recipients see across all sites. New Sites admin tab, site filter and "By site" analytics roll-up, site columns in CSV/JSON export, and a portfolio roster (site Security Directors / PMs → AU regional leadership). AU-branded.

v0.3.0 — 2026-07-09 — Refocused as a one-way critical-alert tool: removed two-way messaging; Send is alert-only. Senders (Property Managers / Security Directors) push alerts, recipients confirm receipt, receipts + timings feed the analysis. Direction-gated by role (recipients can't send; senders land on Send). Added Title on the roster (PM / Security Director / Executive) and an "By sender" analytics breakdown. Receipt-first language throughout.

v0.2.0 — 2026-07-09 — Added exact structured Location (floor / area / specific), audible + on-screen alert on incoming Resolver notifications, Analytics view (incident type by count, by location, by Property Manager, notification-speed stats: avg / median / worst), and full-detail CSV/JSON export with incident and notification date/time split for review.

v0.1.0 — 2026-07-09 — Initial build. Group targeting (Exec / PM / All-Site), Resolver + Message types, 60-minute compliance clock, per-recipient acknowledgment, Supabase REST sync with ~30s poll, localStorage offline fallback.

Critical Incident Notification Tracker · Allied Universal · v1.0.2 · Build 2026-07-10
Allied Universal Security Services · Portfolio-wide · Issues: jonathan.parham@aus.com

Critical Incident Notification Tracker

How this tool works

A timestamped, portfolio-wide record that proves a critical incident was reported to leadership within the one-hour window — who was told, when, how fast, and what leadership directed back. Resolver documents the incident; this proves the urgent notification happened.

Why it matters

When a critical incident happens, ownership's standard is notification within one hour so they can coordinate the response, protect tenants, and get ahead of it. This tool turns that obligation into evidence — an elapsed-time clock on every alert and a receipt from every recipient.

The three roles

Property Manager / Security DirectorOriginates alerts. Fills a mostly-tap form, sends it, and can append timestamped updates as the incident evolves.

Executive (leadership)Receives alerts with an audible alarm. Confirms receipt (timestamped) and can send a recorded directive back to the sender. Does not originate alerts.

AdminFull access — manages the roster, sites, templates, and every dropdown, and sees the whole portfolio ledger.

Sending an alert

Open Send Critical Alert and pick the site, incident type, exact time, and location — almost all taps.
Tap the status fields (current status, emergency services, injuries, tenant impact) and add one short narrative line.
The clock shows elapsed time vs. the 60-minute rule before you send. Tap Send Critical Alert.

Receiving & responding

An incoming alert sounds an alarm and appears under Received.
Tap Confirm Receipt — that stamps who and when.
Tap Respond to PM to send a recorded directive (Notify FDNY, Escalate, Call me, etc.). It attaches to the alert.

The record

Everything lands in the Ledger: each alert's incident-time vs. notification-time, elapsed vs. the one-hour rule, every receipt, and the full two-way thread — all timestamped and exportable. That is the defensible proof the obligation was met.

Allied Universal · Portfolio critical-incident accountability · Issues: jonathan.parham@aus.com

Critical Incident Notification Tracker

My Profile

Alerts

System — Supabase Connection ADMIN

System — Data ADMIN

About

Add User

Add Template

Add Update

Respond to Property Manager

Add Site