What is AfterRun?
AfterRun is a lightweight, low-admin results tool for informal running events where results are optional. It helps organisers prepare simple private results after timed runners opt in and record normally.

Answers for organisers and timed runners using AfterRun for informal running events with optional results.
AfterRun is delayed, private-first, and consent-based, not live timing or a public Strava leaderboard.
AfterRun is a lightweight, low-admin results tool for informal running events where results are optional. It helps organisers prepare simple private results after timed runners opt in and record normally.
AfterRun is for organisers of small or informal running events who want optional results without turning the event into a formal race setup.
Yes. Timing is optional. Timed runners opt in to results, while untimed runners can still take part socially.
Yes. Untimed runners can join socially without connecting with Strava and without appearing in results.
AfterRun helps organisers offer optional results without chips, barcodes, scanners, finish funnels, manual stopwatch timing, live timing infrastructure, or lots of finish-line admin.
No. AfterRun is delayed, not live. It checks for event activities after the organiser's deadline and keeps results private for review.
AfterRun checks at the organiser's upload deadline and then checks once more one hour later.
The first check happens at the upload deadline. It looks for activities from timed runners who opted in and connected with Strava for the event.
The second check happens one hour later. It gives normal Strava sync delays a little extra time without turning AfterRun into constant polling.
Two checks keep the workflow calm and delayed while still giving runners time for normal upload or sync delays.
If the activity appears before the second check, it can still be considered. If it is not available by then, the row may stay missing until the organiser decides what to do.
A timed runner opts in, connects with Strava, records the run normally on their own watch or phone, and lets the activity sync to Strava as normal.
No. Timed runners record and sync through Strava as normal. There is no separate AfterRun activity upload.
Yes. Timed runners use their own watch or phone, just as they normally would.
Timed runners should start recording at the organiser's group start signal and stop at the agreed finish point. They should avoid pausing during the run.
If AfterRun cannot find a suitable synced activity by the checks, the runner's row may stay missing until the organiser reviews it.
No. A timed runner records with their own device and lets the activity sync to Strava. No chip, barcode, bib, or scanner is needed for AfterRun.
The organiser prepares the event, invites timed runners, sets the upload deadline, reviews results after the checks, resolves unclear rows, and decides what is ready.
Yes. AfterRun is review-first. The organiser decides what should be accepted, held for review, or handled privately outside the runner flow.
AfterRun is designed to keep finish-line admin low. It does not require a chip setup, scanners, or a formal finish process.
Yes. Results are private by default and are meant to be reviewed before anything is shared.
Yes. That is the intended shape: informal running events where some people want optional results and others may simply join socially.
Many runners already record activities with Strava. AfterRun uses that existing recording habit so timed runners do not need a new timing device or separate upload.
No. AfterRun does not scrape public Strava leaderboards or public activity pages. It uses consent-based access for timed runners who opt in for an event.
AfterRun uses the minimum Strava access needed for the result check. It is designed around reading a consenting timed runner's activities for the event.
For automatic matching in the current version, the event activity needs to be visible enough for AfterRun to read it, such as Followers or Everyone.
Activities set to Only You or private do not auto-match in this version and may need private organiser review.
No. AfterRun is standalone and is not part of Strava. Runners still record and sync in Strava as normal.
AfterRun results are minimal: runner name, position, time, status, source, and optional category or club where relevant.
Matched means the result has been accepted for the draft results. In the current review build, matched results are shown only in private organiser views.
Needs review means AfterRun found something the organiser should check before ranking the result. It is not an accusation or an error.
Missing means no suitable activity has been found for that timed runner yet.
The current review build does not provide public, self-service, runner-entered, or live organiser manual-entry UI.
Only matched results receive numeric positions. Needs review, missing, and removed rows stay out of rankings until the organiser resolves them.
Needs review, missing, and removed rows are not ranked. They stay out of the ranked results until the organiser resolves them.
No. AfterRun is private and review-first by default. It is not a public leaderboard product.
A result needs review when AfterRun finds something close or unclear that the organiser should check before ranking.
The row should be flagged for organiser review because the activity started outside the expected window.
The row should be flagged for organiser review because the distance was outside the expected range.
AfterRun should not guess. The row should be marked needs review so the organiser can decide.
The organiser should review it before accepting the result.
A significant difference should be reviewed. It may reflect pauses, stopped time, device behaviour, or Strava calculation behaviour.
AfterRun uses elapsed time as the result basis. Moving time is not used for ranking.
The row stays private for organiser review. Any future exception handling or correction must remain organiser-controlled and private, not public or runner-entered.
AfterRun shows minimal result information only, such as runner name, time, position, status, source, and optional category or club.
No. AfterRun does not show maps or GPS traces.
No. AfterRun does not show heart rate, cadence, power, calories, or unnecessary analytics.
AfterRun is designed to avoid storing full Strava activity details as event results. The normal result view stays minimal.
No. Results are private and review-first by default.
Yes. Runners can contact AfterRun to request deletion. See the data deletion page for details.
Read the privacy page, data deletion page, or support page.
No. AfterRun is a lightweight optional-results tool for informal running events.
No. AfterRun does not use chip timing.
No. AfterRun checks later and is not live timing.
No. AfterRun does not scrape public Strava leaderboards or public activity pages.
No. AfterRun is focused on optional delayed results, not full event registration.
No. Timed runners record on their own watch or phone and sync to Strava as normal.
No. AfterRun is a standalone optional-results tool for informal running events.
No. AfterRun is standalone and is not part of Strava.