How to Identify Every Agency Involved in Permitting Your Race Course

A race course can cross several jurisdiction lines in a few miles. The city where an event starts may not control every road, trail, park, or highway the course uses. Before building a permit calendar, identify who manages each part of the route and ask each likely agency to confirm its role.

This guide gives you a repeatable way to do that. It is planning guidance, not an agency determination. Local rules and the final course design control what your event actually needs.

1. Freeze the course version you are reviewing

Start with one dated GPX file and a human-readable route description. Give the file a clear name, such as spring-creek-half-marathon-2027-01-15.gpx.

Record:

• Start and finish locations
• Every road, trail, park, bridge, and public facility used
• Turnaround points and aid stations
• Proposed closures, lane restrictions, crossings, and traffic-control points
• Setup and teardown areas outside the running route

The permit plan is only as reliable as the course version behind it. If the route changes, review the affected segments again rather than assuming the same agencies still apply.

2. Break the route into manageable segments

Review the course one segment at a time. A useful segment begins or ends when the route changes road, crosses a municipal boundary, enters a park or trail system, or moves onto a state highway.

For each segment, capture the road or facility name, nearby cross streets, city or county, and the kind of impact the event creates. Distinguish between simply crossing a road and closing or occupying it. Those details help an agency decide whether it has a permit, traffic-control, staffing, or notification role.

Do not treat a mailing address or city boundary as proof of road ownership. Ask the public works, transportation, parks, or special-events contact to confirm responsibility for uncertain segments.

3. Build an agency matrix

Create one row for each possible authority. Most road races should check at least these categories:

One organization may coordinate several reviews, but do not assume one approval covers another agency's property or road.

4. Ask questions that reveal the actual trigger

Send a concise route summary and map to each likely agency. Ask:

1. Does your agency control any part of this course or event footprint?
2. What permit, approval, or coordination process applies?
3. What filing date should this event use?
4. Which documents are required at the initial application, and which can follow later?
5. Are police, public works, fire, parks, or outside traffic-control providers separate reviews?
6. What insurance wording and limits apply?
7. Are neighborhood, business, transit, or emergency-service notifications required?
8. Who should receive route revisions?

Keep the written response and record the contact's name, department, and date. A confirmed “no permit required” answer is useful project information too.

5. Look for dependencies between agencies

Multi-agency work is rarely a set of independent applications. One reviewer may ask for evidence that local applications are approved or underway. A traffic plan may need to work across city and county boundaries. Police staffing, detours, transit impacts, and emergency access can also involve separate reviewers.

For example, the Colorado State Patrol's published special-event instructions say applicants should provide permits or proof of applications from affected jurisdictions before a state permit is issued. That makes local coordination part of the state-level path, not a task to postpone until afterward.

Turn each dependency into a dated task. “Submit state application” is not enough if the packet first needs a route map, local permit evidence, a W-9, and a coordinated traffic plan.

6. A Colorado course with three possible reviewers

A course running from unincorporated Larimer County into Fort Collins can involve county roads, city property or streets, and state-highway coordination. The official processes illustrate why route-based research matters:

• Larimer County directs special events through a pre-application review and identifies additional review for county-road use, insurance, and traffic diversion.
• Fort Collins uses its own special-event process for events on public property and identifies route maps, insurance, and traffic-control planning among the possible requirements.
• Colorado State Patrol coordinates qualifying events that affect state highways outside municipalities and publishes a separate application package and supporting-document expectations.

The right result is not “every Colorado race needs three permits.” The right result is a short list of likely authorities, followed by direct confirmation based on the actual course and event impacts.

A practical course-to-agency checklist

• Save a dated GPX and route description.
• Mark every jurisdiction boundary and road or facility change.
• List city, county, state, federal, park, trail, railroad, and private-property possibilities.
• Send the same course version to each likely agency.
• Record who confirmed responsibility and when.
• Capture application dates and document milestones separately.
• Note dependencies between permits and reviewers.
• Recheck affected segments whenever the route changes.
• Keep official links and verification dates with the plan.

Related RacePermit reading

• What Permits Does a Running Race Need?
• How Far in Advance Should You Start Race Permitting?
• Race Permitting Best Practices

Official sources used for this guide

• Colorado State Patrol special events and its linked application instructions
• Larimer County special event permits
• City of Fort Collins special event permits

Official pages can change. Confirm current forms, contacts, dates, fees, and event-specific conditions directly with each agency before filing.