Runners download their own — nothing to print, nothing to hand out
A certificate is something runners genuinely want, and one of the most time-consuming things an organizer deals with after the event, because each one carries a name and a time and so cannot be prepared in advance like a medal or a shirt.
Events handing out paper choose between printing in advance with a blank space for the time to be written in by hand, or setting up a printing point on the day and adding another queue to the longest hour of the morning. Either way there is a pile left over from people who never collected, which turns into posting them out one envelope at a time.
Making files yourself is not much lighter: someone has to place a name and a time onto the same design a thousand times over, then send each one back to its owner over chat or email — and one misspelling means another round of corrections.
The other common approach is putting every file in a folder and sending one link to everybody, which simply moves the burden onto the runners, who now search for their own file among a thousand other people’s names — and the ones who cannot find it ask you anyway.
Whichever route you take, it arrives later than it should. A certificate that lands two weeks afterwards arrives once the feeling of the day has faded, so the person who would have posted it on race evening never does — word of mouth the event earned and did not get.
You send us the event’s artwork and the RunLah team places the fields for name, time and anything else you want onto it, then you check a real sample before approving. What runners receive is your event’s design in full, not a generic template every race shares.
No waiting for an announcement and no distribution round. A runner who has finished opens their own result page and the download button is right there — no login, no form to fill in, and no waiting for someone to send them a link.
Their name, bib number, distance, age group, total time, chip time and placing are drawn onto your design at the moment of download. The file saves straight to the device, on a phone or a computer, ready to post or to print later.
You can include a QR pointing back to that bib’s result page, so anyone looking at the certificate can see the splits and placings the system recorded. It is not just a nice image — it can be traced back to a real event.
When a result is corrected after the event, anyone downloading afterwards gets the correct certificate, because it is generated from the latest result every time. There is no folder of stale files to clean up and no wrong version sitting on a link you already sent.
No paper, no printing point, no queue, no leftover pile from people who never collected, and no envelopes to post. How many people download makes no difference to your costs — unlike every other giveaway, which has to be estimated in advance.
Runners have it before they leave the venue, which is when posting peaks. A certificate carrying their name and your event’s branding becomes media they publish for you, rather than a file arriving once the moment has passed.
Everyone who finishes has one waiting on their result page — whether they left early, ran their battery flat or only remembered at home. There is nobody on your side answering questions about where the certificates are.
It is not sent once and gone; it is regenerated on every download. A runner who deleted it, changed phones or wants another copy to print can come back and get one without asking anybody to make it again.
The name on the certificate is the one entered at registration, so anyone using the English site gets their name in Roman script rather than a transliteration somebody at the desk guessed at.
The only way to the certificate is through their own result page — which carries your event name, their placing and a link to next year’s edition. The event gets visitors back after it is over, instead of ending at a single email attachment.
No. The per-bib result page is public, and tapping the button saves the file to the device immediately. No email address or phone number is asked for first.
No — the button appears only for runners with a recorded time at the final point, which is deliberate, since a certificate attests to having finished. They can still see whatever the system recorded on their own result page as usual.
An image at the size set when the design was laid out. If that size is generous enough for A4, it can be printed at a shop. It is not a PDF, so if you intend runners to print and frame it, mention that at design time and we will set the dimensions accordingly.
Yes — overall placing, age-group placing and the prize won, as well as splits with the pace for each section. Events wanting the winners’ certificates to look different from the rest can arrange that at design time.
Not as a file. Runners download it from their result page, but the thank-you email after the event has a button back to their own result — which is how most people come back to download it.
As long as the event’s results page exists, which has no deletion date. Runners can come back and download again at any time, and each download is generated from the latest result.
A file already saved on a runner’s device cannot change — it is theirs. Everything downloaded afterwards is correct, so nobody has to chase the whole field to download again.
Not currently, because the certificate is generated from that bib’s result in RunLah’s system at the moment of download — name, distance, age group and time. Events timed elsewhere have no per-bib result page for the download button to live on.
The entire background is your artwork — logos, colours, graphics, sponsor space, however you want it. The RunLah team places the name and time fields onto it and sends you a real sample to check first, so you do not discover on race day that a long name runs outside its box.