EOC Financial Management Tool
Full-stack web app that lets BC local governments and First Nations communities track EOC response and recovery costs during active incidents and generate EMCR-compliant claim submissions.
Interactive demo
Total expenses
$26,776.25
This period
Claims submitted
3
1 approved
Pending items
12
Awaiting review
Expenses over time
Portfolio simulation using local sample data
Executive overview of totals, claims, and pending items.
Overview
A financial-management application for Emergency Operations Centre (EOC) incidents. It lets local governments and First Nations communities track response and recovery costs in real time and produce EMCR-compliant claim submissions, replacing scattered spreadsheets with a validated, role-aware, multi-tenant workflow. I designed and built it end to end at Innomergence Solutions.
Role: Full stack software developer
Approach & responsibilities
- Owned the full stack: Postgres data model with Row Level Security, server-side data access, React/Tailwind frontend, auth, and middleware.
- Built the Expenditure Authorization Form module covering EMCR EOC Form 530 (expenditure catalogue, BCEMS Response Goals, multi-line estimates).
- Implemented the cost-entry workflow with Response/Recovery classification, Task Number tagging, and automatic per-organization GST rules.
- Wrote unit, integration, and end-to-end tests covering form validation, RLS policies, and incident workflows.
- Ran regular feedback sessions with municipal staff, turning operational pain points into prioritized product changes.
Key features
- Real-time response and recovery cost tracking
- EMCR EOC Form 530 (EAF) with draft → submitted → approved/denied → amendment workflow
- Automatic GST rules per organization type (municipality, First Nations, hospital, school)
- DOCX export matching the official EMCR layout
- Multi-tenant access enforced with Postgres Row Level Security
Architecture
Cost entry (Response/Recovery)
Postgres + RLS
Validation & GST rules
EAF claim grouping
EMCR DOCX export
Challenges & decisions
- Enforcing tenant isolation and role-based access at the database layer with Row Level Security.
- Encoding EMCR claim rules (GST by org type, EAF status flow) without hard-coding one client's process.
- Keeping a compliance-heavy workflow approachable for non-technical EOC staff.
Outcome
- Consolidated scattered spreadsheets into one auditable, EMCR-compliant workflow.
- Shipped to production and shaped directly by ongoing municipal feedback.
Privacy & demonstration note. Screenshots and demo use recreated sample data with fictional organizations and amounts to protect client and organizational information.