Corrections & Updates Log

We make mistakes. When we do, we correct them and log the correction publicly. This page is our published record of every factual error we've found and fixed - with the date, the page, the error, and the corrected text.

5 corrections logged since the site launched - all factual errors, not stylistic changes
We distinguish between factual errors (wrong numbers, misattributed claims) and updates (new data that supersedes older figures)
Corrections are logged with the date, page, error, and corrected text
If you spot an error, we want to know - see the contact page
Our full editorial standards explain how we handle corrections

Full log, our corrections policy, and how to report an error, below.

The Corrections Log

Below is a full list of all factual corrections we've made since the site launched. We do not silently fix errors without acknowledgement.

Date	Page	Error	Correction
2026-02-10	204DTD Knowledge Centre	Stated timing chain tensioner failure typical at 80k miles	Corrected to 60k-120k miles based on revised data [EM-INTERVIEW]
2026-01-28	AJ133 Chain Tensioner Failure	Listed 2014 as the revision year for chain tensioner fix	Corrected to 2013 based on manufacturer TSB [THIRD-PARTY]
2026-01-15	Is It Worth Replacing an X-Type Engine?	Stated reconditioned cost at £2,500-£4,500	Corrected to £2,500-£5,800 based on updated supplier quotes [EM-QUOTE]
2025-12-03	AJ126 vs AJ133 Comparison	Stated AJ126 water pump failure at 80k miles	Corrected to 60k-120k miles based on workshop consensus [EM-INTERVIEW]
2025-11-20	306DT Failure Rate Data	Stated 306DT enquiry volume at 1,050	Corrected to 980 based on updated CRM data [EM-VERIFIED]

This log is updated whenever a factual correction is made. Updates - changes to reflect new data that supersedes older figures - are noted on the page itself but do not require a separate log entry unless the update materially changes a previously published claim.

Corrections Policy

Our corrections policy is simple: when we make a factual error, we correct it and log the correction publicly. We do not silently fix errors without acknowledgement.

We distinguish between factual errors (wrong numbers, misattributed claims, incorrect dates) and updates (new data that supersedes older figures). Factual errors go in the corrections log with a clear acknowledgement of the mistake. Updates are noted on the page itself, but do not require a correction log entry unless the update changes a previously published claim in a materially significant way.

The full policy is set out in our editorial standards. Any disputes about what constitutes a factual error versus a difference of interpretation are resolved by the editorial team, with reference to our expert panel where technical disagreement arises.

What Counts as a Factual Error?

We log:

Wrong numbers - incorrect costs, mileage figures, enquiry volumes, or other quantitative claims
Misattributed claims - statements attributed to the wrong source or data tag
Incorrect dates or model years - wrong production years, revision dates, or recall periods
Factually incorrect descriptions - errors in failure mechanisms, diagnostic steps, or repair procedures

We do not log:

Stylistic changes - rewording, restructuring, or clarification that doesn't alter a factual claim
Updates to reflect new data - unless the new data directly contradicts a previously published claim
Differences of interpretation - where two reasonable interpretations exist, we don't log a correction; we note the alternative interpretation on the page itself

Our Correction Process

When an error is identified - whether by our editorial team, a panel member, or a reader - the process is:

1. Verification - we confirm the error, cross-referencing against our source data or consulting our expert panel
2. Correction - we correct the page and update the relevant data tag, if applicable
3. Logging - we add an entry to this page with the date, the page, the error, and the corrected text
4. Notification - we notify any reader who reported the error that it has been corrected

The corrections log is linked from every page on the site via the footer, so it is always discoverable. Our data verification page explains how we tag and verify data more broadly, and our editorial standards set out the full policy.

Report an Error

If you spot a factual error on this site, we want to know. Please report it via our contact page with:

The page URL - where the error is
The error itself - what you believe is incorrect
Your source or reasoning - if you have a specific source, please share it

We review every error report, and where a factual error is confirmed, we correct it and log it following the process above. We aim to respond to all error reports within 5 working days, and we strive to correct confirmed errors within 10 working days of confirmation.

If you've reported an error and don't hear back, please follow up - we sometimes miss messages, and we'd rather be nudged than leave an error uncorrected. Our contact page has details on how to reach us.

Limitations of This Log

This log is a record of factual errors we have identified and corrected. It is not a record of:

All possible errors - we may have made errors we haven't yet discovered. If you find one, let us know.
Stylistic changes - we don't log rewording or restructuring that doesn't change a factual claim
Updates - new data that supersedes older figures is noted on the page itself, not logged here unless it materially changes a published claim
Disputes we don't resolve in the reporter's favour - where we believe our original claim is correct, we may not log a correction; we will explain our reasoning to the reporter

This log is a living document. It is updated as new corrections are made, and older entries remain visible so the history is transparent.

✓

Public LogEvery factual error we've corrected is logged here.

✓

Policy PublishedYou know how we handle corrections before you need to report one.

✓

Easy to ReportClear process, with a response time commitment.

✓

Linked From Every PageThis log is always discoverable from the footer.