For the safety lead
Be able to show it was done. Not just say it was.
A claim, an injury or an inspector asks what happened and who knew what. PortalBase keeps the signed forms, the inspection video, the certs and the fixes in records you can pull up and export.
Also calledSafety compliance, EHS, Audit readiness, OSHA recordkeeping
Built from
The products this solution puts together.
What the crew sees
The same app, pointed at this job.
Sample company and data, made up for the picture.
The problem on the ground
The paper exists. Finding it is the job.
Clipboards. The toolbox talk is signed on a sheet in a truck. The sheet is in a binder at the yard.
Texts. The hazard report is a photo in someone's messages. The fix is a call nobody wrote down.
Cert gaps. A forklift ticket ran out last month. You find out when someone's already on the machine.
One record. PortalBase puts who, when, where, what was found and what was done on the same page, offline or not.
What gets recorded
Each safety step leaves a record
Signed forms. Job hazard analyses, toolbox talks and site audits, signed on the phone. A submission keeps the form version it was filled on.
Read more →Inspections. Each step gets Pass, Concern or Fail with a photo or video attached. The record notes who, when and where.
Read more →Certifications. Licenses and tickets are stored per worker with an expiry date. The worker and the supervisor get an alert before one lapses.
Read more →Corrective actions. A failed step opens a fix with an owner and a due date. It closes with evidence and a sign-off.
Read more →How a hazard gets handled
From a report to a closed fix
Step 1
Report it
A worker fills the hazard form on the phone. A QR code on the gate lets a subcontractor do it with no login.
Step 2
Route it
A rule you set sends it to the right person at that site. It can open a corrective action on its own.
Step 3
Fix it
The owner attaches a photo of the fix and a supervisor signs to close it.
Step 4
See it
The safety lead sees what's still open and how long it's been open, by site.
Incidents and OSHA records
Designed for the 300, 300A and 301
Incident and near-miss reports, with the investigation attached, are next on the roadmap. They are next on the roadmap.
- You decide what's recordable. The software never makes that call.
- The 301 is the incident record. It carries the investigation, the root cause and the fixes.
- The 300 and 300A are generated. They're built from your incident records plus each establishment's headcount and hours. Privacy cases keep the employee's name off the log.
What this is and isn't
- Does PortalBase make us compliant?
- No. It records and organizes the evidence. Whether your program meets a rule is still your call, and your auditor's. It doesn't guarantee an audit outcome.
- Can a record be changed after it's submitted?
- Submitted records are append-only. A correction is a new version and the original stays. Every record change and admin action is in the audit log.
- Who can see the records?
- Permissions are set by role and by where someone sits in your company, and enforced on the server. Auditors and executives can get read-only access.
- Can we take our records with us?
- Yes. A company can export everything, records, media and history, in open formats, on its own, any time. Any inspection record also exports to PDF.
Walk us through your safety program
Tell us which records you chase every week. We'll show you how PortalBase would hold them.
Book a walkthrough