Stage every reported injury beside the criteria it was read against under 29 CFR 1904.7, run both § 1904.39 clocks, and hold the annual summary a company executive certifies.
2Case context assembledThe injury, the establishment it happened at, the criteria it answers to and the day it was learned of
3Recordability evidence draftedThe case, the tests it was read against, the day counts and completeness
4Controls appliedWork-relatedness checks, first-aid checks, day-count checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is certified at any of them — the agent is assembling, and the safety lane opens at the completeness gate.
5DecisionSplits at the completeness gate
Evidence sufficient
Goes to the certifying executive to approve.
Anything thin
Adds a safety manager read first.
Safety review
The case is held with its criteria, its day counts and the establishment it sits at.
Certify · Append evidence · Send to safety review
Certified — by a company executive▼
6Log and case records updatedOnly where write access and records policy allow it
7Outcome evaluatedRecordability accuracy, clock coverage, reviewer corrections and what the read found
Corrections
Each safety correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Certifying the annual summary under § 1904.32(b)(3).
Deciding that a reported case is not recordable.
Making the § 1904.39 report to OSHA.
Choosing which executive may sign.
Automation boundaryAgent acts unaided
✓Assemble a case beside the § 1904.7 criteria used.
✓Run the seven-day entry clock from the day a report.
✓Track both § 1904.39 clocks from the hour the employer learns.
✓Hold the establishment roster that decides which forms are owed.
Nothing is certified or reported except by a named person, inside the agreed boundaries.
Judging whether a case is work-related.
Telling OSHA the log is complete.
Setting the restriction a clinician recommends.
Changes to the log, the summary or the roster.
Example output
One case, annotated
Our construction safety compliance copilot works safe work method statements for a duty-holder; this record is what one injury carried onto the log.
Log entry · single caseIllustrative example
Case
Recorded as
Test
Evidence of record
Confidence
Held for
Restricted work, § 1904.7(b)(4)
Read against the general recording criteria
Restricted work
Incident report, 3 August 2026
Held uncertified
The certifying executive, by name
As receivedTaken from the incident report and the treatment record — it reaches as far as those sources do.
What the record holdsIncident reportTreatment recordRestriction note
Why no certification hereWhether a case is recordable is a § 1904.7 judgement, not a model output.
ActionCertifyAppend evidenceSend to safety review
What the score decidesBelow the configured threshold a case picks up a safety read before the executive sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every caseFrom the site that reports it
03Evidence
Where the evidence is used
An injury log is not a safety programme: this page records what happened and holds the file, and it makes no claim about whether the hazard was ever controlled.
01Approved path
Recordable is a judgement
Recordability is settled against the general recording criteria of § 1904.7, and the agent supplies the rationale rather than the answer.
02Human review
What was checked, and not found
An eCFR banner reporting a 2026 amendment to part 1904 could not be matched to any Federal Register document, the standing of § 1904.12 was left unresolved, the text of directive CPL 02-00-172 was not read, no State Plan variation under § 1904.37 was surveyed, and no injury-rate or recordkeeping-cost figure was confirmed from a primary source.
04Build an evidence trail
The injury, the test it was read against and the executive who certified stay on the log.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Incident and report sourcesReport forms · hotline Supervisor incident reports
Occupational healthClinic records · case notes Treatment and restriction records
People and establishmentsHR system · roster feed Hours and headcount records
Agent
EHS incident recordkeeping
Reads the cases Assembles the log Holds for the executive
Case and records systemsEHS platform · ticketing Log, summary and retention records
Integration availability depends on the client's existing systems and API access.
Agent controls
Six locks between the model and the executive
Six locks turned in order, the last one stiffest. Whatever opens them all is drawn in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeNarrow the agent to evidence assembly when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and recording rules; no section of part 1904 was amended in 2025 or 2026, and the electronic filing duty of 88 FR 47254 has bound since 1 January 2024.Track
L4TraceabilityRecord each case, the criteria behind it, the establishment it sits at and every read of the file.Record
L3Executive releaseHold the summary for a company executive named by § 1904.32(b)(4); the hold governs release, not whether an injury should have been logged.Gate
L2Criteria guardrailsTest each case against §§ 1904.4 to 1904.11 as configured; the first-aid list of § 1904.7(b)(5) is closed, and so is the privacy list at § 1904.29(b)(7).Restrict
L1Confidence thresholdsRoute a thin case to a safety read first; § 1904.32(a) puts the year-end log review ahead of the summary that follows it.Require review
Model coreEvidence assembled — the case, the criteria, the day counts and completeness
L1 – L2Test whether a case may stand
L3Puts the certification in a person's hands
L4 – L5Keep the injury and the test behind it
L6Holds the summary uncertified when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the log entry that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the summary an inspector reads
Depth of coverage ▼
E1Final-output evaluationDid the entry record what the case actually was?
E2Step-level evaluationDid the agent read the right case, the right criteria and the live roster?
E3Tool evaluationDid it read and write the correct case record and the correct log?
E4Confidence calibrationDo low-confidence cases actually attract more safety corrections?
E5Slice evaluationHow does performance change across specific establishment types?
E6Business outcomeHow many cases needed a correction before the executive certified?
Floor — the log the employer answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each fixed at the stage where it first surfaces.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
KR-03
Stale roster read
The headcount read is not the one now on site.
Stage gathersThe cases, the tests, the dates and the roster
02 · Reasoning2 modes
KR-04
Recordability called early
A case is logged before the criteria are met.
KR-06
First aid read as treatment
Care on the closed list is worked as recordable.
Stage proposesThe cases, their tests and completeness
03 · Tool / write2 modes
KR-02
Thin case passed forward
A case moves on without the safety read.
KR-05
Bound to the wrong establishment
An injury is filed against the wrong site.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
KR-01
Certified, evidence unrecorded
The record shows a certification but not what supported it.
Stage returnsThe summary an executive certifies and OSHA reads
05 · Change / Version1 mode
KR-07
Silent clock regression
A configuration change moves the clock, not the case.
Stage tracksModel, prompt, recording rules and log fields
Sev-1 · a fatality report past eight hoursSev-2 · wrong evidence reaches the logSev-3 · source degrades, case held uncertified
An establishment-level recordability figure can read clean while warehouse and distribution sites carry most of the rework. Nestack reports the correction rate by establishment type, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Warehouse and distribution sites
7.5%
3.6×
Review
Manufacturing establishments
5.4%
2.6×
Review
Field and service establishments
3.3%
1.6×
Watch
Office establishments
1.8%
0.9×
Normal
Bar: correction-rate lift vs. office establishment baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a missed case costs
A cycle shuts when the late fatality report is a regression case. That suite is what the next case logged is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on warehouse and distribution sites.
02Diagnose
The strain that was first aid on Friday and restricted duty on Monday is read back until one cause remains.
03Improve
The change ships numbered, and the cases that forced it ride with it.
04Verify
Nothing releases while one touched case entry is still red.
05Learn
It is retained for good, and the recording rules are amended in that same commit.
Learn → DetectThe return edge. The next log is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, case assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Recordability-criteria and automation-boundary work.
02Incident, treatment and roster sources.
03Case-to-criteria and clock-coverage rule mapping.
04Case and treatment ingestion.
05Case, criteria and record binding.
06Completeness scoring and review routing.
07Executive certification workflow.
08Occupational-health system integration.
09Recordability and clock cases.
10Guardrails and executive controls.
11Case-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne establishment, one yearProductionProduction recordkeeping workflowAdvancedMultiple sites / entities
Introduced at Pilot
Case assembly to your criteria✓✓✓
Certifying executive release✓✓✓
Establishment-roster baseline✓✓✓
Introduced at Production
Reporting by establishment—✓✓
Certification workflow in your systems—✓✓
Approved write-back—✓✓
Occupational-health integration—✓✓
Introduced at Advanced
Multi-site rosters——✓
Cross-year evidence packs——✓
Large case loads——✓
Multi-clock notification controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, case volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your establishments and the roster behind each one→Establishment mapping and case captureWeek 1
02Representative incident, treatment and restriction records→Record binding, criteria logic and the log baselineWeek 2
03Your reporting procedure under § 1904.35(b)(1)(i)→Criteria mapping, clock binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Incident, health and roster-source assessment, then integration setupWeek 2
05Logs you would not want certified→Recordability cases and failure testingWeek 4
06What no injury log may establish→Completeness scoring, review routing, guardrails and release controlsWeek 3
07A company executive who satisfies § 1904.32(b)(4)→Certification workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Each width is the time a phase honestly takes and not a layout choice, so week five holds a pair.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1EHS workflow discovery, criteria mapping and the automation boundaryW2Source integration and the recordability baselineW3Case assembly, clock logic and release controlsW4Evaluation suite, recordability cases and failure-mode testingW5Health-record integration, pilot cases and targeted correctionsW6One recordkeeping year run under the certifying executive, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for. The fifth carries a pair because the work does.
At the end of W6Validation closes on live logs, and Agent Care picks up the watch.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Facilities AI agent
Build a recordkeeping agent around the case that changes character between Friday and Monday.
Show us one case and the criteria it was read against. Only § 1904.32(b)(4) says who may certify: an owner, an officer of the corporation, the highest-ranking official at that establishment, or that official's immediate supervisor.
