EventIntel Weekly

The intelligence briefing for senior event leaders.

Issue 003 — 6 September 2026Archive

The Five

The five most important developments event leaders should know this week.

01

Manchester City / Radisson, Hilton Stories, Hyatt Newsroom · Bookings live from 1 September 2026

UK hotel opening radar: the autumn properties worth a site visit, and the one that will not hold your conference

Three openings matter to corporate programmes this autumn. The Medlock, the 401-room Radisson Blu on Manchester City's Etihad Campus, opened bookings on 1 September ahead of its planned late-2026 opening; the hotel sits alongside the stadium's existing suite and conference facilities, and Radisson has not published in-hotel meeting capacities, so confirm what is hotel space and what is stadium space before you contract. Waldorf Astoria London — Admiralty Arch opens on The Mall this autumn with 114 rooms in a Grade I-listed building; reservations opened on 17 June and event-space capacities have not been published. Hyatt Regency London Olympia opened on 7 July with 204 rooms inside the £1.3bn Olympia redevelopment, and its own largest verified meeting room seats around 62 — the scale sits next door in the exhibition halls, not in the hotel. We found no confirmed 500-plus-room UK opening with a published ballroom capacity landing between September and December. That is worth knowing in itself: UK large-group supply is not growing this autumn.

Why it matters

EVENTINTEL VERDICT. The Medlock is the only one of the three that can take a genuine room block: north-of-England conferences, sales kick-offs and multi-day team events with a built-in evening venue. Admiralty Arch is a board dinner, a client reception or a leadership offsite for twenty people who need to be impressed — not a conference hotel. Hyatt Regency Olympia is an accommodation and hospitality base for exhibitors and delegates attending Olympia, and should be sourced as part of that campus rather than as a standalone venue. SO WHAT FOR CORPORATE EVENT LEADERS? Ask each operator's press office for a signed capacity chart before you diarise a site visit; none of the three has published one.

Keep reading EventIntel Weekly

Get the complete weekly intelligence briefing, including The Five, AI Watch, Steal This Idea, EventIntel Take, The AI Prompt and On My Radar.

Free. Delivered weekly. Unsubscribe at any time.

Already subscribed?

Prompt of the Week

One AI prompt worth stealing this week.

The event pre-mortem

Copy + paste this prompt

You are running a structured pre-mortem on a corporate event. Assume the event has already taken place and it went badly. Work backwards to explain why. I will paste the event brief below this prompt. Analyse it from all seven of the following perspectives, and say explicitly when a perspective cannot be assessed because the brief does not contain the information: Global Head of Events, CFO, Procurement, Security and Risk, a senior attendee, a first-time attendee, and the event operations lead. Then produce the following, in this order. 1. Fifteen ways this event could fail. State each one as a specific failure, not a category. For each, name the perspective that would see it first. 2. Assumptions. List the assumptions the planning team appears to be making but has not stated. Quote the wording in the brief that reveals each assumption. 3. Risk ranking. Rank the fifteen failures in a table by likelihood (high, medium, low) and impact (high, medium, low), with a one-line justification for each rating. Put the high-likelihood, high-impact rows at the top. 4. Budget vulnerabilities. Identify where this budget is most likely to be exceeded, which costs are unquantified in the brief, and which are exposed to attendance numbers, currency, guarantees or late change. 5. Attendee experience weaknesses. Separate what a senior attendee would notice from what a first-time attendee would notice. 6. Operational dependencies. Identify every single point of failure: one supplier, one venue system, one person, one delivery window, one approval. 7. Reputational risks. Internal and external, including anything that would read badly if it appeared on social media or in trade press. 8. Accessibility and inclusion concerns. Cover physical access, sensory considerations, dietary provision, language, caring responsibilities, travel burden and participation format. 9. Sustainability issues. Cover travel, food waste, materials, energy and any environmental claim in the brief that would be difficult to substantiate. 10. Preventative actions. For the top ten risks only, give one specific preventative action, who owns it, and the date by which it must be done relative to the event date. 11. Five questions the event leader should be asking that are not in the brief. Make them uncomfortable and specific. Rules. Use only what is in the brief. Where the brief is silent, say so rather than inventing detail. Do not soften your assessment. Do not repeat the brief back to me. Where you are uncertain, mark the item as an assumption on your part. Before you begin: do not paste confidential contracts, attendee personal data or commercially sensitive pricing into an AI platform that your organisation has not approved for that use. EVENT BRIEF: [paste your brief here]

Why use it

A post-mortem tells you what went wrong after you have paid for it. This one forces the same analysis while the brief is still editable, and the seven perspectives surface the objections your stakeholders will raise later anyway — usually in the room where the budget is signed.

Before uploading budgets, contracts or confidential company information to an AI platform, follow your organisation’s AI and data-security policies.

EventIntel is exploring

Do you influence where events happen?

I’m exploring a new way to connect credible event-industry content creators with hotels, venues and destinations that want to reach actual event buyers.

This isn’t traditional influencer marketing. The idea is to connect suppliers with people whose audiences genuinely work in, buy and influence events.

For now, I’m simply testing interest from both sides.