// AI for traffic control companies
AI for traffic control companies, tested on permits and field tickets you already closed.
For firms that set up work zones, supply flaggers and rent devices to road, utility and commercial contractors. Two jobs make a fair first test: reading a city or county right-of-way permit into a draft plan packet for your designer, or checking daily field tickets against a customer's rate sheet before the invoice goes out. Either one runs as a free AI proof of concept on copies of 20 to 30 permits or ticket batches your office has finished. Your reviewer, the colleague who knows that paperwork best, compares every draft with what your team actually did.
- First job
- Permit plan packets, or device and flagger billing logs
- From you
- 20 to 30 closed permits or ticket batches, copied after the NDA
- We touch
- Copies only: no dispatch, billing or permit portal login
- Never
- A plan designed, a closure called allowed, an invoice changed
- Reviewer
- Named by the owner, often your designer or billing lead
- Price
- A range first, fixed before you sign
// Jobs we would test
From the permit counter to the billing desk
Right-of-way permit plan packets
A city or county permit's requirements and the job's scope read into a draft packet for your traffic control designer: hours allowed, lane closure limits as stated, notification periods, the typical plans the agency names, and every requirement with no matching document.
See the permit packet pageDevice and flagger billing logs
Daily field tickets read against the customer's rate sheet or bid schedule before invoicing: device counts and days as written, flagger hours and certifications as recorded, per-unit pay items, and each difference listed for your billing desk.
See the billing log pageFlagger and supervisor card files
Each person's flagger card or supervisor certificate listed with its issuing state and expiration date, for whoever staffs tomorrow's crews.
Traffic control bid takeoffs
A prime contractor's plans and special provisions read into a list of traffic control pay items and units, for whoever prices the quote.
// Why these two first
A work zone starts as someone's permit and ends as a count of devices and hours
One manual sits behind the whole shoulder. OSHA's construction rules, at 29 CFR 1926.200(g) and 1926.201(a), hold devices used to protect construction workers, flaggers and the garments flaggers wear to Part 6 of the Manual on Uniform Traffic Control Devices. The Federal Highway Administration published the 11th edition on December 19, 2023 and gave states until January 18, 2026 to adopt it or keep a state version in substantial conformance. Minnesota now lists its own 11th edition, and San Diego's permit bulletin names the 2026 California manual, so a packet has to carry whichever title the permit actually names.
On federal-aid work, the plan and the pay item share a section. Under 23 CFR 630.1012, a project's plans, specifications and estimates carry a transportation management plan or provisions for the contractor to develop one. The temporary traffic control part may point to the manual or to standard plans, or be designed for that project. The same section asks for pay item provisions to carry the plan out and has the state and the contractor each name a trained person. Your designer and your billing desk are reading one contract from opposite ends.
A city's permit has its own shorthand. Charlotte's transportation department covers temporary use of the right-of-way for more than five minutes and less than 30 days. Applicants name the diagrams they will follow from its Work Area Traffic Control Handbook, known as WATCH. The department reviews and issues permits 72 hours from first contact, wants a full street closure request at least 10 days ahead, and refuses closures during weekday morning and afternoon congestion. A permit you closed last spring shows how your designer answered questions like those, so it is a complete test on its own.
People carry end dates too. Washington requires a flagger card that expires no more than three years after issue, and accepts cards from reciprocity states such as Oregon, Idaho and Montana. The American Traffic Safety Services Association certifies traffic control technicians, supervisors and design specialists for up to four years and says flagger standards vary by state. Minnesota's supervisor certification runs five years. Wyoming's runs four, counted from the dates on the association's paperwork behind it. Any ticket naming a flagger leans on one of those dates.
One arrow board can be sold by the hour, the day or the month. North Carolina DOT's 2018 division-wide contract for work zone traffic control as needed took prices on arrow panels, message signs, attenuators and flaggers by the day and again by the hour, with signs by the square foot and barricades by the linear foot. Texas measures its barricades, signs and traffic handling item by the month, pays attenuators and portable message signs under separate items, and counts law enforcement by the hour per person. A private contractor's rate sheet can differ from both, which is why the billing check starts from each customer's own schedule.
One limit covers both jobs. The proof of concept never touches your dispatch or billing system, a permit portal, a live plan or a live invoice. It never designs a traffic control plan, decides that a closure is allowed or changes an invoice. A certified designer signs every plan, and a person in billing resolves every difference. The rules named here vary by agency and change over time, and nothing on this page is legal or engineering advice.
// How the test runs
Three steps on work already off the road
- Step 01
Choose the desk, name the reviewer
Your owner chooses between the two desks and puts a name on the reviewer: commonly whoever draws your plans, or whoever builds invoices from tickets. Before anything is copied, you'll have the success criteria on paper, a price range for live use and an NDA with both signatures.
- Step 02
Run closed work through it
Send 20 to 30 permits with the packets your designer built, or 20 to 30 ticket batches with the invoices they became. We call this stage the sandbox, a free AI proof of concept on paperwork your crews have already finished. If copies can't leave the yard, your reviewer helps us build look-alikes.
- Step 03
Then about 30 days live, after a yes
New permits or the next run of tickets go through the same job for about a month, and someone on your staff approves each packet or log before it goes anywhere. A further job would be its own decision at its own price, with monthly support once it runs.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
Rob sets the range on the call from three counts: permits you pull in a month, customers with their own rate sheets, and crews still writing paper tickets.
// Questions
What traffic control companies ask first
Will the AI draw or approve a traffic control plan?
Do you log in to our dispatch software, billing system or a city's permit portal?
Every customer pays us differently. Can one sample cover that?
Our crews still write tickets by hand. Is that a problem?
Do flagger cards have to leave our office?
We work under primes on state jobs and for utilities on city permits. Can both be tested?

Rob Eason, founder
// Book a proof of concept call
Start with last month's permits or tickets.
A half hour with Rob on your crews, your role, the desk you'd test first and roughly how many permits or ticket batches you handle in a month. Permits, plans and tickets stay in your office until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
