A virtual run removes the shared start line, but it does not remove the organiser's work. Participants still need to know exactly what they are joining, when an activity counts, what evidence to submit, how decisions are made, and what happens after they finish.
The most trustworthy events are not necessarily the largest or most expensive. They are the ones whose promises, rules, systems, and team capacity agree with each other. This playbook helps clubs, schools, companies, charities, and community teams design that complete experience.
Quick start: make these decisions before creating the event
- What is the event's purpose, intended audience, and measurable definition of success?
- Will the target be completed in one activity or accumulated across several activities?
- Which activity types, locations, devices, and evidence will be accepted?
- What are the registration, activity, submission, review, results, and reward dates in one named timezone?
- Is the event free or paid, and what exactly does any fee include?
- How will payment receipts, run results, corrections, duplicates, and appeals be reviewed?
- Will the event rank speed, accumulated distance, completion, teams, or nothing competitive?
- What participant data is truly required, who may access it, and when will it be removed?
- Who owns participant support, payment review, result review, communications, and escalation?
- What will happen if weather, technology, demand, fulfilment, or staffing does not follow the plan?
Do not publish yet if the team cannot answer a question that affects eligibility, money, proof acceptance, safety, ranking, privacy, or rewards. A clear draft is easier to repair than a live promise.
How this playbook was prepared
This is practical planning guidance, not legal, tax, insurance, medical, financial, or safeguarding advice. It combines HelloRun's current virtual-event workflow with event risk-management, data-minimisation, and accessible-form guidance available in July 2026.
Requirements vary by country, participant age, event structure, fundraising model, prize value, and organisation type. Confirm applicable local laws, permits, insurance, consumer rules, tax treatment, safeguarding duties, and payment obligations before accepting registrations or money. A waiver records acknowledgement; it does not erase an organiser's responsibilities or replace professional advice.
1. Write a one-page event brief
Begin with a short internal brief rather than a poster. If the operating team cannot explain the event on one page, participants will struggle to understand it on a registration page.
Copyable event brief
- Purpose: Why does this event exist?
- Audience: Who is it designed for, and who is not eligible?
- Format: Single activity, accumulated distance, completion-only, or competitive.
- Goal: The exact distance or completion requirement.
- Dates and timezone: Every opening, closing, and publication date.
- Entry model: Free or paid, inclusions, payment method, and refund position.
- Evidence: Accepted sources and the minimum fields reviewers need.
- Recognition: Certificate, badge, leaderboard, physical reward, or participation record.
- People: Named owners for operations, reviews, support, and communications.
- Success measures: Registrations, paid confirmations, valid completions, response time, participant satisfaction, or another useful outcome.
- Constraints: Budget, staffing, fulfilment capacity, platform limits, and legal requirements.
Use success measures that the team can act on. Registration count alone does not reveal whether payment review was timely, instructions were understood, submissions were valid, or participants received what was promised.
2. Choose a format that matches the purpose
Single-activity virtual run
The participant completes the full target in one recorded activity. This suits a race-like 3K, 5K, 10K, or other distance when a comparable single result matters. It is simpler to review, but it may be less accessible to beginners or people with limited scheduling flexibility.
Accumulated-distance challenge
The participant combines approved activities during the event window. This suits consistency, wellness, club mileage, and longer goals. The rules must explain minimum activity distance, maximum or unlimited entries, allowed activity types, how totals are calculated, and whether exceeding the target affects ranking.
Completion-only or competitive
A completion event recognises participants who meet the published requirement. A competitive event ranks an approved result using a disclosed method. Do not add a speed leaderboard merely because the platform can display one. Ranking changes participant behaviour, review workload, tie handling, and dispute risk.
Time-based, team, charity, or mixed-mode concepts may need processes beyond a standard distance event. Confirm that the chosen platform and team can support the mechanics before advertising them.
3. Build one timeline with six distinct stages
“Event ends Friday” is not enough. Publish exact dates, times, and a named timezone for each stage:
- Registration window: When entries open and close.
- Activity window: When qualifying activities may occur.
- Submission window: When evidence may be uploaded, including any grace period after the activity window.
- Review window: When the team expects to decide pending evidence and corrections.
- Results date: When rankings or the verified finisher list become final.
- Recognition or fulfilment date: When certificates, badges, or physical items should become available or ship.
Separate the activity deadline from the submission deadline if runners are allowed time to upload proof. State whether the deadline follows the participant's location or the organiser's timezone. Decide how daylight-saving changes or a platform outage will be handled before they become disputes.
4. Publish complete mechanics before registration
Rules should let a reasonable participant decide whether to join and complete the event without relying on private messages. Use headings and lists instead of hiding critical terms inside promotion copy.
Copyable mechanics outline
- Eligibility: Age, location, organisation, membership, and guardian requirements.
- Categories: Distance, mode, team, or participant categories and how to choose one.
- Qualifying activity: Run, walk, wheelchair activity, treadmill, or another expressly allowed type.
- Completion rule: One activity or accumulated activities; minimum distance; overshoot and rounding treatment.
- Timing rule: Elapsed or moving time, pauses, and whether pace affects eligibility or ranking.
- Evidence: Accepted apps, watches, screenshots, links, treadmill records, and manual entries.
- Required fields: Date, distance, duration, activity type, source, identity, and route only when necessary.
- Corrections: What happens when proof is unclear, incomplete, or submitted to the wrong category.
- Deadlines: Exact dates, times, timezone, and any grace period.
- Ranking: Metric, eligibility, approval requirement, tie-break method, and publication date.
- Invalidation: Duplicate evidence, dates outside the window, prohibited activities, manipulated records, or other defined reasons.
- Privacy: What is collected, what becomes public, who reviews it, and where participants can ask questions.
- Recognition: Certificate, badge, reward, shipping limitations, and conditions.
- Changes and disputes: How necessary changes are announced and how a participant may request review.
Avoid broad clauses that let the team change anything without explanation. If a material change becomes unavoidable, document the reason, notify affected participants through the promised channels, and offer the remedy required by applicable rules and policies.
5. Design proof rules around the event's risk
A casual completion challenge and a prize-bearing speed competition should not use identical review standards. Decide what evidence is proportionate to the consequence of approval.
Minimum useful activity evidence
- Activity date within the permitted window.
- Distance and visible unit.
- Duration or time when relevant.
- Activity type.
- Recognisable app or device source.
- Participant identity only to the extent required to match the registration.
- Route or supporting fields only when the published policy requires them.
Decide explicitly whether treadmill activities and manual entries count. A treadmill may be reasonable for completion but excluded from a GPS-based ranking. Manual evidence may require a second supporting record. These are event choices, not universal rules.
Read What Counts as Valid Run Proof? and the virtual run tracking-app comparison before writing the policy.
6. Create a fair review and correction policy
Reviewers need the same rubric. Without it, identical submissions can receive different outcomes depending on who opens the queue.
Separate unclear evidence from invalid evidence
- Unclear: A required field is hidden, the image is blurry, the unit is ambiguous, or the wrong file was attached. Allow correction when the published rules permit it.
- Invalid: The activity is outside the event window, below the required distance, duplicated, prohibited by the mechanics, or cannot be matched to an eligible registration.
- Needs escalation: The rules are ambiguous, a system issue affected the submission, or manipulation is suspected but not established.
Record a concise reason for rejection or correction. Avoid accusing a participant of fraud based only on an automated flag. OCR, duplicate detection, pace checks, and other signals can help reviewers notice inconsistencies; a responsible human decision still requires the original evidence, submitted values, event rules, and available context.
7. Define the leaderboard before accepting entries
A leaderboard should answer one published question. Examples include fastest approved time for a single distance, greatest approved accumulated distance, or completion status without ordinal ranking.
- Include only results whose status qualifies under the rules.
- Define whether ranking uses elapsed time, moving time, distance, percentage completed, or another metric.
- Publish category and mode boundaries.
- Choose a tie-break method before the first tie.
- State when rankings remain provisional and when they become final.
- Do not expose proof images, contact details, review flags, or private notes on a public leaderboard.
HelloRun's public leaderboard is based on approved submissions by default. The guide How Leaderboards Work in Virtual Running Events explains why pending evidence should not be treated as a final result.
8. Plan free, paid, charity, and reward-based events honestly
Free events
Free does not mean costless to operate. Estimate platform work, design, participant support, reviewer time, certificates, prizes, storage, and fulfilment before promising scale.
Paid events
State the price, currency, inclusions, exclusions, payment instructions, confirmation process, cancellation terms, refund rules, and fulfilment expectations before checkout or receipt submission. Keep payment evidence separate from activity evidence.
HelloRun's current paid-registration flow uses participant-uploaded payment receipts and organiser review. It should not be described as an integrated payment gateway or instant payment confirmation. Reviewers compare the receipt with the registration and published payment instructions, then approve or reject it with an appropriate explanation.
Charity or advocacy events
Name the beneficiary accurately, confirm authority to use its name and branding, explain whether entry fees or a defined amount support the cause, identify deductions or costs where required, and avoid tax-deductibility claims unless they are valid in the relevant jurisdiction. Keep records appropriate to applicable fundraising and accounting obligations.
Prizes and physical rewards
Publish eligibility, quantity, selection method, tie handling, geographic restrictions, shipping responsibility, expected dates, and substitution or delay terms. Do not advertise a medal, shirt, prize, badge, or certificate that has not been approved and operationally planned.
9. Minimise participant data and protect route privacy
Identify why every requested field is needed. Data-minimisation guidance recommends collecting information that is adequate and relevant for a defined purpose, but no more than necessary. Decide who can access registration records, payment receipts, activity proof, and review notes, plus how long each category should be retained.
- Do not collect emergency contacts for a purely virtual activity unless there is a justified operational purpose.
- Do not make payment receipts or proof screenshots public.
- Warn participants when route maps may reveal a home, school, or workplace.
- Separate public leaderboard fields from private operational records.
- Publish a contact path for privacy questions and applicable rights requests.
Review the HelloRun Privacy Policy and Organiser Terms. An organiser may have additional responsibilities under its own policies and local law.
10. Make registration and communication accessible
Accessible forms are easier for everyone. Use clear labels, concise instructions, understandable validation, visible error messages, and confirmation after submission. Avoid relying on colour alone or placing essential rules only inside an image.
- Use plain-language headings and short rule sections.
- Provide meaningful alternative text for event images.
- Test registration and proof instructions with keyboard and mobile navigation.
- Explain errors and how to correct them.
- Offer a support route for participants who cannot use the default evidence process.
Youth events need an appropriate safeguarding plan, guardian consent where required, age-appropriate communication, restricted data collection, and clear escalation responsibilities. Obtain qualified local guidance rather than copying an adult community event waiver.
11. Assign operating roles before launch
One person may hold several roles in a small event, but every responsibility still needs an owner and backup.
- Event owner: Final decisions, published promises, budget, and escalation.
- Platform operator: Event setup, categories, dates, access, and status changes.
- Participant support: Questions, corrections, accessibility needs, and response targets.
- Payment reviewer: Receipt review for paid registrations.
- Result reviewer: Activity evidence, notes, approvals, rejections, and escalation.
- Communications owner: Launch, reminders, changes, results, and fulfilment notices.
- Privacy or safeguarding contact: Sensitive issues and appropriate referrals.
Define who may approve their own entry or the entry of a close associate. For competitive or prize-bearing events, use a second reviewer or escalation path when a conflict could undermine trust.
12. Configure HelloRun without overstating automation
An approved organiser can create and preview an event, configure its format and dates, publish registration information, manage registrants, review payment receipts for paid events, review run proof, and configure supported recognition features.
HelloRun does not continuously track a participant's GPS location. Runners submit activity evidence or import supported activity data, and OCR may assist with extracting fields from screenshots. OCR is not perfect and does not replace organiser or admin review.
For paid events, manual payment-receipt review is separate from run-result review. Approved submissions can feed eligible leaderboards, and approved results may receive configured certificates. Do not promise a certificate, badge, ranking, or physical item merely because a setting exists; finish configuration and test the output first.
Start an organiser application if required, or open Create Event when your account is eligible. Review the runner-facing How It Works page so your instructions use the same workflow participants will see.
13. Test the full runner journey before publishing
Do not test only the organiser form. Use a realistic participant perspective from discovery through completion.
- Find the event from the public Events page.
- Read the description, categories, dates, fee, rules, and reward promises on mobile.
- Register with the minimum required information.
- For a paid test, verify that payment instructions and receipt status are understandable.
- Confirm when run-result submission becomes available.
- Upload representative valid and unclear evidence.
- Review the organiser decision and participant-facing reason.
- Confirm the approved result appears only where the rules say it should.
- Preview the certificate or badge when one is promised.
- Check every email, support link, policy link, deadline, and timezone.
Ask someone who did not write the mechanics to perform the test. Familiarity hides assumptions.
14. Promote the exact event you built
Promotion should summarize the event, not replace its rules. Use the same title, categories, fee, dates, inclusions, and reward terms everywhere. Link back to one authoritative event page.
- Do not use invented participant counts, testimonials, partnerships, scarcity, or prize claims.
- Do not call an activity free when a mandatory purchase or fee applies.
- Do not imply that a charity receives all proceeds when costs or deductions apply.
- Do not encourage unsafe routes, deadline chasing, or exercise beyond a participant's capacity.
- Schedule reminders for registration close, activity start, submission deadline, and status checking.
Link participants to the low-light running safety guide when flexible timing may lead them to complete activities before sunrise or after dark.
15. Operate the event in manageable queues
Review regularly rather than waiting for the final deadline. Track registrations, unpaid or pending payment receipts, submitted results, correction requests, escalations, and participant questions separately.
- Publish a realistic response time and update it if demand changes.
- Use standard reasons, but add enough context for the participant to act.
- Do not bulk-approve evidence merely to clear the queue.
- Escalate ambiguous cases instead of inventing a private exception.
- Keep an audit trail of material rule changes and review decisions.
- Communicate widespread system issues once, through the official channel.
16. Prepare failure plans
- Unsafe weather: Remind participants that they choose safe local conditions; extend or adjust only through a documented, consistently applied decision.
- Tracking-app outage: Use the prepublished alternative-evidence rule rather than improvising for individual runners.
- Deadline surge: Add reviewers, triage incomplete entries, and communicate revised review timing without silently changing activity eligibility.
- Platform interruption: Record the affected period, preserve reports from participants, and publish one remedy for similarly affected entries.
- Ambiguous mechanics: Pause disputed decisions, document the interpretation, and apply it consistently.
- Suspected manipulation: Preserve evidence, restrict sensitive details, and use the review/escalation process rather than public accusations.
- Reward delay: Tell affected participants what changed, what remains confirmed, and when the next update will arrive.
- Low registration: Deliver the published event unless the cancellation policy allows another outcome; do not fabricate momentum.
17. Finalise results and close the event
Resolve pending reviews and corrections before marking rankings final. Publish only the participant information required by the event. Release configured certificates or badges after the qualifying result is approved, and communicate physical fulfilment separately.
Closeout checklist
- All payment and result queues reviewed or assigned a documented status.
- Leaderboard filters, categories, tie handling, and final status checked.
- Certificates, badges, prizes, and shipping lists reconciled against eligible records.
- Participants told where to find results and how to report a genuine error.
- Refund, cancellation, and fulfilment obligations tracked to completion.
- Sensitive exports and temporary working files restricted or removed according to the retention plan.
- Team review completed using registration, completion, support, review-time, and feedback measures.
Ask concise feedback questions: Were the rules understandable? Was registration manageable? Did participants know what proof to submit? Were decisions explained? Did recognition arrive as promised? Use the answers to change the next brief, not merely the next poster.
Pre-launch checklist
- Purpose, audience, format, and success measures approved.
- Dates, timezone, categories, activities, and completion rules consistent everywhere.
- Fee, payment, refund, charity, prize, and fulfilment statements verified.
- Proof requirements, correction rules, invalidation reasons, and ranking method published.
- Privacy, retention, accessibility, youth, and safeguarding needs reviewed.
- Operating owners and backups assigned.
- Valid, unclear, invalid, duplicate, and late submission scenarios tested.
- Public event page, registration, support, review, leaderboard, and certificate journey tested.
- Failure plans and participant communications prepared.
Frequently asked questions
How long should a virtual run remain open?
Match the activity window to the format and audience. A single 5K may need a weekend or a flexible multi-day window; a large accumulated target may need several weeks. Also allow realistic time for evidence submission and review. There is no universal ideal duration.
Should treadmill activities count?
They can count when the published event design allows them. Define acceptable treadmill evidence and whether indoor results qualify for completion, ranking, or both.
Can OCR approve results automatically?
No. OCR can assist with reading fields from an image, but extraction may be incomplete or wrong. The runner should review submitted values, and the organiser or admin should decide according to the event rules and original evidence.
Should every virtual run have a leaderboard?
No. Completion-only recognition may better fit beginner, school, workplace, charity, or wellbeing events. Use a leaderboard only when competition serves the purpose and the review process can support it fairly.
What data should registration collect?
Collect only what has a defined purpose for eligibility, communication, payment, results, recognition, or a justified operational requirement. Do not request information merely because another event did.
Does a waiver remove organiser liability?
No document should be presented as removing every responsibility. Waiver effect and event obligations depend on applicable law and circumstances. Obtain qualified advice for the actual event.
Where can organisers get HelloRun help?
Review the HelloRun FAQ, relevant policies, and contact support with the event name and a specific workflow question.
Final takeaway
A well-run virtual event is a chain of aligned decisions: purpose, format, rules, registration, money, evidence, reviews, communication, results, and recognition. Weakness in one link becomes participant confusion somewhere else.
Start with the one-page brief. Publish only promises the team and platform can deliver. Test the runner journey, review consistently, protect participant data, communicate problems early, and close every obligation after the final result.
Official and platform sources
This playbook was reviewed against the following resources in July 2026:
Story gallery
