Case study / Internal web application

Emergency Services Reporting System

A structured internal reporting platform designed to simplify operational reporting, reduce fragmented manual processes and create a clearer workflow for service teams.

Role
Product design & development
Type
Internal web application
Focus
Operational reporting & workflow
Stack
ReactTypeScriptAPI integration
ems-reporting

Active units

12

Open reports

34

Avg. response

6.2m

Report queue

RPT-2291
Approved
RPT-2290
Submitted
RPT-2288
Draft

Crew status

Unit 04
Dispatched
Unit 02
Available
Unit 07
On call

Project overview

The application was designed for an operational environment where reporting needs to be consistent, fast and easy to complete.

The goal was to bring multiple reporting scenarios into one structured digital interface and guide users through the correct workflow depending on the type of report or operational event.

Summary

  • Internal web application
  • Structured reporting
  • Dynamic forms
  • Operational workflows
  • Data validation
  • API integration

The problem

Operational reporting shouldn't depend on fragmented processes.

  • Multiple reporting scenarios exist across different operational situations.
  • Each report type requires different information and structure.
  • Manual or fragmented workflows create inconsistency between submissions.
  • Users need a fast, clear interface during operational work.
  • Incomplete or incorrect entries need to be reduced through better structure.
  • The system has to stay understandable even as forms become more complex.

Report needed

Identify report type

Manual step

Find correct process

Manual step

Enter data

Validate

Submit

The solution

One structured workflow for different reporting scenarios.

The application uses structured selections and dynamic forms so the user only sees fields relevant to the current workflow.

  • Guided report selection
  • Conditional, dynamic forms
  • Reusable form sections
  • Structured data validation
  • Clear success and error feedback
  • Vehicle, service and crew-related reporting flows
  • Consistent UI patterns throughout
  • API-driven data handling

Select report

Choose context

Fill structured sections

Validate

Submit

Designed around real operational workflows

01

Dynamic reporting flows

Forms adapt based on the selected report type, service context or operational event.

02

Structured validation

Required information and validation rules help reduce incomplete or inconsistent submissions.

03

Vehicle and service workflows

Dedicated flows support reporting around service operations and vehicle changes.

04

Equipment and material sections

Structured categories help organize information related to devices, medication and operational material.

05

Clear system feedback

Success and error states provide immediate feedback after actions and submissions.

06

Reusable interface patterns

Consistent components make complex forms easier to understand and maintain.

The interface

Anonymized examples of the reporting interface, using example units, vehicles and reference numbers only.

new-report

Report type

Incident report
Equipment check
Vehicle change
Shift handover

Equipment check

Unit

Unit 04

Item name

e.g. Defibrillator pads

Condition

OperationalNeeds attentionMissing
Continue
vehicle-change
1
2
3
Vehicle A12
Selected
Vehicle B07
In service
Vehicle C03
Maintenance
feedback

Unit

Required field

Report submitted

Report 2291

Technical approach

Built as a maintainable operational application.

Frontend

React / TypeScript

Architecture

Reusable components and structured form logic

Data

API-driven application workflows

Validation

Client-side validation and structured error handling

Responsive UI

Designed for clear use across different screen sizes

Maintainability

Reusable sections, shared data structures and predictable component patterns

React · TypeScript · API · Component architecture · Form validation

Outcome

A clearer digital reporting workflow.

  • Reporting scenarios organized into one interface
  • Clearer, guided workflows for operational teams
  • Less reliance on fragmented, manual steps
  • Consistent input structure across report types
  • Easier extension of new reporting flows in the future
  • A maintainable, reusable application structure

The project demonstrates how software can simplify a complex operational process without forcing users to understand the underlying system complexity.

Have a workflow that has become too complicated?

A custom application can often replace fragmented spreadsheets, forms and manual steps with one structured system.