Corrections Policy
If you find a factual issue, an outdated official link, or a misleading profile detail, use this page to understand how corrections should be reported and reviewed.
The fastest corrections include the exact page URL, the detail that looks wrong, and the official source that should be checked against the current page output.
What to report
Incorrect university facts, broken official website links, outdated geography details, or misleading summaries that do not match the best official source.
What helps most
A precise page URL, a short explanation, and an official link or document that makes the correction check straightforward.
Where to send it
Use the contact page and make the subject line clear so the issue can be triaged quickly.
What to include
Share the page URL, the exact detail that appears incorrect, and the best official source showing the correct information. Screenshots are useful if the issue is time-sensitive or likely to change quickly.
How we review reports
We compare the report against the current data record, the page template, and the relevant official source. Confirmed issues are corrected in the data layer or the page output, depending on where the error originated.
Contact route
Use the contact page and include "Correction request" in the message subject line so the issue can be triaged faster.
What slows corrections down
Vague reports without a page URL, a clear explanation, or a supporting official source usually take longer to resolve. Specific evidence helps the corrections process stay accurate as the directory grows.
Where corrections usually come from
Most valid reports involve an official link that has changed, a provider detail that moved after the last dataset import, or wording that needs to be tightened so the page better reflects the source.
Related trust pages
If you want to understand how pages are sourced before reporting an issue, review data sources and the editorial policy.
That context often makes correction requests faster and more precise.
Corrections matter more as the directory scales
A broader UK database creates more value for readers, but it also means the corrections process must stay structured so accuracy can scale with the site.
Publishable pages
Verified websites
Source datasets
UK nations
Top regions in the live directory
Popular university types
Coverage signals
Largest subject hubs in the current import
Dataset depth
The UK database currently stores 1,589,749 normalized HESA observation rows. That extra depth is what allows the site to grow beyond thin listing pages into stronger long-form guidance and research support content.