Editorial standards
The process, written down rather than implied
Every guide on this site goes through the same five steps. All 140 of them carry a named writer and the date they were last checked.
- 01
Written to a real question
Every guide starts from a query as someone would actually type it, and has to answer that question in its first three sentences. If the short answer cannot be written, the guide is not commissioned.
- 02
Specific enough to follow
Pressure, rhythm, duration, position, the exact sentence to say. A guide that would leave a reader still guessing does not pass this stage, and vagueness is the most common reason something goes back.
- 03
Clinical review
Anything touching anatomy, pain, medication or risk goes to a clinician who can hold it indefinitely. The reviewer's name and the review date go on the page once that has happened. A guide without one has not been through this step yet, and does not claim to have been.
- 04
Sourced claim by claim
Each factual claim is tied to the kind of source that supports it, listed at the foot of the guide under 'How we know this'. In this build those are labelled empty slots rather than invented references.
- 05
Re-reviewed, and dated honestly
Guides carry the date they were last reviewed. Not the date they were posted, and never a rolling timestamp that moves without anyone reading the page.
What we will not do
- Take affiliate commission or advertising in editorial
- Recommend a product we have a financial interest in
- Publish a technique guide to someone describing pain
- Invent a citation, a credential, a testimonial or a statistic
- Pretend something is finished when it isn't
- Use a rolling 'last updated' date that nobody actually acted on
If we got something wrong
Corrections are published on the guide itself with the date, not quietly edited in. Tell us and we will either fix it or explain why we think it is right.
Who we areThe quiz rule
If it hurts, the quiz stops
If someone says it hurts, or that she does it when she doesn't want to, the quiz drops the score and tells her to sort that out first. That answer overrides every other one. It is enforced in code and checked before each build.