A useful shared run starts with an agreed time, route and purpose. A QR code or invitation link helps people find the session; it does not explain how the group will run together. Use this checklist for a local crew or friends joining from different places.
Decide what counts as taking part
Choose a social run, a shared duration or a distance challenge. Write down whether walking is welcome, whether runners need the same route and how someone can leave early. For a remote 10K, specify whether each runner completes their own measured route or an organiser supplies one. Hills, crossings and GPS conditions make remote performances difficult to compare directly.
Give the start time with a time zone. A calendar invitation is easier to interpret than “Saturday at nine” when a club has members in several countries. Include an organiser contact and a fallback plan if the app or network is unavailable.
Test the invitation before the day
Ask one participant to open the link or scan the QR code on the device they will use. Check the session name and host before joining. If the code fails, request a fresh invitation from the organiser rather than guessing codes. Share invitations within the intended group, especially when the session exposes live locations.
Confirm that each runner is joining as a participant, not opening the spectator link. Agree which device records the run. Recording the same activity on several devices can complicate the results and subsequent uploads.
Countdown and active sessions
A shared countdown is a coordination cue. Network delays, device clocks and the moment someone starts moving can differ; a five-second animation is not certified race timing. For a friendly sprint, choose a clear, traffic-free area with permission to use it and agree a visible finish. Use an event organiser's timing system for official results.
If an app permits only one active session, finish or leave the previous one before joining another. Do not abandon an active recording solely to fix an invitation without checking whether it has saved.
Where Runwiv fits
Runwiv is being built around shared sessions and browser spectators. Public app access is still in pre-launch, so these are planning checks rather than a promise that a specific screen or countdown is available today. Read the current product facts, explore running with friends, or try the spectator demo.