Skip to content
EventConsultant.com.my

Running the pre-event venue operations meeting

The booking is signed and the programme is nearly final, but the venue's operations team and your suppliers have not yet sat down together.

Discuss venue operations coordinationOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.

The short answer

A venue operations meeting is one structured session, usually held some weeks before the event, where the organiser, the venue's operations and catering contacts and the main suppliers agree who does what, when and where. It closes open items and produces a written action log.

Send the agenda and your current documents in advance, so the meeting is for decisions and not for reading.

Who should be in the room

Invite the venue's event or operations contact, the catering contact, and anyone who controls access, loading and technical services. From your side, include the project lead, the event owner and the main suppliers: AV, registration, décor and any exhibition contractor.

Keep the meeting small. Anyone who is only needed for one item can join for that part.

An agenda that closes things

ItemWhat to settleDocument used
Programme and room useFinal room allocation, layouts and turnoverAllocation worksheet, run-of-show
Access and loadingWindows, routes, who needs to be whereLoad-in plan, credential rules
Food and beverageFunction order, numbers, deadlinesFunction order, numbers sheet
Technical needsPower, AV, internet, staff on siteSupplier requirements
People and flowSpeaker room, registration, signage, organiser officeSite plans
Open questionsAnything not yet confirmed in writingEvidence log
Day-of contactsWho is reachable, and on which numberContact sheet

Before, during and after

  1. Before: circulate the agenda, the run-of-show and the open-items list a few days ahead, and ask the venue to bring its own function sheet.
  2. During: take the agenda in order, name an owner and a date for every action, and record any point the venue says it cannot confirm.
  3. After: send the action log within one working day and ask each party to confirm its items by reply.
  4. Update the run-of-show and ask the venue to confirm any changes in writing.

Things that go wrong

  • Key suppliers are not invited, so decisions are made without them.
  • The meeting repeats items already in writing, leaving no time for open questions.
  • Actions are agreed verbally and nobody records them.
  • The venue's contact for the day itself is never named.
  • A second meeting is needed because documents were not shared first.

Worked example · Fictional example

A two-day conference meeting its venue's operations team

Fictional organisation and figures, written to show the level of detail that is useful.

A fictional association holds an operations meeting with the venue's event manager and catering lead, the AV supplier and its own project lead. The agenda has seven items and the open-items list has nine entries, of which three are about loading and two about signage.

By the end, six items are closed and three have an owner and a date. The action log goes out the next morning, and the venue replies confirming the loading windows in writing. The project lead updates the run-of-show and attaches the revised version.

Use this yourself

Operations meeting agenda and action log

Copy this into your meeting invitation and keep the log open in the shared document during the meeting.

  1. Meeting date, place or link, and attendees with roles:
  2. Documents sent in advance (run-of-show, allocation worksheet, function order, access plan):
  3. Agenda item 1: programme and room use. Decision, owner, date:
  4. Agenda item 2: access, loading and storage. Decision, owner, date:
  5. Agenda item 3: food and beverage. Decision, owner, date:
  6. Agenda item 4: technical needs. Decision, owner, date:
  7. Agenda item 5: people flow, signage and organiser office. Decision, owner, date:
  8. Open questions the venue could not confirm, and when it will:
  9. Named day-of contacts (venue and organiser) and how they will be reached:
  10. Date the action log will be sent, and the reply deadline:
  11. Date of any follow-up meeting or call:

Open the tool: Venue site-visit evidence log

Handle it in-house, or bring in help?

Your team can usually handle this when

  • One venue contact and one or two suppliers.
  • The programme is stable and most items are already in writing.
  • Your team can write the action log the same day.

Outside planning help earns its fee when

  • Several suppliers, rooms and contacts need to agree on interlocking items.
  • Previous meetings left open items and nobody chased them.
  • Venue operations, catering and technical teams are separate and need one organiser voice.

Need someone to chair the operations meeting?

A conference project lead can prepare the agenda from your documents, chair the meeting, keep the action log and chase each party to confirm in writing. Decisions on programme and budget stay with your organisation.

Discuss venue operations coordinationOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.Conference project lead

Questions organisers ask

When should the operations meeting be held?

Late enough that the programme, numbers and suppliers are largely known, and early enough that open items can still be fixed. Ask your venue when its own planning cycle runs.

Who has to attend?

The venue's operations contact, catering contact and anyone controlling access and technical services, plus your project lead and the main suppliers. Others can join for one item.

Is it a problem if the venue sends a different contact on the day?

It is common. Ask who the day-of contact will be, how to reach them, and have the planning contact brief them using your action log.

Can the meeting be online?

Yes, if everyone can see the same documents. Hold a site walk-through separately if there are layout or access questions to check in person.

Related resources

Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.