# How to Organize a Marathon or Community Run in 2027: A Planning Checklist

> A 2027 planning checklist for a marathon or community run: route and permissions, safety, entries, runner messages, kit pickup, race-day check-in and money.

Source: https://laces.run/blog/how-to-organize-marathon (HTML version of this page)

To organize a marathon or community run, secure your route and permissions first, then plan safety, set your distances and a realistic cap, open entries on one link, and run a separate process for kit pickup and race-morning check-in. Your course and your safety plan set every other limit. This checklist works for a neighbourhood 5K and for a full marathon.

[Create your race](https://laces.run/app): Set them up as ticket types with their own price and places, and take entries from one link.

## Choose the format first

A 5K in a neighbourhood and a full marathon are different events. Before you pick a date for 2027, decide these, because they set the size of everything else:

- **Distances,** and whether all of them start from one place.
- **Who it is for:** first-timers, club runners, families, or all of them.
- **Competitive or not.** Prizes and rankings bring timing, rules and more disputes. A fun run needs none of that.
- **The purpose:** profit, a cause, or the start of a yearly event.

If you are raising money for a cause, read our guide to [charity runs and fundraising walks](https://laces.run/blog/how-to-organize-a-charity-run-2027) as well.

## Before you announce anything

Runners start training the day you announce, so sort out these points first.

- [ ] **Date:** check it against other races and big public events.
- [ ] **Start and finish area:** room for your full field, parking, toilets and an ambulance.
- [ ] **Route:** drive it, then walk the tricky parts at the time of day you will run.
- [ ] **Permissions:** ask the venue, the local authorities and the police what your event needs, and get the answers in writing. Requirements depend on the place and the roads, so don't rely on a generic list.
- [ ] **Distances:** only those your route and team can support safely.
- [ ] **Cap:** set by the course, the start area and your supply of shirts and water, not by your ambition.
- [ ] **Budget:** written quotes for the big items, and a sum for how many entries you need to break even.

If you want a measured course or official recognition, ask your national athletics federation what applies. In Uganda that is the [Uganda Athletics Federation](https://ugandaathletics.org/).

## Build the safety plan

- [ ] Qualified medical cover at the finish, and a way to reach any point on the course.
- [ ] A named person who can stop or change the race.
- [ ] Marshals at every junction and turn, with a way of contacting the race office.
- [ ] Water stations spaced for the distance and the expected heat.
- [ ] Traffic control agreed with the responsible authorities.
- [ ] Clear signs at each turn, and distance markers.
- [ ] A cut-off time and a sweep vehicle or back marker.
- [ ] A bad weather plan.

Choose your start time with heat in mind, and publish the cut-off.

## Set up your entries

You set up most of this in the Laces app, and our page for [runs and marathons](https://laces.run/solutions/marathons) shows how it looks.

- [ ] **A ticket type for each distance,** each with its own price and number of places.
- [ ] **Shirt sizes and colours,** collected at registration if you give a shirt.
- [ ] **Emergency contact.** Ask for anything else only if you will use it.
- [ ] **Age group** if you award age categories. Use a ticket type for each category or an age-group question.
- [ ] **Medical notes,** only if your medical team will read them on the day.
- [ ] **Refund policy.** State it in your event description. Without one, the [Laces refund policy](https://laces.run/legal/refund-policy) applies. Decide whether entries can be transferred, and until when.
- [ ] **Payment clearance.** Your organization must be cleared before runners can register, even on a free ticket. Apply early, because a person at Laces reviews it. See [getting your event live](https://laces.run/guides/getting-started).
- [ ] **Closing date.** Entries close when the race starts unless you set an earlier time. If you order shirts from your entry list, close entries in time to place that order.

Be aware of what Laces does not do. It has no start waves, no automatic price rise on a date, and no timing or results. If you need chip timing, book a timing provider separately, and plan how you will give them your entry list. The app's participant CSV lists each paid runner by name, phone, ticket type and bib.

Then buy one low-priced entry yourself on a phone, on mobile data. Check the total and the ticket email.

Runners pay in the browser, with no app and no account. In Uganda they pay by MTN MoMo, Airtel Money or card. Kenya has M-Pesa and Airtel Money, Ghana has MTN MoMo, Telecel Cash and AT Money, Rwanda has MTN MoMo and Airtel Money, and Zambia has MTN MoMo, Airtel Money and Zamtel Kwacha. The service fee comes on top of your entry price, so the entry fee reaches you in full. Check the rates for [Uganda](https://laces.run/pricing/ug), [Kenya](https://laces.run/pricing/ke), [Ghana](https://laces.run/pricing/gh), [Rwanda](https://laces.run/pricing/rw) or [Zambia](https://laces.run/pricing/zm) before you set it.

[Try your entry fee](https://laces.run/pricing/ug): Enter a price per distance and see what runners pay at checkout and what you receive.

## Send runners the right message at each stage

A runner should not have to search a social media feed to find race information. Keep one up-to-date source, your event page, and plan your messages in advance:

- [ ] **At entry:** what they bought, and when and where they collect kit. The ticket email handles the confirmation, so your job is to make the event page answer the rest.
- [ ] **When entries open:** what to do if a payment seems to fail. Stay on the payment page, tap Check again, then send the prompt again or change the number there. Starting over from the event link can mean paying twice.
- [ ] **A few weeks out:** the route map, start times, cut-offs and pickup hours.
- [ ] **The week of the race:** arrival, parking, bag drop, what to do about the weather.
- [ ] **Race eve:** only what has changed. Late safety updates need to stand out.

## Plan kit pickup as its own event

Avoid leaving kit pickup to race morning if you can.

- [ ] Choose pickup places and hours, and publish them before you open entries.
- [ ] Order shirts from your size list, with a margin. The list shows each runner's size.
- [ ] Share stock out between pickup points according to what each one should expect.
- [ ] Plan for the awkward cases: a lost ticket, a wrong size, someone collecting for a friend.
- [ ] Decide what happens to kit nobody collects.

On Laces, your team scans the runner's QR ticket to see what they are owed. Confirming the handover takes a Pickup point lead or higher, so a Volunteer can't do it: give that role to whoever runs each table. If a screen is cracked, staff can search by name or phone, or type the order code.

## Set up race-morning check-in

- [ ] **Invite your team to the Laces app.** You can limit a volunteer to one event, and volunteers do not see your revenue.
- [ ] **Test every scanning phone the day before,** at the start area. Each scan checks the ticket online, so plan for a data connection on race day.
- [ ] **Separate lanes:** one for scanning, one for problems.
- [ ] **Have walk-ups covered.** A late entrant can register on your link from their own phone until entries close. If you also accept cash on the day, keep a separate signed list, because those runners will not be on your Laces list and will not have a ticket to scan.
- [ ] **Agree who handles the awkward cases:** a name that does not match, a lost email, or a ticket that has already been scanned. A repeat scan still reads as verified, with the time of the first check-in shown, so staff need to know what that means. These go to the problem lane.
- [ ] **Keep a backup:** a phone charger, a spare phone and a printed list from your export.

Do not treat a scan as your safety record. It tells you who collected or checked in, not who is still on the course. Use your start and finish counts for that, and have the medical team and marshals report by radio or phone.

## Keep money and operations in step

Vendors tend to want paying before the race, so check the timing of your income. In Uganda:

- **MTN MoMo** entries are withdrawable from your Instant Wallet immediately.
- **Airtel Money** entries are available in your Standard Wallet the next day.
- **Card** entries are available in your Standard Wallet the next day.

Outside Uganda, check the Earnings tab in the app and plan from what is ready. Your first withdrawal per organization is free. Budget for a transfer fee on each one after that, charged by the providers that move the money and shown before you confirm.

Cancelling the race makes you liable for refunds, including entry money you have already taken out, as our [payments guide](https://laces.run/guides/accept-payments) explains. Keep enough aside until the race has been run.

[Talk to the team](https://laces.run/contact): Send us your distances and details on WhatsApp or email, and a real person will help you set them up.

## After the finish

- [ ] Publish results only if you have a timing source you trust, and with runners' permission where needed.
- [ ] Reconcile entries, cash, refunds and withdrawals in one sheet.
- [ ] Pay vendors and thank volunteers, sponsors and authorities.
- [ ] Ask runners what went wrong at pickup, on the course and at the finish.
- [ ] Note your numbers for the next edition, while you remember them.

Announce the next date as soon as it is firm. Our guide to [promoting a running event](https://laces.run/blog/running-event-marketing-uganda) can help you build the next field.

## Frequently asked questions

### How far in advance should I open entries?

Open them once your route, permissions, price and refund policy are firm, and leave enough time to order kit from real numbers. Longer races need more notice, because runners need time to train.

### Can one race sell several distances?

Yes. Offer one ticket type per distance, each with its own price and number of places.

### Does Laces do chip timing or results?

No. Laces handles entries, payments, tickets, kit pickup and check-in. Book timing separately.

### Can a team or running club enter together?

Yes. One person can buy several entries in one order and give each runner's details. Each runner gets a ticket, and all of them lead to the order's one QR code, so staff scan it and tap the runner's name. Test the order yourself before you promote it.

### Can volunteers scan tickets on their own phones?

Yes. Invite them to your organization in the Laces app, and have each one try a scan before the day.
