Earned on
the track.

Evidence before entry approval.

1. Pre-register before a published cutoff. Collect contact details, edition, size, two recent comparable 400m times, dates, screenshots, and original activity or race-result links. A provisional 90-day window keeps the evidence recent; confirm that rule during the pilot.
2. Review every baseline. Confirm identity and source, elapsed time, measured 400m distance, standing start, and comparable timing. Use the fastest eligible result, not an average the runner can lower with an easy session. An organizer may accept an official result instead of two device screenshots if the final rules allow it.
3. Request better evidence when needed. A GPS best-effort segment can include a flying start or distance error. Screenshots can be edited. If the evidence is unclear, arrange a supervised baseline session before the qualifying event.
4. Lock the target before race day. Keep a record of the approved baseline, reviewer, source, rule version, and target. Later edits must trigger review again. Use the same start protocol and timing method for the qualification attempt.
5. Validate the finish. An organizer records the official result and confirms eligibility. Only then does the participant receive an earned reward.

Strava's Best Efforts documentation uses elapsed time, while its distance guide explains GPS-derived distance. App evidence is a useful input, not a substitute for a measured event.

The target is personal.

The preview uses target = approved baseline × 0.97. A 90.00-second baseline gives an 87.30-second target; a 60.00-second baseline gives 58.20. The runner must finish at or under the target.

Three percent is an example, not a validated standard. Pilot the threshold and timing precision with a small group before announcing it. Do not publish hundredth-second qualification if the timing system cannot reliably resolve it.

Use separate baseline sessions and review to reduce intentionally slow qualifying evidence. No system based only on submitted screenshots can fully prevent manipulation.

The shirt, then the club reward.

Issue the discount after verification, not with registration. A shared public code would be easy to circulate. Final terms, exclusions, expiry, and margins need approval before launch.

Neither showing up nor uploading evidence earns a shirt automatically. Participation stays free; the published performance target determines the earned reward.

Fund the promise first.

Set a funded participant cap so every approved runner who qualifies can receive the promised item. Do not use “while supplies last” after someone has already earned it. Reserve sizes, or explain a guaranteed later fulfillment plan before entry.

For the discount, model contribution as 0.8 × order value − product cost − payment, fulfillment, and shipping costs. Add the event garment and event costs when evaluating whether a qualifying customer's purchase covers the full program cost.

Run a small pilot with one garment and one timing protocol. The twelve designs can remain a library until the event budget supports more editions.

What a live sign-up needs.

The current site is a local preview. A real launch needs private evidence storage, applicant consent and retention terms, organizer-only review access, confirmation emails, a locked-baseline record, official results, and one-time reward redemption connected to the shop.

Keep screenshots private to the participant and authorized reviewers. Collect only the necessary evidence; do not publish images or profile information on a leaderboard. Decide the retention period before collecting files.