Corrections policy
Requirements change, source pages move, and mistakes can happen. We want reports to be easy to submit and possible to verify.
Report an error
Send the affected page, the value you believe is wrong, and—if possible—the exact government or exam-board page that supports the correction through our contact page. Screenshots are useful, but a live source link or dated notice makes the change easier to confirm.
What makes a report actionable
- The easyPhoto URL where the statement appears.
- The exact sentence, table row, or tool value that may be outdated.
- The application workflow and notice cycle you are using.
- A first-party instruction page or PDF, including its paragraph or page number.
We do not need a copy of your photo, signature, identity document, or completed application to investigate a specification. Please remove personal details from any screenshot you choose to send.
What happens next
We compare the report with the responsible authority's current instructions and the source already recorded for the page. If the evidence supports a correction, we update the underlying specification and any dependent copy, then record a new verification or review date. If sources conflict, we keep the uncertainty visible rather than choose an unsupported number.
A review date shows when a source comparison occurred. It does not mean the receiving authority has endorsed easyPhoto or guarantees acceptance.
Corrections are applied to the shared source record where possible so the affected guide, specification table, and tool read the same revised value. Editorial wording is updated separately when the change alters the workflow rather than a number. We do not silently turn unresolved reports into confirmed requirements.
Reports about broken downloads or browser behaviour follow the same evidence-first approach. We reproduce the steps with a non-sensitive test file, identify the affected browser or device, and distinguish a software defect from a portal-side message before changing user guidance.