From Reporting
to Response.

A reporting system only works when people use it.

Safety reporting had been distributed across multiple forms and processes. That made an already-sensitive task feel more administrative than helpful, particularly when people needed to report a hazard, near miss, injury, incident, or property damage quickly.

I approached the problem as more than a form redesign: how could one familiar entry point make reporting accessible across the organization, improve the quality of information captured, and support more timely follow-through?

The six-to-one figure describes the consolidation strategy developed for the new form, not a verified count of fully retired legacy workflows.

THE DROP: a simpler way to speak up.

The Safety Reporting Form — promoted through the internal THE DROP experience — was designed to capture different kinds of events without making every employee navigate every possible question.

Designing for what happens next.

The form was designed as an easier point of entry, but the operating process had to begin earlier and continue further. A supervisor-focused reporting and response guide developed with the Risk & Benefits Analyst emphasized immediate care, prompt notification, the minimum information needed to act, and continued support through recovery. Reporting should enable that response—not delay it.

Adapted from the jointly prepared supervisor reporting-and-response toolkit. This sequence represents operational guidance, not a claim that each step was automatically orchestrated through the software.

This is a simplified project workflow, not a claim that every stage was automatically integrated or fully deployed.

The 2026 Accident Reporting & Response Process toolkit was co-prepared with Megan Queen, Risk & Benefits Analyst. It documents the existing FastField/manual reporting options at that time and is cited here for the response philosophy—not as proof that the Jotform replacement had been adopted organization-wide.

Building the foundations of an EHS system.

As reporting evolved, I began developing a broader safety-management platform that would bring related work into a more coherent environment: a dashboard for visibility, job safety analysis (JSA) management, reporting, and a separate field-assessment experience for managers and safety staff.

Microsoft 365 applications and Power Automate were part of the broader workflow and integration approach. The available project records do not establish which specific automations were deployed, so this case study distinguishes the platform architecture from proven production integrations.

From collecting reports to creating visibility.

The completed reporting work provided a more accessible route for raising concerns, with a consolidated design and more intentional data capture. The wider EHS platform advanced as a developing system rather than a fully completed rollout.

The financial case also mattered: replacing the legacy FastField approach was estimated to offer substantial annual savings, but that figure was a projection, not verified realized savings. I chose not to present it as an achieved financial outcome.

A form can capture an event. A well-designed system can make it easier for people to speak up, help others respond, and reveal what the organization needs to learn.