Key Takeaways
- TCIR and DART rate are lagging indicators. They measure what was recorded, not whether any root cause behind those incidents was corrected. A project with declining TCIR may still carry an unresolved corrective action backlog.
- On construction and engineering projects, the accountability gap between filing an incident report and verifying a corrective action closed is where repeat incidents originate.
- Corrective action tracking software assigns each CAPA to a named owner with a deadline, requires a second party to verify the fix, and records the closure with a timestamp, producing an audit-ready record the incident log does not contain.
- CAPA closure rate is a leading safety indicator. When more corrective actions are opened than closed, the pattern is visible before the next incident occurs.
- ISO 45001:2018 clause 10.2 and ANSI/ASSP Z10.0-2019 require organizations to document, investigate, and take corrective action on incidents. OSHA’s injury and illness recordkeeping rule, 29 CFR Part 1904, does not.
Your end-of-quarter safety review shows TCIR trending down and 4 fewer recordable incidents than the previous quarter. 3 corrective actions from 8 weeks ago are still open. Nobody has confirmed whether the conditions they were written to address have been fixed, and the review will close without anybody asking.
Incident counts measure what was recorded, and corrective action closure measures what was done about it. On an active project with several trade contractors, those 2 records diverge. A site that records every incident and closes no corrective action ends the quarter with a well-maintained log and a hazard pool nobody has addressed since the first report.
That gap is where repeat incidents come from, and it is visible in your own data long before the next one happens. The count of corrective actions still open is the data that shows it. Most project teams never put that count next to their incident rate.
What Incident Counts Measure on an Engineering Project Site
Why TCIR and DART Are Lagging Indicators
The Total Case Incident Rate multiplies recordable cases by 200,000 and divides by total hours worked, giving a rate per 100 full-time equivalent workers. The DART rate applies that same formula to cases involving days away, restricted duty or job transfer. Both are derived from your OSHA 300 log, and both describe the same thing.
What it measures | Source | What it cannot tell you |
|---|---|---|
TCIR, recordable cases per 100 FTE | OSHA 300 log | Whether any cause was corrected |
DART, days away and restricted duty | OSHA 300 log | Whether the condition still exists |
CAPA closure rate | Corrective action record | Both of the above |
Neither figure tells you what happened after an incident was recorded. The Bureau of Labor Statistics reported a private-industry TCIR of 2.3 per 100 full-time equivalent workers in 2024, the lowest in a series running back to 2003. That national trend reflects real improvement and says nothing about any single site. Your own site has its own number and its own backlog of open actions.
At project level, TCIR counts what was documented in 3 months. Whether any condition behind them changed is a separate question, and the rate cannot answer it. Your corrective action record is where that question gets its answer.
Construction and engineering projects create a sharper version of that gap, because site conditions change every few weeks as work advances from groundwork through structure to finishes and handover. Each phase hands the next a different set of exposures. A condition left open across that handover is an open condition in a changed environment.
A corrective action opened during excavation and still unverified when structural trades arrive is that case. Your TCIR will not surface it, because the rate counts events and not open conditions. A corrective action record surfaces it on the day it goes overdue. By then the excavation crew has usually left the site.
Large projects carry a second limitation in their aggregate TCIR. A structural steel crew, a concrete placement team and a finishing electrical contractor on one site generate different incidents at different rates, and a site-level figure averages all 3 together. The average describes none of them.
Seeing TCIR only at that aggregate level leaves you unable to say which trade sequence produces the volume in a given phase. Corrective action tracking organized by trade and hazard category answers it directly, which an incident log cannot do at any level of manual effort you put into reading it. Each trade then has its own open-action count and its own overdue list.
Why Engineering Projects Lose Safety Performance Between the Incident Report and the Fix
The Accountability Gap That Keeps Hazards Open Longer Than They Should
The standard post-incident workflow moves through 4 steps and stalls at the last one, and the stall is always in the same place. The first 3 steps produce a record, and the fourth produces a change on site. Those 4 steps run in this order.
- The incident is recorded on the OSHA 300 log
- An investigation is opened
- A corrective action is identified and assigned, verbally or by email or as a spreadsheet note
- Confirmed closure by a second party, which rarely happens without a system requiring it
Step 4 is the one that decides whether anything changed on site. That gap is structural and not a matter of effort. Most project safety programs manage incident documentation separately from corrective action follow-up, so the record of what happened and the record of what was done end up in different places.
The corrective action ends up in an inbox or a notebook. When that subcontractor rotates off site, the action loses its owner. Nobody notices until the condition produces a second incident.
3 conditions keep that gap open, and all 3 start with a missing owner. Corrective actions get assigned informally, so no system records the owner. No deadline is attached to that owner either, so nothing escalates when weeks pass.
Without a verification step, even work completed in good faith has no proof. An action marked complete by the person who assigned it establishes nothing about the underlying condition. That is the third condition, and it is the one an auditor asks about.
Corrective action tracking changes all 3 conditions at once. Assignment becomes formal, timestamped and tied to a named individual. Closure then requires a second named party to confirm the fix, which is the step that turns a recorded intention into an outcome somebody can verify on the record.
Close Corrective Actions With a Named Verifier
See how KC Safety assigns corrective actions to named owners, tracks each one to second-party verified closure, and connects the fix to the incident record it came from.
What Corrective Action Tracking Software Does That an Incident Log Cannot
5 Capabilities That Turn a Filed Report into a Verified Fix
An incident log documents what occurred under 29 CFR Part 1904. Corrective action tracking software documents what was done about it. The two serve different functions in a construction safety program. Safety incident reporting software that captures what happened without tracking what was done about it covers only the first half of the workflow and leaves the second half to memory.
Corrective action tracking software adds 5 capabilities an incident log does not provide. Each one closes a different part of the gap described above. The 5 parts together cover assignment through to verified closure.
- Named owner and due date per corrective action: every CA opens with an assigned responsible party and a specific closure deadline, so no part of it rests on a general expectation that someone will handle it.
- Automated reminders and escalation for overdue CAs: when a deadline passes, the system notifies the owner and escalates to the next management level without requiring a safety manager to manually follow up on each open item.
- Second-person verification before closure: a corrective action cannot be marked closed by the person who opened or was assigned it; a second named party must confirm the fix with a timestamp before the record closes.
- Audit-ready corrective action record: each CA carries the originating incident reference, the assigned owner, the completion date, and the verifying party, producing a traceable record for insurance review, certification audits, or regulatory inspection.
- Closure-rate analytics by trade, phase, and hazard type: project managers can see which subcontractors, work sequences, and hazard categories generate corrective actions that close on time versus those that accumulate past their deadlines.
How Construction Project Managers Use CAPA Closure Rates to Prevent Repeat Incidents
Using a Leading Indicator to Intervene Before the Pattern Repeats
Your CAPA closure rate is the number of corrective actions verified closed in a period divided by the number opened in it. Anything below 100% means open actions are accumulating faster than closures. A quarterly view hides how fast those actions accumulate.
Tracking that figure beside TCIR shows a pattern neither number reveals alone. TCIR describes how often incidents happen and the closure rate describes whether the response keeps pace, so the pair tells you something each one hides from you on its own. Corrective action tracking for construction projects is what puts both in the same system.
KC Safety holds live TCIR and DART dashboards beside the corrective action record, so a weekly review shows both trends in one view without anybody assembling a report first. The pattern worth watching in that view is divergence between the 2. A rising open-CA count beside a stable TCIR is what that divergence looks like.
What the 2 numbers show | What it means | What to do about it |
|---|---|---|
TCIR flat, open CAs rising | Resolution is behind identification | Review the backlog by trade |
TCIR falling, closure rate above 90% | Both halves keep pace | Hold the current review cycle |
Backlog inside one contractor's scope | The gap belongs to one scope | Raise it with that contractor |
What the 2 numbers show | What it means | What to do about it |
|---|---|---|
TCIR flat, open CAs rising | Resolution is behind identification | Review the backlog by trade |
TCIR falling, closure rate above 90% | Both halves keep pace | Hold the current review cycle |
Backlog inside one contractor's scope | The gap belongs to one scope | Raise it with that contractor |
That divergence tells you where to intervene across the 3 or 4 trades on site. When the backlog concentrates in one contractor's scope, talk to them. Bring the overdue list for their scope to that conversation.
When overdue actions cluster around one hazard type, such as housekeeping on overhead platforms, you target that category before it produces the next recordable event, weeks before the incident rate moves. Tracking software makes that targeting possible, where a spreadsheet cannot. Sort your open actions by hazard category this week and see what clusters.
The TCIR Gap: When a Strong Incident Rate Hides an Unclosed Corrective Action Backlog
What the Incident Count Does Not Show
A site can post a falling TCIR with 30 actions still unverified. The rate measures what was documented in each period and nothing else. Whether any documented event produced an action that was assigned, tracked to a deadline and independently confirmed by a second party is a question the rate was never built to answer.
- A falling TCIR with a rising open-CA count
- Corrective actions closed by the person who opened them
- Actions that lose their owner when a subcontractor rotates off site
- A backlog concentrated in one trade or one hazard category
COMPLIANCE CONTEXT
ISO 45001:2018 clause 10.2 requires adopters to document and investigate incidents. It also requires corrective action to eliminate the root causes. ANSI/ASSP Z10.0-2019 carries equivalent requirements for corrective action documentation and closure verification.
OSHA’s rule at 29 CFR Part 1904 requires recording and reporting. It does not require a corrective action to follow that record. 29 CFR 1910.119(m) requires PSM-covered processes to resolve and document them.
Sources for this section are ISO 45001:2018, ANSI/ASSP Z10.0-2019, 29 CFR Part 1904 and 29 CFR 1910.119(m).
The practical question is what your own safety records document. An incident log answers the first and stops there. A corrective action record answers the second.
Projects that close this gap do not necessarily record fewer incidents in the first period. The immediate effect is documentation showing the program resolves the hazards behind the incidents it records, which is a different claim from a lower rate and a more durable one. That documentation is what an insurer or a certification auditor asks to see.
Across 2 or 3 reporting periods that resolution record produces a different pattern. Recurring hazard types appear less often once their root causes close. The ones left open in somebody's inbox keep returning.
Setting up Corrective Action Tracking for Construction Projects Before the Next Incident Cycle
The Configuration That Makes Every Future Fix Verifiable
Configuration for a construction or engineering project covers 3 elements. All 3 work better in place before your first incident. Build them into the project setup during mobilization, before the first crew arrives.
Ownership mapping is the first of the 3 elements. Every hazard category in scope gets a default responsible party. When an action opens, it routes to the mapped owner for that hazard and work area without waiting for somebody on site to decide who handles it and when.
Verification requirements are the second of the 3 elements. A second named party has to confirm each action before the record closes, and that confirmation is timestamped and attached to the action, which stays linked to the originating incident. The person who opened the action cannot be the one who closes it.
At 30, 60 and 90 days the system prompts a re-check. An action noted as done on day 12 stays open regardless. Those prompts keep a stale sign-off from passing as a closed record.
Closure-rate dashboards are the third of the 3 elements. The analytics view breaks open counts and overdue rates down by trade. Configure that view at the start of the engagement, before the first action opens. Your leading indicator is then visible from the first week of data.
A project running corrective action tracking from the start of an incident cycle will not necessarily record fewer incidents in month 1. It will produce the record an auditor asks for. Across a whole project that record is what separates a program with documented, verified resolution from one carrying a tidy incident log and an unresolved backlog behind it.
CAPA and Incident Management for Engineering Project Sites
Corrective action tracking built for teams managing safety across complex, multi-trade environments. The 6 capabilities below cover assignment through verified closure. Each capability maps to one step in the loop described above.
- CAPA workflow with named owner and deadline: every corrective action opens with an assigned responsible party and a due date; no informal assignments.
- Second-person verification at 30, 60, and 90 days: closure requires independent confirmation; re-check prompts prevent actions from going stale after initial sign-off.
- Live TCIR and DART dashboards: incident rate metrics and CAPA closure rates in the same view, updated in real time.
- OSHA 300, 300A, and 301 auto-generation: recordkeeping forms generated directly from incident data, with no manual log reconstruction.
- Automated retraining: when a corrective action includes a training requirement, the retraining assignment is triggered in KC LMS and completion is tracked as part of the CAPA record.
- Multi-trade tracking: ownership mapping, escalation routing, and closure analytics organized by contractor, phase, and hazard type.
Projects that close corrective actions reliably connect the finding to the training that follows it. Our work on what construction incident reports reveal about training gaps covers the pattern, and our piece on standardizing safety across every site covers the program around it. Teams across construction and engineering run the same loop.
Frequently Asked Questions
1. What is corrective action tracking software and how is it different from an incident log?
An incident log documents what occurred. It captures the date, nature, and severity of a workplace injury or near-miss. Corrective action tracking software documents what was done about it. It records who was assigned to address the root cause, what the deadline was, who verified the fix, and when closure was confirmed. The two tools answer different questions, and safety incident reporting software that covers only the first question leaves the accountability record incomplete.
2. Does OSHA require corrective actions after a recorded workplace incident?
OSHA’s injury and illness recordkeeping rule, 29 CFR Part 1904, requires employers to record and report work-related injuries and illnesses. It does not require a corrective action to follow that record. For Process Safety Management-covered processes, 29 CFR 1910.119(m) does require that incident investigation findings and corrective actions be resolved and documented. ISO 45001:2018 clause 10.2 and ANSI/ASSP Z10.0-2019 require corrective action documentation and closure for organizations that have adopted those standards.
3. What is a CAPA closure rate and how do construction project managers use it?
The CAPA closure rate is the number of corrective actions verified closed in a period divided by the number opened in the same period. A rate below 100% means the project is accumulating open corrective actions. Construction project managers use this rate alongside TCIR to detect divergence. A stable incident rate combined with a rising open-CA count signals that the resolution pace is falling behind the identification pace. Corrective action tracking for construction projects makes this leading indicator visible without waiting for the next recordable event.
4. How does KC Safety verify that a corrective action has been completed on a construction project?
KC Safety requires a second, named party to confirm each corrective action before the record can close. This verification is timestamped and linked to the original incident record. At 30, 60, and 90 days after initial completion, KC Safety prompts a re-check of any corrective action that has not cleared the independent verification step. This corrective action tracking software workflow prevents closure by the same person who opened the action and produces an audit-ready record for each CAPA on the project.
References
- U.S. Bureau of Labor Statistics. Employer-Reported Workplace Injuries and Illnesses, 2024. https://www.bls.gov/news.release/osh.nr0.htm.
- U.S. Bureau of Labor Statistics. Injuries, Illnesses, and Fatalities: Incident Rate Calculator. https://data.bls.gov/iirc/.
- OSHA. 29 CFR Part 1904. Recording and Reporting Occupational Injuries and Illnesses. https://www.osha.gov/laws-regs/regulations/standardnumber/1904.
- Cornell Law School Legal Information Institute. 29 CFR 1910.119. OSHA Process Safety Management of Highly Hazardous Chemicals. https://www.law.cornell.edu/cfr/text/29/1910.119.
- International Organization for Standardization. ISO 45001:2018 Occupational Health and Safety Management Systems. https://www.iso.org/standard/63787.html.