Skip to content

Importing your finish times.

Import results so each runner's time and place can appear with their photos.

On this page 8

Availability: Results import is available for supported files and configured provider connections. It is not a timing system and does not enable live results by itself.

Why finish times matter

When you import finish times, a runner's time and place can appear on eligible photos. This helps connect race results with race-day photos; results import does not create finisher certificates.

Import your results

Open your event and go to the Finish times tab. Pick where your times come from. Most races use one source:

  • RunSignup: sync your results directly.
  • Athlinks: save your event id, then sync.
  • MYLAPS or ChronoTrack: connect with your credentials, validate, then sync.
  • Manual CSV: upload a results file.

After importing you will see counts for imported results, results held until athlete verification, and unmatched bibs. A held result already matches a private roster row, so you do not need to create an athlete account or public profile for it. PodiumBase attaches it automatically after that athlete signs in with the roster email and confirms the event and bib.

An unmatched bib is different: no active roster row has that event and bib. Fix those on the Athletes tab so those runners are not left out.

You do not need to connect RunSignup to use this workflow. A roster CSV before the race and a results CSV afterward are enough. Keep the bib values consistent between both files.

Public results and runner names

For official results from an organizer CSV or a configured RunSignup connection, account verification is separate from public results and photo processing. Unclaimed entries can appear in the public results table with their bib, finish time, and overall place, and contribute to the event's results analysis. When this event is set to show names, eligible roster display names can also appear; choose Bib numbers only to hide names in its public result views. Contact details are not published through this path.

To choose how runners appear in this event's public results, use Public result display on the Finish times tab. Select Names or Bib numbers only, then choose Save result display. Bib-only display hides runner names and athlete passport links in public result views; imported names remain available to event staff.

Finish times on public photos

After the normal review window, the official time and overall place can also appear on eligible public photos without an account claim. A photo must resolve safely to one roster entrant by bib. Ambiguous photos, youth results, and photos excluded by privacy or safety settings do not receive this overlay. Correcting a roster result removes its old overlay and restarts the review window; linking it to an account hands it over to the normal verified-result checks.

The public photo download uses the same gallery/share image, including its finish-time overlay when available. The standard clean high-resolution download remains a separate image without that overlay.

Splits for triathlon and multisport races

A results CSV can carry each runner's legs. Add one column per leg, named split_ plus the leg name, in race order: for example split_Swim, split_T1, split_Bike, split_T2, split_Run. Each cell is the time spent on that leg, as H:MM:SS or MM:SS. Leave a cell empty when a runner has no time for that leg.

The legs show on the runner's result page in the order of your columns, and only while their finish time is public. A runner who hides their times hides their splits too. If a split cell cannot be read, PodiumBase still imports that runner's finish time, leaves their splits out, and tells you how many rows it skipped. Uploading a file without split columns keeps the splits you imported before. Include split columns before results lock. Once a result is locked, a new upload cannot change it; add or fix its splits through Scoring and locks instead.

Locking happens automatically

You do not lock results by hand. Results lock automatically a set time after import, usually about a day later. Locking finalizes results and can release finish-time overlays for eligible photos. A locked result may enter the certificate queue, but issuance is a separate, gated process: certificate rendering must be enabled and the athlete must meet the eligibility checks. Results import alone does not guarantee a certificate. Athletes can check Media for a certificate already issued to them. The tab shows whether results are still pending or already locked.

If you need finish times live sooner than the automatic window, ask in the chat and a teammate can help.

Fixing a locked result

A locked result is final, so nothing changes it by accident. When one is wrong, use Scoring and locks on the Finish times tab: find the runner by bib, and an Org Admin unlocks that one row with a short reason. You or another organizer of the event can then fix the status, times, places or splits. Saving locks the row again. If nobody saves, the row locks again on its own after the usual window. The unlock reason shows on the row until it locks again, and the runner can see it on their own record meanwhile, so keep it factual.

Correction requests from runners

A runner can ask you to check their own result from their result page. Their requests appear under Correction requests on the Finish times tab, with what they say is wrong and, if they gave one, the time they think is right. Only you and that runner see a request. Marking a request fixed does not change the result, so fix the row first, then mark it fixed or decline it with a note.

For results while the race is running, first read understanding live-results availability. If live results are not confirmed for the event, keep the timing provider's official link as the live destination and import the final results here afterward.

Next step

Upload your results from your organization admin.

your organization admin
Did this answer your question?