Attended a ServiceNow Meetup on Health & Safety — Here’s What I have Learn

By Priyanka Umarao

Honestly, when I saw “Health & Safety” on the agenda for the ServiceNow Pune Developer User Group meetup, I wasn’t sure what to expect.

As a ServiceNow developer, I spend most of my time in ITSM, incident management, workflows — the usual. Health & Safety felt like something for a different team. Maybe compliance. Maybe HR.

This article is me trying to put into words what I took away from that session. Not a copy of the slides. Just what actually stuck with me.

The Question That Set the Tone

Priya didn’t open with features or architecture. She asked something simple:

“If a worker on your factory floor noticed something unsafe right now — how would they report it?”

The room got a little quiet. Because when you actually think about it, most organizations don’t have a clean answer. An email? A phone call? A form that lives on a shared drive somewhere?

That one question reframed everything for me. Because the problem isn’t that organizations don’t care about safety — it’s that the systems they use make it hard to act on it quickly and consistently.

That’s the gap ServiceNow Health & Safety is designed to close.

It’s Not Just for Big Industrial Companies

I think one of my assumptions going in was that this module is really only relevant for construction sites, factories, mining operations — places with obvious physical danger.

Priya quickly made it clear that the scope is much wider. The module is built for agriculture, healthcare, transportation, energy, chemicals — basically any industry where people face real risk. And when she listed out the types of hazards the platform covers, I had to stop and think for a second.

Physical hazards like noise and extreme temperatures — okay, expected. Chemical, biological, electrical — sure. But then she mentioned psychosocial hazards. Workplace bullying. Excessive workload. Burnout as a recognized safety risk.

That one genuinely surprised me. And it made the whole thing feel a lot more relevant to more workplaces than I’d originally assumed.

The Two Sides of the Module

The way Priya structured the session made a lot of sense. She split it into two parts — and understanding why helps you understand what the module actually does.

Side 1: After Something Goes Wrong — Incident Management

This is the part most people imagine when they think “safety software.” Someone gets hurt, or nearly does. What happens next?

What I found interesting was how much the design focuses on removing barriers to reporting. The whole point of omnichannel reporting — employees being able to submit incidents from the Now Mobile app, right from their phone — is that if reporting is painful, people won’t do it. Near-misses go unlogged. Patterns don’t get spotted. Problems fester.

The investigation side is equally well thought out. There’s a dedicated workbench where the safety team captures witness statements, injury details, root cause analysis — everything in one structured place instead of across fifteen email threads.

And then there’s CAPA — Corrective and Preventive Actions. This is where a lot of organizations actually fail, not in identifying problems but in following through on fixing them. In ServiceNow, the actions get assigned, tracked, and closed out inside the system. Nobody can quietly drop the ball.

The compliance piece — auto-generating OSHA 300, 300A, and 301 reports — is something I hadn’t thought about before but immediately made sense. Manually pulling together regulatory reports is exactly the kind of high-stress, error-prone work that a platform should be doing for you.

Side 2: Before Something Goes Wrong — Risk Management

This half of the session was where I started paying even closer attention, because this is genuinely the more interesting engineering challenge.

Job Safety Analysis (JSA) — before starting any high-risk task, workers submit a structured analysis through the system. What could go wrong? What controls are in place? It forces the conversation to happen before work begins, not after.

Audits and Inspections — what caught my attention here was the offline capability. Field workers can conduct inspections on mobile even without connectivity, and the data syncs when they’re back online. As a developer, I found myself thinking about how that’s built — and also just appreciating that someone actually thought through the real-world constraint.

Safety Registers — a centralized log of all hazardous materials on site, each linked to its Safety Data Sheet. Sounds basic, but replacing a filing cabinet and a binder with something searchable and accessible on a phone is genuinely useful.

Exposure and Permit Management — these two together are what I’d call the “guard rails” of the module. Exposure tracking watches each worker’s cumulative contact with hazards over time and flags when they’re approaching limits. Permit to Work ensures that before any high-risk activity starts, all the right approvals and checklists are done — not assumed to be done.

What the Q&A Taught Me

The session questions were genuinely good, and a couple of things came up that I’ve been thinking about since.

Someone asked about integration with HRSD. The answer is yes — when a safety incident involves an employee (injury, illness, return-to-work), the connected HR workflows can kick in automatically. It means HR and safety aren’t operating in separate bubbles, which honestly is how most orgs still work today.

There was also an honest conversation about adoption. The technology side is solid. The harder part is getting workers — especially those without desks or devices — to actually use it. That’s a people and change management challenge more than a technical one. But the mobile-first design at least removes one big excuse.

The thing that surprised me most? A few people in the room mentioned their organizations didn’t even know this module existed. Which honestly tracks. Health & Safety doesn’t get talked about the way ITSM or AI does in the ServiceNow community. But after this session, I think it should.

What I’m Taking Back With Me

I came into this session thinking Health & Safety was someone else’s problem to configure.

I’m leaving it thinking it’s one of the most human-centered modules on the platform. Because the people it’s built for aren’t IT managers managing ticket queues — they’re workers in warehouses and construction sites and labs who need to be able to flag something dangerous in thirty seconds, from wherever they are, and trust that it won’t disappear into a void.

When a system like this works well, nobody notices it. Things just don’t go wrong as often.

As a developer, there’s something satisfying about building something that quietly does that.

Thanks to Priya Parwani Gurnani for such a clear and practical session — you made a module I’d never explored feel immediately relevant. And thanks to Gaurav Shirsat, Anubhav Ritolia, and Shreya Wani for putting together an event worth showing up for.

— Priyanka Umarao, ServiceNow Developer