Incident records built for OSHA, not optics.
Every incident is captured in the detail an OSHA or workers'-compensation review actually requires, alongside daily hazard checks and a fully attributed communication history per employee.
One incident record, five categories of detail.
An incident record is not a single free-text box. It is organized into the categories a compensation claim or an OSHA inquiry will actually ask for.
Employee Details
Full name, sex, date of birth, job title, date of hire, time on job site and in occupation, home address and home phone.
Incident Details
Job name and code, weather conditions, supervisor, incident date and time, specific work area, worker start time, and who conducted the investigation.
Medical & Investigation
Where the worker was treated, the treating phone number, who took the report, and whether a drug test was performed.
Workers' Compensation
DWC first-report-of-injury form status and the dates it was given to and received from the employee.
Injury Information
Body part affected, nature of the injury, and a free-text incident summary, plus who reported it and when.
Up to five photos per incident.
Each incident record can carry up to five photos, attached directly to the record that will be reviewed later.
Named acknowledgements, not a headcount.
A Field Manager authors each daily or weekly meeting, hazard Q&A and damaged-tools or PPE prompts included, and the record tracks exactly which employees, by name, acknowledged it. This is distinct from the punch-in and punch-out Safety Q&A covered on Verification & Enforcement.
Not every incident is the same shape.
The Incident Reports list carries a job code, job name, employee, date and time, attachment count, and an Incident Type column so records can be filtered by what actually happened, not just when.
Near Miss
A close call that didn't result in injury still gets its own incident record, not a footnote on another one.
Equipment
Incidents tied to tools, machinery, or job equipment are typed separately from vehicle or near-miss events.
Vehicle
Vehicle-involved incidents carry their own type, distinct from equipment and near-miss records.
Two categories, one level deeper.
The five categories above are not just headers. The fields underneath them are the same fields a workers'-comp claim or a drug-test policy actually needs answered.
DWC form status, tracked to the date.
The record tracks whether the DWC first-report-of-injury form was completed, the date it was given to the employee, and the date it was received back. A compensation claim doesn't just need the injury on file, it needs the paperwork trail dated.
Drug test performed, yes or no, with an explanation.
Every incident record captures whether a drug test was performed. When it wasn't, the record requires an explanation rather than leaving the field blank, so the reason is on file alongside the result.
A hazard record a crew can't rubber-stamp.
Every Daily or Weekly Safety Meeting is authored by a Field Manager and tied to a specific job and date, with a running count of who acknowledged it. Weekly meetings go further, with instructional copy written to stop the record from being filled out on autopilot.
Daily Safety Meeting
Weekly Safety Meeting
| Attribute | Daily | Weekly |
|---|---|---|
| Keyed to | A single job and date. | A Week Start Date rather than a single day. |
| Author | Field Manager on record. | Same job, same Field Manager as Daily. |
| Hazard Q&A | HAZARDS section, free-text answers including "Any new Hazards?" and "Any damaged tools?", each explicitly attributed as "Answer Submitted by Field Manager." | Its own hazard-identification prompts, in addition to the Daily pattern. |
| PPE / controls | Not a separate section. | Dedicated PPE and controls-mitigation prompts. |
| Incidents section | Not a separate section. | Dedicated INCIDENTS section asking "Did the jobsite have any close calls or incidents?" |
| Acknowledgements | Separate, named Employee Acknowledgements list. | Same named-acknowledgement pattern as Daily. |
Every call and message, logged against the person.
Admins log a call against any employee with an explicit direction choice and notes, building a full timestamped call history on that person's record. Separately, a dedicated per-employee message thread carries the written conversation. Both directions, admin-initiated and employee-initiated, are attributed and timestamped against the specific person.
Call Out logs an admin-placed call, with notes, into that employee's Recent call history.
Call In logs a call received from the employee, attributed and timestamped the same way.
A dedicated "Message with [Name]" thread keeps the written conversation with that employee in one place, separate from the call log.
Onboarding
Activation
Field Execution
Monitoring
Completion
Exit
Safety and incident records accumulate throughout Monitoring and carry through into Completion, where the record has to hold up on its own.
A safety record built
to hold up under review.
We will map Hirebase to your compliance framework,
your ERP and your region.
© 2026 Hirebase. All rights reserved.