Designing WCF’s first unified mobile and web inspection workflow for field consultants.
Inspectors relied on handwritten notes, PDFs, and personal devices, causing errors and inefficiency. The team needed a unified mobile and web workflow to standardize inspections, improve accuracy, and reduce manual work.
I designed and launched WCF’s first digital inspection platform for Safety Consultants, replacing a fragmented process of handwritten notes, PDFs, and personal photos. The connected mobile and web experience standardizes inspections, reduces manual effort, and provides a scalable foundation for future workflows.
Safety Consultants conduct on site inspections and create client facing reports, but before this project, each inspector relied on their own workflow mixing PDFs, handwritten notes, and personal photos.
I spoke with two inspectors, Evan and Marcus, to see how they prepare, capture data, and assemble reports. Their feedback revealed consistent pain points:
Consistent pain points:
These insights confirmed the need for a single, connected workflow across mobile and web, letting inspectors focus on the inspection itself rather than managing scattered tools.
I structured both the mobile and web experiences around the inspectors’ real workflow rather than around internal systems or document types. The platform follows a clear progression from assignment intake to preparation, on site data capture, review, and report completion.
Designing the IA around task flow reduced navigation complexity in the field, helped inspectors understand where they were in the process, and minimized the risk of missed steps or incomplete data.
The user flow maps the full inspection journey across mobile and web. Inspectors begin inspections in the field on mobile, then continue seamlessly on web with all notes and photos automatically synced. This flow emphasizes continuity between devices and eliminates duplicate work during report creation.
These screens highlight the first unified inspection workflow ever created for WCF. Before this project, every inspector used their own process, mixing notebooks, PDFs, personal phones, and improvised workarounds. Nothing connected, and no two inspectors handled inspections the same way.
This new system brings everything into one organized, consistent experience that supports inspectors in the field and improves the experience for the businesses they work with.
The mobile experience supports the majority of inspection work in the field. Since no mobile workflow previously existed, inspectors relied on personal habits and improvised tools. The new mobile flow provides a clear, standardized way to conduct inspections while minimizing cognitive load during on site visits.
The mobile flow is where inspectors complete the bulk of their work on site. Since no mobile workflow existed before, inspectors relied on their own habits — handwritten notes, personal photos, half used PDFs, and whatever worked for them. The new mobile experience finally gives them a clear, reliable, standardized way to conduct inspections.
.png)
Starting an inspection from an assigned visit was intentionally designed as the primary path to replace the previously unstructured, inspector by inspector process. By guiding inspectors through a clear starting point, this flow helps ensure inspections are completed consistently and with the correct context.
.png)
Inspectors previously relied on PDFs, notes, and phone photos, which caused errors and inefficiency. I structured the mobile forms to mirror the existing PDFs, keeping familiar questions while handling nested questions in a clear, guided way.
These decisions created a consistent, reliable workflow, reduced errors, and allowed inspectors to be more present with clients.
At the end of an inspection, the app automatically saves all progress in real time, reducing the risk of lost data and allowing inspectors to focus on the visit rather than manually tracking notes or photos.
This flow standardizes how inspections are finalized, prevents errors, and ensures all data is securely captured and associated with the correct visit—solving one of the biggest pain points from the old manual system.
The web experience replaced a fragmented, manual reporting process with a single, structured workflow. Inspections completed on mobile automatically populate on the web, reducing duplicate work and speeding up final submission.
The web experience is designed for review, validation, and completion. Inspections completed on mobile automatically populate on web, reducing duplicate work and improving data accuracy. By mirroring the mobile structure, the web flow minimizes cognitive load while allowing inspectors to carefully validate information before submission.
The web dashboard became the operational hub for inspectors and internal teams, replacing fragmented, inspector-specific workflows with a single source of truth. By centralizing visits and inspections across the company, I reduced time spent searching for records, improved visibility into inspection status, and created a consistent system that scaled beyond individual workflows.
.png)
Starting an inspection on web was designed to support continuation and validation of field work, not duplication. This flow allowed inspectors to pick up exactly where they left off on mobile, reducing rework and enforcing a standardized inspection process across teams.
.png)
The web inspection forms were optimized for review, correction, and accuracy. By mirroring the mobile structure, I minimized cognitive load while allowing inspectors to carefully validate data before submission, improving overall data quality and compliance.
.png)
All photos captured on mobile are automatically synced to the web, streamlining the final stages of inspection.
The end to end screen flow became a core UX artifact for the project. Mapping every mobile and web screen into a single diagram allowed the team to evaluate the experience at a system level rather than as isolated features.
Walking through this flow with inspectors surfaced compliance concerns and edge cases early. Sharing the same artifact with the PM, BA, and development team improved alignment, clarified scope, and reduced ambiguity throughout implementation.
Sharing this flow with the BA, PM, and development team created much stronger alignment. Instead of talking through requirements in pieces, we could anchor every conversation to the actual user path. This reduced ambiguity, clarified scope, and helped the team identify dependencies earlier.
This project strengthened my ability to design end to end workflows within real operational and compliance constraints. Working closely with users reinforced the importance of observing real world behaviors rather than relying on assumptions. I also learned how system level artifacts like end to end flows can significantly improve cross functional alignment and execution.