Field Inspections,
Faster.
Bringing hazard code lookup
into the field.
INSafe consultants spend a significant portion of every site visit manually cross-referencing observed workplace hazards against federal safety codes. The process was slow, error-prone, and relied on paper documentation that made field work unnecessarily cumbersome. The goal of this project was to design a mobile application that allows consultants to enter hazard data and search a structured database directly in the field — dramatically reducing lookup time and improving accuracy.
The app needed to support the full consultation workflow — from logging a hazard observation to linking it with the corresponding federal regulation — all within a few taps, even in environments with limited connectivity.
Looking up codes was the bottleneck.
When INSafe consultants observed a hazard on-site, their next step was to match that observation to the correct federal code — a process that required flipping through printed references or navigating dense regulatory documents. This lookup step was consuming a disproportionate amount of time during consultations, slowing down the entire inspection workflow and creating opportunities for documentation errors.
The existing tools weren't built for the field. Consultants needed something fast, mobile-first, and purpose-built around the actual consultation process — not a digitized version of a paper form.
Looking up a single hazard code could take 10–15 minutes. Multiply that across every observation in a consultation, and you've lost the better part of a workday.
Manual Code Lookup
- Printed regulatory references in the field
- No dedicated tool for hazard-to-code matching
- Time-consuming documentation and error-prone records
Searchable Mobile Database
- Searchable Mobile Application
- Structured data entry form built for field conditions
- Faster, more accurate consultation documentation
Mapping the objects,
defining the structure.
Discovery began by building a comprehensive map of all the objects within the INSafe consultation system. Through competitive analysis, subject matter expert interviews, and a thorough review of existing process documentation, I catalogued every element consultants interact with — from individual hazard observations to the regulatory codes they reference. Each object was then analyzed to define its structure and its hierarchical relationship to other objects in the system.
This object mapping directly informed the navigation architecture — ensuring that users could reach the right items at the right moments within the consultation flow, without unnecessary steps or dead ends.
Objects are deeply nested
The consultation system has multiple layers of nested data — hazards sit under observations, which sit under visits — making navigation design critical to usability.
Navigation must match the workflow
Users move through the consultation process in a defined sequence. The navigation needed to reflect that sequence — surfacing the right data at each step without forcing users to jump around.
From paper process
to structured system.
The object mapping exercise surfaced a key reframe: consultants weren't struggling with the inspection itself they were struggling with how information was organized and accessed. The design challenge shifted from "how do we digitize the form" to "how do we structure access to the right code at the right moment."
What code applies to this hazard I'm looking at?
Manual lookup from printed references. No consistent structure for matching observations to codes. Documentation completed after the visit, introducing recall errors.
How do I get the right code to the consultant at the exact moment they need it?
Structured mobile database with fast search. Navigation designed around the consultation sequence. Real-time data entry at the point of observation.
Defining the navigation structure required alignment across key stakeholders before moving into design. I facilitated working sessions with:
The design decisions that
shaped the app.
With the object map and navigation structure defined, design decisions were made to serve one goal: get the right federal code in front of the consultant as fast as possible, with as little friction as possible.
Design for search, not browse
Consultants know what they observed they need to find its matching code fast. Rather than navigating a category tree, the primary interaction model became a keyword search that returns relevant federal codes instantly.
Structure navigation around the consultation sequence
The object map revealed a clear consultation flow. Navigation was designed to mirror that sequence each screen surfaces only what the consultant needs at that step, reducing cognitive load during active inspections.
Prioritize UI clarity for field conditions
Inspections happen in noisy, high-movement environments. The UI was designed with large tap targets, high-contrast elements, and minimal text input keeping interactions fast and reliable even when conditions aren't ideal.
Color and Logo
UI elements built for
mobile clarity.
The visual design system was built around the constraints of mobile field use. The color palette, app icon, and component library were designed to be immediately legible, functionally distinct, and consistent across every screen in the prototype.
Mockups and prototypes were built in Sketch, with the interactive prototype validating navigation flow and task completion across the key consultation scenarios.
App Icon & Color Palette
A purpose-designed app icon and color system establishing brand identity and visual hierarchy within the mobile environment.
Mockups & Prototype
High-fidelity screen mockups and a fully interactive Sketch prototype demonstrating the complete consultation workflow.
Time savings estimated based on pre/post comparison of average hazard lookup time during SME interviews. Full prototype available for review.
What I'd push
further.
If I were revisiting this project today, I'd invest more time in usability testing with consultants in actual field conditions not just in controlled settings. The object mapping and navigation structure held up well, but real-world use would surface friction points that desk research can't fully anticipate. I'd also explore offline-first functionality more deliberately, since connectivity in industrial settings can be unreliable.
The structured approach to object mapping proved valuable beyond this project it's a method I now apply early in any system-level design engagement. When you understand how the objects in a system relate to each other, the navigation almost designs itself.
When you map the objects first, the navigation writes itself. Structure is the design.
— Michaela Hoffman, UX/UI Designer