Staff for a company dinner: coordinating reception, hospitality and speeches
A dinner with reception, table service and speeches needs every team to know who gives the next cue. This procedure helps prepare the briefing and handovers; included roles, staff and coordination are confirmed in the proposal.
1. One shared programme and a current version
List arrivals, welcome, service, speeches, any awards, music and close. Identify the contact, start cue and dependencies for each moment. Catering confirms when service can run and the programme contact validates speeches; the host needs that version to prepare transitions.
Agree who authorises changes and how reception, hospitality and technical contacts are informed. A speech change can affect service: telling only the host leaves other teams working from old instructions.
2. Separate decisions from delivery
Reception
Checks the approved list, gives directions and communicates arrivals.
Refers to: Guest contact for exceptions or seating.
Hospitality and catering
Service and table changes around the agreed plan.
Refers to: Catering contact for menu, service or individual requirements.
Host
Speeches and transitions in the approved script.
Refers to: Programme contact for order, messages or changes.
Technical team
Microphones, sound, screens and agreed cues.
Refers to: Technical lead and production contact.
Coordination, when commissioned
Connects teams, collects incidents and communicates decisions.
Refers to: Client or designated contact for approval of scope changes.
Use the matrix to assign actual names and contacts before the event. It does not imply all roles are included or that one person can cover simultaneous tasks. The proposal defines services and responsibilities.
3. Prepare the handover before leaving a post
For a break or shift change, confirm who covers the post and what they need to know: pending tasks, the next cue and the contact for an open incident. The replacement should know what can be resolved and what needs approval.
Avoid transferring complete guest lists or individual details through channels that have not been agreed. The general briefing needs the procedure; information required for each post is shared with authorised people.
4. Three incidents to rehearse in the briefing
The following are planning examples, not accounts of events delivered by Wira.
A person arrives who is not on the list: reception consults the guest contact while continuing to assist other arrivals. It does not decide admission or change seating on its own initiative.
A speech overruns while service is being prepared: the programme and catering contacts agree the next transition. The designated person communicates the decision to the host, technical team and hospitality team.
A microphone stops working: use the alternative rehearsed with the technical team and inform the programme contact. Do not promise that an incident will be imperceptible or improvise a technical solution without a responsible contact.
5. Close services and leave clear outstanding actions
Before finishing, confirm the close of reception, hospitality, programme and commissioned resources. Record materials to return, outstanding incidents and who receives them. Extra hours or new services need a decision by the authorised person and confirmed terms.
A later review can separate handover timing, incident referrals and team coordination. These operational checks do not by themselves establish universal satisfaction, sales or commercial results.
Prepare the proposal
Include city, date, venue, estimated attendance, programme moments and the roles you need covered. A named guest list is not needed for the first enquiry. The header illustration represents coordination between reception, dinner service and speeches; it is not a photograph or a delivered assignment.
Before the briefing
Are all roles in the matrix included?
The matrix is a planning tool. The proposal confirms commissioned roles, duties, hours and coordination, together with what the venue and each supplier provide.
Who authorises a change during dinner?
The organiser’s designated person. Programme, catering and technical contacts assess dependencies; the agreed contact communicates the decision to affected teams.
What do staff receive before the service?
The current programme, role and hours, incident contact, start cues and handover procedure. Each post receives the information it needs through the agreed channel.
Are the incident examples real assignments?
No. They are planning scenarios for rehearsing decisions and communication in the briefing, not accounts of company dinners delivered by Wira.
Tell us the staff roles and running order