The short version
Key takeaways
- Good For Age is a race-specific route name, not a universal set of marathon rules.
- A valid result must satisfy the edition's category, window, course, distance, and verification requirements.
- Some standards create eligibility to apply, while other organiser programmes classify an approved application as guaranteed entry.
- Qualifying windows and application windows are separate deadlines and both can change each edition.
Two labels for race-specific performance routes
Good For Age is the name London Marathon Events uses for one of its performance-based entry routes. Other organisers use terms such as time qualifier, qualifying standard, or qualifier registration. These labels describe related ideas but do not create one shared rulebook.
The broad pattern is to run a required time for your category during an eligible period, then submit that result through a separate organiser process. Residency, accepted events, allocation, and evidence can still differ substantially by race.
A qualifying time has several conditions
A finish time is useful only when it meets every condition for the target edition. Organisers commonly specify an age and gender category, a qualifying window, an accepted distance, a certified course, an official result, and a later application deadline.
Even age can be measured differently. London currently uses the runner's age when the qualifying performance was achieved, while Boston and Chicago use age on their marathon's race day. Check the current definition before choosing a qualifying race.
- Confirm that the performance falls inside the published qualifying window.
- Check the accepted distance and the course-certification requirement.
- Use the official net or chip time when the organiser requires it.
- Make sure the result can be verified on the event's official results page.
- Record the separate application opening and closing dates.
Meeting a standard may only unlock an application
London's Good For Age route is currently limited to UK residents, has a capped field, and allocates places fastest-first relative to age and the published standard. Boston likewise states that achieving its standard permits an application rather than assuring acceptance; when qualified demand exceeds capacity, faster applicants are accepted.
Other systems differ. Chicago's current organiser page classifies a verified time-qualifier application made within its entry window as a guaranteed-entry route, subject to review and completion. New York currently distinguishes qualifying results achieved at specified NYRR events from a limited pool for qualifying times achieved elsewhere.
Read what the organiser promises after verification, not only the headline time. Racera can explain and track the route but does not certify performances or control acceptance.
Prepare verifiable evidence before applications open
Keep the official results URL rather than relying on a screenshot, watch activity, or training-app record. The page should clearly identify the runner, event, date, distance, and finish time so the receiving organiser can verify the performance.
London currently also asks for proof of age and UK residence. Other races may check course certification, the gender category attached to the result, or additional course rules. Personal details should match across the qualifying result and application wherever possible.
- Save the official result URL and a copy of the displayed result.
- Check whether identity, age, or residence evidence is required.
- Confirm the certifying body accepted by the target organiser.
- Allow time for verification rather than applying at the final minute.
Do not assume the qualifier replaces the ballot
Only follow the target organiser's guidance on overlapping applications. London currently encourages some Good For Age candidates to enter its ballot because meeting the qualifying criteria does not itself assure a place; successful Good For Age applicants are then removed from the draw.
Another organiser may combine, separate, or restrict its entry applications differently. Track both windows until the official rules make the relationship clear, and never assume that one application automatically carries into another route.
