Before the SLA Bites: Structuring the First Quarter of an FM Contract

Contract signature is a milestone, not a finish line. In UK commercial property, the period between award and steady-state service is where expectations are set, data is proved and relationships are tested. Yet mobilisation is often treated as an administrative preamble to the "real" contract. The result is predictable: incomplete asset registers, unresolved TUPE queries, a helpdesk that cannot log a job correctly and KPIs that are disputed before the first monthly report is due.

The remedy is not more goodwill. It is project discipline. A new facilities management (FM) contract deserves the same structured approach as a fit-out: a named mobilisation lead, a dated plan with dependencies, a defined budget and a formal readiness review before service commencement. The first quarter should be managed as a phase with its own deliverables, not as an extension of the tender process.

Appoint a mobilisation lead with authority

Mobilisation fails quietly when accountability is diffuse. The client-side project sponsor and the contractor's mobilisation manager must be named before contract award, not after. Each needs delegated authority to make decisions on data formats, access arrangements and interim staffing without returning to a steering group for every query.

A practical mobilisation plan should be dated from contract award to day ninety, with workstreams for people, property data, systems, compliance and governance. Dependencies matter: the helpdesk cannot go live before the asset register is validated, and the asset register cannot be validated without access to site and to the previous provider's records. Setting these sequences out in writing turns a vague handover into a controllable programme.

TUPE and the people plan

Where TUPE applies, the people workstream is rarely the longest item on the plan, but it is the one most likely to disrupt service at the point of transfer. Employee liability information must be requested and reviewed early, and consultation should begin on a timetable that allows incoming staff to understand shift patterns, site allocations and reporting lines before day one.

Beyond the legal mechanics, there is an operational point: transferred staff often hold the site knowledge that no asset register captures. A structured induction for incoming and transferring employees, covering permit systems, escalation routes and site-specific risks, protects continuity. It also reduces the risk of early service failures being attributed to the contract rather than to an avoidable induction gap.

Asset and compliance data handover

Compliance obligations do not pause while systems are migrated. The mobilisation plan should identify the statutory and mandatory records that must be transferred and verified before day one: asbestos registers and management plans, water hygiene records under L8, fire risk assessments and associated actions, electrical safety certificates, gas safety records and lifting equipment inspections. The list will vary by property type, but the principle is constant: the incoming contractor must be able to evidence that it has received, understood and scheduled the relevant obligations.

Asset data deserves particular scrutiny. A register that lists plant without location codes, service history or criticality ratings will generate inaccurate planned preventative maintenance schedules and distorted KPIs. A validation exercise during mobilisation, even a sample-based one, is cheaper than correcting the register after the first quarter's reporting cycle.

Site inductions, access and the day-one pack

Mobilisation is often described in contractual language, but it is experienced by operatives as a series of practical questions: where do I park, who signs me in, which riser holds the isolation valve, who authorises a permit? A day-one pack for each site should answer these questions in plain terms and be issued before the service start date.

Site inductions should be scheduled for all regular attendees, including subcontractors who will attend under the new contract. Access arrangements, keys, fobs and building management system credentials need to be tested, not assumed. Where a landlord or managing agent controls access, the mobilisation plan should record who is responsible for issuing credentials and by when.

Helpdesk cutover and escalation routes

The helpdesk is the contract's front door. If it is not ready, every later failure is harder to manage. Cutover planning should cover the transfer of open work orders, the mapping of priorities against the new service levels, the routing of out-of-hours calls and the communication of new contact details to occupiers and site teams.

Escalation routes should be tested during mobilisation with a small number of live or simulated jobs. A named escalation matrix, with response times and deputies, is more useful than a generic contact list. The first disputed job is far easier to resolve when both parties know who should have been called and when.

KPIs, reporting and the first review

The service level agreement may be signed, but its practical meaning is settled in the first reporting cycle. Mobilisation should include a dry run of the monthly report, using a sample of data, so that both parties can see how availability, response and completion are calculated. Any ambiguity in the KPI definitions should be resolved before the first scored month, not after it.

A short set of leading indicators is worth adding to the mobilisation dashboard: percentage of assets validated, compliance records received, staff inducted, helpdesk jobs logged correctly and open work orders transferred. These are not contractual performance measures, but they give the mobilisation board an early warning of where the service is likely to struggle.

Governance and the readiness review

A weekly mobilisation meeting with a live actions log, named owners and RAG status is sufficient for most contracts, provided it reports into a decision-making forum. The point is not to create bureaucracy but to catch early failures while they are still administrative rather than contractual.

Before day one, hold a formal readiness review. The review should test the workstreams against agreed exit criteria: people transferred or inducted, asset register validated to the agreed standard, compliance records received and scheduled, helpdesk tested, escalation routes published and day-one packs issued. Where a criterion is not met, the review should record the gap, the interim control and the date by which it will be closed.

That single gate changes the tone of mobilisation. It gives the client evidence that the contractor is ready, and it gives the contractor a fair opportunity to fix problems before service levels begin to bite. In a contract that may run for several years, ninety days of structured preparation is a modest investment against the cost of a disputed first quarter.