Traffic Control Plan General Notes Explained: The Text That Changes What You Have to Build

Estimators look at the drawing. They count signs, measure the taper, and check the arrow board. Then the job starts, and the inspector points to a line of small text on the first sheet that says work is not allowed before 9 a.m., that all channelizing devices must be drums, and that the contractor must notify the school district five days ahead.

Those lines are the general notes. They are the part of a traffic control plan most likely to change what a job costs, and the part least likely to be read. This guide covers what they are, what they usually contain, and how to read them before you commit to a price.

Practice varies by state, agency and designer. What follows describes how notes are commonly used. On a real project, the contract documents and the owner decide what they mean.

What general notes are for

A drawing shows where things go. It cannot show when, for how long, in what condition, or who is responsible. Notes carry all of that.

The national manual recognizes the need. Section 6B.01 of Part 6 of the MUTCD says temporary traffic control plans range from very detailed to simply referencing typical drawings in the manual, standard agency drawings, or drawings in the contract documents, and that important auxiliary provisions that cannot conveniently be specified on project plans can be incorporated into special provisions within the plan.

Owners implement that in different ways. Some put nearly everything on standard sheets. TxDOT's plan set guidance on traffic control plan sheets, for example, says plans for minor projects should include, at a minimum, the traffic control standards and the BC standard sheets for advance signage requirements. Those sheets carry their own notes, which apply wherever the sheet is referenced. A city permit plan may carry a dozen notes typed on the drawing. Either way, the text is part of the plan.

See what is a traffic control plan and reading a traffic control plan in the field for the drawing side.

What they typically cover

Not every plan has every category. These are the ones that recur.

Governing standards

A note stating which manual, standard sheets and specifications the work must follow, and which edition. It matters because it tells you where to look for everything the plan does not say. In Texas that points to the Texas MUTCD and TxDOT's standards; see TxDOT traffic control standard sheets explained.

Work hours and lane closure windows

When lanes may be closed, when they must be open, holiday and event restrictions, and sometimes penalties for late opening. This note decides whether the job is day work or night work and how many hours of production fit in a shift. See lane closure restriction windows and curfews.

Device requirements

Which devices are required or prohibited. Drums instead of cones for overnight setups, a minimum cone height, sheeting grade, sign substrate, lights on barricades. Notes can narrow an approved list. TxDOT's Compliant Work Zone Traffic Control Device List says so directly: the engineer may, through a general note in the plans, disallow specific devices on the list or require that specific ones be used. See the TxDOT compliant device list explained.

Sign handling

Covering or removing signs when they do not apply, covering conflicting permanent signs, and how long signs may stay up when no work is happening. Notes on sign covering generate daily labor that is easy to leave out of a price.

Maintenance and inspection

Who inspects the setup, how often, at night as well as by day, and how quickly a damaged or displaced device must be fixed. Some notes require a named person on call around the clock with a phone number given to the agency. That is a staffing commitment. See work zone inspections and agency audits.

Personnel

Required credentials for flaggers and for the person supervising traffic control. See traffic control supervisor certification explained.

Notifications

Advance notice to the agency, emergency services, transit, schools, businesses and residents, with lead times. Message signs placed days ahead of a closure are often specified here. See customer and public notifications for lane closures.

Access

Keeping driveways, businesses and side streets open, and maintaining pedestrian routes. See maintaining driveway and business access in work zones.

Emergency vehicles

How emergency vehicles get through or around the closure. See emergency vehicle access through work zones.

Pavement and drop-offs

What must be done at the end of a shift: plates, temporary markings, edge drop-off protection, and whether lanes must be restored each night.

Speed limits and enforcement

Whether a reduced limit is authorized and who provides enforcement. See law enforcement in work zones.

Changes

How the plan may be modified in the field and who approves it. The manual's guidance is that an alternate or modified plan should have the approval of the responsible highway agency or owner before it is implemented. The note tells you who that is on this job. See field changes to an approved traffic control plan.

Measurement and payment

On public work, how traffic control is paid: lump sum, by the day, by the device, or incidental to other work. This note, or the specification it points to, decides whether an extra week costs you or the owner. See lump sum vs unit price traffic control bid items.

Where notes sit in the hierarchy

A plan set has several layers of text: the standard specifications, special provisions, standard sheets with their own notes, project general notes, and the drawings. When two of them disagree, the contract's order of precedence says which wins.

Do not assume the order. It varies between owners, and it is usually stated in the general conditions or the standard specifications. What you can rely on is the practical rule: if a note conflicts with the drawing or with a specification, ask the owner or the engineer in writing before bid day, and keep the answer. A question asked before the bid is a clarification. The same question asked after is a dispute.

The second trap is the standard sheet. When a plan says "see standard sheet such-and-such," every note on that sheet is now part of your job, even though it is not printed on the project drawings. Pull the referenced sheets and read them.

Reading notes before you price

A routine that takes fifteen minutes and saves the most money of any step in estimating:

1. Read every note on every traffic control sheet, and on each standard sheet referenced.
2. Mark each one that costs labor, equipment or time. Night inspections, an on-call person, daily sign covering, drums instead of cones, message signs a week ahead.
3. Check the hours note against the production the contractor is assuming. A six-hour window is not an eight-hour shift.
4. Check device notes against what you own. If the note requires something you do not stock, price the rental or the purchase.
5. Find the payment note. Know whether duration is your risk.
6. List anything unclear or contradictory and ask.
7. Carry the costly notes into your quote as line items or as stated assumptions.

That last step is how the notes protect you. If your proposal says it is based on day work with cones, and the notes require night work with drums, the proposal should say which notes you have priced. See exclusions and assumptions in traffic control proposals and traffic control plan quantity takeoffs.

Notes also affect what the plan itself costs to prepare. A plan for an agency with long standard notes and strict review takes more time than one for a private lot. See traffic control plan cost.

When you are the one writing them

Traffic control companies that prepare plans for customers end up writing notes. A few principles keep that safe.

• Use the agency's standard notes where it publishes them. Reviewers expect their own wording, and invented notes are a common cause of rejection. See traffic control plan rejections: common reasons.
• Do not restate the manual in your own words as a requirement. Reference the standard. Paraphrased rules drift from the source.
• Do not write a note you cannot perform. "Contractor shall inspect devices every two hours" is a promise somebody has to keep.
• Keep notes specific to the job. A page of boilerplate hides the two notes that matter.
• Know who may prepare or seal the plan in that jurisdiction. See who can prepare a traffic control plan.

Layouts that follow a typical application still need the right notes with them; our guide to how to use MUTCD typical applications explains that the notes to each typical application are part of it, and taper length and buffer space covers the dimensions the notes often refer to. State practice differs: Pennsylvania's PA Pub 213 is one example of a state document with its own notes and figures.

Getting the notes to the crew

The crew lead in the field usually has the drawing. The notes are on a different sheet, in the office, or in an email. That is how a setup that matches the drawing still fails inspection.

The fix is to turn the notes that affect the field into job instructions: allowed hours, required devices, who to call, what to cover at the end of the shift. They belong on the work order the crew sees, with the plan attached.

Traffic OS keeps the job, its files and its instructions in one record that the crew opens on a phone, and the daily ticket records what was actually set. The features page lists what is included and pricing is by flat monthly tier. Our quoting guide covers carrying assumptions from the quote into the job.

To see how plan files and job instructions appear to a crew, book a walkthrough.

The short version

General notes are the written half of a traffic control plan. They set hours, devices, maintenance, notification, access and how changes are approved, and standard sheets bring their own notes with them. Read all of them before pricing, mark the ones that cost money, ask about conflicts in writing, state in your quote what you have priced, and put the field-relevant notes in front of the crew.