Last updated: 2026-09-10
1. Venue basics come from jobs we actually worked
Hall counts, table capacity, addresses and service records come from our own job sheets, accumulated since 2016 while running events on site. This is not a scraped directory — these are rooms we have carried equipment into, walked the floor of, and plugged a projector in at.
That gives the data a clear boundary: venues we have never worked are thinner in our records. We do not fill in fields with numbers we are not sure of.
2. Event counts include only completed events
The "events delivered" figure on a venue page counts only events that actually happened and are marked complete or normal. Enquiries, leads, trials and lost bids are excluded.
This makes our numbers considerably smaller than our internal totals, but it means something precise: we really did work this many events at this venue. Better to under-report than over-report.
3. Ratings and reviews come from Google Maps
Star ratings and review counts are taken directly from Google Maps. We do not edit, filter or hide negative reviews, and displayed reviews link back to the original on Google.
There is a lag between our snapshot and Google. Treat Google Maps as authoritative for the current figure.
4. AI summaries condense, they do not invent
The review summary asks an AI model to condense the specific themes that recur across a venue's Google reviews — space, food, service flow, parking, AV. Our instructions require it to summarise only what reviews actually mention, to reflect complaints as faithfully as praise, and to avoid promotional language.
The discussion summary works only from forum post titles and is explicitly forbidden from inferring the content or sentiment of those posts — because we store only titles and links, never the body text.
The underlying material sits one click below every summary. The summary is there to save you time, not to replace the source.
5. The heat score, and how it is calculated
Heat is not a popularity vote and not an ad slot. It is a weighted score of five inputs:
| Input | Weight | Notes |
|---|---|---|
| Events delivered | 55% | Total completed events |
| Share in last two years | 20% | Whether the venue is still active |
| Recency | 10% | How recently we last worked there |
| Venue scale | 10% | Hall count and table capacity |
| Service variety | 5% | How many service types we have run there |
Heat reflects only how active a venue is in our records. It is not a quality ranking and not a recommendation.
6. Which venues get their own page
We list far more venues than we give pages to. A venue gets a standalone page only when the record is substantial enough — it has an address, and either three or more delivered events or three or more halls.
That threshold is deliberate. Thin pages help no one and are noise to search engines. Other venues still appear in the regional listings.
7. Photos and third-party content
Venue photos come from Google Maps or public wedding-venue sites, and every one carries its source. We do not republish third-party descriptions — external text is used only as internal reference, and the description you read is rewritten from our own factual fields and checked against a banned-phrase list.
Forum discussions are stored as title and link only. Clicking through takes you to the original.
8. What we deliberately do not do
No paid ranking. Venue ordering is determined entirely by the heat score. There are no paid positions.
No deleting negative reviews. Ratings and reviews appear as they are, including low scores.
No invented figures. Fields without data stay empty rather than being filled with estimates.
No republishing third-party body text. External content appears as titles and links only.
9. Found something wrong?
Venues change and we get things wrong. If any detail is incorrect — hall count changed, venue closed, address moved — tell us on LINE. We will verify, correct it, and note the update date.
Corrections from the venue itself go to the front of the queue.