By Sagar Shankaran, Founder of CallSphere
Driver screening tools and cab-facing cameras put carriers under Illinois, Texas and NYC rules in 2026. What to document, and what is genuinely out of scope.
Key takeaways
Every carrier owner I have talked to since January has the same reaction to AI regulation: we haul freight in 48 states, we don't sell software, none of this is aimed at us. Broadly, correct. The August 2, 2026 compliance date under the EU AI Act is not coming for a dry van fleet running Dallas to Chicago. California's SB 53, which took effect January 1, 2026, targets the companies building the largest AI systems — you are not one of them and you never will be.
But there are two AI systems already running in your operation that were bought by two different people for two different reasons, and both of them make findings about human beings. That is the category state legislatures went after. The rule that matters for a carrier is simple: regulation in 2026 follows AI that makes or influences decisions about people — drivers and applicants — not AI that routes trucks.
First, driver recruiting. If you run applications through Tenstreet or DriverReach and anything in that flow scores, ranks, filters or auto-rejects applicants — a screening rule on employment gaps, an automated MVR or PSP read, a "fit" score — that is an automated tool influencing an employment decision. Illinois amended its Human Rights Act effective January 1, 2026 to reach exactly this, including a specific prohibition on using zip code as a proxy. Colorado's law covers consequential decisions in employment. New York City has required bias audits and candidate notice for automated employment decision tools since 2023, and if you recruit drivers in the five boroughs it applies to you regardless of where your terminal is.
Second, the cameras. Driver-facing units from Samsara, Motive or Lytx that detect faces, eyes or identity are collecting biometric identifiers. Illinois's biometric statute has been the most expensive law in this industry for a decade and it applies to your drivers, not your customers. Texas has its own biometric identifier law, and Texas TRAIGA took effect January 1, 2026 with its own requirements on biometric handling and on intentionally discriminatory AI use.
Neither of those was bought as "AI." One was bought by a recruiter to fill seats. One was bought by the safety director to get an insurance credit. That is exactly why they never got reviewed.
flowchart TD
A["List every AI tool touching a person"] --> B{"Does it score or filter driver applicants?"}
B -->|Yes| C["Notice, human review, audit trail, Illinois and NYC rules"]
B -->|No| D{"Does it capture faces or eye tracking in the cab?"}
D -->|Yes| E["Written consent, retention and destruction policy"]
D -->|No| F{"Any EU-based driver, applicant or employee?"}
F -->|Yes| G["Review EU AI Act obligations before August 2"]
F -->|No| H["Log the decision and the date, revisit annually"]
Not a compliance program. A folder. For a 60-truck carrier, the honest list is short enough to finish in an afternoon:
Hear it before you finish reading
Talk to a live CallSphere AI voice agent for logistics in your browser — 60 seconds, no signup.
California SB 53 applies to developers of the largest frontier AI systems. You are a deployer of somebody else's tool. It is not your obligation.
The EU AI Act reaches US companies whose systems affect people in the EU. A domestic carrier with no EU drivers, no EU applicants and no software product sold into Europe is outside it. The exceptions are narrow but real: a cross-border operation with EU-based employees, or a carrier that has built a tool it licenses to European customers. Systems already on the market before the obligations applied may be grandfathered from some requirements — do not assume that saves you, but do not panic either. Read the August 2 date as "check whether you touch the EU at all," not as a deadline you are already behind on.
Route optimization, load matching, predictive maintenance on your own equipment, fuel purchase routing, and rate forecasting are not decisions about people. They carry no notice or consent obligation. Nobody is coming for your PC*MILER settings.
One more thing owners ask about weekly: yes, there has been talk of federal preemption of state AI rules. As of July 2026 it is unsettled. State law binds you today, and building your folder around the state you actually operate in is the only defensible position.
The cost side is small and knowable. The exposure side is a multiplier, which is what makes it worth an afternoon.
| Safety director time to build inventory and consent forms | 6 hrs |
| Recruiter time to add notice and reviewer sign-off | 3 hrs |
| Loaded hourly cost | $54/hr = $486 |
| Outside counsel review of two forms | ~$1,500 one-time |
| One-time cost | ~$1,986, plus about an hour a quarter |
| Drivers seated today | 60 |
| Annual turnover at 70% | 42 replacements/yr |
| People whose faces were captured over three years | ~186 |
Assumptions: 60 seats, industry-typical turnover, and cameras running the whole period. The point of the last line is not a dollar figure — biometric statutes assess damages per person, per violation, and I am not going to invent a number for you. The point is that the multiplier in a trucking company is not your customer count, it is your driver count times your turnover, and in this industry that number gets large fast. A signed consent form at orientation costs four minutes per driver.
Adverse hiring decisions. If a screening tool ranks an applicant out, a person reviews it and that review is documented. This is the one place where several statutes converge on the same answer, and it is also plain good practice — the driver market has not loosened, and auto-rejecting a 12-year veteran because of a six-month gap in 2021 is a business mistake before it is a legal one.
Still reading? Stop comparing — try CallSphere live.
See the logistics AI agent handle a real call — complete, industry-specific, and live in your browser. No signup.
Coaching and termination off camera events. A harsh-braking or distraction event flagged by the camera is evidence, not a verdict. The safety director watches the clip. Anything that ends in discipline needs a human name on it.
Anything that touches a DOT file. The 3-year safety performance history under 391.23, the Clearinghouse queries, the annual MVR review — those are regulated processes with prescribed steps. Use software to gather and remind. Do not let it decide.
Some rules carry employee-count thresholds and some do not. Biometric consent obligations generally do not turn on headcount. The safest read for a small fleet is that the consent and notice items apply to you and the heavier documentation and audit obligations mostly do not.
No. The vendor makes the tool; you are the one collecting data from your drivers in your cabs. Get their documentation in writing and file it, but the consent from your driver is your obligation and your record.
Disclosure requirements in several states focus on consumers, and a broker coordinator is not a consumer. That said, the cost of disclosure is zero and the cost of a customer feeling deceived is not. Have the agent say what it is.
Nothing in your folder is wasted if it does. An inventory, applicant notice, driver consent forms and a named human reviewer are the same things a plaintiff's attorney, an insurance underwriter and a large shipper's vendor questionnaire will ask you for anyway.
One item on that inventory is often the phone. If you use an AI agent to answer the dispatch line after hours, make sure it identifies itself, sticks to gathering load details and callbacks, and keeps a clean record of every call. That is how CallSphere builds AI voice and chat agents — answering, disclosing what they are, capturing the lane, the equipment and the contact, and logging it so the call is documented rather than remembered.
Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
The EU AI Act's August 2 date, Texas TRAIGA and California SB 53 all landed. What a US rehab clinic must document, disclose and log, and what it can skip.
Two casino systems land in the EU AI Act high-risk bucket: face matching and marker scoring. What US gaming operators document, disclose and can ignore.
What a US registered investment adviser must actually document, disclose and log in 2026 — and which AI statutes are genuinely out of scope for the firm.
The EU AI Act's August 2, 2026 date reaches US studios delivering to EU viewers. Here is what to log, disclose and consent for, and what is out of scope.
Admissions, placement tests and proctoring put private schools inside 2026 AI rules. The inventory, the file, the parent notice, and what is out of scope.
What a US employee benefits broker must log, disclose and review after the EU AI Act's 2 August 2026 date, plus the state AI laws in force since January.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI