Itemise every container against the datasheet library that 29 CFR 1910.1200(e)(1)(i) requires, apply the part 370 threshold tests at each location, and hold the return an owner or operator signs.
A chemical arrives, and § 370.10(a) keys the reporting duty to the OSHA datasheet.
02
A datasheet is revised, and § 1910.1200(e)(1)(i) wants the chemical list current.
Reason
03
A supplier label arrives revised, and 91 FR 1695 sets the employer date at 20 November 2026.
04
A quantity crosses the reporting threshold, and § 370.20 opens both duties.
05
A calendar year shuts, and § 370.45(a) sets 1 March for the year before it.
Decide
06
A return is assembled, and § 370.42(a) adds a penalty-of-law certification.
07
An extremely hazardous substance lands, and § 355.20 allows sixty days to notify.
Out
08
A release trips a reportable quantity, and § 355.43 says immediately.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent maintains the inventory and tracks the clocks. The owner or operator, or an officially designated representative, certifies under § 370.42(a).
Example workflow
One chemical, container to certification
AgentHuman
1Container evidence receivedSafety data sheets, purchase records, store logs or stock feeds
2Chemical context assembledThe chemical, the location it is stored at, the threshold it answers to and the amount held
3Threshold evidence draftedThe chemical, the tests it was read against, the amounts and completeness
4Controls appliedDatasheet checks, threshold checks, storage-location 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 officer to approve.
Anything thin
Adds a safety manager read first.
Safety review
The chemical is held with its datasheet, its amounts and the store it sits in.
Certify · Append evidence · Send to safety review
Certified — by the owner or operator▼
6Inventory and store records updatedOnly where write access and records policy allow it
7Outcome evaluatedThreshold accuracy, datasheet 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 Tier II return under § 370.42(a).
Deciding a chemical sits below the reporting threshold.
Making the § 355.43 release notification.
Naming the officially designated representative.
Automation boundaryAgent acts unaided
✓Maintain the container inventory against the current.
✓Apply the § 370.10 threshold tests separately at each.
✓Track the 1 March return and the 20 November programme date together.
✓Assemble the return, its page count and the pages awaiting signature.
Nothing is certified or notified except by a named person, inside the agreed boundaries.
Judging whether a mixture is one chemical or many.
Telling a fire department the inventory is complete.
Setting the hazard class a supplier has assigned.
Changes to the inventory, the labels or the datasheets.
Example output
One chemical, annotated
Our EHS incident recordkeeping agent certifies what happened to people; this one certifies what is held in the building.
Inventory line · single chemicalIllustrative example
Chemical
Recorded as
Test
Evidence of record
Confidence
Held for
Above threshold, § 370.10(a)(2)
Read against the datasheet and the store log
Above the reporting threshold
Safety data sheet, 3 August 2026
Held uncertified
The owner or operator, by name
As receivedTaken from the safety data sheet and the store log — it reaches as far as those sources do.
What the record holdsSafety data sheetContainer recordStorage location
Why no certification hereWhether a threshold is crossed is a § 370.10 judgement, not a model output.
ActionCertifyAppend evidenceSend to safety review
What the score decidesBelow the configured threshold a line picks up a safety read before the officer 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 chemicalFrom the store that holds it
03Evidence
Where the evidence is used
A chemical inventory is not an emissions programme: this page records what sits in the building, while Title V permit reporting stays with the manufacturing environmental agent.
01Approved path
One list, two regulators
40 CFR 370.10(a) makes the OSHA datasheet duty the applicability test for part 370, so a single chemical list answers to both.
02Human review
What was checked, and not found
The employee-count criterion at § 372.22(b) was never read verbatim, whether § 370.41 carries a certification of its own stayed unresolved, the exact last-amended date of part 355 could not be pinned, the Federal Register page of the 2023 chemicals-of-special-concern rule was not located, no state fee schedule reached primary text, the claim that every state collects Tier II rather than Tier I remains unconfirmed, and the extremely hazardous substance list, its planning quantities and the reportable quantities behind § 355.33 were not retrieved.
04Build an evidence trail
The chemical, the quantity held and the officer who certified stay on the return.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Chemical and datasheet sourcesSDS library · supplier feeds Product identifiers and labels
Container and storage recordsStore logs · stock records Quantities held by location
Sites and storage locationsProperty system · site roster Storage conditions and coordinates
Agent
Chemical inventory reporting
Reads the datasheets Assembles the return Holds for the officer
Filing and case systemsState portal · ticketing Return, receipt and retention records
Integration availability depends on the client's existing systems and API access.
Agent controls
Six nets between the model and the officer
Six nets hung in sequence, the finest last. Whatever passes every one is drawn in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeNarrow the agent to inventory assembly when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and threshold rules; part 370 was last amended 13 June 2016, 91 FR 1695 of 15 January 2026 moved the employer date to 20 November 2026, and no federal rule sets the Tier II filing channel — each state does, with certification fields of its own.Track
L4TraceabilityRecord each chemical, the datasheet behind it, the location it sits at and every read of the line.Record
L3Officer releaseHold the return for the owner or operator named by § 370.42(a) before § 370.44 sends it to the SERC, the LEPC and the fire department; the hold governs release, not whether a threshold was in fact crossed.Gate
L2Threshold guardrailsTest each chemical against § 370.10 as configured; the lower threshold sits at (a)(1) and the retail fuel thresholds at (a)(2)(ii) and (a)(2)(iii).Restrict
L1Confidence thresholdsRoute a thin line to a safety read first; nothing in 29 CFR 1910.1200 is signed or certified, so the written programme offers no attestation to lean on.Require review
Model coreEvidence assembled — the chemical, the datasheet, the amounts and completeness
L1 – L2Test whether a line may stand
L3Puts the certification in a person's hands
L4 – L5Keep the chemical and the quantity behind it
L6Holds the return uncertified when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the inventory line that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the return a fire officer reads
Depth of coverage ▼
E1Final-output evaluationDid the line record what the store actually holds?
E2Step-level evaluationDid the agent read the right datasheet, the right threshold and the live stock?
E3Tool evaluationDid it read and write the correct container record and the correct return?
E4Confidence calibrationDo low-confidence lines actually attract more safety corrections?
E5Slice evaluationHow does performance change across specific hazard classes?
E6Business outcomeHow many lines needed a correction before the officer certified?
Floor — the inventory the operator answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each pinned at the stage where it first shows.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
KI-03
Stale stock read
The amount read is not the one now in the store.
Stage gathersThe chemicals, the sheets, the amounts and the sites
02 · Reasoning2 modes
KI-04
Threshold called on old stock
A quantity is judged against a superseded log.
KI-06
Mixture read as one chemical
A blend is carried forward as a single entry.
Stage proposesThe chemicals, their thresholds and completeness
03 · Tool / write2 modes
KI-02
Thin line passed forward
A line moves on without the safety read.
KI-05
Bound to the wrong store
A container is filed against the wrong location.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
KI-01
Certified, evidence unrecorded
The record shows a signature but not what backed it.
Stage returnsThe return an officer signs and a fire crew reads
05 · Change / Version1 mode
KI-07
Silent threshold regression
A configuration change moves the threshold, not the line.
Stage tracksModel, prompt, threshold rules and return fields
Sev-1 · a chemical missing from the returnSev-2 · wrong amount reaches the returnSev-3 · source degrades, line held uncertified
A class-level inventory-completeness figure can read clean while flammable liquid stores carry most of the rework. Nestack reports the correction rate by hazard class, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Flammable liquid stores
9.8%
3.6×
Review
Corrosive chemical stores
7.0%
2.6×
Review
Compressed gas stores
4.4%
1.6×
Watch
Cleaning and janitorial stores
1.7%
0.6×
Normal
Bar: correction-rate lift vs. cleaning and janitorial store baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an uncounted drum costs
A cycle ends when the unlisted container is a standing case. That suite is what the next return assembled is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on flammable liquid stores.
02Diagnose
The container in the yard that reached a threshold nobody had counted to is read back until one cause remains.
03Improve
Changes leave numbered, and the chemicals that forced them travel attached.
04Verify
One chemical case still failing is enough to stop the whole release.
05Learn
The case is kept, and the inventory rules are rewritten alongside it.
Learn → DetectThe return edge. The next filing 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, inventory assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Threshold-determination and automation-boundary work.
02Datasheet, container and site sources.
03Chemical-to-datasheet and threshold-rule mapping.
04Container and datasheet ingestion.
05Chemical, location and record binding.
06Completeness scoring and review routing.
07Officer certification workflow.
08Chemical-register system integration.
09Threshold and datasheet cases.
10Guardrails and certification controls.
11Inventory-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 site, one reporting yearProductionProduction inventory workflowAdvancedMultiple sites / entities
Introduced at Pilot
Inventory assembly to your thresholds✓✓✓
Certifying officer release✓✓✓
Container-inventory baseline✓✓✓
Introduced at Production
Reporting by hazard class—✓✓
Certification workflow in your systems—✓✓
Approved write-back—✓✓
Datasheet-library integration—✓✓
Introduced at Advanced
Multi-site chemical stores——✓
Cross-year evidence packs——✓
Large chemical registers——✓
Multi-deadline threshold controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, register size, 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 storage locations and what each one holds→Site mapping and container captureWeek 1
02Representative datasheets, labels and stock records→Record binding, threshold logic and the inventory baselineWeek 2
03Your written programme under § 1910.1200(e)(1)→Threshold mapping, datasheet binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Datasheet, container and site-source assessment, then integration setupWeek 2
05Returns you would not want inspected→Threshold cases and the evaluation suiteWeek 4
06What no chemical inventory may guarantee→Completeness scoring, review routing, guardrails and release controlsWeek 3
07An owner or operator who may sign under § 370.42(a)→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
The bars are drawn to the weeks the work genuinely needs, which is why the fifth carries a pair.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Inventory workflow discovery, threshold mapping and the automation boundaryW2Source integration and the container-inventory baselineW3Chemical assembly, threshold logic and release controlsW4Evaluation suite, threshold cases and failure-mode testingW5Datasheet-library integration, pilot lines and targeted correctionsW6One reporting year run under the site certifying officer, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for. Two of them sit inside week five, because the work does.
At the end of W6When the inventory record validates, Agent Care picks the agent up.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Facilities AI agent
Build an inventory agent around the drum that crossed a threshold nobody counted to.
Show us one storage location and the datasheets behind it. Not a permit programme. A container inventory certified under penalty of law by the owner or operator under 40 CFR 370.42(a), beside a written hazard communication programme that nobody signs at all.
