Course
AI for Traffic and Transportation Engineers
Counts, crash data, study reports and agency comments. You still hold the stamp.
Start with
- AI at Work: FoundationsStart from zero and finish with three things you can actually use.
Who this is for
Traffic, transportation and civil engineers and planners in consulting and agency roles. Every example follows Leila, a licensed traffic engineer at a transportation consultancy, running impact studies, signal timing, ITS design and corridor plans for state and local agencies.
You will be able to
- Turn a request for proposal into a scope, a task list and a fee structure the principal fills
- Analyse count and crash exports into the tables and findings a study needs
- Draft the traffic study report in the agency's format with every number traceable to a source
- Write an ITS specification section from the agency standard and the project needs
- Respond to agency review comments in a comment and response matrix
- Prepare public meeting boards and a plain-language summary in Claude Design
Stops
- The project ProjectOne Project per job, holding the scope, the agency template, the standards and the two rules that keep a licensed engineer out of trouble. Set once
- RFP to scope and feeAn agency RFP becomes a scope narrative, a task list with assumptions, a fee table Leila fills, and the questions worth sending before the deadline. Weekly
- Count and crash dataCount exports and a stripped crash file become peak hour tables, trend lines, a crash pattern list and the figures the report will need. Weekly
- The study reportFindings into the agency's report format, with every number tied to a table and every conclusion left in brackets for the engineer who signs it. Weekly
- The ITS specificationThe agency standard plus the project needs become a specification section, clause by clause, with the edition check left where it belongs. Weekly
- Review commentsAn agency comment letter becomes a comment and response matrix, with the disagreements written in the tone that ends them. Daily
- Public meeting materialsBoards, a one-page handout and a plain-language summary in Claude Design, plus the twelve questions the room will actually ask. Later
- Leila's weekThree routines on a timer, Cowork on the figure list, and one study taken from RFP to submitted report. Weekly

Written for Claude. The ideas transfer to ChatGPT and Gemini; the menu paths don't. Current as of September 2026; where a feature may change we link to support.claude.com.
Claude helped Dasow draft and structure every course. A human at Dasow reviewed every stop.