How to set editorial standards
Editorial standards readers can see, and your team can follow, are a trust asset. Here’s how to write the useful kind.
A standard is testable or it is a slogan. The difference shows up in the shape of the document: numbered clauses rather than paragraphs, a version and an effective date, a named owner, and a worked example beside each rule.
Our own are published at editorial-standards: version 3.0, effective 12 September 2026, five numbered standards, each clause numbered (1.1, 1.2, 1.3) with an example of what passes and what does not, maintained by a named team at a published address, with a version history. Every structural choice there is one this guide recommends, and you can check whether we followed it.
What follows is how to get from a value to a clause, which four areas to cover, and how to leave a reader something to check.
Be specific enough to be testable
“We are committed to accuracy” proves nothing, because every publisher writes it. A clause names who acts, when, and against what bar.
Clause 2.1 of our own standards reads: a correction states the current text, the proposed text and the reason, and cites a source a reader can follow. That is checkable in both directions. A reader can open any correction and see whether all four parts are there, and a contributor knows before submitting what will be rejected.
“We value accuracy.”
“Every page is reviewed by someone with topic expertise before publishing, and corrections are recorded publicly.”
What to cover
Useful standards describe how your content actually gets made and maintained. The core areas readers care about, and that genuinely shape quality, are:
- Review, how content is reviewed, and by whom (see how to run an editorial review)
- Accuracy and sourcing, how claims are verified and how sources are cited
- Corrections, how they’re made and shown (see how to handle a correction)
- Credit, how contributors are acknowledged (see how to credit contributors)
For each, write what you actually do, specifically. Standards that describe a real, followed process are worth far more than aspirational ones, because the gap between stated and lived standards is exactly what erodes trust when readers notice it. Write the standards you genuinely keep, then keep raising them.
From slogan to standard, area by area
Four areas, each pushed from a value to a clause:
| Area | The vague version | The testable standard |
|---|---|---|
| Review | “Our content is carefully reviewed.” | “Every page is reviewed by someone with expertise in its topic before it’s published.” |
| Sourcing | “We use reliable sources.” | “Factual claims link to a primary source a reader can check, with the date noted.” |
| Corrections | “We fix errors promptly.” | “Corrections are made openly, with a dated note of what changed, and the person who flagged it is credited.” |
| Credit | “We value our contributors.” | “Each page names who wrote, reviewed, and checked it for accuracy, with links to their records.” |
Each right-hand version names an actor, a moment and something external to check. Clause 3.2 of ours goes further and names what is excluded: reviewers review only work independent of them, their co-authors, institution and email domain, with a shared institutional domain excluded automatically. A rule that names its own exclusions is harder to write and much harder to argue with.
The test: could a skeptical reader check this against one of your real pages and find it true? If there is nothing for them to open, it is still a slogan.
Keep standards living
Version the page and keep the history. Ours is on version 3.0 with an effective date on the page and earlier versions still listed, so a reader can see what changed and when rather than taking “last updated” on faith.
Publish what you keep today and raise it later. A version history makes that honest: the improvement is visible as a change rather than quietly backdated.
Make them public and verifiable
Each clause should point at something a reader can open. Promise named reviewers and the name has to be on the page; promise a public correction record and there has to be a record to reach.
Ours is 1,753 accepted corrections across 1,700 articles from 8 publishers, each carrying its contributor, date, error category and the text before and after. Clause 1.3 is the part that costs something: once accepted, a contribution is permanent, and if it later proves wrong a new correction is recorded against it and both stay visible. A standard that only ever makes you look good is not being tested.
Numbered clauses, a version and date, a named owner, and something a reader can open behind each rule.
Quick checklist
- Every clause describes something the team actually does today
- Each clause names an actor, a moment and a bar
- Review, sourcing, corrections and credit are each covered
- The page is public, versioned and dated, with a named maintainer
- Each clause points at something a reader can open
Common questions
What should editorial standards include?
Review, sourcing, corrections and credit, each written as a numbered clause rather than a value. Ours adds conflicts of interest and review confidentiality, which is five standards in total.
How do editorial standards build trust?
Mostly not by being read. They build trust by being followed visibly on the pages themselves, which is why each clause needs something external to point at.
Should I publish standards I’m still working toward?
No. A stated standard you do not meet is the gap readers notice. Publish what you keep, version the page, and let the history show the improvement.
How detailed should editorial standards be?
Numbered clauses with an example beside each, which is what keeps them short. Ours runs to five standards and fits on one page.
How do I show readers I actually follow my standards?
Put the proof where the claim is. Named reviewers on the page you said was reviewed, the source on the claim you said was sourced, and a correction record a reader can reach from the article itself.