How we check

Every fact on an event page comes from the organiser’s own website. Software reads that page, an AI writes up what it finds, and a separate AI checks the result. No person reviews individual events, so this page says exactly what does.

Last updated 28 Oct 2026

Where the facts come from

We start from the organiser’s own website, then other official pages such as the venue, the ticket seller the organiser names or the host city. Each event page links to the official page it rests on, and says when we last checked it.

Wikipedia and Wikivoyage may help us describe what an event is and what it is like. They never supply a date, a place, a price, a ticket rule or whether an event is going ahead. When one of them helps with a page, the page credits it with a link to the article.

How a fact is checked

Each fact goes through the same steps, and any step can stop a page from being published.

1. Code fetches the official page, within the rules in About our bot, and cuts out the passages that hold dates, places and ticket words.
2. An AI researcher reads only those passages and fills in the facts, each with the exact words from the page that back it.
3. Code checks that every one of those quotes appears, word for word, in the page. A fact without a matching quote is not confirmed.
4. A second AI, working independently of the researcher, reviews each fact against the page and confirms it, corrects it or removes it.
5. An AI writes the page text from the checked facts only. Code checks the text for banned phrases and for sentences copied from a source, and a further AI review compares it with the facts.
6. A last set of code checks decides whether the page may be published at all.

Pencil and ink

A date or detail we cannot match to the official source is drawn in pencil: grey, dashed and labelled as an estimate. It is our best reading, not a fact.

A fact becomes ink, solid and in the brand colour, only when it matches the official page and the quote is found there. Only ink facts go into the structured data that search engines read.

How often we check

Code re-reads each official page on a schedule that depends on how soon something matters, and notices when a page changes. Each page’s exact time varies by up to 10 per cent, so checks do not bunch together.

Starts more than 60 days away: About every 28 days.
Starts within 60 days: About every 7 days.
Dates not yet confirmed, or postponed: About every 7 days.
A pencil date, from the month before the usual announcement: About every 7 days.
Ticket sales open within 30 days: About every 7 days.
Tickets on sale, or a deadline within 72 hours: About every 24 hours.
A deadline less than 24 hours away: About every 12 hours.

The “Checked” line on an event page follows from the age of the last check.

Checked: The last check was at most 7 days ago, or at most 30 days ago when the event starts more than 60 days away.
May have changed: For an event starting within 60 days: the last check was more than 7 and at most 30 days ago.
Confirm on the official site: The last check was more than 30 days ago, or a deadline is less than 72 hours away and the last check was more than 24 hours ago. We show no countdown then.

The audit and the error budget

This audit has not started on the live catalogue yet. It is being built, and this page will change the day it begins. Until then, the review and the code checks above are the only checks.

A separate AI auditor starts again from the official pages and re-checks every newly confirmed date and every event a reader reports, plus 20 random events every month.

We hold ourselves to an error budget, read over the last 92 days: no wrong confirmed date, and no more than 2 per cent of audited facts wrong. If the budget is broken, we stop confirming new dates until the cause is fixed and a fresh sample checks out.

When a site blocks us

If an organiser’s site asks us not to read it, or blocks our crawler, we stop and do not try to get round it. The facts from that site then age honestly: the date of the last check stays where it was, and the “Checked” line moves to “May have changed” and then “Confirm on the official site”.

Researched and written with AI

The research, the writing and the reviews above are done by AI models, with code checks around them. No person reviews individual events or pages. Each page says so, and shows the date it was last checked against the official source. We label it plainly because readers should know, and because the EU’s AI Act asks for AI-written text to be disclosed.

If something is wrong

Write to support@lingoblend.app with the page and what is wrong. We re-check the fact against the official source.

Sources and credits

What the site is made from, and where each part comes from.

Dates, places, prices and ticket details: The organiser’s official pages, linked from each event page.
Photos: Where a page shows a photo, it comes from Wikimedia Commons under its licence, and the credit with the author’s name sits on the page.
Place names, coordinates and time zones: Wikidata, which is released under the CC0 public-domain dedication.
Background descriptions: Sometimes Wikipedia and Wikivoyage, under their CC BY-SA licence, written again in our own words and credited on the page.