Permitting a Race on Colorado Roads: CSP, CDOT, Counties, and Cities

A course can leave downtown, cross a county line, touch a state highway, and finish in a park before most runners have reached mile ten. On the map it is one continuous line. For permitting, it may be four different conversations.

The useful first question is not “Which race permit do I need?” It is “Who controls every road and property my event will use?” In Colorado, the answer may involve a city, a county, the Colorado State Patrol (CSP), the Colorado Department of Transportation (CDOT), a parks department, or another land manager. Your permit list follows those boundaries.

Begin with the course, not the application forms

Put the latest route into a map that shows road names, start and finish areas, aid stations, staging areas, and every location where traffic will be stopped or redirected. Then divide the course by road owner and land manager.

That ownership check matters because a familiar road name does not always tell you who controls it. A state highway may serve as a town’s main street. A road with a city mailing address may sit in unincorporated county territory. A trail can cross land managed by more than one agency.

For each segment, record:

• the road or property name;
• the city or county it is in;
• the agency that owns or manages it;
• the traffic impact you are requesting;
• the first agency contact; and
• how that agency wants the route submitted.

Do not rely on a pin dropped at the start line. Review the entire course, including detours and the roads used by race vehicles.

City streets usually begin with the city

When a race uses municipal streets, the city’s special-event, transportation, police, public works, or parks staff will usually be the starting point. The exact office varies.

Ask the city whether one special-event application coordinates the internal review or whether separate street-use, park, traffic-control, fire, or alcohol approvals are required. Also ask who approves the traffic control plan. The special-events coordinator may receive the packet while a transportation engineer or police traffic unit makes the operational decision.

Fort Collins, for example, maintains a city special-event permit process and a separate work-area traffic-control permit program. That is a good reminder that “the city is involved” does not necessarily mean there is only one city review.

Denver provides another Colorado example. Its transportation department's current street-occupancy packet calls for a closure request, insurance certificate, notification flyer, and site plan, while races also involve the Denver Police special-events unit. The city's published material says a modification after approval requires resubmittal. Confirm the current path with Denver before using those documents for an event; the example shows how responsibilities can be divided inside one city.

County roads are their own jurisdiction

Once the course enters unincorporated territory, the county may need to review the event even if the nearest town appears in the mailing address. Counties often involve road and bridge staff, the sheriff, planning, risk management, and open-space or parks staff.

Larimer County separates special-event paths for county roads, private land, and parks or open lands. Its county-road category includes foot races and events that restrict or close a county road. The county directs organizers to a pre-application meeting so staff can identify the documents and timing for that event.

Boulder County uses an Event on County Roadways permit whenever an event uses a road in unincorporated Boulder County. Its current page specifically lists foot races or walks with more than 50 people and gives most events a submission window of at least 60 days and no more than 364 days before the event. Treat those numbers as Boulder County rules, not statewide thresholds.

That early meeting is valuable. Bring the route, expected field size, event schedule, closure windows, turnaround points, major intersections, and a plain description of how residents and emergency traffic will retain access.

State highways bring CSP and CDOT into the picture

CDOT’s public special-event page directs organizers to CSP’s application process. CSP says it coordinates special-event road closures with CDOT.

CSP’s published instructions identify several situations that can trigger its process, including an event outside an incorporated municipality and an event that closes, restricts, encroaches on, or may significantly disrupt traffic on a state highway. The instructions also call for a detailed route map, traffic-control points, detours, schedules, and evidence that affected local approvals are issued or underway.

The practical move is to send the route to CSP early when it touches a numbered state highway or creates traffic effects near one. Tell the city or county reviewer at the same time. Do not assume one agency’s approval automatically covers the other’s interests.

CDOT divides the state into engineering regions and publishes region contacts for highway right-of-way questions. The formal event path may run through CSP, but CDOT staff can still be part of the roadway and traffic-control review.

Parks, trails, and public land create another layer

A road permit does not grant the right to use a park, trailhead, reservoir, open-space property, school, or private parking lot. The start and finish deserve the same ownership check as the course.

Look closely at:

• finish festivals and awards areas;
• packet pickup or expo sites;
• aid stations placed off the roadway;
• trail connections and underpasses;
• parking and shuttle loading zones; and
• equipment stored before or after race day.

A land manager may have its own capacity limits, seasonal restrictions, insurance language, restoration requirements, or blackout dates.

A workable Colorado agency map

Imagine a half marathon that starts in a city park, uses city streets, travels two miles on a state highway, turns onto a county road, and finishes back in the park. The working agency list might look like this:

This is an example, not a permit determination. The actual list depends on the exact route and event operations.

What to send in the first email

Make it easy for an agency contact to route your question correctly. Include:

• event name and proposed date;
• start time and expected reopening time;
• estimated participants and spectators;
• a link to the route plus a PDF map;
• GPX or KML if requested;
• requested closures, lane restrictions, or traffic holds;
• start, finish, aid station, parking, and staging locations;
• whether the event occurred before and what changed; and
• the name, phone number, and email of the person managing permits.

Ask two direct questions: Does your agency have authority over any part of this plan? Who else should review it? Those questions often reveal a missed road owner or internal department.

Contacts change; keep the role as well as the name

Record a person’s name, but also record the office and responsibility: county special events, CSP troop office, CDOT region traffic, city transportation reviewer. Staff changes are less disruptive when your notes explain why the contact mattered.

Before each annual cycle, confirm the current application, submission method, fee schedule, insurance wording, and lead time. A repeat course reduces discovery work, but it does not freeze the rules.

Your next move is simple: print the route, mark every jurisdiction transition, and schedule the first conversations before drafting a polished permit packet. A clean agency map prevents weeks of sending the right information to the wrong office.

Official sources

• CDOT Special Event Permits and Information
• Colorado State Patrol Special Event Application Instructions
• CDOT permits and region contacts
• Larimer County Special Event Permits
• City of Fort Collins Special Event Permits
• Boulder County Special Events
• Denver DOTI Special Event Street Occupancy Permit