From the Transportation edition of November 6, 2026
Louisiana DOTD I-12 AI queue-detection pilot confirmed not to record video, stills or alert logs
Louisiana Department of Transportation and Development (DOTD) · State DOT interstate traffic management / queue warning · I-12 westbound near I-12/I-10 merge, Denham Springs / Baton Rouge area, Louisiana, United States
- Publisher
- Chris Corzo Injury Attorneys (reporting DOTD written responses); corroborated by KPEL/WBRZ
- Original publication
- 2026-08-03 (DOTD written confirmation via Corzo); deployment reported June 29-30, 2026
- Source retrieved
- 2026-11-07
- Event date
- 2026-06-29
What happened
Louisiana DOTD's first camera-based AI queue-detection system on westbound I-12 (near the I-12/I-10 merge after College Drive) measures vehicle speeds and traffic frequency to warn drivers of forming backups via flashing prepare-to-stop signs, without facial recognition or license-plate logging per June 2026 local reporting. In an Aug 3, 2026 publication, Chris Corzo Injury Attorneys released DOTD's written answers stating the pilot cameras do not record video or still images and do not retain queue alerts, traffic measurements, warning-light activations, TMC logs or operator notes for later crash requests. Why-now: addresses the 2026-11-05 edition's named gap on U.S. state DOT AI operations and privacy design.
Why it matters
Rare documented U.S. state DOT posture that roadside AI traffic cameras can be scoped to ephemeral queue detection without building a surveillance archive—useful for DOTs answering privacy objections while piloting AI incident/queue tools.
Evidence and measured results
Corzo Aug 3, 2026 Q&A table quoting DOTD (representative name omitted; firm says it retains correspondence). KPEL June 30 and WBRZ June 29 describe first-in-state camera AI queue detection and no facial recognition/LPR.
Limitations and uncertainty
Attorney-published correspondence rather than a DOTD press PDF; no published detection-time or crash-reduction metrics; June deployment news is older than the last edition date.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- State DOTs want AI queue/incident detection for safety but face surveillance and records-request concerns about roadside cameras.
- Stakeholders
- DOT secretary/TMC leadership
- State privacy/legal counsel
- Motorists and civil-liberties groups
- Legislators
- Maintenance/ITS contractors
- Discovery questions
- Do queue cameras record or only stream?
- What alerts and measurements are retained?
- Is LPR/face detection enabled?
- How will crash litigants be told no footage exists?
- Value hypothesis
- An ephemeral AI queue-warning design can deliver earlier DMS activation while remaining politically and legally defensible if non-retention is verified and published.
- Potential engagement
- Policy-and-architecture review to draft a camera retention matrix and pilot acceptance tests for non-enforcement AI traffic detection.
- Unsupported claims
- Proven crash or congestion reductions on I-12
- That all Louisiana cameras follow this pilot's rules
- Transfer of attorney-reported Q&A without DOTD primary PDF
Pre-sales engineering
Role takeaway
- Fit
- Interstate TMC queue warning and wrong-way/slowdown detection programs that must avoid becoming surveillance systems.
- Architecture and integration
- Camera to real-time analytics to DMS/TMC alert; no media archive; configuration-as-code for retention flags.
- Prerequisites
- Detection-zone calibration
- DMS control integration
- Written retention standard
- Operator live-view procedures
- Constraints
- Limited performance metrics published
- Attorney secondary publication of DOTD answers
- Pilot geography only
- Security
- Protect live TMC camera access; ensure analytics hosts cannot be reconfigured to record without change control.
- Proof of value
- Warning lead time vs prior sensors
- Rear-end crash proxy metrics
- Configuration audit showing storage off
- Public FAQ accuracy check
Delivery
Role takeaway
- Work
- Deploy pilot zone, lock non-retention settings, publish FAQ, evaluate warning effectiveness, decide expansion.
- Dependencies
- DOT legal/records
- TMC operations
- ITS vendor
- Communications
- Ownership
- DOTD owns policy and ops; vendor owns analytics under DOT change control.
- Skills and adoption
- Train operators that no replay exists; train public affairs on privacy messaging.
- Governance checkpoints
- Retention matrix sign-off
- Pre-go-live config audit
- 30/90-day performance review
- Expansion decision
- Acceptance criteria
- DOT-confirmed non-retention
- No LPR/face features enabled
- DMS activation tested
- Public documentation live
- Risks
- Discovery disputes if any recording is found later
- Safety critics wanting retained video
- Scope creep into enforcement uses
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Design queue AI as real-time speed/volume analytics driving DMS activation without persistent media storage; separate any enforcement cameras into different systems with explicit retention rules.
Governance
Who approves, reviews and stays accountable for outcomes?
Publish retention matrices for AI roadway cameras before pilots; answer FOIA/discovery questions with written scope limits.
Security and privacy
What data, permissions and controls need testing?
Non-retention reduces privacy and discovery risk but also limits after-action learning from video; agencies must still secure live camera views in the TMC.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Earlier queue warnings can protect all drivers including commercial and aging road users; TMC staff must understand live-only workflows without replay.
Procurement
What should contracts, pricing and exit terms secure?
Specify non-retention and no-biometric analytics in ITS contracts with audit rights on storage configuration.
Operating model
Which teams own the service once it runs?
Separate safety queue-warning AI from enforcement camera programs with distinct policies and hardware.
What changed
June deployment reporting predates last run; included because Aug 3 DOTD written non-retention confirmation newly documents U.S. state DOT privacy controls for roadway AI—explicit gap from the 2026-11-05 edition.
Publication history
- 2026-11-06Transportation · Issue 095 resources
Stable resource ID: ladotd-i12-ai-queue-detection-no-retention-2026