Fit the loop to the run
Choose distance, surface and route conditions appropriate for the planned session. A loop can enclose an area while still following familiar public streets or paths.
Marchh records activity context such as route, distance, duration and pace from accepted samples.
Return around with usable GPS
Dense buildings, tunnels and heavy tree cover can reduce accuracy. Keeping normal location permission and a usable satellite view helps, but no device can guarantee perfect geometry.
An apparent loop on the ground may not form a valid closed area in the accepted data.
Treat the claim as an outcome, not a promise
Marchh can reject or adjust a claim because of technical quality, geometry, integrity criteria or existing territory.
Do not spoof a better result or repeat fabricated data. A legitimate technical concern belongs with support.
Separate route planning from territory validation
A runner controls the intended route, but Marchh controls whether the recorded activity produces eligible territory. That distinction prevents an on-screen preview from becoming a promise.
Plan around distance, surface, traffic and familiarity first. Let territory remain a result evaluated after genuine movement rather than a reason to force the final segment of a run.
Questions people ask
Does every activity create territory?
No. A completed activity does not guarantee a claim. Route geometry, location quality, activity integrity, territory conflicts and other Marchh validation rules can affect eligibility.
