Learn what a clear run proof screenshot should show and how to avoid common approval delays. This HelloRun guide uses practical virtual running examples for runners and organizers in the Philippines.
Why proof matters
HelloRun uses proof submission so organizers can review results before they count toward completion, certificates, or leaderboards. A result is stronger when it is supported by a clear activity record instead of a claim typed into a form.
What your screenshot should show
A good screenshot should show the activity date, distance, duration, and source app or device. If possible, include pace, route, and activity type. The organizer should be able to understand what was completed without asking for extra explanation.
Use the right registration
Before submitting, check that you are uploading proof to the correct event and distance. A 10K screenshot submitted to a 5K event might still be valid for completion, but the organizer needs to know which registration it belongs to. For accumulated challenges, choose the registration that should receive the activity credit.
Example for an accumulated challenge
If you joined a 25K accumulated event, you might submit five separate 5K activities. Each activity should fall inside the event window and meet the minimum activity distance if the organizer configured one. Only approved activities count toward the total.
Common mistakes
Avoid cropped screenshots that hide the date, app screenshots that show only calories, duplicate submissions, payment receipts uploaded as activity proof, and screenshots from outside the event period. If your app uses miles, explain the unit clearly when submitting.
What to do next
After submitting, monitor your registration or runner dashboard. If the result is rejected, read the reason carefully and resubmit clearer proof when the event allows it. For general proof questions, check the FAQ or contact HelloRun support.
Comments