Transportation AI agent · Hazmat programme
Hazmat Programme Records AI Agent
Pin each training record to the function it covers, run the registration year, the three-year cycle and the annual plan review on one calendar, and hold the programme for the named official.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Named official
- July to June
- After launch
- Agent Care
What this agent does
Assembles the programme, never the certification
In
- 01
A plan is revised, and § 172.704(c)(2) puts in-depth security training within 90 days of that.
- 02
A registration year turns, and § 107.608 opens it on 1 July with the statement due by 30 June.
Reason
- 03
A programme detail moves, and § 107.608(c) leaves 30 days for an amended registration statement.
- 04
A hazmat employee takes a new function, and § 172.704(c)(1) allows 90 days of direct supervision.
- 05
A recurrent cycle comes round, and § 172.704(c)(2) wants training at least once every three years.
Decide
- 06
A record travels in from an earlier employer, and § 172.704(c)(3) wants it current, not historic.
- 07
A security plan sits unread, and § 172.802(c) sets that review annually, not on the training cycle.
Out
- 08
An incident happens, and § 171.15(a) runs 12 hours from it while § 171.16(a) runs from discovery.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The agent holds the programme and tracks its cycles. The employer certifies that a named employee was trained and tested; a named senior management official owns the security plan.
Example workflow
One programme record, source to certification
- 1Training or programme record receivedCourse completions, plan revisions, registration statements and function changes
- 2Programme context assembledThe employee, the functions performed, the section each record answers to and the date it carries
- 3Programme state draftedThe records present, their elements, gaps and completeness
- 4Controls appliedCycle checks, element checks, function-coverage 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 hazmat lane opens at the completeness gate.
Goes to the named official to certify and date.
Adds a hazmat-desk read first.
Hazmat review
The record is held with its gaps, its cycles and the functions it covers.
Certify · Append record · Send to the hazmat desk
Certified — by the named official, dated
- 6Personnel and training records updatedOnly where write access and records policy allow it
- 7Outcome evaluatedElement coverage, cycle coverage, desk corrections and what review found
Corrections
Each hazmat-desk correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Deciding a hazmat employee may perform a function.
- Signing the registration statement on the form.
- Owning the security plan as senior management.
- Judging that an incident is reportable at all.
Automation boundary
Agent acts unaided
- ✓Hold each element § 172.704(d) names, with the date.
- ✓Track the three-year cycle beside the annual plan review it outruns.
- ✓Chase the training record a previous employer has still not produced.
- ✓Flag the plan revision that restarted a security training clock.
Nothing is signed or certified except by a named person, inside the agreed boundaries.
- Deciding whether the whole programme is current.
- Telling an inspector the training is complete.
- Setting the functions a training record is kept for.
- Changes to personnel, training or plan records.
Example output
One training record, annotated
Our freight document processing agent never generates or amends a document; this record is what one hazmat training file held.
Programme state · single employee
Illustrative example- Record
- Recurrent training, § 172.704(c)(2)
- Recorded as
- Trained and tested, elements present
- Function
- Placarded loads
- Source of record
- Training provider record, 3 August 2026
- Confidence
- Held uncertified
- Held for
- The employer, by name
As received
Taken from the training provider record and the personnel file — it reaches as far as those sources do.
What the record holds
- Completion date
- Training materials
- Provider name, address
Why no certification here
Whether an employee may perform is a § 172.702(b) call, not a model output.
What the score decides
Below the configured threshold the record picks up a desk read before the official sees it.
Action
CertifyAppend recordSend to the hazmat deskValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every record
From the system of record behind it
Where the record is used
Our lithium battery shipping evidence agent owns § 172.204 on one consignment; this page is the standing programme that has to be current before anything is offered.
A revision restarts a clock
§ 172.704(c)(2) dates in-depth security training from the day a revised plan is implemented, and leaves 90 days, not another cycle.
What was checked, and not found
No signature or certification clause was found inside § 107.608 itself — what it carries is the year, the operating prohibition and the amendment window, and the certification is executed on the registration form. A final rule published 4 August 2026 allows that certificate in electronic or paper form from 3 September 2026.
Build an evidence trail
The employee, the training that covered them and the employer who certified stay on the record.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Training and testing
- Learning system
- courses
- Provider name and address
Registration
- PHMSA registration portal
- Certificate of Registration
Personnel and functions
- HR systems
- job titles
- Function change records
Agent
Hazmat programme records
- Reads the programme
- Tracks each cycle
- Holds for the official
Security plan and incidents
- Plan revisions
- reviews
- Incident notice records
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six meshes between the model and the official
Six passes, every one narrower than the pass before. What is still there at the end is mapped below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a record may stand
- L3
- Puts the certification in a person's hands
- L4 – L5
- Keep the employee and the training behind it
- L6
- Holds the programme record open when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the record that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the record an inspector reads
- E1Final-output evaluationDid the record carry each element § 172.704(d) asks for?
- E2Step-level evaluationDid the agent read the right employee, the right function and the plan now in force?
- E3Tool evaluationDid it read and write the correct personnel record and the correct cycle?
- E4Confidence calibrationDo low-confidence records actually attract more desk corrections?
- E5Slice evaluationHow does performance change across specific hazmat functions?
- E6Business outcomeHow many records needed a correction before the official certified one?
Floor — the programme the employer answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each named at the stage where it first emerges.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- JJ-03
Stale plan revision read
The plan read is not the revision now in force.
Stage gathers
The employees, the functions, the records and the dates
02 · Reasoning
2 modes
- JJ-04
Record asserted, not shown
A record is called current without its elements.
- JJ-06
Proposed rule read as live
The harmonisation NPRM is worked as settled law.
Stage proposes
The records, their elements and completeness
03 · Tool / write
2 modes
- JJ-02
Thin record passed forward
A record moves on without the hazmat-desk read.
- JJ-05
Element bound to wrong employee
An element is filed against the wrong employee.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- JJ-01
Certified, elements unrecorded
The record shows a certification but not what it covered.
Stage returns
The record an official certifies and an inspector reads
05 · Change / Version
1 mode
- JJ-07
Silent cycle regression
A configuration change moves the cycle, not the record.
Stage tracks
Model, prompt, cycle rules and record elements
- Sev-1 · a record current on no training
- Sev-2 · wrong element reaches the record
- Sev-3 · source degrades, record holds open
Affected slices
New hires absorb the corrections
A function-level coverage figure can read clean while new hires inside 90 days carry most of the corrections. Nestack reports the correction rate by function, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| New hires inside 90 days | 7.1% | 3.6× | Review | |
| Functions changed mid-cycle | 5.1% | 2.6× | Review | |
| Security-plan functions | 3.2% | 1.6× | Watch | |
| Settled placarding functions | 1.9% | 1.0× | Normal |
Bar: correction-rate lift vs. settled-function baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
What a lapsed review costs
A cycle finishes when the lapsed plan review is a standing case. That suite is what the next record kept is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Correction rate rises on new hires inside 90 days.
- 02
Diagnose
The plan somebody improved in March, restarting a training clock nobody reset, is read back until one cause remains.
- 03
Improve
Each change ships numbered, and the functions behind it are filed with it.
- 04
Verify
While one touched function case is red the release waits.
- 05
Learn
The case stays on permanently, and the interval rules are amended beside it.
Learn → Detect
The return edge. Whatever comes next answers to a suite that is 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, record assembly, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Hazmat-programme discovery and boundary-setting work.Week 1
- 02Training, registration and plan sources.Week 1, Week 2
- 03Record-to-section and function-coverage mapping.Week 1, Week 2
- 04Programme record ingestion.Week 2
- 05Employee, function and source binding.Week 2, Week 3
- 06Completeness scoring and review routing.Week 3
- 07Named-official certification workflow.Week 3, Week 4
- 08Personnel and training-system integration.Week 5
- 09Interval and coverage cases.Week 4, Week 5
- 10Guardrails and employer-signing controls.Week 4
- 11Programme-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final 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 tier | PilotOne function, one programme year | ProductionProduction programme workflow | AdvancedMultiple functions / sites |
|---|---|---|---|
| Introduced at Pilot | |||
| Record assembly to your functions | ✓ | ✓ | ✓ |
| Named-official release | ✓ | ✓ | ✓ |
| Function-coverage baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by function | — | ✓ | ✓ |
| Certification workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Personnel-record integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-site programmes | — | — | ✓ |
| Cross-cycle record packs | — | — | ✓ |
| Large hazmat rosters | — | — | ✓ |
| Multi-cycle interval controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, programme scale, approval controls and deployment requirements.
- Separate from build
- Build 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 bring
We build with it
01Your hazmat employees and the functions they perform
→Roster mapping and record capture
Week 102Representative training, registration and plan records
→Source binding, cycle logic and the record baseline
Week 203Your security plan under § 172.802(b)
→Record mapping, function binding and the automation boundary
Week 104Access to relevant APIs, feeds or exports
→Training, registration and plan-source assessment, then integration setup
Week 205Records you would not want produced
→Interval cases and the evaluation suite
Week 406What no training record may certify
→Completeness scoring, review routing, guardrails and release controls
Week 307A named senior management official
→Named-official workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
These bands measure real work rather than drawing space, which is why the fifth week is doubled up.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Hazmat programme discovery, record mapping and the automation boundary
W2Source integration and the function-coverage baseline
W3Record assembly, cycle logic and release controls
W4Evaluation suite, interval cases and failure-mode testing
W5Record integration, pilot programmes and targeted corrections
W6One programme year run under the named security official, then Agent Care handover
- Reading the band
- Each bar covers only the weeks its own work is named for. The fifth week carries two because the work does.
- At the end of W6
- When the programme record validates, Agent Care assumes the watch.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Transportation AI agent
Build a hazmat programme agent around the cycles your named official already owns.
Show us the plan you revised most recently and the training record that ought to have moved with it. A registration year that opened on 1 July and a review dated annually under § 172.802(c) sit on one calendar here.
- Typical delivery
- 4–6 weeks
- Deployment
- Your hazmat roster
- Named official
- July to June
- After launch
- Agent Care available
Nestack Agents · Hazmat programme
AGT-TR-23 · Agent Care available after launch