Challenge a Claim

This project's whole method depends on being checkable and correctable (see How We Reach Conclusions). This page is where a reader can act on that, rather than just read about it.

Every submission is reviewed by a named person against the same sourcing standard applied to everything else on this site, the one described on the methodology page and applied document by document in the Sources Register. Nothing is published or acted on automatically. If a submission leads to a change, the change is logged in the Update Register with the reason, where every other correction to this site is recorded.

Submitting a challenge needs the same free registration used to back a proposal: a verified email address and UK mobile number, with your first name and postcode district. It isn't an anonymous form. That is a deliberate choice, not friction for its own sake: a challenge that changes a published argument should meet the same standard of accountability this project asks of everything else on it.

What Happens Next

A submission doesn't publish or change anything automatically. As How We Reach Conclusions explains, a claim is corrected only once the evidence behind it has been checked, whether the challenge comes from a reader, a fresh round of research or newly published data. Claims that don't survive the check are corrected. Claims that do survive it stay, and the reasons for keeping them can be explained on request.

This is a deliberately simple first version of the fuller challenge process described in Platform Integrity. It works: submissions are structured, tied to a verified registration and reviewed by a named person. It doesn't yet include the identity check or the AI-assisted first review the fuller version plans, because both depend on outside services not yet set up. The part that matters most works today: you can submit a challenge, and if you're right, the content changes.