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.
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
AgentHuman
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.
5DecisionSplits at the completeness gate
Record complete
Goes to the named official to certify and date.
Anything lapsed
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 required8 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 boundaryAgent 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 employeeIllustrative example
Record
Recorded as
Function
Source of record
Confidence
Held for
Recurrent training, § 172.704(c)(2)
Trained and tested, elements present
Placarded loads
Training provider record, 3 August 2026
Held uncertified
The employer, by name
As receivedTaken from the training provider record and the personnel file — it reaches as far as those sources do.
What the record holdsCompletion dateTraining materialsProvider name, address
Why no certification hereWhether an employee may perform is a § 172.702(b) call, not a model output.
ActionCertifyAppend recordSend to the hazmat desk
What the score decidesBelow the configured threshold the record picks up a desk read before the official 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 recordFrom the system of record behind it
03Programme
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.
01Approved path
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.
02Human review
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.
04Build 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 testingLearning system · courses Provider name and address
RegistrationPHMSA registration portal Certificate of Registration
Personnel and functionsHR systems · job titles Function change records
Agent
Hazmat programme records
Reads the programme Tracks each cycle Holds for the official
Security plan and incidentsPlan revisions · reviews Incident notice records
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 aggregateIllustrative 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 threshold2 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 stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on new hires inside 90 days.
02Diagnose
The plan somebody improved in March, restarting a training clock nobody reset, is read back until one cause remains.
03Improve
Each change ships numbered, and the functions behind it are filed with it.
04Verify
While one touched function case is red the release waits.
05Learn
The case stays on permanently, and the interval rules are amended beside it.
Learn → DetectThe 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.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Hazmat-programme discovery and boundary-setting work.
02Training, registration and plan sources.
03Record-to-section and function-coverage mapping.
04Programme record ingestion.
05Employee, function and source binding.
06Completeness scoring and review routing.
07Named-official certification workflow.
08Personnel and training-system integration.
09Interval and coverage cases.
10Guardrails and employer-signing controls.
11Programme-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 function, one programme yearProductionProduction programme workflowAdvancedMultiple 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 priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, programme scale, 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 hazmat employees and the functions they perform→Roster mapping and record captureWeek 1
02Representative training, registration and plan records→Source binding, cycle logic and the record baselineWeek 2
03Your security plan under § 172.802(b)→Record mapping, function binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Training, registration and plan-source assessment, then integration setupWeek 2
05Records you would not want produced→Interval cases and the evaluation suiteWeek 4
06What no training record may certify→Completeness scoring, review routing, guardrails and release controlsWeek 3
07A named senior management official→Named-official 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
These bands measure real work rather than drawing space, which is why the fifth week is doubled up.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Hazmat programme discovery, record mapping and the automation boundaryW2Source integration and the function-coverage baselineW3Record assembly, cycle logic and release controlsW4Evaluation suite, interval cases and failure-mode testingW5Record integration, pilot programmes and targeted correctionsW6One programme year run under the named security official, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for. The fifth week carries two because the work does.
At the end of W6When the programme record validates, Agent Care assumes the watch.
DurationSix-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.
