Race Permit Readiness Checklist

Permit-ready does not mean every decision is final. It means the race is defined well enough for an agency to understand the request, identify the likely process, and tell you what comes next.

Use this checklist before a pre-application meeting or the first formal submission. Print or copy it, then mark each item Ready, Needs work, or Waiting on agency. The third status matters: some answers should come from the reviewer rather than from a guess inside the race organization.

The first five-minute check

If any of these are missing, resolve them before building a detailed permit calendar:

• A proposed event date and operating window
• One current, dated course map or GPX
• A clear start and finish location
• A reasonable participant and spectator estimate
• A named person responsible for agency communication

Those five items are enough to begin many early agency conversations. They are not necessarily enough for an application.

Course and event footprint

• The route shows direction of travel, start, finish, and turnaround points
• Street names, trail names, parks, bridges, and major intersections are identifiable
• Corrals, staging, aid stations, medical areas, and dispersal areas are shown
• Proposed full closures, lane restrictions, crossings, and temporary no-parking areas are marked
• Setup, equipment delivery, activation, reopening, and teardown times are documented
• Parking, shuttles, loading, and participant drop-off are included
• Finish-area tents, stages, vendors, alcohol, food, generators, signs, and toilets are included
• The course file and human-readable map carry the same version and date

Seattle's event-map guidance is a useful example of why the footprint matters. Its race maps can need closure points, barricades, requested police-control locations, trained monitors, and water stops in addition to the running line.

Agencies and property owners

• Each route segment has a likely road or land manager
• City, county, state, federal, park, trail, railroad, and private-property possibilities have been checked
• Each likely agency has confirmed its role or has an open question to answer
• The team knows which application coordinates other departments and which approvals remain separate
• Contacts include a name, department, email or phone number, and date of last communication
• Written “no permit required” responses are saved with the project

Do not use a mailing address as proof of road ownership. A road inside a city can still involve another authority, and a start area can introduce a property approval that the course does not.

Dates and dependencies

• Every known application has an official deadline
• The team has an earlier internal target for each submission
• Pre-application meetings and calendar-reservation windows are recorded
• Supporting milestones have their own dates rather than sharing the main application deadline
• Dependencies between local, county, state, and land-use approvals are visible
• Review time and at least one revision cycle are included in the working schedule
• Blackout dates, construction, competing events, and seasonal restrictions have been checked

Larimer County begins its county special-event process with event details and a pre-application meeting, then establishes the documentation and submission deadline for that event. That is a useful reminder that the correct plan sometimes starts with a conversation rather than a generic deadline copied from another race.

Traffic control and public safety

• The team has asked whether a traffic-control plan is required
• The required preparer or qualification has been confirmed
• Closure types and operating windows are understood
• Intersections, detours, local access, transit, and temporary parking restrictions are identified
• Emergency access is shown and has an operational owner
• Police, fire, EMS, public works, and traffic-control responsibilities are separated
• Officer, flagger, traffic technician, and volunteer roles are not being treated as interchangeable
• Reopening criteria and the final-participant or sweep process are defined
• One person owns weather monitoring and has written stop, shelter, evacuation, and restart decision points
• Medical leadership, communications, response locations, and transport access are assigned

FHWA's planned-special-event guidance treats traffic, transit, parking, pedestrian access, traveler information, and incident response as connected parts of the event operation. FEMA's special-event planning material adds the planning team, hazard analysis, and incident command. For a complex race, use the checklist to identify these conversations; let the responsible public-safety and transportation agencies define the required plans.

The National Weather Service recommends a specific lightning-safety plan for organized outdoor activities. RRCA's running-event guidance also calls for a detailed safety and security plan tailored to the event and location. Use those prompts to make the plan more complete, then confirm it with the local agencies and professionals responsible for the event.

Sanction and course status

• The team has decided whether it will seek a sport-governing-body sanction
• Any sanction application, conditions, and insurance evidence have their own tasks
• The team has decided whether the measured distance needs official certification
• A course revision triggers a separate check of sanction and certification status

These decisions support race operations and competition goals. They do not replace the permits or property permissions identified above.

Insurance and agreements

• The named insured matches the event organizer or sponsor required by the agency
• Required coverage types, limits, and dates have been obtained in writing
• The certificate holder name and address are exact
• Additional-insured and endorsement requirements have been sent to the broker
• Requirements for vehicles, alcohol, vendors, contractors, and land use have been checked
• Private-property permissions and facility agreements are documented
• Certificate and endorsement files are kept as separate, recognizable documents

See Insurance Certificates for Race Permits before requesting evidence from a broker.

Application packet and working record

• The application uses the current course version
• Maps, site plans, schedules, safety plans, and traffic plans agree with one another
• Required signatures, forms, fees, and tax documents are identified
• File names make the event, document, and version obvious
• Each submission has a date, confirmation, recipient, and stored copy
• Questions and requested revisions have an owner and due date
• Submitted and Approved are different statuses
• Permit conditions will be turned into race-day assignments

Colorado State Patrol's published instructions, for example, say incomplete applications will be returned and call for a detailed map, traffic-control points, suggested detours, timelines, itineraries, and a W-9. They also explain that affected local permits or in-process applications may be needed before a CSP permit can be issued. Your agencies will have their own packet and sequence.

Communication and change control

• The team knows who must receive neighborhood, business, transit, or property-owner notice
• Notices explain dates, operating times, closures, access, and a monitored contact
• The public map matches the route being reviewed
• One person controls route versions and distributes accepted changes
• A route change triggers a review of agencies, applications, traffic control, safety, insurance, vendors, and notices
• Agency decisions are recorded with the contact and date

How to use the result

Do not turn the checklist into one large completion percentage. A race with a perfect vendor list but no confirmed road authority is not 90% ready.

Instead, pull the unresolved items into three short lists:

1. Blocks agency contact: missing route, date, footprint, or event description
2. Needs an agency answer: permit trigger, deadline, required plan, staffing, insurance wording
3. Becomes a project task: document preparation, vendor coordination, payment, notification, or revision

Bring those lists to the first meeting. A good outcome is not a room full of instant answers; it is a confirmed path with owners and dates.

Related RacePermit reading

• What Permits Does a Running Race Need?
• How Far in Advance Should You Start Race Permitting?
• How Route Changes Affect Race Permits

Sources used for this resource

• Seattle special-event application instructions
• Seattle guidance for creating an event map
• Seattle permitting process
• Larimer County special-event permits
• Colorado State Patrol special-event application guidelines
• FHWA transportation management plan components
• FEMA special-events contingency planning
• Bureau of Land Management Special Recreation Permits
• National Weather Service lightning safety for organized sports
• RRCA Safe Event Guidelines
• USATF Course Certification

This is a planning check, not an application form. Replace its prompts with the current instructions and event-specific requests from every authority reviewing your race.