If a page is inaccurate, a link is broken, or a tool does not produce the Printable it promises, we want to know. Use the contact form’s “Report an error on a page” topic or email [email protected]. A real person reads every report.
1. What counts as a correction
- A factual mistake about paper sizes, line spacing, printing, or a tool’s behaviour.
- A page that describes a feature, preset, or limit differently from the tool that ships.
- A broken download, a missing PDF, a preview that does not match the Printable, or an action that fails silently.
- A broken internal or external link, or a page that sends readers to the wrong tool.
- Outdated information, including a page whose guidance no longer matches the current release.
- A claim that overstates what the site or a printable can do, including an invented credential or an unsupported medical or clinical claim.
- An accessibility barrier. You can also use the route described in the accessibility statement.
- A privacy or legal statement that does not match how the site actually works.
Disagreement with a teaching approach is not, by itself, an error. If a page describes a practice accurately and you prefer another method, tell us why — we may add the trade-off or a note, but we will not remove an accurate statement because a reader disagrees with it.
2. How to report an error
Use the contact form with the “Report an error on a page” topic. It opens the form with the topic already selected. If the form is unavailable, email [email protected] with “Correction” in the subject.
A useful report includes:
- The page URL, or the tool and preset you were using.
- What the page says or does, and what you expected instead.
- For a tool or PDF problem: the paper size, browser, device, and whether the issue appears in the preview, the download, or the printed page.
- Any public source that supports the correction, if the issue is factual.
Please do not send a child’s name, photo, or other personal information. Tool inputs stay in your browser, and we do not need them to investigate a report.
3. What happens next
| Step | What happens | Target |
|---|---|---|
| Acknowledgement | We confirm the report arrived and ask for anything missing. | Within two business days |
| Assessment | We reproduce the issue and decide whether the page or tool is wrong. | As soon as we can reproduce it |
| Simple fix | A typo, broken link, or wording correction is fixed and deployed. | Usually within ten business days |
| Tool or PDF defect | We fix the export, the preview, or the page copy and add a regression test where the seam allows it. | Scheduled with the next release |
| Privacy, legal, or safety issue | We prioritise the report, and we may remove a claim or a page while we investigate. | Immediately |
4. How we update a page
When a correction changes a fact, a limit, a recommendation, or the description of a tool, we update the page and move its last-reviewed date forward. The date is the one shown in the review line on every tool and guide page and comes from the site’s single editorial record. We do not rewrite a page silently and leave an old date in place.
If we cannot confirm a report, we explain why. If a report is right but the fix will take longer, we say what is still wrong rather than closing the report as if it were resolved.
5. What we will not do
- Remove accurate content because someone prefers a different approach, product, or school of thought.
- Accept payment or another benefit to change, hide, or add a statement.
- Publish a correction that identifies a child or shares a reader’s private information.
- Claim that a fix has shipped when it has not. If delivery is broken, we say so and offer the email path.
6. Related pages
The editorial standards explain how pages are written and reviewed. About the author and the site names the person accountable for the content. The privacy policy explains what happens to a contact message.
Corrections are handled by Amir Khan, Founder and developer. Reports are not used for marketing and are not added to a mailing list.