Bruno Amorim — Resume
Use the options below to download the file or view it directly in your browser.
Case Study
A mobile and web safety workflow, developed and delivered for Comgás, that replaced paper-based Risk Analysis and Work Permit forms, guiding technicians through eight high-risk scenarios in the field and giving supervisors and office teams a structured record to approve and review.
30-second read
Risk Analysis and Work Permit procedures ran on paper: filled by hand on site, slow to approve, hard to review, easy to lose.
Sole designer: field research, usability testing, stakeholder alignment, flows, UI and the Design System.
Paper forms became conditional flows for 8 high-risk scenarios
Completion works offline, with evidence captured on site
Supervisor approval moved into the workflow
Developed and delivered: mobile + web workflows replacing the paper procedures.
Field research
Before any screen, I went to a Comgás field site to see the process end to end: the printed "PT" (permissão de trabalho) form technicians fill by hand, and the risk-analysis checklist used before starting a task. Digitizing without seeing this would have missed how much of it happens standing up, outdoors, under time pressure.
Key decisions
The paper process wasn't just a form to digitize. It carried safety rules, different risk scenarios and a sign-off step, and it happens outdoors, under time pressure. These were the decisions that shaped the product.
Instead of one long generic form, the flow branches by activity. Each of the eight high-risk scenarios (such as work at height) shows only the questions and checks that apply to it, so nothing relevant is skipped and nothing irrelevant slows the technician down.
The app couldn't assume a connection on site. Technicians can complete the analysis and capture evidence offline, so the safety process never depends on signal.
Approval, which used to depend on paper and signatures, became a step in the flow: the supervisor reviews the same structured record the technician submitted.
Photos, videos and contextual data are attached where the risk is registered, linking what happened in the field to what the office reviews.
Stakeholders and testing
The office and the field didn't share the same picture of the paperwork. Managers had one idea of how it was done (the order of the steps and what came first), while the technicians filling it in on site had another. The product couldn't simply digitize either version; it had to reconcile both.
I ran several alignment sessions with the safety area and field supervisors to bring those two views together into one flow: an order and set of priorities that matched how the work really happens and still gave the office the control it needed.
The second challenge was adoption. For technicians, a new app could easily read as just another way to be monitored. So the flow had to be useful to them first, showing only what applied to their task, working offline and capturing evidence in the moment, instead of adding paperwork. Usability tests in the field checked that it held up in real conditions.
Risk registration
The interface walks technicians through the same questions as the paper form (type of activity, depth, location, risk level) one at a time, so nothing gets skipped under time pressure, and the office team gets a structured submission instead of a scanned sheet.
Evidence capture
Technicians attach photo or video evidence directly to the risk submission, creating a reliable link between what happened in the field and what the office team reviews, instead of a paper form with no visual record.
Web
On the web side, submitted reports, evidence, status, location and operational data come together for managers, replacing scattered paper and spreadsheets with one review environment.
Mobile-first design
Screens stay focused (short forms, clear labels, visible progress), so a technician can complete the process outdoors without unnecessary friction.
Design System and delivery
Eight scenarios sharing the same building blocks needed consistency more than new screens. I created the project's Design System, with components for form steps, evidence capture and EPI checks, so each scenario could be assembled from the same parts.
I handed the flows, components and documentation to development and supported homologation in the team's agile routine, until the app was delivered.
Outcome
The product was developed and delivered, replacing paper-based Risk Analysis and Work Permit procedures with a connected mobile and web workflow, from the technician on site to the supervisor's approval and the office review.
Developed and delivered
Mobile app + web workflows replacing the paper procedures.
Eight high-risk scenarios covered
Conditional flows with offline completion, evidence capture and supervisor approval.
Validated with stakeholders and users
Rules aligned with the safety area and supervisors; flows tested with users.
Design System
Created for the project to keep the scenarios consistent and speed up delivery.
Next project