Unlock conditions

Where: Achievements → Add or Edit Achievement

What a participant has to do to earn it.

Activity conditions

Activity Type decides which activities count. Preset groups — outdoor, indoor, all — expand into the underlying activity types, so you can pick a sensible set without listing every one.

All Activities counts everything the event accepts.

Keep this consistent with what the leaderboard counts. An achievement that counts activity types your event otherwise ignores creates a participant who has earned a badge for a ride that does not appear in their total — which reads as a bug.

Combining activities

Combine Activities With decides whether several activities add up towards the threshold, or whether one activity must reach it alone.

The difference is significant and invisible from the participant's side until they miss out. "Ride 100 km" as a cumulative total is achievable by most of your field; as a single ride it is a serious effort. Decide which you mean, and say so in the description.

Amount thresholds

Amount sets the value that must be reached.

Check the unit before saving

A threshold that is correct in the wrong unit is either trivially met by everyone or unreachable by anyone. Neither shows up on this screen — both show up as an unlock count that makes no sense.

Set thresholds against what your field will realistically do. Look at a previous event if you have one. A milestone only your top ten reach motivates only your top ten.

Date windows

Challenge Period measures the condition over your event dates. A custom period fixes it to dates you set. Award From sets when qualifying activity starts counting.

Prefer Challenge Period. It follows your event automatically, so moving your event dates does not silently strip an achievement of its window — which is exactly the failure that produces an achievement nobody can earn.

Custom windows are for genuinely time-boxed things: a launch-week bonus, a final-weekend push.

Purchase and donation conditions carry their own date windows, set the same way.

Fundraising and purchase conditions

Achievements can also unlock on donations raised or purchases made, with their own thresholds and windows.

These are among the most effective, because they reward the behaviour that funds the event. An achievement at a realistic first fundraising milestone gives participants a reason to make the first ask, which is the hardest one.

Results-date conditions

Some conditions are gated on the Results Date — anything that should not be final until standings are.

These are chosen from a fixed set of options rather than typed. If you are expecting to enter a date and are offered a list, that is why.

The host is excluded

Achievement conditions exclude the host's own activity, in the same way leaderboards do, so your own team does not accumulate awards alongside participants.

This depends on the host user being set correctly. If your organisation's account is collecting achievements, check Setup → Host.

Testing

For each achievement, confirm two things before the event starts:

1. It can be earned. Someone plausible in your field can meet it.
2. It actually fires. Test with a real qualifying activity — the condition being sensible is not the same as it being wired correctly.