# Command center for environmental emergency response

> From the call to closure. Crew dispatch, tasks by stage, job safety analysis signed in the field and real-time evidence, in three languages.

Source: https://boosting.tech/en/case-studies/environmental-emergency-response/
The client is not named. We describe the sector, the problem and what was built.

**Case summary:** An environmental emergency response company coordinated incidents by phone, messages and spreadsheets. We built a command center that records the call, dispatches crews and vehicles, assigns tasks by stage and receives evidence from the field in real time. The job safety analysis is filled in and signed on a phone.

- Sector: Environmental and industrial emergency response
- Users: Command center, operational bases and field technicians
- Platform: Installable web system (PWA) with push notifications
- Technology: Ruby on Rails 8, Hotwire, PostgreSQL, Tailwind CSS
- Languages: Portuguese, English and Spanish
- Evolving since: 2025

## What the system does

- Incident intake by the command center
- Dispatch of crews, responders and vehicles
- Incident stages with template tasks
- Job safety analysis with signatures
- Air monitoring during the operation
- Evidence and comments in real time
- Weather conditions log
- Crew workday and attendance
- Safety alerts and technical library

## What was the problem?

In an environmental emergency, the first hour matters most, and that was exactly when information scattered. The call came in by phone, dispatch was arranged by message, and what happened on site only reached the center as loose photos in chat groups. Reconstructing afterwards who did what, and when, took effort.

## What was built?

A command center where the incident is at the center of everything. The center records the call, classifies the incident type and the hazardous products involved, and dispatches crews and vehicles from an operational base. Each incident type already comes with stages and template tasks, so the crew does not start from a blank screen.

The system has two views. The center's view is built for a monitor, with the timeline and task progress. The technician's view is built for a phone, with what they need to do now.

## How does it work day to day?

On dispatch, the technician gets a push notification. Before starting, they fill in the job safety analysis on the phone, step by step, and the crew signs on screen. During the operation they record air monitoring readings, send photos as evidence and mark tasks as done.

At the center, each record appears on the timeline without reloading the page. Weather conditions are logged with the incident. Crew workdays, with check-in and check-out, are tracked in the same system, which integrates with the client's field project management platform.

## What changed in the operation?

The incident now has a single record, with time and author of each action. The job safety analysis stopped being a form filled in afterwards. Crews who speak different languages use the same system, each in their own.

This project uses [custom web systems](/en/services/custom-web-systems/) with an [app](/en/services/mobile-apps/) experience for the field. For another operational safety case, see [port operations](/en/case-studies/port-operations/).

## Frequently asked questions about emergency response systems

### Does the technician need to install an app from a store?

No. The system is installed from the browser and receives push notifications like a regular app.

### How does the system handle several languages?

The whole interface and the technical library exist in Portuguese, English and Spanish. The user picks a language, and incident content stays in the language it was recorded in.

### Can the tasks for each incident type be adjusted?

Yes. Stages and template tasks are configured per incident type, and the center can add specific tasks during the operation.