01
What facility management mobilisation should achieve
Facility management mobilisation is the structured work between appointment and stable service delivery. It converts the agreed scope, service levels, commercial schedules and responsibilities into practical operating arrangements for a particular property. A provider transition adds another layer: information, access, work in progress and supplier interfaces may need to move from an outgoing team without losing visibility or ownership.
The mobilisation plan should identify what must be ready for go-live, what can be verified during an agreed stabilisation period and what remains an owner or third-party dependency. The plan should match the property and contract rather than rely on a universal duration. An occupied building with several specialist systems may need different controls from a small property with complete records and fewer interfaces.
02
Set governance, decisions and start conditions
Begin with a mobilisation charter or responsibility schedule naming the owner representative, incoming provider lead, outgoing-provider contact where applicable and relevant specialist interfaces. Define who can approve access, expenditure, subcontractors, shutdowns, communications, system changes and document acceptance. A weekly meeting alone is not governance unless actions, decisions, evidence and due dates have accountable owners.
Separate contract commencement, physical access, data handover, service go-live and baseline acceptance because these events may not occur at the same time. Record the conditions required for each milestone and the consequence of an unmet dependency. Formal contract, employment, insurance, licensing, safety or regulatory matters should be reviewed by the owner’s appropriate advisers; the mobilisation register should track them without pretending to replace that advice.
03
Create a controlled handover information register
List the information needed to operate the property: approved scope documents, drawings, manuals, asset registers, warranties, maintenance schedules, recent reports, open quotations, permits, access instructions, contact lists and relevant service history. For each item, record the requested source, received date, version, owner, review status and any limitation. A shared folder is useful only when the team knows which document is current and which information is still missing.
Do not treat inherited data as verified merely because it has been handed over. Mark information as received, reviewed, sampled, verified or superseded using agreed definitions. Protect confidential information and restrict access to people who need it for the operating purpose. Where records cannot be transferred, document the gap and the interim control rather than allowing the missing information to disappear from the mobilisation discussion.
04
Verify the property, assets and baseline condition
Walk the maintained areas and reconcile available asset information with what can be identified safely and practically on site. Useful fields include asset reference, description, location, operating status, service responsibility, known warranty or specialist arrangement and whether the record still needs technical confirmation. The mobilisation team should not invent capacities, condition ratings or maintenance histories where evidence is absent.
Record baseline observations separately from confirmed defects and specialist findings. Photographs, locations and dates can help preserve what was visible at handover, but they do not replace competent inspection or testing. Agree how material discrepancies affect the planned schedule, commercial scope or owner decisions. This protects the operating baseline from becoming a silent mixture of inherited errors and new assumptions.
05
Transfer open work, risks and specialist dependencies
Create an open-work register covering active faults, temporary measures, outstanding recommendations, approved work not yet completed, pending quotations, warranty claims and access-dependent items. Each entry should identify the location or asset, current status, available evidence, responsible party, next decision and commercial route. Priority labels should use the agreed service definitions instead of informal descriptions that different teams may interpret differently.
Map every specialist provider and retained contract that affects facility operations. Record the service, contact route, agreement owner, expiry or review point where known, access requirements, reports expected and the incoming provider’s role. Do not imply that a subcontractor or warranty obligation has transferred until the relevant contractual parties confirm it. The objective is continuity of visibility, not an unsupported assumption of responsibility.
06
Prepare people, access and property communications
Define the proposed organisation, named roles, attendance arrangement, reporting line and cover model that support the accepted scope. Confirm induction, identification, keys, cards, restricted areas, parking, loading, work permits and access to plant or service spaces through the property’s approved procedures. Where employment transfer or workforce matters may apply, obtain appropriate specialist advice rather than treating them as a simple operational checklist item.
Plan communications for owners, managers, occupants, tenants and retained suppliers according to their real need. Explain the start date, reporting route, contact changes and any temporary process without publishing unsupported availability or response promises. Keep private resident, tenant and personnel details out of broad circulation. A short, approved communication with one clear request route is usually more useful than several uncoordinated announcements.
07
Build the maintenance and request workflows
Translate the contracted scope into operating workflows for planned maintenance, reactive requests, inspections, quotations, approvals, specialist escalation and close-out. Define the minimum information required when a request is raised, who reviews it, how priority is assigned, when owner approval is required and what evidence closes the item. Test the route with realistic examples before go-live so gaps appear while they can still be corrected.
The planned-maintenance schedule should connect agreed assets, tasks, frequency basis, permitted windows, evidence and specialist responsibility. If asset verification is incomplete, identify which schedule lines are provisional and when they will be confirmed. Avoid filling the calendar with generic tasks solely to make it look complete. A controlled provisional plan is more reliable than a detailed schedule built on unverified assets.
08
Configure reporting, SLAs and commercial controls
Configure request categories, priority rules, acknowledgement and attendance stages, permitted exclusions and escalation routes from the accepted SLA definitions. Confirm which timestamp starts each measure and what evidence stops it. A system label should not silently change the contractual meaning. Sample reports should be reviewed before service begins so owners can see whether planned work, open risks, repeat issues and overdue decisions will remain visible.
Set the commercial workflow for recurring scope, materials, specialist work, variations, emergency authority where agreed and owner approvals. Record quotation content, approval evidence, purchase-order requirements and invoice support expected by the contract. Mobilisation costs and one-off setup items should remain distinguishable from recurring service charges. These controls help the operating team act within authority without turning every request into an unresolved commercial question.
09
Run readiness reviews before go-live
Use a readiness checklist grouped by critical operating areas: governance, people, access, information, assets, open issues, suppliers, planned maintenance, reactive workflow, reporting, communications and commercial controls. Each item should have an evidence reference and a status such as ready, ready with an interim control, not ready or not applicable. Percentage completion alone can be misleading when a small number of unresolved items carry most of the operating consequence.
Hold a go-live decision review with the authorised parties. Record unresolved dependencies, interim controls, owners and review dates. If a critical requirement is not ready, the decision should be made through the agreed governance route rather than hidden inside a progress report. A day-one contact sheet, escalation route, open-work list and planned schedule should be accessible to the people who will actually operate them.
10
Stabilise the service and close mobilisation
After go-live, review request quality, access failures, incomplete records, schedule changes, reporting accuracy, repeat issues and supplier interfaces at an agreed frequency. The first operating period often reveals assumptions that were not visible in documents. Record them through change control and distinguish correction of mobilisation gaps from changes to the contracted scope.
Close mobilisation only when the agreed deliverables and outstanding actions have been reviewed, transferred or accepted through the proper authority. Preserve the final asset baseline, operating contacts, schedule, responsibility matrix, open-risk register, reporting format and approved changes as controlled records. Lessons learned should be specific enough to improve the next transition rather than becoming a generic statement that communication should be better.
Friends Facilities Management can review a Dubai property brief and discuss mobilisation requirements for an annual, outsourced or coordinated facility management proposal. Final timelines, access, staffing, systems, services, reporting, specialist responsibilities, exclusions and commercial terms must be confirmed for the specific property in an accepted written agreement. This guide is general information and not legal, employment, safety, regulatory or technical advice.