# How to Organize a Festival in 2027: Tickets, Gates and Payments

> Organize a festival in 2027: set capacity per day, build passes your gate staff can read, keep sales open after day one, and manage vendors separately.

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

To organize a festival in 2027, start from how many people your site can safely hold on each day. Then build passes around that number, plan your gates for several days instead of one, and run vendors as a separate operation with its own paperwork. A festival is not a long concert. The hard questions are about day two: who may come back, who is new, and whether you can still sell.

[Create your festival](https://laces.run/app): Set up day passes, full passes and VIP as ticket types, each with its own price and limit.

## Work out what the site holds each day

Your limit comes from the site and whoever licenses it, not from your hopes. Before you set a price, walk the ground with a site plan and mark:

- Entrances, exits and emergency vehicle access
- Stages, and how sound carries to the neighbours
- Toilets, water, power and waste
- Vendor rows, with room for deliveries
- Shade, and where people will go if it rains

Ask for professional safety advice once your crowd is large, and get your approvals in writing. Who approves what varies by country and town, so start with our guide for [Uganda](https://laces.run/blog/how-to-organize-event-uganda), [Kenya](https://laces.run/blog/how-to-organize-event-kenya), [Ghana](https://laces.run/blog/how-to-organize-event-ghana), [Rwanda](https://laces.run/blog/how-to-organize-event-rwanda) or [Zambia](https://laces.run/blog/how-to-organize-event-zambia). If you have overnight camping, alcohol or fireworks, raise them early, because each can bring its own questions.

## Build passes your gate staff can read

On Laces, a pass is a ticket type with a name, a price and a number of places. You can create as many as you need. Name them so a tired volunteer can read one at a glance on day two:

| Ticket type name | Who it admits | Good name? |
| --- | --- | --- |
| Saturday only | Saturday's gate | Yes |
| Sunday only | Sunday's gate | Yes |
| Full festival | Both days | Yes |
| Full festival VIP | Both days, plus the VIP area | Yes |
| Early bird | Nobody knows without asking | No. Try "Early bird: Saturday only" |

**Each limit applies to one ticket type, not to a day.** Laces does not know that a full pass also takes up a place on Saturday, so do that sum yourself. Here is an illustration with made-up numbers. If the site holds 5,000 a day and you sell 2,000 full passes, then each single-day ticket type can be capped at 3,000. Change one of those caps and you have to recheck the rest.

Prices do not rise on their own. An early rate has to be its own capped ticket type, which sells out and leaves the standard price on the page.

Laces has no seat maps, so reserved seating has to be handled outside it. Sell a seated area as its own capped ticket type, and let people choose their seat on arrival.

## Know what a scan does on day two

This is where a festival parts from a one-night show, so brief your team on it.

Every ticket on an order carries that order's QR code. If the order has several people, the scan lists them and staff tap the guest. That first scan records their arrival. The app does not hold rules about which day a pass is valid. So:

- **A "Saturday only" ticket still reads as verified on Sunday.** The scan confirms it is a paid ticket for this event, and it shows the guest's name and ticket type. Reading that ticket type and turning the person away is the scanner's job.
- **A returning guest reads as verified too.** The screen adds a label such as "Checked in 18:40". It shows the time of the first arrival with no date, so on Sunday that label may refer to Saturday.
- **Laces does not issue wristbands** and is not linked to any wristband system.

A plan that works around this is to scan each guest at first entry, then give them a wristband for that day, in a colour that changes daily. Re-entry during the day is then a visual check, and the scanner is only for people without today's wristband. Keep your own count of wristbands issued per day, because you will want that daily figure for your safety team and your sponsors.

Print a card for each gate showing today's date, today's wristband colour and the ticket types valid today. Do the rest of your training from the [QR check-in guide](https://laces.run/blog/qr-code-tickets-event-check-in).

## Keep sales open after the first morning

Here is a trap for anyone running more than one day. **By default, Laces closes online sales when the event starts.** That suits a race, but on a two-day festival it would stop Sunday sales at the moment Saturday's gates open.

To change it, turn on the registration close setting in the app and pick a later time, up to the end of the event. The switch is worded as closing before the event, but it accepts a later time. Test it from a phone once it is set. While you are there, make sure your event's start and end times cover the whole festival.

Leaving sales open has a side effect: a "Saturday only" ticket stays on sale until you stop it. Once Saturday has begun, lower that ticket type's limit to the number already sold, so nobody buys it on Sunday by mistake.

## Take payment in the wallets people have

Guests pay from your link, with no app and no account:

- **Uganda:** MTN MoMo, Airtel Money or card
- **Kenya:** M-Pesa or Airtel Money
- **Ghana:** MTN MoMo, Telecel Cash or AT Money
- **Rwanda:** MTN MoMo or Airtel Money
- **Zambia:** MTN MoMo, Airtel Money or Zamtel Kwacha

Cards are offered in Uganda only. Visitors with a wallet from another of these countries can choose it under Paying from. For anyone from further away, see the [page for buyers abroad](https://laces.run/pricing/ww), and test it on your own event before you promise it. Outside Uganda, buyers type their number after the country code, without the first 0.

The guest pays a service fee on top of your price, shown before they pay, so you receive the full ticket price. Your organization must be cleared for payments first. Allow time for this.

One order can carry several people, which suits families and groups. They share one QR code, and staff tap each name at the gate. If a payment seems to fail, the guest should stay on the payment page, tap Check again, then send the prompt again or change the number there. Going back to the event link to start over risks a second charge.

[Try your pass prices](https://laces.run/pricing/ug): Enter each price to see what guests pay at checkout in your country, and what reaches you.

## Staff the gates for the arrival peak

Estimate each day separately, because Saturday afternoon and Sunday morning will look nothing alike. Have a help desk away from the scanning line, and test the data connection at every gate at the hour you expect the peak, because each scan needs a connection. A field that has signal at noon on a Tuesday may not have it with thousands of phones around it. Decide in advance who makes the call if the network fails, and what your staff should do.

Invite scanners through the app. A volunteer is tied to one event and does not see your revenue.

## Run vendors as their own operation

Laces sells entry to your festival. It does not manage stalls, take payment for food and drink on site, or settle money with vendors. Run that part in your own system:

- **Agreement:** a signed page for each vendor, covering the stall size and location, fee, what they sell, set-up and pack-down times, and power.
- **Compliance:** ask your local authority what food sellers and alcohol sellers need, and ask each vendor for it before you assign a stall.
- **Vendor staff:** free tickets are visible to anyone with your link, so don't use one for vendor passes. Give the gate a named list or a separate vendor entrance.
- **Settlement:** if you take a share of a vendor's sales, agree in writing how sales are counted. Otherwise a flat stall fee is far simpler.
- **Deliveries:** set hours when vehicles can come in, and keep them apart from the crowd.

## Keep the information in one place

Put everything in your event description: gate times per day, what is banned, re-entry rules, transport, and what you will do in bad weather. Laces events can also have an agenda page set out day by day, which you build in the app. Link to it, so your social posts don't become the record of what is on.

Your refund policy is optional. Write it in the event description, or the [Laces refund policy](https://laces.run/legal/refund-policy) applies. A festival needs one more answer than most: if one day is cancelled, what do full-pass holders get?

## After the gates close

Download your orders and your paid participant list from the app. Compare your sales by ticket type with your own gate and wristband counts, and settle with vendors from their agreements. Our guide to [managing registrations, payments and attendance](https://laces.run/blog/manage-event-registration-payments-attendance) shows how those records fit together.

Your first withdrawal per organization is free. After that, a fee charged by the providers that move your money is shown before you confirm. Keep something back until the event is over, since a cancellation leaves you responsible for refunds, even of money you have already withdrawn. The pricing page 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) shows what applies.

If your event is a single night, our guide on [how to organize a concert](https://laces.run/blog/how-to-organize-a-concert-2027) covers the artist and licensing side in more detail.

[Talk to the team](https://laces.run/contact): Send us your days and your gate plan. The team can tell you what Laces will and will not do.

## Frequently asked questions

### Can I sell day passes and full-festival passes?

Yes. Create a ticket type for each, with its own price and number of places. Each cap applies to that ticket type alone, so work out the daily total yourself.

### Does a day pass stop working on the wrong day?

No. The app does not block a ticket by date. It shows the ticket type, and your staff decide.

### Does Laces handle re-entry?

Not as a rule you can set. A repeat scan still reads as verified, with the first check-in time shown. A wristband alongside it is one way to handle this.

### Can I sell tickets after the festival has started?

Yes, if you set the registration close time later than the start. Otherwise online sales stop when the event starts.

### Can vendors pay for their stalls through Laces?

Laces has no vendor feature. Handle stall agreements and fees in your own system.
