Event Manager Interview Questions

I start by turning the brief into a clear set of objectives and success criteria before any logistical decisions are made. A vague brief like "create a memorable experience" needs to become "generate 200 qualified leads and achieve a net promoter score above 8 from attendees" before I can make meaningful planning choices. Once objectives are clear I build a project plan with a master timeline, working backwards from the event date to set hard deadlines for venue confirmation, supplier contracts, communications, and production. I assign a named owner and deadline to every task, not just a category. For budget management I run a live tracker that separates committed spend from forecasted spend, which means I always know my exposure if something changes. I also build a contingency reserve of at least 10 percent into every event budget, listed as a line item rather than hidden in other costs, so stakeholders know it exists and we have a conversation before it is spent.

I treat supplier relationships as ongoing partnerships rather than transactional arrangements, because the quality of your event depends heavily on how your suppliers behave when things go wrong. Before any negotiation I do thorough research: what is the market rate for this type of supplier, what are the standard contract terms, and what flexibility exists on price versus specification? I always get at least three competitive quotes for significant spend categories, not just to benchmark price but to understand what different suppliers include as standard. In negotiation I focus on total value rather than headline price: a venue that includes AV, catering, and event staff in the day-rate is often better value than a lower headline rate with large add-on costs. I also negotiate the exit and change clauses as carefully as the pricing: a contract that does not protect you if the supplier underdelivers is not a good contract regardless of the price. After each event I give honest feedback to suppliers and I keep a supplier performance log that I refer to when making future recommendations.

Scope creep is the single biggest risk to most event budgets and timelines, and it almost always starts with a stakeholder asking for something reasonable-sounding mid-process. My approach is to be very explicit at the start about how changes will be handled: any request that affects scope, budget, or programme after the planning phase is signed off goes through a formal change request, which documents what is being added, what it costs, and what the impact is on the overall plan. This is not bureaucracy for its own sake; it is a tool for having a genuine conversation about trade-offs. When a stakeholder asks for something additional I do not just say yes or no: I present the cost and programme impact clearly and ask which priority they would like to reduce to accommodate it. I find that most scope creep disappears when stakeholders see the full cost of their request rather than just the headline addition.

My measurement framework is built before the event, not after. I agree the success metrics with the client or stakeholder at brief stage, set a pre-event baseline where relevant, and design the data collection into the event itself: registration forms, on-site surveys, badge scans, and post-event NPS questionnaires. Immediately after the event I capture the operational metrics: total attendance versus target, no-show rate, session attendance rates for multi-track events, and any incidents or near-misses. Within a week I produce a post-event report that covers performance against each pre-agreed success metric, the financial outturn against budget with an explanation of any variance, and three or four specific recommendations for future events based on what I observed. I share this report with all stakeholders, not just the ones who asked for it, because the learnings are only useful if they inform future decisions. I also debrief the delivery team within 48 hours while observations are fresh.

I was delivering a 400-person annual conference for a financial services client when our keynote speaker called in sick four hours before the event opened. He was the centrepiece of the morning programme and had been heavily promoted in the pre-event communications. My first action was to call three back-up speakers from a pre-vetted list I maintain for exactly this type of situation: one was available and could travel. While my team rearranged the running order to buy 45 minutes, I briefed the client on the situation and the proposed solution before making any public announcement. We ran a revised programme that moved the afternoon panel forward as the new morning highlight, the replacement speaker delivered a well-received session, and we sent an updated programme to all registered attendees an hour before doors opened. The client was nervous during the crisis but complimentary in the debrief. The lesson I applied afterwards was to always have signed availability agreements with back-up speakers, not just a list of contacts.

I inherited a hospitality event that had been running with the same supplier set for five years at a cost of approximately £85,000 per year. When I reviewed the contracts I found that we were paying above-market rates on catering, AV, and print, largely because no one had gone to competitive tender in several years. I ran a full competitive tender process for all three categories, which took about six weeks and required careful briefing to ensure the specifications were precise enough for genuine like-for-like comparison. The new suppliers delivered the same specification at a combined saving of £22,000, a reduction of about 26 percent. The only element where I chose the more expensive supplier was AV, where the quality difference between the two quotes was significant and visible to attendees. I also introduced a print consolidation policy that reduced the number of print runs from four to two, which saved additional cost on setup and logistics. Attendee satisfaction scores did not change materially between the two events.

I was managing a product launch event where the marketing director wanted a high-energy consumer experience, the sales director wanted a structured briefing format for key accounts, and the CEO wanted something that would generate press coverage. All three were legitimate objectives but they were pulling the event format in incompatible directions. Rather than trying to negotiate verbally, I prepared a simple one-page format comparison that mapped each option against each objective and showed clearly which format served which stakeholder priority. I ran a 45-minute meeting with all three together, presented the options neutrally, and asked them to agree on a priority order rather than debating each detail. They agreed that press coverage was the primary objective, which made the format choice much clearer. I then designed a hybrid format that served that primary objective while incorporating elements the other two stakeholders cared most about. The event generated coverage in three trade publications and the sales briefing was run as a separate afternoon session.

I use a combination of tools depending on the event scale and the client's own systems. For large multi-workstream events I use Asana or Monday.com for task tracking, with custom views for each supplier workstream so that dependencies between teams are visible. For smaller events I often use a shared Google Sheet with a master timeline and status tracker, which is simpler and more accessible for teams with limited tool access. In either case the core management artefacts are the same: a master timeline with hard deadlines and named owners, a live budget tracker separating committed from forecast spend, a risk register with likelihood and impact ratings, a contact directory for all suppliers and key stakeholders, and a day-of run sheet that is the single source of truth on event day. I run a weekly status call during the planning phase and a daily check-in in the final two weeks. I send a written status summary after each call so there is always a record of what was agreed.

Health and safety is the non-negotiable foundation of any event, and I treat it that way from the initial planning stage. For any event with over 100 attendees I produce a formal risk assessment that covers venue-specific hazards, crowd management, medical provision, fire safety, and any activities with a higher inherent risk profile such as outdoor events or product demonstrations. I liaise directly with the venue's health and safety officer and the local authority if required, and I ensure all supplier contracts include their liability insurance certificates. On-site I designate a named safety officer with clear authority to stop or modify any activity if a safety concern arises, and I brief the full team on emergency procedures at the production meeting the day before. I also maintain a written incident log throughout the event: even minor incidents are recorded so that there is a full picture if anything is followed up afterwards. Since GDPR I have also integrated data protection into my event planning for any event that collects personal data.

My technology stack varies by event type and budget, but I always start with the measurement objective and work backwards to the technology choice, rather than choosing a platform and fitting the measurement to it. For registration I use Eventbrite or a custom registration form depending on whether the client needs integration with their CRM, because the data structure of registration determines what analysis is possible afterwards. For engagement during the event I have used polling tools like Slido, app-based agendas, and QR-code-based content distribution, all of which generate attendance and engagement data alongside the content they deliver. For post-event measurement I run a short automated survey that goes out within 24 hours, when recall is highest, rather than waiting until the following week. I also use badge scan data from expo-style events to measure session attendance and dwell time, which is much more reliable than asking attendees to self-report. I always present a data dashboard in the post-event report rather than a text summary, because visualised data communicates patterns much more clearly.