Quick answer. A fun run checklist runs in phases: approvals, team and money, course and safety, registration or pledges, volunteers, final week, event day and close-out. Start about 12 weeks out for a lap run on campus, about 4 months out for a run in a public park, and about 6 months out for a route on public roads, because the date and insurance must be settled before you apply for the permit. Print the checklist below or generate a dated version for your event.
This fun run checklist covers both kinds of fun run: a lap run on a school campus and a route run of 1 mile to 5K in a park or on public roads. Start with the timeline for your format, tick through the checklist by phase, then use the supply list and the event-day run sheet. Every task here matches the fun run timeline generator, so you can get the same plan with real dates attached. For the reasoning behind each step, read how to plan a fun run; for everything else about raising money with a run, see the fun run fundraising hub.
Print it or edit it: download the fun run planning checklist as a PDF or as a Word document you can edit. Both are built from this page, phases and supply list included.
Get your dated fun run timeline
Enter your event date and format. For park and road events, set the permit lead time from your own city's or park's rules. The generator lists every task with a due date, moves any planning task that lands on a Saturday or Sunday to the Friday before (it does not adjust for holidays), marks anything already past due, and tells you how many days of lead time the format needs.
Fun run timeline generator
Your plan
| Due | Task | Phase |
|---|
Week-by-week timeline: campus lap run
A lap run on school grounds needs about 12 weeks from the first approval. If the date is approved and the leads are named, the remaining work fits in 8 weeks.
| When | Tasks |
|---|---|
| 12 weeks out | Principal or board approves the date, a rain or heat date and the format |
| 10 weeks | Name the chair and leads: course, volunteers, money, communications, safety |
| 9 weeks | Set the goal, funding model and budget |
| 8 weeks | Confirm insurance and district or PTA money-handling rules; send sponsor letters |
| 7 weeks | Measure and map the loop; plan water, first aid and an accessible route |
| 6 weeks | Write heat, lightning and lost-child plans with the nurse |
| 4 weeks | Order shirts (sponsor logos final) |
| 3 weeks | Kickoff assembly; pledge sheets home; online donations open (about three weeks of fundraising); open volunteer sign-ups by role, with backups |
| 2 weeks | Print lap cards, signs and maps; fill in the one-page fun run safety plan and give every lead a copy; send a progress update |
| 1 week | Walk the course; confirm volunteers, first aid, water and sound |
| 3 days | Check the forecast against your heat and lightning plan |
| 1 day | Mark the course; set up check-in and the lap-count area |
| Event day | Brief volunteers; run heats; collect lap cards |
| 2 days after | Send totals to any per-lap or per-mile donors; thank volunteers and sponsors |
| 2 weeks after | Close collection; two people count cash; deposit and reconcile |
| 3 weeks after | Receipts, results note to families, debrief |
Week-by-week timeline: public-road route run
A route on public roads needs about 26 weeks, or six months, when the city wants the permit application 120 days ahead, which is the timeline generator's default. That matches the Road Runners Club of America's advice to allow six months or more for permitting. The city sets the deadline itself: Arvada, Colorado wants race applications at least 60 days out with a traffic control plan for street events, and Fort Worth, Texas wants 60 days for a run or walk under 500 people and longer for larger events. With a 60-day deadline, the generator's plan starts about 17 weeks out, but six months is still the safer plan for streets. Whatever the deadline, the date, the call to the city and the insurance certificate come before the application, because cities want insurance submitted with it.
| When | Tasks |
|---|---|
| 26 weeks out (permit deadline + about 2 months) | Pick a date and a backup; check city, park and school calendars |
| 24 weeks (deadline + about 6 weeks) | Ask the city what permits, police and insurance certificates it requires |
| 19 weeks (deadline + 2 weeks) | Arrange event insurance and the certificate of insurance the city requires |
| 17 weeks (120 days, or your city's deadline) | Submit the permit application with the route map and insurance certificate |
| 10 weeks | Name the remaining leads |
| 9 weeks | Set the goal, entry fee and budget |
| 8 weeks | Send sponsor letters |
| 7 weeks | Open registration and online giving; measure and map the route; plan water, first aid and accessible options |
| 6 weeks | Write weather and lost-child plans; request police or traffic control |
| 4 weeks | Order shirts at the registration cutoff |
| 3 weeks | Open volunteer sign-ups to the course planner's numbers |
| 2 weeks | Print bibs, signs and course maps; fill in the one-page safety plan and give every lead a copy |
| 1 week to event day | Same as the campus plan, plus barricades, cones and the finish chute |
| After | Send totals to any per-mile donors, post results, thank sponsors, close the books, debrief |
Fun run checklist by phase
Items marked for lap runs or route runs apply only to that format; everything else applies to both.
Approvals
- ☐ Principal, board or venue approves the date, backup date and format in writing
- ☐ District rules checked: facility use, fundraising, money handling, flyers
- ☐ Insurance confirmed for the group running the event, not just the school
- ☐ Certificates of insurance requested for every venue that asks
- ☐ Route runs: permit filed by the city's deadline with route map, traffic control plan and insurance certificate
- ☐ Route runs: police or traffic control booked where the city requires it
Team and money
- ☐ Chair and leads named: course and safety, money, volunteers, communications, sponsors
- ☐ Goal set from your own numbers with the profit calculator
- ☐ Funding model chosen: entry fee, donations, or both
- ☐ Budget approved with a spending ceiling for the chair
- ☐ Two-person rule set for counting cash
- ☐ Sponsor letters and packet sent
Course and safety
- ☐ Course measured and mapped, with start, finish, water and first aid marked
- ☐ Accessible route or loop identified for walkers, wheelchairs and strollers
- ☐ Medical lead named and first-aid post planned
- ☐ Heat plan written with the trigger and the person who makes the call
- ☐ Lightning plan written, with a shelter big enough for everyone
- ☐ Lost-child plan and a meeting point set
- ☐ Waiver or permission form reviewed by whoever advises your group
Registration and pledges
- ☐ Lap runs: pledge sheets printed with a per-lap cap and return date
- ☐ Online donation page tested end to end
- ☐ Route runs: registration form with waiver, fee, shirt size and cutoff date
- ☐ Kickoff assembly or launch announcement done
- ☐ Photo opt-out list from the school in hand
- ☐ Mid-campaign update sent, with no money leaderboard
Volunteers
- ☐ Roles and counts set from the course planner, plus backups
- ☐ Volunteer screening done to your district's or group's rules
- ☐ Shifts assigned and job cards printed
- ☐ Adult marshals with vests at every crossing and turn (teens can hand out water, cheer, count laps or help at check-in with an adult lead, but never marshal)
Final week
- ☐ Course walked with the course lead and the medical lead
- ☐ Volunteers confirmed by name; backups on standby
- ☐ Forecast checked against the heat and lightning plan
- ☐ Sound system, timer and announcer script tested
- ☐ Course marked, check-in and finish area set up the day before
Event day
- ☐ Volunteer briefing before the first heat or wave
- ☐ First aid in place before anyone runs
- ☐ Lap runs: heats run to the clock; lap cards collected per class
- ☐ Route runs: waves started; sweep behind the last walker; finishers recorded
- ☐ Cash counted by two people and sealed before it leaves the site
- ☐ Course cleared and trash removed
After the event
- ☐ Totals sent to any per-lap or per-mile donors within two days
- ☐ Volunteers, sponsors, teachers and staff thanked
- ☐ Collection closed; deposit made; books reconciled
- ☐ Receipts and disclosures sent where required
- ☐ Results note sent to families
- ☐ Debrief numbers filled in on the Debrief tab of the fun run budget spreadsheet: participants, share who collected, donors, gross, costs, net, net per participant, pledge collection rate, sponsorships, volunteers, unfilled shifts, incidents, timing vs. plan
- ☐ Family and volunteer survey sent within a week
- ☐ Debrief held and keep, change and stop notes saved for next year
Fun run supply list
- ☐ Course markers: cones, flags or chalk
- ☐ Start and finish banners or signs
- ☐ Sound system, microphone and a backup timer
- ☐ Water, cups and trash bags
- ☐ First-aid kit, ice packs and the medical lead's contact sheet
- ☐ Safety vests for every marshal
- ☐ Clipboards, pens and printed run sheets
- ☐ Check-in tables, rosters and name tags for volunteers
- ☐ Lap runs: lap cards or tally sheets, hole punches or markers, class bins
- ☐ Lap runs: shade for waiting classes
- ☐ Route runs: bibs and safety pins
- ☐ Route runs: finish chute materials and a finish-recording sheet
- ☐ Route runs: barricades and signs required by the permit
- ☐ Route runs: portable toilets, with accessible units (at least 5 percent and never fewer than one, per the ADA National Network's event guide)
- ☐ Cash box, deposit bags and a two-signature count sheet
Event-day run sheet (illustrative)
Illustrative: a Saturday route run with a 1-mile family run and a 5K. Shift the times to your start and stretch the blocks if your course planner shows a longer finish window.
| Time | What happens | Who |
|---|---|---|
| 6:30 | Course setup, signs, water, first aid | Course lead, setup crew |
| 7:15 | Volunteer check-in and briefing | Volunteer lead |
| 7:30 | Registration and bib pickup open | Check-in team |
| 7:50 | Marshals at crossings; weather check | Safety lead |
| 8:00 | 5K start in waves: runners, then joggers, then walkers | Starter, lead and sweep |
| 9:20 | Last 5K walker in; sweep reports course clear | Sweep |
| 9:30 | 1-mile family run start | Starter |
| 10:00 | Awards and thank-yous | Chair |
| 10:30 | Teardown; cash counted by two people | Money lead, setup crew |
The 9:20 sweep time comes from the course planner's default walker pace (24 minutes per mile at the slow end) over 3.1 miles, about 75 minutes, plus wave gaps. For heat-by-heat school schedules, announcer scripts and lightning holds, see the fun run event-day schedule. If your event is a walk rather than a run, the walk-a-thon checklist drops the timing and finish-line work.
Two safety rules belong on every run sheet: the National Weather Service advises waiting 30 minutes after the last thunder before going back outside, and the Road Runners Club of America advises sending runners home if there is not adequate safe shelter for everyone to wait out a storm.
Frequently asked questions
How far in advance should you plan a fun run?
Start about 12 weeks ahead for a lap run on school grounds, about 4 months ahead for a run in a public park, and about 6 months ahead for a route on public roads. RRCA advises allowing six months or more for permitting, and you need a date, a route and an insurance certificate before you can apply.
Can you plan a fun run in four weeks?
A simple lap run on campus is possible in four to six weeks if the principal approves quickly and you skip custom shirts and sponsor packages, but about 12 weeks is the recommended plan. A route on public roads usually cannot be done that fast, because most city permit deadlines are longer than that.
What supplies do you need for a school fun run?
At minimum: course markers, a sound system and timer, water and cups, a first-aid kit, safety vests, lap cards or tally sheets, clipboards, and a cash box with a count sheet. Shade for waiting classes helps on warm days.
Is the printable checklist free to edit?
Yes. The Word version can be edited to add your own tasks, names and dates, and the PDF prints with tick boxes. Neither requires an account or an email address.
What is the most commonly forgotten fun run task?
Writing down who makes the weather call and what triggers it. Committees often agree that heat or lightning matters but leave the decision to whoever is standing nearest on the day.