FireTrack PNG —
Fire Protection Tracking

This showcase explores one place for a fire protection service-trade in Papua New Guinea to track companies, buildings, extinguishers, alarms, and compliance certificates. We built a staff-only web app: five screens — Dashboard, Clients & sites, Assets, Inspections, and Compliance — with full create, edit, and delete, not a display-only mock. The dashboard opens on overdue inspections and certificates in the 30-day window, with CSV export for the week's run sheet. Logging work is a guided flow, Carry out a service visit: pick the site (due sites float first, with access notes like gate keys), tick the assets serviced (overdue items pre-selected), then record pass, fail, or needs-repair with notes. Saving writes an inspection against each asset and rolls last-service and next-due forward from the equipment type's interval. Urgency is computed from today's date every time someone opens the app — assets overdue below zero days, due soon within 14; certificates expired below zero, due soon within 30 — so stored status flags are never the source of truth. Only staff sign in; the first visit creates the admin account and there is no public signup. The app runs on Cloudflare Workers beside a D1 database (Postgres via Neon is a switch, not a rewrite), so hosting at this scale is typically free. This is a showcase, not a live client deployment. Job scheduling, invoicing, SMS reminders, and PDF certificates are in the schema for a later phase and are not in this build.