EventIntel Weekly

The intelligence briefing for senior event leaders.

Issue 004 — 13 September 2026Archive

The Five

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

01

The Register — Copilot web outage and resilience test · 10 September 2026

Copilot went down. Does your event team have an AI continuity plan?

Microsoft's Copilot web service was unavailable for about 100 minutes overnight on 9–10 September, returning a Cloudflare routing error. At around the same time, some Copilot Chat users lost suggested prompts during what Microsoft described to reporters as a separate resilience test. On 11 September, Microsoft investigated another access disruption under incident CP1470554; users reported failed access, blank replies and incomplete content. NHSmail also logged a Copilot Chat degradation alert on 10 September. These should not be collapsed into one dramatic global failure. Public reporting does not establish a user count, Microsoft has not published a root-cause review for the incidents we could verify, and the public Copilot website is not the same service surface as Microsoft 365 Copilot. What the sequence does establish is more useful: AI availability is no longer an abstract technology question when venue comparisons, RFP analysis, briefs, meeting summaries, schedules and reporting are beginning to depend on it.

Why it matters

SO WHAT FOR CORPORATE EVENT LEADERS? Separate the AI layer from the underlying work. If Copilot is unavailable, your team should still be able to reach the current brief, venue proposals, run of show, supplier contacts and approved templates. Save critical prompts and agent instructions outside the AI platform, name an owner for AI-dependent workflows and agree the manual fallback for anything that matters during show week. This is not a case for an elaborate disaster-recovery programme. It is the same proportionate discipline you already apply to registration, connectivity and production.

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.

Build my IMEX America plan

Copy + paste this prompt

BUILD MY IMEX AMERICA PLAN Act as an experienced executive assistant and event-industry strategist. Help me build a realistic, commercially useful plan for IMEX America. Do not fill every minute, invent programme information or assume an appointment is confirmed. I will provide some or all of the following: - IMEX dates and the days I will attend - flight details and airport transfers - hotel and check-in/check-out times - confirmed appointments - companies or exhibitors I need to meet - destinations and venues I want to investigate - education interests - business objectives - people I want to network with - hosted-buyer commitments, if applicable - social events - personal commitments - preferred working style - time I want protected for email, rest or preparation. First, ask only the missing questions that materially affect the plan. Separate confirmed information from assumptions. If you cannot verify a show time, session, exhibitor location or travel duration from information I provide, label it CHECK rather than inventing it. Then create the following in order. 1. THREE PRIMARY OBJECTIVES FOR IMEX Turn my business objectives into three specific outcomes. For each, state what evidence at the end of the trip would show it was achieved. 2. PRIORITY MEETING LIST Sort every proposed meeting into MUST DO, USEFUL or OPTIONAL. For each, explain the ranking, the objective it serves and whether it is confirmed, requested or still to arrange. Flag duplicate conversations and meetings that could happen by video after the show. 3. DAILY ITINERARY Build a realistic itinerary for each day. Include confirmed appointments, selected education, purposeful networking, walking or travel buffers, food, two email/work windows and recovery time. Protect the time I requested. Do not fill every minute. Identify conflicts and give a recommended choice rather than silently moving a commitment. 4. MEETING PREP For every MUST DO meeting, provide: why it matters; three questions to ask; information to capture; any useful evidence or document to request; and what a successful outcome looks like. Keep each brief short enough to read while walking to the meeting. 5. DAILY MORNING BRIEF Create a breakfast-length briefing for each day: today's three priorities, first appointment and location, preparation still required, timetable risks, people to look out for, and the one thing I should decline if the day becomes overloaded. 6. END-OF-DAY PROCESS When I paste my notes, return: decisions; actions with owner and date; follow-ups; people to reconnect with; opportunities; supplier or destination intelligence; unanswered questions; and changes required to tomorrow's schedule. Mark sensitive or unverified information clearly. Never present an inference from my notes as a fact. 7. POST-IMEX REPORT Produce an executive summary, key supplier and destination findings, commercial opportunities, evidence-backed trends observed, follow-up actions with owners and dates, and recommended next steps. Separate what I learned from what I inferred. Add a short section called WHAT WAS NOT WORTH THE TIME so next year's plan improves. Rules: - Use UK English. - Be concise and commercially aware. - Do not optimise for the number of meetings. - Preserve white space and recovery time. - Never invent show information, travel times, appointments or evidence. - Flag any item that needs checking against the official IMEX programme. - Do not ask me to upload attendee personal data, confidential contracts, supplier pricing, private meeting notes or other commercially sensitive information to an AI platform that my organisation has not approved. MY INFORMATION: [Paste your details here]

Why use it

Most show planning starts with available diary slots. This starts with the three outcomes that justify the trip, then makes every meeting, session and follow-up compete for a place against them.

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.