
HSE incident reporting in Power Apps is a phone form a supervisor fills in where the incident happened, a Dataverse table that stores it, and Power Automate flows that alert people according to severity, escalate when nobody responds, and track each corrective action until someone else has checked it. The escalation rules matter more than the form.
Most HSE teams already have a reporting form. It is often paper, a Word template or a shared spreadsheet, and the trouble comes afterwards: the report sits in an inbox, nobody is sure who owns the follow-up, and the corrective action agreed at the toolbox talk is never closed.
What should an incident report capture on site?
Only what the person on site knows in the first few minutes: what happened, where, when, who was involved, how serious it looks, what was done straight away, and photos. Root cause, investigation findings and corrective actions come later, from different people, on a different screen. A first screen that asks for everything gets filled in late or not at all.
A workable first screen asks for:
- Type. Injury, near miss, property damage, environmental, unsafe condition. A choice, never free text.
- Site and area. Picked from a list, so reports can be grouped and routed.
- Date and time. Defaulted to now, editable for late reports.
- People involved. Picked from the people records, with a free-text option for visitors and subcontractors.
- Severity. A short scale your HSE lead defines. It drives the escalation, so define it carefully.
- Immediate action taken. One line.
- Photos. Taken inside the app, saved with the report.
Near misses deserve special attention. They are the reports people skip when the form is slow, and they are also the ones that warn you before someone gets hurt. If logging a near miss takes longer than describing it out loud, fewer get logged.
Photo capture on a phone has its own trade-offs, covered in How to Build an Inspection App in Power Apps, together with what changes if your sites have no signal.
Should incidents live in Dataverse or a SharePoint list?
Dataverse, for most HSE systems. Incidents link to people, sites, corrective actions and training records, and injury details are personal information that should be visible to a few people only. Dataverse handles both: real relationships between tables, and security by role. A SharePoint list can work for a simple near-miss log on one site.
| Table | One row per | Links to |
|---|---|---|
| Incident | Report | Site, people involved, reporter |
| Corrective action | Action agreed after an incident | Incident, owner, verifier |
| Person | Employee or regular subcontractor | Training records, incidents |
| Training record | Certificate held | Person, expiry date |
| Site | Location | Incidents, responsible manager |
The link between people and training is the one spreadsheets can't express. An incident involving someone whose certificate has lapsed is a pattern HSE management exists to catch. Keeping incidents and training records in one app is what makes that pattern visible. The HSE management app case study describes an app that brought both together for an industrial operator in the Gulf.
For the general version of this decision, see Dataverse vs SharePoint Lists.
How should escalation work?
By severity and by time. Severity decides who hears straight away. Time decides who hears next when nobody has acknowledged the report or acted on it. Both rules belong to your HSE lead, written down before anything is built, and the flow simply carries them out the same way every time.
A typical shape looks like this. The roles are examples, and the waiting times are left for you to fill in.
| Severity | Told on submission | If nobody acknowledges it in time |
|---|---|---|
| Near miss or low | Site supervisor | Reminder to supervisor, then the HSE lead |
| Medium | Supervisor and HSE lead | Site manager |
| High | HSE lead, site manager, operations lead, and a post in the HSE Teams channel | Senior management |
If a regulator where you operate sets deadlines for reporting certain incidents, start from those deadlines and work backwards. They are fixed, and your internal escalation has to beat them.
In Power Automate this is two flows:
- On submission. A flow triggered by the new incident record branches on severity and sends the notifications in the table. For high severity, post to a Teams channel as well as sending email, so the alert does not depend on one person reading their inbox.
- On a schedule. A flow runs at whatever interval the fastest escalation needs, finds incidents with no acknowledgement recorded, and escalates them one step.
"Acknowledged" needs to be a real field on the record, set by a button in the app, with the person and time captured. Without it, the escalation flow has no way to tell a report that is being handled from one nobody has opened.
How do you track corrective actions to closure?
As their own records, separate from the incident. Each action gets an owner, a due date and a status. It is checked by someone other than its owner before it closes, and the incident only closes once every action linked to it has been verified. That last rule is what stops an incident looking finished when the guard rail still hasn't been fitted.
Reminders follow the same pattern as escalation: a scheduled flow chases actions approaching their due date, then overdue ones, then tells the owner's manager.
Verification is a good use of the Approvals connector, with one design constraint. A cloud flow run lasts at most 30 days, and pending approvals time out after that, according to Power Automate's limits page (checked November 2026). Corrective actions often run longer. Microsoft's guidance on long-running approvals is to store approvals in Dataverse and use two flows: one sends the request with Create an approval (v2), and a second acts on the response, even after the first run has ended.
The general approval pattern, with reminders and escalation, is in How to Build a Power Automate Approval Flow.
What about training and certificate expiry?
Hold training records against the same people the incidents name, with an expiry date on each certificate. A scheduled flow then warns the person and their manager before a certificate runs out. On the incident side, the report can show whether anyone involved held a lapsed certificate on the day, which is a question an investigation always asks.
What licences does an HSE app need?
If it stores data in Dataverse, premium licences for everyone who runs it. Microsoft lists Dataverse among its premium connectors, and an app using any premium connector is classed as Premium, which means each user needs a per app or per user plan (app license designation, checked November 2026).
That includes supervisors who only submit reports, so count them before you choose. A near-miss log on a SharePoint list stays on standard connectors and avoids the cost, at the price of the relationships and security described above.
Frequently asked questions
Can workers report hazards anonymously? Not through the main app, which always knows who is signed in. If anonymous reporting matters to your safety culture, add a separate Microsoft Form that does not record names, and have a flow create the report from each response. Make sure that form is easy to find on site.
Can it produce reports for management? Yes. With the data in Dataverse, Power BI reports on it directly, so incident trends, open actions and upcoming certificate expiries come from the live records rather than from a spreadsheet someone compiles each month.
Should we replace dedicated HSE software with this? If you already have an HSE platform that people use and that fits your process, keep it. Power Apps makes sense when reporting runs on paper, email and spreadsheets, and the company already uses Microsoft 365.
Does it work on sites with poor signal? It can, if it runs in the Power Apps mobile app and is designed for offline use from the start. Decide this before building, because it affects the data model.
Getting it built for your sites
The construction and contractors page shows how this fits with site inspections, snags and approvals, and the HSE management app case study shows one build in detail. If you want to talk through how incidents are reported on your sites today, book a free 30-minute consultation.
Last updated
- Power Apps
- Power Automate
- Dataverse
- HSE
