A clear explanation of valid run proof, common rejection reasons, and what reviewers usually need to see. This HelloRun guide uses practical virtual running examples for runners and organizers in the Philippines.
Valid proof is clear proof
Valid run proof is evidence that lets an organizer confirm what activity happened, when it happened, and whether it meets the event rules. The best proof is simple, complete, and easy to read.
Core details reviewers check
Reviewers commonly check date, distance, duration, activity type, app source, and whether the proof matches the registered participant. For paid events, payment receipt review is separate from run proof review.
Screenshots that usually work
A good app screenshot shows the completed distance, elapsed time, date, and source. A treadmill proof may work if the event accepts treadmill records and the image clearly shows distance and time. Manual entries may require extra context.
Example
A 10K virtual run proof should show at least 10 kilometers completed during the event window. If the screenshot shows 9.8K, the organizer may reject it unless the event has a published tolerance rule.
Common rejection reasons
Common problems include missing date, cropped distance, blurry image, wrong event period, duplicated proof, name mismatch, suspicious edits, or activity type not allowed by the event. Clear proof protects both the runner and the organizer.
What to do next
Review your screenshot before submitting. If you are unsure, read the FAQ or contact support with the event name and confirmation code.
Comments