Wrong name, date, link or summary
Send the public page URL, the corrected fact and the source that supports the correction.
Email this routeCorrections · source tips · reader feedback
Use this route for factual corrections, broken links, missing source records, unclear plain-English summaries and reader-safety issues. The aim is simple: fix what matters and keep the public record easy to check.
Start with the kind of fix you need. The route stays email-only for now so source links, right-of-reply context and public documents can arrive with enough detail.
Send the public page URL, the corrected fact and the source that supports the correction.
Email this routeSend the public document, notice, agenda, FOI response, tender or event listing so it can be checked against the issue.
Email this routeSend the affected page, the point you want answered, and a public route readers can use to verify the response.
Email this routeLead with the date/time, the changed official source and whether readers need an urgent route update.
Email this routePick the closest route. Each one opens the same mailbox, but the labels help readers understand what belongs here.
A name, date, link, quote, agenda item, deadline or summary needs correcting.
Email a correctionSend a Tynwald paper, FOI response, tender, consultation, notice, event listing or official update.
Send a source tipFlag a section where the who, what changed, deadline or reader impact needs sharpening.
Ask for clarificationReport a broken advert link, outdated offer, unclear disclosure or reader-safety concern.
Report advert issueThe fastest useful correction is specific, source-backed and tied to a visible page.
The correction route is public-facing, but the checking work stays bounded and privacy-safe.
Corrections and source tips are routed to the Moghrey Mie mailbox, not a private personal inbox.
The issue is compared with source material, public records or the original link trail.
When a correction is needed, the website archive is updated and the next relevant issue can acknowledge it.
Subscriber data, credentials and private account information are never exposed on public pages.
Send the issue link, the problem, and any public source evidence. That gives the team enough to check and update the archive.