Worker
Sees only their own incidents.
- Pages
- Home, My incidents, My briefings, What's being fixed, Safety procedures
- Can start
- Report an incident, New incident
My incidents
Workplace safety incident reporting portal
A safety incident reporting portal is where workers report incidents and near misses from the floor, the safety officer investigates each one on a board, and closes it out once the corrective action is in place. Workers can see where each report they've made stands.
Pattern: RequestsDescribe it to Pory
“Workers at our three warehouses need to report incidents and near misses. Our safety officer investigates each one and closes it out when the fix is in place.”
Viewing as
In plain English
How Pory sets it up
Pory gives every worker and safety officer a sign-in of their own. Each worker sees only their own incidents. It covers report → investigate → close. Incidents, corrective actions, safety briefings and people live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Workers report a near miss before the shift ends, with photos
Near misses went unreported because the form was a Word document on a PC in the site office, and injuries were written up days later from memory. A worker picks what kind of incident it was, when it happened, describes it and adds photos from their phone. It reaches the safety officer as Reported the same shift, while the details are still fresh.
Forms to submit a recordDone by: Worker
The safety officer works each incident from reported to resolved
Open incidents lived in an incident log spreadsheet, and whether an investigation had started depended on who you asked. Every incident is a card in Reported, Investigating, Actions open or Resolved, and the safety officer drags it along, writing investigation notes and corrective actions on the incident itself. The toolbox talk starts from the board instead of a log nobody trusts.
Board by statusDone by: Safety officer
An incident closes only when the corrective action is in place
Incidents were marked closed the moment someone replied to the email, whether or not the racking had been fixed. The safety officer opens the incident, checks each corrective action is Done, and marks it Resolved, or withdraws a duplicate with the reason written on it. The log stops showing closed incidents whose hazards are still standing in aisle 7.
Approve / reject with a reasonDone by: Safety officer
Who sees what in a safety incident reporting portal
Every person signs in to their own view. This is what each role in the demo gets.
Safety officer
Sees every incident in the portal.
- Pages
- Home, Incidents, Corrective actions, Briefings, Incident calendar, Safety procedures
- Can start
- Add a briefing
- Decides
- Marks incidents Resolved or Withdrawn, with a reason
What’s in the safety incident reporting portal template
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Incidents
- Incident (text)
- Type (choice: Near miss, Injury, Property damage, Hazard, Environmental)
- Occurred on (date)
- What happened (long text)
- Photos (file)
- Site (choice: Carson, Fontana, Ontario)
- Severity (choice: Low, Medium, High)
- Reported by (link)
- Status (choice: Reported, Investigating, Actions open, Resolved, Withdrawn)
- Investigation notes (long text)
- Corrective action (long text)
Corrective actions
- Action (text)
- Due (date)
- Incident (link)
- Owner (link)
- Status (choice: Open, In progress, Done)
Safety briefings
- Briefing (text)
- Read by (date)
- Site (choice: Carson, Fontana, Ontario, All sites)
- Worker (link)
- Status (choice: To read, Read)
- What it says (long text)
People
- Name (text)
- Role (text)
- Site (choice: Carson, Fontana, Ontario, All sites)
- Phone (text)
The parts behind this portal
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Collect
1 partForms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Decide
2 partsApprove / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Board by status
Cards in columns. Drag a record to move it along.
Control
3 partsWho sees which records
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
Passwordless sign-in
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colors, your logo. Members see you.
Frequently asked questions
A worker signs in with a link sent to their email and lands on Home. They see Home, My incidents, My briefings, What's being fixed and Safety procedures, and only the incidents that are theirs. From there they can use “Report an incident” and “New incident”.
Safety officer decide: they mark each one Resolved or Withdrawn and give a reason. Everyone else sees the decision and the reason on the record, without the buttons to change it.
You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.
More field service portals
All field service portalsField-service dispatch portalJob → assign → completeInspection reports portalChecklist → photos → defects assignedEquipment maintenance logs portalSchedule & historyCleaning & janitorial portalJob checklists & photo proofLandscaping & pool service portalService visits & each client's historyRestaurant & franchise ops portalChecklists & incident logs
Build your safety incident reporting portal with Pory
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited workers.