Designing an Enterprise Safety App for Field Operations

Reduce friction at the point of reporting

A hazard can be observed in seconds. If reporting requires too many screens or unclear navigation, the software adds friction at exactly the wrong moment.

Hazard Quick Capture was designed around this constraint. The mobile flow favors a short path to recording the condition, while the backend preserves the information needed for follow-up and reporting.

• Keep the first capture flow short and legible.
• Support evidence without turning attachment handling into the main task.
• Make status and follow-up understandable after submission.

Model safety work as connected modules

Safety operations are broader than incident capture. In HSES, OSM workflows, hazard management, and commissioning each have different data and document needs, but they still belong to the same operational ecosystem.

A modular architecture allows those workflows to evolve independently while sharing identity, storage, reporting, deployment, and monitoring foundations.

Move heavy reporting away from request memory

Large exports can create memory spikes and timeouts when the application tries to load an entire dataset at once. Streaming and pagination let the backend process records progressively, while background processing separates heavier work from interactive requests.

This is an important distinction for enterprise applications: a feature can be functionally correct and still be operationally unsafe if its resource use is unbounded.

Treat document storage as architecture

Attachments and evidence grow with daily operations. Moving documents from server storage to Amazon S3 provided a more scalable boundary, while structured object keys kept files organized by module and entity.

The reconstruct-on-read approach allowed historical documents to remain readable while new storage conventions were introduced. This avoided a single high-risk migration event and reduced disruption to the production system.

• Use predictable object keys based on business context.
• Preserve compatibility with historical document references.
• Separate file storage from application containers.
• Apply encryption and infrastructure controls consistently.

Reliability is part of the user experience

For a field application, usability includes more than interface design. Container deployment, reverse proxy behavior, load balancing, storage access, and production troubleshooting all affect whether a user can complete a safety task.

The HSES work combined Flutter mobile development, React web interfaces, NestJS services, PostgreSQL, Docker, Nginx, AWS infrastructure, S3, and KMS around that operational requirement.