Corrections Policy

We publish technical guidance, so errors have consequences. This page describes how to report one and what happens next.

How to report an error

Write to [email protected] with the page URL, the statement you believe is wrong, and — where you have one — the source that contradicts it. A source is not required to report an error, but it makes the assessment much faster.

How we assess it

We check the disputed statement against the source it was drawn from, and against current published standards or manufacturer data where relevant. Three outcomes are possible:

• Factual error. The statement is wrong. We correct it and note the correction on the page.
• Scope error. The statement is true under conditions we failed to state. We add the missing condition. This is treated as a correction, not a clarification.
• Disagreement, not error. The statement is supportable and the disagreement is about judgement or regional practice. We may add the alternative view, and we say so rather than silently changing the text.

How corrections appear

A substantive correction updates the article’s revised date and is described in a note on the page. We do not quietly edit a technical claim and leave the date untouched — the date is meant to tell you whether what you read last year still stands.

Typographical fixes, formatting and link repairs are made without a note.

Timing

We aim to acknowledge a report within five working days and to resolve it within fifteen. Where a claim requires checking against a standard we do not hold, resolution can take longer, and we will say so rather than leave the report open silently.

What we will not do

We will not remove accurate content because a manufacturer or supplier objects to it, and we will not add or alter a technical claim in exchange for payment, links or product.