Open entries without building a website or configuring anything yourself
Taking entries through a Google Form and bank transfers pushes all the real work into the back office: checking transfer slips one by one, answering chat messages about whether the money arrived, and reconciling it all in an Excel file that exists in several versions.
Switching to an off-the-shelf system usually just moves the problem to the setup screen — early-bird pricing with no end date, a cap set on the wrong distance, entries opened before the payment channel is connected. Mistakes like these do not merely make the entry page untidy; they take money off the top of the event, and they are usually discovered after runners have started entering.
Most organizers are experts at running events, not at configuring software. Having to guess what each field means in the days before you go on sale is a risk you should not have to carry.
The other route many events take is commissioning their own registration site. It looks the part, but it has no audience: a brand-new site has no traffic and no track record for runners to judge it by, and when it comes to entering card details or transferring money to a site they have never seen before, a meaningful share of people close the tab instead. That lost revenue is nearly invisible, because it never appears in any report.
And the moment that catches people out most is the opening minute, when everyone arrives at once: payment queues form, and some entrants pay twice, get stuck mid-payment or drop out halfway. This happens at every event — the only difference is whether someone prepared for it.
Distances, prices, sale periods, caps, age groups and what each distance includes — send them over and we check them first for anything that contradicts itself or is missing: early-bird pricing with no end date, overlapping age groups, a distance with no cap on it.
We set up every distance, price tier, cap, solo and team option, add-on and event-specific question, then send you the live screens to review before the on-sale date. You never have to learn the system to open entries, or wonder whether it was set up correctly.
Runners enter and pay themselves and get their own confirmation email; teams and relays are handled on a single entry. Nobody has to answer "has my payment gone through?" in chat, and nobody has to key anything in afterwards. Meanwhile you can see which days entries move and which distances are filling fast or slow — the numbers you need to decide on promotions and how much merchandise to order, while there is still time.
The list used for bibs, timing, pack collection and results is the same data the runner entered on day one. Nothing is exported and re-imported, which is where entrant data most often drifts out of sync.
Set the whole price ladder in advance and the system applies the right price based on the day the runner enters. Nobody has to get up at midnight to change prices, and the entry page shows past tiers struck through — which creates urgency without you having to announce anything.
Set a window that requires a code to reach the entry form — for last year’s runners, club members, or people holding a reserved place. Everyone else cannot open the form yet, and it gives you a chance to test the whole flow with a small group before the real on-sale date.
Set team sizes from 2 to 10 per distance. The captain fills in the whole team on one entry and pays once, so your team never has to work out who belongs to which team across a pile of separate entries.
Set male and female age groups with whatever bands you use, and choose whether age is counted from the year of birth or the exact date. Runners are placed in their group at entry, so nothing has to be re-sorted when results are published or prizes are awarded.
Add your own questions: shirt size, delivery address, blood type, emergency contact, a photo upload, or tax invoice details. You decide which are required, which distances they apply to, and how long entrants can go back and change them.
Extra shirts, shuttle buses, accommodation or souvenirs — each with its own price and stock cap. Runners choose them while entering and pay once, so you get both the revenue and the quantities to prepare in the same place.
One distance can carry different rates by nationality or country, which suits events with overseas entrants or a local rate. There is no need to duplicate the distance and confuse everyone choosing from the list.
Runners can complete an entry and pay without signing up, which stops you losing the ones who will not stop to set a password. If they later log in with the same email address, the entry is pulled into their account automatically.
Your own site helps as a shop front, but it comes with no audience — the people who reach it are the ones who already know your event. On the platform, your race sits where 100,000+ visits a month and a base of 600,000+ registered runners already circulate. The point that gets overlooked is trust: runners who have entered and paid through this same system before decide faster than they do on a payment page they are seeing for the first time.
The opening minute is the heaviest load of the entire event, and the most expensive moment to get wrong. After twelve years around race entries we know where it tends to break: before you go on sale we verify the payment channel and run a real entry end to end, and during the opening the team watches the sale so anything unusual is handled immediately, rather than waiting for you to report it.
We do. Duplicate payments, money taken with no entry created, sessions abandoned halfway — we have seen these thousands of times over twelve years, so there is a repeatable way to find and fix each one. You are not left matching transfer slips against totals, and the runner gets an answer from someone looking at the actual record rather than being told to try again.
Because registration settings are tied directly to money. An early-bird end date that is one day out, or a cap left open on a distance that has already filled, is real revenue lost and not always recoverable. So we check and configure every event before it goes on sale, and you review it against what you intended — which takes less of your time and is far harder to get wrong.
Send it over any time and we will make the change the same day, and we can give you edit rights if you would rather do it yourself. The real limits are that price tiers already in the past cannot be changed retroactively, and the tier currently on sale can only have its end date moved — so entries already sold are never re-priced after the fact.
Distances and the price for each tier, how many places per distance, the age groups competing for prizes, what each distance includes, the questions you want to ask entrants, and your payment channel. You can start before all of it is final — we configure what is ready and fill in the rest before the on-sale date.
Yes, by the runner or by your team, within the window you set. The system keeps a history of who changed what and when, so it can be checked later without relying on anyone’s memory.
The data belongs to the organizer. You can download it whenever you like, in a format that is ready to work with. RunLah stores and processes it as your service provider, nothing more.