My incidents
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
What is a 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. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (worker and safety officer) that shows only what that role should see, and flat pricing with unlimited workers.
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 a register 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 register 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 the corrective action, and marks it resolved, or withdraws a duplicate with the reason written on it. The register stops showing closed incidents whose hazards are still standing in aisle 7.
Approve / reject with a reasonDone by: Safety officer
The parts every portal is built from
Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.
Collect
Forms
Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.
Public pages
An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.
Self sign-up
People create their own account and land in the role you chose for them.
File attachments
Upload and view files on the record they belong to — not in a folder named FINAL v2.
Decide
Approve / reject with a reason
Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.
Status tracker
“Where's my request?” answered as a progress bar on the submitter's own page.
Board by status
Cards in columns. Drag a record to move it along.
Checklists
Task lists ticked off per record, with progress — onboarding runs, inspections, opening duties.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Notes & scores
A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.
Reminders by date
Renewals, expiries and overdue work, in an in-app inbox and by email.
Share
Tables
Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.
People directory
Portraits, names, and roles from a table, shown only to the roles allowed to see them.
Calendar
Records on a month or week view, by date.
Gallery & image grid
Records as cards or photos.
Record pop-up & linked records
A shareable pop-up with a record's details and what's linked to it. Edit, change status, or add a linked record from there.
Notices & info pages
Check-in details, benefits, updates — a page for a role to read.
Counts, totals & averages
Live figures over the rows a viewer is allowed to read.
Control
Role & row access
Own, assigned, managed, and team rows; hidden fields per role. Generated from your description, not configured field by field.
No-Password Doors
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colours, your logo. Members see you.
On purpose
Four things Pory won’t do
A portal runs a program, a service, or a process. These jobs belong to tools built for them, and Pory keeps the records around them instead.
Take payments
Pory tracks who owes what and who has paid. It doesn't collect the money — keep your payment tool for that.
Book time slots
Availability, capacity, time zones, and reschedules are a whole product. Pory holds what happens after the booking.
Host the conversation
No feeds, threads, likes, or polls. A note on a record, yes; a forum, no. Where members talk is another tool's job.
Plan routes
Pory keeps the service record, not the map.
Frequently asked questions
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
Your safety incident reporting portal, live today.
Describe it in a sentence and send the invite. Unlimited workers, flat price.