Training & certifications
Worker training and certification tracking, with expirations surfaced before a credential lapses on site.
The pre-task plan the crew signs, the toolbox talk the foreman runs, the inspection that passes or fails, the punch item that gets closed — all captured on the same record as the work, time-stamped and attributable. When a recordable happens you already have the JHA, the training, and the observation history. And AOS watches the incidents for the pattern before it becomes the next one.
Incidents are logged where they happen, classified, and rolled into the OSHA 300 by establishment — so the 300A is a click, not a January project. Pre-task plans and JHAs are completed and signed in the field, observations and PPE checks build a history, and root-cause analysis closes the loop with corrective actions and return-to-work tracking.
| Case | Class | Days |
|---|---|---|
| Laceration — hand | Restricted | 4 |
| Strain — back | First aid | 0 |
| Contusion — foot | DART | 2 |
| 300A summary | Ready | post |
AOS drafts the toolbox talk from what's actually on the schedule and the conditions — silica when there's cutting, heat illness when it's August — then the foreman runs it and crew signatures are captured on the spot. The talk, the attendees, and the signatures land on the project record, not a clipboard that disappears into a truck.
Build the ITP per project, set hold and witness points, and gate the work so the next activity can't proceed until the inspection passes. First-piece inspection catches the systemic defect on unit one instead of unit fifty, and the AI spec-book reads the project specifications so an inspector can ask what the spec actually requires.
| Point | Type | Status |
|---|---|---|
| Rebar pre-pour | Hold | Passed |
| Embed layout | Witness | Passed |
| Slump test | Hold | Open |
| Finish — first piece | First-piece | Waiting |
Schedule inspections, record findings with photos and comments, and route each item to the responsible party through to closure. Punch items track the same way, and a RAID register keeps risks, assumptions, issues, and dependencies visible — with a weekly digest and a path to promote an issue into a change order when it turns into cost.
| Item | Type | Owner |
|---|---|---|
| Soil bearing below assumed | Risk | Geotech |
| Long-lead switchgear | Dependency | Electrical |
| Curtain wall RFI open | Issue | A/E |
| Promote → CO-119 | Issue | PM |
Every incident, near-miss, and observation feeds a detector that looks across the data for what a single report can't show — the same injury type clustering on one trade, one shift, one task. When a pattern crosses the threshold it raises an alert and opens a workflow, with weather context where it's relevant. The safety metrics your insurer and your owner ask for are computed, not assembled.
Clusters across incidents, near-misses, and observations surfaced — by trade, task, shift, or body part.
When a trend crosses the line it pages the right people and opens a workflow, not a buried report.
Heat, cold, and storm context attached to incidents and alerts so the cause isn't guessed at.
TRIR, DART, and the rates your insurer wants computed from the log — ready for the owner packet.
Worker training and certification tracking, with expirations surfaced before a credential lapses on site.
Driver qualification and motor-vehicle records tracked for crews behind the wheel of company equipment.
Hot-work and other high-risk permits issued, time-boxed, and logged to the project record.
Safety-meeting attendance and sign-off captured digitally and attached to the meeting.
Site-specific weather alerts flag heat, cold, and storm risk for scope that's exposed to it.
Hold points and inspections gate schedule activities — quality lives in the CPM schedule, not beside it.
30 minutes. Bring last year's OSHA 300 and a current ITP. We'll show you the log, the toolbox talks, the inspections, and what the pattern detector would have flagged.