Why proof matters
A long-distance hike rarely produces one perfect document. The record is usually distributed across a watch or phone, an activity service, photographs, bookings, permits, trail stamps, messages from a guide, and the hiker’s own account. Evidence review brings those fragments together to answer a narrow question: does the submitted material reasonably support the stated trail completion, dates, and verification level? It is not an attempt to recreate every moment of the journey or to turn a personal experience into surveillance.
Good proof protects both the hiker and the certificate. It gives a reviewer enough context to make a consistent decision, gives the certificate a defensible basis, and helps a future viewer understand what the verification level means. The aim is a proportionate record. A short regional route may need less context than a multi-week trail with alternatives, transport sections, seasonal diversions, or an incomplete GPS track.
Start with route and time evidence
GPX, FIT, and TCX files are often the strongest starting point because they can connect movement, date, and route shape. A trusted activity link can provide similar context when an export is unavailable. Reviewers may look at file type, time range, continuity, point count, plausible movement, and whether the route broadly corresponds with the trail or the variant you describe. Exact coordinates remain in the private review layer and are not published on the QR verification page.
A file does not need to be aesthetically tidy. Batteries fail, devices restart, tree cover interferes with location, and multi-day tracks are sometimes recorded as separate activities. Submit the useful files and explain the gaps. Do not merge or edit tracks in a way that hides material facts. An honest note about a missing day is more helpful than a polished file that no longer reflects what happened.
Use supporting evidence to tell a consistent story
Dated trail photographs can establish place, weather, group context, or recognisable landmarks. Stamps and trail passports can show progress through a route network. Permits, hut bookings, transport records, guide confirmations, and event lists can support dates and participation. None of these is automatically conclusive, and a stack of weak screenshots is not necessarily stronger than one clear activity file plus a concise explanation.
Choose evidence that adds information. A photograph at the start, a mid-route checkpoint, and the finish may be more useful than fifty nearly identical images. A permit can support presence in a region but may not prove the complete route. A booking can explain an overnight stop without proving the walking section. Reviewers consider how the items reinforce or contradict one another.
Explain completion dates and route variants
Use the first and final walking dates for the completion range, then explain rest days, acclimatisation days, weather holds, side trips, or days recorded on another device. If the trail has multiple recognised variants, name the one you took where possible. If you skipped or used transport through a section, state it plainly. The registry can assess a section record or route variant only when the requested certificate and evidence align.
Distance is especially sensitive on routes with alternatives. Do not rely on a marketing distance as if every hiker follows the same line. Verified Hikes uses reviewed distance where available and safe variable-distance wording otherwise. Your narrative should focus on the actual route taken, not on forcing it to match a single published number.
What reviewers look for
Reviewers look for consistency across trail, dates, recipient, route, and evidence source. They consider whether the material covers enough of the completion, whether gaps are explained, whether file safety checks have passed, and whether the requested verification level is supported. They do not need a public social-media history, a dramatic personal story, or sensitive identity documents to make an ordinary trail decision.
The review is human because context matters. A broken device, an organised group, a permit system, a trail passport, and an open-route network each produce different evidence. The same standard still applies: verify only what the submitted material supports, use conservative wording, and ask a focused clarification question when one answer could resolve an uncertainty.
Keep private material out of public channels
Do not post raw GPS files, permit numbers, booking references, identity documents, or original photo metadata on a public verification page or in a public support message. Use the authenticated upload area. Before uploading, inspect track start and end points for home addresses or private accommodation, remove unrelated photographs, and avoid submitting information about another person unless it is necessary and you have permission.
Verified Hikes separates evidence from verification metadata. Reviewers may access the private files for the application. A person scanning the certificate sees safe fields such as status, trail, privacy-controlled display name, dates, verification level, issue date, fingerprint, and signature state. They do not receive the underlying proof.
If the evidence is unclear
A clarification request is not a rejection. It should identify the uncertainty and the smallest useful next step: explain a route gap, add the missing activity day, identify a transport section, provide a clearer date, or upload one supporting item. Respond in the dashboard so the reply remains attached to the review record. Do not create a new application unless support asks you to do so.
If the evidence still does not support the requested certificate, the outcome may be rejection or a suggestion to request a narrower record. Rejection means the available evidence was insufficient for the registry claim. It does not mean the hike did not happen. Refund treatment depends on the review stage and the published policy.
Final proof checklist
Before payment, confirm that the trail page matches your route and that you can provide a meaningful combination of route, date, and context evidence. Check that completion dates are accurate, recipient display and privacy mode are intentional, files use supported formats, and each upload adds something useful. Prepare a short narrative that explains variants and gaps without including private details that do not help the review.
A strong submission is not the largest submission. It is the clearest one: a coherent route record, a small set of supporting items, honest context, and a privacy-aware upload. That gives the reviewer a defensible basis and lets the final certificate remain simple, beautiful, and safe to verify publicly.