Editorial policy
How TruePace Run writes and checks its content.
TruePace Run is built around a calculator, but the surrounding articles and guides matter too. This page explains how the site uses sources, what it avoids claiming and how corrections are handled.
Purpose
The site exists to help age-group runners understand race results with more context than raw finish time alone. Articles should answer practical runner questions, explain calculator outputs clearly and link back to useful actions rather than publishing filler pages.
Sources and calculator data
Calculator results currently use sourced 2025 road-running age standards from Alan Lytton Jones' Age-Grade-Tables project under its CC0-1.0 licence. Source notes remain visible near calculator results, and the methodology page explains what the calculator does and does not adjust for.
Articles include visible source sections when they rely on outside data, research, public definitions or safety guidance. TruePace Run does not copy unlicensed tables, invent citations or present calculator estimates as official rankings.
Source choices are practical: prefer primary sources, public project documentation, peer-reviewed research, official support pages and clearly licensed datasets. If a source cannot be checked, licensed or explained plainly, it should not be used as the basis for calculator data or factual claims.
Article standards
Articles should be useful to a runner with a real result in mind. They should explain the question in plain English, include original interpretation, link to the calculator or methodology where helpful, and avoid thin pages that only repeat a keyword in different clothes.
When examples are shown, they should either come from the current calculator logic or be clearly described as illustrative. Articles should not make medical claims, coaching plans or promises about what a runner should be able to achieve.
Review and updates
Article pages show published and last-updated dates. Updates are made when source data changes, when a page needs clearer limitations, or when a reader reports something that should be checked. The site is small, so review is practical rather than theatrical: read the page, check the source, improve the wording, and leave the calculator source notes visible.
The last-updated date should change when an article is materially edited, when examples are recalculated, when source links are added or changed, or when limitations are clarified. Tiny typo fixes do not need to pretend the whole page has been freshly reviewed.
If the calculator source data changes, affected calculator pages, methodology notes and articles should be checked together so the site does not mix old explanations with new results.
What TruePace Run avoids claiming
TruePace Run does not provide medical advice, coaching advice, official race results, qualification decisions or governing-body rankings. It is independent from parkrun, WMA, USATF, race organisers and timing providers.
Corrections
If a calculation, source note or article looks wrong, email hello@truepacerun.net. Include the page URL and, for calculator issues, the distance, time, age and gender entered.
Corrections should be checked against the current methodology and source data before the page is changed. If the correction affects a calculator result, the source note and any related article examples should be reviewed too. If the correction is about wording, the fix should make the limitation clearer without turning an estimate into a stronger claim.