Safety Management in Field PM: JSAs, Incidents, and TRIR

The disconnect most safety programs run on

Most contractors have real safety content — JSAs written for the work, toolbox talks delivered weekly, incident reports filed when something happens. What they usually lack is a system that ties it together. A JSA signed on paper by six crew members proves nothing three months later if it cannot be pulled up and matched to the actual work being done that day. A toolbox talk log kept in a binder in the site trailer is functionally invisible to anyone not standing in that trailer.

The consequence shows up at the worst possible time: an OSHA audit, an insurance renewal, or a prequalification questionnaire asking for TRIR and DART rates the safety manager now has to calculate by hand from files scattered across job sites, trucks, and email threads.

JSAs and toolbox talks, captured where the work happens

Field PM's <a href="/features/form-library">form library</a> includes pre-built JSA and toolbox talk templates a foreman can pull up on a phone before work starts, walk the crew through, and capture e-signatures from everyone present — no paper, no separate sign-in sheet that has to be scanned and filed later.

Because these live in the same system as daily reports and the project record, a JSA for a specific scope of work is tied to that project and that date automatically, and a safety manager can pull every JSA delivered on a job — or across the whole company — in seconds instead of requesting files from every site.

Incident reporting with e-signature hold points

• •Structured incident report captured from the field at the time of the event, not reconstructed later from memory
• •E-signature capture from the injured worker, witnesses, and supervisor, built into the same form
• •Classification captured at intake — first aid, recordable, DART (days away/restricted/transferred), or near miss — so the OSHA log math has the right inputs from day one
• •Routing and review built in, so an incident does not sit unreviewed because it went to one manager's inbox and got buried

TRIR, DART, and EMR calculated from real data

TRIR (total recordable incident rate) is calculated as (Number of Recordable Incidents x 200,000) / Total Hours Worked — the 200,000 representing 100 employees working 40 hours a week, 50 weeks a year, the OSHA-standard base rate. DART rate uses the same formula but counts only incidents resulting in days away, restricted duty, or job transfer.

Both numbers are only as good as their inputs: an accurate recordable-incident count and an accurate total-hours-worked figure. Field PM already has hours worked from the geofenced <a href="/features/time-clock">time clock</a> and cost-coded daily reports, and incident classification from the incident report form, so TRIR and DART calculate directly from data the system already has — not a spreadsheet a safety manager rebuilds once a year from separate hour totals and incident logs.

EMR (experience modification rate) is calculated by the insurance carrier from several years of claims history, not something software calculates directly — but clean, complete incident records and accurate payroll/hours data are exactly what keeps an EMR calculation fair, since missing or miscategorized incidents and hours are a common source of a worse-than-deserved rate.

Why this belongs in the field PM system, not a separate safety app

The reason to keep JSAs, toolbox talks, and incident reports inside the same system as daily reports and job costing — rather than a standalone safety app — is that a foreman is already opening that system every day. A separate safety-only tool is one more login, one more app crews forget to open, and one more place data has to be reconciled from at reporting time. Field PM's <a href="/features/safety">safety module</a> is part of the same daily field workflow crews already use, so the safety record gets built as a byproduct of normal daily use, not as an extra task competing for attention.