Events
Larger organised occasions — conferences, town halls, corporate functions — beyond routine meeting-room support, genuinely testing cross-service FM integration.
An events service is only as good as the weakest of the four or five services it has to coordinate on the day.
Why this service exists
Events draw simultaneously on catering, reception, AV, security and porterage — a coordination exercise that reveals, more clearly than almost any other service, whether an FM organisation's services actually integrate or merely coexist.
What the service covers
- Event planning and coordination.
- Cross-service scheduling (catering, AV, security, porterage).
- On-the-day delivery management.
- Post-event breakdown.
Assets and objects
- Event/conference spaces.
- Whichever assets the specific event draws on across other services.
Who takes part
- Events coordinatorRequired
Mandatory role, single point of accountability.
- Representatives from each contributing serviceRequired
Deliver their part of the event.
- Demand-side event organiserSituational
Sets the event requirements.
What the service needs
- Event brief and requirements.
- Cross-service availability and capacity.
How delivery runs
- 01Translate the event brief into cross-service requirements (catering headcount, AV spec, security needs, room setup).
- 02Coordinate scheduling and confirm capacity across every contributing service.
- 03Manage on-the-day delivery, with a single point of accountability for the whole event, not per-service accountability only.
- 04Execute breakdown and post-event review.
What is delivered
- Delivered event.
- Post-event review/lessons-learned record.
From output to outcome
An event delivered per brief.
A successfully delivered occasion.
Genuinely the platform's clearest practical test of service integration, since the outcome depends on multiple services performing in coordination, not independently.
Where it gets tense
- Events run with per-service accountability only and no single coordinating owner, so a failure in one contributing service (AV, catering) has nobody positioned to catch and compensate for it on the day.
Strategic, tactical, operational
Minimal beyond recognising events as a genuine integration test worth using diagnostically.
Advance-booking lead times need to be realistic against every contributing service's own capacity constraints, not just the primary venue booking.
A single on-the-day accountable owner, with real authority to redirect any contributing service, is the difference between smooth delivery and visible on-the-day scrambling.
Performance indicators
- Event satisfaction score
Experience indicator.
- On-time delivery rate
Delivery indicator.
- Cross-service coordination lead time
Process indicator.
Risks
- Inherits whatever statutory considerations apply to the specific contributing services engaged (fire capacity limits for large events being the most consistently relevant).
Statutory context
Fire/occupancy capacity regulation is jurisdiction-specific and the most consistently relevant statutory touchpoint for large events.
Sourcing options
- In-house
Typically an internal FM coordination function drawing on whichever services are otherwise sourced (in-house or outsourced) for their individual delivery.
Technology and data
- Event management/booking software integrating with room-booking and catering-ordering systems.
Competencies required
- Cross-functional coordination.
- Event management.
Common mistakes
- Treating events as a booking exercise rather than a genuine cross-service coordination discipline with a single accountable owner.