30-min call with RobBook a proof-of-concept call
Job 02 · Billing desk

// Traffic control companies · Billing logs

Device and flagger billing logs, checked against the rate sheet before the invoice goes out.

A crew writes down what went on the road, and days later someone in your office has to turn those tickets into an invoice the customer will accept. In a free AI proof of concept on copies of 20 to 30 ticket batches you already invoiced, AI reads each ticket against the rate sheet or bid schedule and lists every difference. Your reviewer, whoever on your billing desk knows these customers best, compares that list with what your team actually billed.

Book a proof-of-concept call30 minutes with Rob
Ticket batches
20 to 30
Invoices changed by the AI
None
Billing logins
None

// The one job

From a day's field ticket to a log your billing desk can trust

Each shift leaves a ticket or a log: which signs, drums and arrow boards stayed out, which attenuator and message board ran, who flagged, from when to when, and who signed for it. Your billing desk sets that against what this customer agreed to pay, whether an hourly and daily rate sheet, a public bid schedule or a per-unit pay item, and works out what can go on the invoice.

In the test, AI reads copies of those tickets and schedules and drafts the billing log: device counts and days as written, flagger hours and certifications as recorded, per-unit pay items, and a list of each difference between the ticket and the agreed terms. It changes no invoice and decides no dispute. Your reviewer checks the log against the invoice you sent.

Daily field ticketOne shift
Job
Customer
Supervisor
Shift start and end
Device or flaggerCount or hoursSigned
Illustration, not a real ticket
Read against
the rate sheet
Billing logDraft for billing
Rate sheet
Pay item
Unit
Period
Ticket saysSchedule saysDifference
Made-up log, for illustration

// What makes it hard

Why a field ticket doesn't go straight onto an invoice

The unit belongs to the contract, and devices don't share one. A June 2016 section on maintaining traffic, published by the Hampton Roads Planning District Commission in Virginia, pays flagger service, pilot vehicles and electronic arrows by the hour, warning lights on signs by the day, and Group 2 channelizing devices by the day. Group 1 devices aren't measured at all. Group 2 devices moved to a new location are measured again, while devices slid across a lane line without leaving the road earn nothing more. Montana's 2023 rate schedule turns each device into a count of units: an arrow board carries one value per hour for setting up and taking down each shift, another per day for long term use and a third for the first installation.

A day may have a defined length. Clark County, Washington's annual traffic control and flagging bid, opened March 18, 2025, sets daily rates for trucks, attenuators, message boards, signs, barricades, cones and drums at nine hours, and prices attenuators by the week at 40 hours and by the month at 175. Supervisors, flaggers and laborers each carry regular, overtime and double time lines. Colorado's pilot traffic control provision measures a night shift that crosses midnight on the calendar day it ends. It pays traffic control management or traffic control inspection for a calendar day, never both, and pays one day of management no matter how many supervisors the work takes. The log shows which day each hour fell on and which clause it read.

Not every flagger hour is billable. That same Colorado provision counts actual flagging hours authorized under an approved method of handling traffic. It doesn't pay for time flaggers spend setting up or taking down devices or for extra flaggers covering breaks, puts haul-route flagging at the contractor's expense, and limits reimbursement to the project and 500 feet beyond, apart from locations the engineer adds and approved detours. When an automated flagger assistance device runs, the person operating it isn't paid separately in Colorado or under that Hampton Roads section. A private customer's rate sheet may say something else entirely. So the log keeps start and stop times as recorded and shows any hours the schedule appears to leave out, for your billing desk to read.

The daily record is where the proof sits. Colorado has the supervisor file a daily diary within 24 hours of the work date, listing operations in place with their setup and takedown times and approved method number, types and quantities of devices, and each flagger's name, start, stop, location and hours. Washington's Form 421-040B, revised in 2019, uses a separate sheet for each setup and records stations and times, the sign legend, whether the setup matched the approved plan, flagger and other labor hours, and when the traffic control was set up, checked and removed. Tukwila's May 2026 daily log asks for a supervisor's certificate number, shift start and end, and an hourly inspection row. The draft reads those fields where your tickets have them and lists any day with a device count and no signature, or a flagger hour with no location.

Certifications and rates travel with the person. Portsmouth, New Hampshire's 2016 flagging request wanted a staff list with each employee's certificate type, kept certificates current and on file with public works, took one hourly rate and a second after 40 hours, and let private companies working in the city buy at the municipal rate. Bellevue, Washington's October 2023 sheet has a Traffic Control Supervisor carry both a current state supervisor card and a flagger card and serve one permitted project at a time. Your reviewer will look for devices billed on days the ticket doesn't show, flagger hours that don't tie to the log, a rate taken from the wrong schedule, and a certification missing or past its date as recorded. The log describes each one and stops. The public provisions named here differ by agency and contract, and nothing on this page is legal advice.

// What you send

Ticket batches you already invoiced

Copies only
Hourly, daily and per-unit
01

20 to 30 invoiced ticket batches

Daily tickets or logs for a billing period, each with the invoice it became. Mix hourly, daily and per-unit customers, and include one a customer disputed.

02

The rate sheet or bid schedule

Each customer's agreed rates, minimums, overtime terms and pay items in force on those dates, along with any changes made to them.

03

How your team settled differences

Marked-up tickets, credit memos or emails showing what billing changed and why, plus the crew roster with card types and expiration dates as your records keep them.

04

NDA first, cards blacked out

Once the NDA is signed, black out photographs and identifying numbers on any flagger card before it is copied. If tickets can't leave, we build look-alikes with your reviewer. We never sign in to your dispatch or billing system or a customer's portal.

// Before it starts

Decided while the tickets are still in the binder

Billing differences are judgment calls, so your owner sets how they're scored ahead of time.

Terms for the billing log testSet by your owner
Your reviewer
The owner's pick: generally your billing lead or office manager
Success criteria
In writing: which fields must tie, and how a missed difference scores
The sample
Your reviewer's choice: hourly, daily and per-unit customers, day and night shifts
Who decides
A person in billing, on every difference and every invoice
Price
A range for running it live, named ahead of any copying
NDA
Signed before a single ticket moves

// How the test is judged

Your invoice and the draft log, ticket by ticket

Line by line
against what you billed
Across the same 20 to 30 batchesWhat your team billedDraft billing log
Device counts and days, as written on the ticketFilled in on your ticketsFilled in on your tickets
Flagger hours, as recorded, and the shift they belong toFilled in on your ticketsFilled in on your tickets
Certification recorded for each flagger and supervisorFilled in on your ticketsFilled in on your tickets
Per-unit pay items and the schedule they came fromFilled in on your ticketsFilled in on your tickets
Rate applied: regular, overtime, day, week or monthFilled in on your ticketsFilled in on your tickets
Differences listed for billing, each with its reasonFilled in on your ticketsFilled in on your tickets
Tickets held back for a person, and whyFilled in on your ticketsFilled in on your tickets
Still blank. Your own closed tickets have to run before a cell holds a mark.The reviewer scores each one and makes the call.

// After a yes

Roughly a month of new field tickets

With your reviewer's yes, the next month of tickets gets the same check for about 30 days.

A person in billing resolves every difference, approves each log before anything posts, and builds the invoice in the system your office already uses.

The comparison stays running on live work. Whatever follows is a separate decision, priced by itself, with monthly support after it goes live.

// Possible next jobs

After billing logs, if you want more

Ideas, ranked
Priced one at a time
  1. 01

    Right-of-way permit plan packets

    A permit's conditions read into a draft for your traffic control designer, with every unmatched requirement listed.

    Next
  2. 02

    Flagger and supervisor card files

    Card types, issuing states and expiration dates gathered on one list for whoever fills tomorrow's crews.

    Then
  3. 03

    Device damage and loss notes

    Tickets and crew notes on hit, missing or replaced devices gathered by job for whoever pursues the charge.

    After that

// One hard limit

No invoice gets changed by the AI.

The proof of concept reads copies and drafts a log of differences. It never touches your dispatch or billing system, a permit portal, a live plan or a live invoice, and it never designs a traffic control plan, decides that a closure is allowed, changes an invoice or contacts a customer. A person in billing resolves every difference. The public provisions named on this page vary by agency and contract, and nothing here is legal advice.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

Rob gives the range on the call, after hearing how many ticket batches you invoice in a month and how many customers have their own rate sheet.

// Questions

Billing log questions

Will it change an invoice or short-bill a customer?
No. The log only lists where a ticket and the agreed terms part ways, and why. A person in billing decides what to do about it and builds the invoice, and the test contacts no customer.
Does it know whether a flagger's card was actually valid?
It reads what your tickets and roster record: the name, the card type and the date. It doesn't check a card with a state or a training provider, and a missing or past date goes on the difference list.
Can it handle day rates, hourly rates and per-unit pay items in one batch?
Yes, when that customer's schedule comes with it. Each line names the unit it used and the page that set it, and a ticket matching no unit on the schedule is held for your billing desk.
What about night shifts that run past midnight?
The log keeps the start and stop as written and shows which calendar day the customer's terms assign them to, if the terms say. If they don't say, the shift is marked for a person.
Does this replace our dispatch or billing software?
No. It sits beside them and reads copies. Nothing connects to those systems during the test, and if it earns a yes, the live month is set up around how your office already works.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Start with last month's field tickets.

Half an hour with Rob on your crews, your role, how many customers bill on their own schedule and roughly how many ticket batches you invoice each month. Tickets and rate sheets 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.