September 11, 2026 · The Key Bot
Who Does What in a Traffic Control Company
The roles a traffic control company actually needs, the order they get added as you grow, and the specific handoffs that break when one person is still doing three jobs.

The org chart of a traffic control company is not complicated, but the order the roles get added in matters a great deal, and most owners add them in the wrong order — because the role that hurts most is not the role that looks most important.
This is a map of the functions, what each is actually accountable for, and where the handoffs break.
The functions, regardless of headcount
Every traffic control company performs these functions. In a three-person company one person does five of them; that is fine, and it is still worth naming them separately, because the failures happen at the seams rather than inside the boxes.
Sales and estimating. Finding work, qualifying it, pricing it, submitting it. Accountable for margin at bid, not just for winning.
Plan production. Producing or procuring the traffic control plan, and getting it approved. How traffic control plans get drawn covers the work; who can prepare a traffic control plan covers the qualification question, which constrains whether this can be in-house at all.
Permitting. Identifying jurisdictions, submitting applications, tracking conditions and expiries. Distinct from plan production even though they are often done by the same person.
Dispatch and scheduling. Matching crews and equipment to jobs, daily. The operational heart of the business.
Field execution. Crew leads and crews. Setting up, maintaining, documenting and removing.
Yard and equipment. Load-out, returns, inventory accuracy, condition, maintenance.
Safety. Training, certifications, incident recording, inspections, near-miss collection.
Billing and collections. Turning tickets and deployments into invoices, and invoices into money.
Admin, payroll and compliance. Payroll including certified payroll where applicable, insurance, licensing.
The order roles get added
This is the sequence that works for most companies, with the reasoning.
1–3 crews: the owner does almost everything. Sells, prices, dispatches from a truck, and does the books at night. It works, and it is the correct structure at this size. The thing to avoid is building habits that will not survive the next step — particularly keeping the schedule and the equipment picture entirely in your own head.
3–6 crews: hire dispatch first. This is the contrarian one, and it is the most common mistake. Owners hold onto dispatch because it feels like control and hire an estimator because estimating feels like revenue.
Dispatch should go first for three reasons. It is the role with the highest interruption cost — it fragments the morning, which is the only time an owner could be selling. It cannot be deferred to the evening, unlike estimating and billing. And it is the hard cap on how many crews you can run: a person who is dispatching cannot simultaneously be on a site walk with a prospect. The daily dispatch routine covers what the role actually consists of.
6–10 crews: add yard and equipment ownership, and name safety. The yard stops working on memory somewhere around here — yard organization covers the physical side. Safety does not need to be full-time, but it needs a name against it, because unowned safety responsibility produces late incident records and panicked prequalification packages. Measuring safety performance covers what that person should be tracking.
10–15 crews: separate estimating from the owner, and put someone on billing. Billing becomes a real job once rental deployments and daily tickets are both material. This is also where job costing becomes possible and necessary.
15+ crews: operations management, and permitting as a dedicated function. At this size a single person owning the whole board stops scaling and you need a layer between dispatch and the owner. Permitting becomes dedicated because multi-jurisdiction permit tracking is genuinely a full-time problem across enough agencies.
The four handoffs that break
More useful than the org chart is knowing where the failures occur. Four seams account for most of them.
Estimate to field. The estimator prices six devices and two flaggers; the field arrives and needs nine devices because of a driveway nobody saw. If this never flows back as data, the estimator keeps pricing the same job wrong. The fix is routine job costing, not a conversation after a bad job. Bidding traffic control jobs covers the estimating side.
Plan to crew. The approved plan revision exists as a PDF in an email thread. The crew works from a printed sheet that may be a revision behind. This is the seam that produces the worst outcomes, because a zone built to a superseded plan is an unapproved zone. Reading a traffic control plan in the field covers the crew's side; field changes to an approved traffic control plan covers what happens when reality differs.
Field to billing. The single most expensive seam in this business. Hours and equipment happen in a truck; invoices are produced in an office from whatever arrived. What did not arrive does not get billed, and nobody knows what did not arrive. Preventing daily ticket disputes and getting paid faster cover the two halves.
Yard to dispatch. The dispatcher assumes equipment is available; the yard knows it is on a job. When these disagree, crews get sent without what they need or jobs get padded with equipment that is not free. Tracking traffic control devices by job site is the structural answer.
Notice that all four are information handoffs, not authority handoffs. They are not solved by a clearer reporting line.
Certification constrains the org chart
Two roles are constrained by qualification rather than by headcount, and it is worth knowing which before you write a job description.
Flaggers. Certification requirements vary by state and by agency, and some contracts specify the acceptable programme. Flagger certification requirements covers the landscape.
Supervisors. Several states and many agency specifications require a named, qualified person responsible for the work zone on a project — the Georgia specification's Worksite Traffic Control Supervisor is one example, covered in Georgia work zone requirements. Traffic control supervisor certification covers the general position.
The commercial consequence is that a certified supervisor is a constraint on how many projects you can run concurrently, independent of how many crews you have. That belongs in your capacity planning and in your bid decisions. Bid/no-bid decisions covers the second part.
Why role clarity is a safety matter
Unowned responsibility is where safety programmes fail, and the exposure is not theoretical.
BLS Census of Fatal Occupational Injuries data compiled by the National Work Zone Safety Information Clearinghouse shows between 82 and 143 fatal worker injuries at road construction sites annually from 2015 through 2024, with an average of 52.7% across 2022 to 2024 being workers on foot struck by a vehicle. The National Work Zone Safety Information Clearinghouse also records 763 fatal work zone crashes and 850 work zone fatalities in 2024 from FARS data.
The controls that address that dominant mechanism — escape route discipline, apparel condition, intrusion response, setup sequence — are behavioural and they degrade without someone whose job includes noticing. In a company where safety is everyone's responsibility in the abstract, the tailgate briefing is the first thing dropped on a busy morning. Tailgate safety meetings covers making it survive contact with 6 a.m.
The staffing problem underneath all of this
Everything above assumes you can hire. In this trade that is the binding constraint more often than the org chart is — hiring and retaining flaggers covers the market reality, and managing seasonality covers the pattern that makes it harder, since most companies need to double their field headcount for part of the year.
The practical consequence for role design: the roles that require certification and institutional knowledge — crew lead, supervisor, dispatcher — need to be stable year-round jobs even if the crew count is not. Treating a crew lead as a seasonal position is how a company ends up re-teaching its standards every spring. Training new traffic control crew leads covers building that bench deliberately.
Where the system fits
The four broken seams above are all cases of the same fact needing to exist in two places. A single job record carrying the plan revision, the crew, the equipment deployment, the signed ticket and the cost means the handoff is a lookup rather than a transfer.
Traffic OS holds that record, and is priced in flat monthly tiers — $499, $949 and $1,499 as of September 2026 — rather than per user, so a seasonal crew member who needs to see the current plan revision is not a licensing decision. The features page covers what is in it; a walkthrough is the fastest way to see the handoffs in practice. The broader growth question is in scaling a traffic control company.
Requirements for certification, supervision and who may prepare plans vary by state, county and city. Verify with the authority having jurisdiction before building an org chart around an assumption.
Frequently asked questions
What is the first role an owner should hire out of?+
Dispatch, in most cases. It is the role with the highest interruption cost, it is the one that cannot be done later in the evening, and it is the one that silently caps how many crews you can run. Owners usually hold onto estimating longer because it feels like the revenue role, which means dispatch is the thing consuming their mornings.
Do we need a dedicated safety person?+
Not necessarily a full-time one early on, but the responsibility has to be named. Unowned safety responsibility means incident records get created late or not at all, prequalification packages get assembled in a panic, and near misses are never collected. Assigning it to a specific person part-time is very different from assuming everyone does it.
Should crew leads do their own scheduling?+
Generally no. Crew leads scheduling themselves produces local optimisation — each lead builds a sensible week and the company ends up with equipment conflicts and idle crews that nobody can see. Crew leads should own execution and field judgment; the schedule needs someone looking at the whole board.
Who owns permits?+
Someone specific, and the same person consistently. Permits have lead times, conditions and expiries, and they fail quietly — nobody notices a lapsed permit until an inspector does. Splitting permits across whoever is handling the job is the most common way an expiry gets missed on a long-running closure.
When does a company need a plans person?+
When plan production becomes a schedule constraint on winning work, or when the volume means the owner is drawing at night. Whether that person can be in-house depends on your state's requirements for who may prepare and seal plans, which vary — confirm before you build a job description around it.
How do we avoid the estimator and the field disagreeing?+
Close the loop with job costing. An estimator who never sees actual hours and equipment days against their estimate cannot improve, and the field cannot tell whether it is being asked to do something that was never priced. The feedback needs to be routine and unemotional rather than triggered by a bad job.