Skip to content
PortalBase
Yellow hard hats lined up on a bench

Safety compliance software: 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 certs and the fixes in records you can pull up and export.

Also calledSafety compliance, EHS, Audit readiness, OSHA recordkeeping

The real screens

Every problem gets an owner and a date.

A hazard or a bad result turns into a corrective action with who fixes it, by when, and the photos and signature that close it.

A closed corrective action, Get radio 2 working at the Main St flagger station: what was wrong, and the fix Leo Castellan recorded, with when.

Build the steps as a flow.

Steps run down the page, and a decision splits into its answers side by side. Add a step with the plus, test run it, then publish. Start from one of five, or from blank.

The workflow builder showing the Permit request workflow, version 2 published, with Test run and Publish changes. Down the middle, a card that starts by hand, then a card that asks whoever manages work there to decide, splitting into If they pick Approve and Otherwise.

Know who holds what, and what's about to run out.

Every certification shows how many people hold it, how many are expiring and how many have run out. Each person carries theirs on the phone.

Certifications: cards for Competent person, excavation, First aid and CPR, Flagger card and Forklift operator, each with how many hold it, are expiring and have run out, and a tab for the 2 expiring in the next 30 days.
The Certificates tab in the phone app's Training screen: the worker's First aid and CPR certification, good through April 7, 2028, marked Current.

Every number opens the records behind it.

Who signed in, who finished, what's late, by site, crew or role. Click any number to see the records, and export them when an auditor asks.

The Reports overview: 24 people, 24 who signed in, 404 sign-ins (down 2 percent) and 22 using it (up 38 percent), set against the month before.

Sample data from our own demo company.

What the crew sees

The same app, pointed at this job.

Safety and incidents
Forms and logs
Inspections

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.

How a hazard gets handled

From a report to a closed fix

  1. 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.

  2. 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.

  3. Step 3

    Fix it

    The owner attaches a photo of the fix and a supervisor signs to close it.

  4. 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

Incident reports and the OSHA logs.

Incident and near-miss reports, with the investigation attached, feed the OSHA 300 log, the 300A summary and the 301, kept in Reports by establishment.

  • You decide what's recordable. The software never makes that call.
  • Incident reports are live. An incident report is a form kind, kept at least five years. Corrective actions follow from it.
  • The 300, 300A and 301 are in Reports. Built from your incident reports, with PDFs on OSHA's current forms and CSV files for OSHA's online filing. You download the CSV and upload it yourself. PortalBase doesn't file with OSHA for you.

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