What is an equipment kit in traffic control software?

A saved list of devices and quantities for a standard setup. Applying the kit to a quote or a job adds every line at once, in place of typing each sign, drum and stand. The quantities can then be adjusted for the job.

How many kits does a traffic control company need?

Fewer than most people expect. Start with the five or six setups that make up most of your jobs, such as a shoulder closure, a single-lane closure at low and high speed, a flagging operation and a road closure. Add more only when a setup keeps recurring.

Where do the quantities in a kit come from?

From the plan, typical application or agency standard sheet the setup is built to, counted for a defined speed and length. A kit should name its source so that someone can check it when the standard changes.

Does a kit replace the traffic control plan?

No. The approved plan governs what goes on the road. A kit is a starting list for quoting and loading. If the plan for a job differs from the kit, the plan wins and the quantities are edited.

Should kits include spares?

Most companies add a small allowance for devices that get hit or blown over, and carry it as a separate line so it is clear what is required by the plan and what is extra.

Equipment Kits for Lane Closure Packages: Building Them

An equipment kit is a saved device list for a standard setup, such as a single-lane closure on a 45 mph road. Kits speed up quoting and load-out and cut the number of short trucks. Here is how to build kits from the plans you actually run, what to put in them, and how software should handle them.

Ask three crew leads what goes on the truck for a single-lane closure and you will get three lists. Each list works, more or less, and each is in somebody's head. When that person is off, the truck leaves short.

An equipment kit puts the list in the system. It is a saved set of devices and quantities for a standard setup. Applied to a quote, it prices the package. Applied to a job, it becomes the load-out. This post covers how to build kits that are worth using and what to expect from software that claims to support them.

What a kit is and is not

A kit is a template. A typical one might be called "Single-lane closure, two-lane road, 45 mph, flagger control" and contain lines for advance warning signs, sign stands, cones, a pair of stop/slow paddles, radios and flags.

A kit is not the traffic control plan. The plan, the agency's standard and the permit decide what goes on the road. A kit is a fast, consistent starting point that gets edited to match the job.

It is also not a price. A kit holds quantities. Pricing comes from your rate sheet applied to those quantities, for the rental days on the job. See traffic control device rental rates and pricing.

Why kits pay for themselves

Quotes go out faster. Most requests are a variation of a setup you have done a hundred times. Applying a kit and adjusting two lines takes a minute. See quoting traffic control jobs faster.

Quotes are consistent. Two estimators pricing the same job should reach the same device count. Without kits, they often do not.

Trucks leave complete. The load-out list comes from the same kit as the quote, so the yard loads what was sold. See daily dispatch routine for traffic control companies.

Inventory is reserved correctly. When a kit is applied to a job, the system knows 14 signs and 60 cones are committed for those dates. That is how you find out on Tuesday, not Thursday morning, that Thursday is short. See tracking traffic control devices by job site.

New people learn the setups. A new dispatcher or crew lead can read the kit and see what a standard closure needs.

Building kits from what you actually run

Do not start by designing an ideal library. Start from your last three months of jobs.

List the setups. Go through recent tickets and group them. Most companies find that five or six setups cover the large majority of their work.
Find the source for each. Every standard setup is built to something: a typical application in the manual, a state standard sheet, or a city detail. Write it down.
Count the devices from the source. Take the quantities from the drawing for a defined speed and length, the way you would for a takeoff. See traffic control plan quantity takeoffs.
Compare with what crews actually load. If the crew list and the plan list differ, find out why before choosing. Sometimes the crew is carrying sensible spares. Sometimes they have been running short of the plan for years.
Name it clearly. Road type, speed, lanes and control method in the name.

On sources: the national reference for common layouts is the typical applications in Chapter 6P of the MUTCD 11th Edition, Part 6. The manual is clear that these are starting points. Section 6N.03 says other devices may be added to supplement those in the typical applications and device spacing adjusted, and that fewer devices may be needed when conditions are less complex. A kit inherits that character. See MUTCD typical applications: how to use them.

State agencies often publish their own layouts. TxDOT, for example, maintains Barricade and Construction, Work Zone and Traffic Control Plan standards for state work. If most of your jobs are built to a state sheet, build the kit from that sheet. See TxDOT traffic control standard sheets explained. Requirements vary by state and agency, so confirm which standard applies to your work with the agency that has jurisdiction.

What goes in a kit

A complete kit covers more than the devices on the drawing.

Category	Examples
Signs	Each advance warning sign by legend and size, plus regulatory signs the layout needs
Supports	Sign stands, with ballast
Channelizing devices	Cones or drums for the taper, the tangent and the downstream taper
Electronic devices	Arrow board, message sign, warning lights where the layout calls for them
Flagging equipment	Stop/slow paddles, radios, flagger-ahead signs
Vehicles	Shadow truck with attenuator where required
Spares	An allowance for knockdowns, on a separate line

Things people forget: sandbags, the second set of signs for the opposite approach on a two-lane road, and sign covers for signs that stay in place between shifts. See sign stands, sandbags and ballast in work zones.

Variables that change the quantities

A single kit cannot cover every version of a setup, because the quantities depend on a few inputs.

Speed. Taper length and sign spacing grow with speed, so the cone or drum count does too. See taper length and buffer space explained and advance warning sign spacing explained.

Length of the work area. The tangent section scales with the length of the closure. See channelizing device spacing explained.

Day or night. Night versions swap cones for drums or add lights, depending on the standard. See work duration categories in temporary traffic control.

Number of approaches. An intersection job multiplies the sign sets.

There are two ways to handle this. One is separate kits for the main speed bands, such as 35, 45 and 55 mph and above. The other is a base kit for the fixed items, with the taper and tangent quantities entered per job. Either works. What does not work is one kit with average quantities that is wrong for every job.

Keeping kits honest

Kits go stale. A kit built two years ago to an old standard sheet quietly under-supplies every job.

Put the source and date in the kit description. "Built from standard sheet X, revision dated Y."
Assign an owner. One person approves kit changes. Otherwise every estimator edits them.
Review when a standard changes. A new manual edition or a revised state sheet is a trigger. Texas contractors, for example, should check their kits against the 2025 edition of the state manual. See the 2025 Texas MUTCD explained.
Feed back from the field. If crews keep adding the same items to a kit on site, the kit is wrong. If tickets show the same items coming back unused every time, it is padded.
Check against tickets quarterly. Compare kit quantities with what daily tickets show was deployed. See preventing daily ticket disputes.

What to ask of the software

Vendors use the word "kit" loosely. Ask to see these in a demo.

Can a kit be applied to a quote and carry through to the job? Re-keying at each step defeats the purpose.
Can quantities be edited after the kit is applied, without changing the template?
Does applying a kit reserve inventory for the job dates and warn about shortages?
Can a kit contain rental items, sale items and labor together?
Can kits be nested or combined? For example, a base lane closure plus a night add-on.
Does the load-out list group items the way the yard is laid out?
Do kit items flow to the daily ticket and the invoice, including rental days?
Who can edit a kit? It should be controlled by role. See user roles and permissions in traffic control software.

General field service software often lacks a real rental object, which is why kits and rental days are awkward in it. See rental software vs field service software for traffic control and traffic control software demo questions to ask.

How Traffic OS handles kits

Traffic OS is built for traffic control, barricade and lane-closure companies, and equipment kits are part of the product. A kit is applied to a quote or job in one step, quantities are edited per job, and the items draw from multi-yard inventory. Recurring rentals bill long-running setups, and GPS-stamped signed daily tickets record what was deployed.

Pricing is flat by tier at $499, $949 or $1,499 per month as of October 2026, with no per-user charge, so every estimator and crew lead can use it. See pricing and features. If you are comparing against a general field service platform, see Traffic OS vs ServiceTitan. To see kits applied to one of your own setups, book a demo.

Equipment Kits for Lane Closure Packages: Building Them and Keeping Them Honest