Verification
What we check before publishing a first-person story, and the line between a verified fact and a lived experience.
Last updated
Experience is not the same as fact
Almost everything here is one practitioner’s account of something that happened to them. We can confirm that the person is real, that they held the role they describe, and that they stand behind the account. We generally cannot confirm what a third party was thinking, or that a result was caused by the change described.
So we do not present those things as established. A story says what someone did and what they observed. Where a claim is checkable, we check it. Where it is not, the writing says so.
What we check before publishing
- The person exists and is who they say. Confirmed privately with the contributor; never inferred from a confirmed email address alone.
- The role and context are accurate as stated in the context card — role, sector, organization size, region.
- Third parties are protected. Colleagues, employees and employers must not be identifiable without their consent.
- Checkable claims. Published research, legal statements and named public facts are checked against sources.
- The contributor approves the exact text that will appear, including title, dek and byline.
What we do not do
- We do not award a “verified expert” badge. Confirming an email address proves an inbox, not expertise.
- We do not independently audit an organization’s internal numbers. If a story cites one, it is attributed to the contributor.
- We do not present a single experiment as evidence that something works in general.
When we get it wrong
Errors are corrected in public and logged, dated, on the corrections page. We do not quietly edit a published story and leave no trace.