The first weeks of facility management should not be spent reacting to whichever fault is loudest. Mobilisation is the period when the operating system is established: responsibilities, asset information, maintenance routines, vendor obligations, documentation and management reporting.
Begin with a baseline of the asset and its current operating condition.
A new handover and an existing building both need a starting point. The team should understand what equipment exists, what records are available, which systems are critical, what defects are open and which service providers are already engaged.
For an existing asset, maintenance history can be as important as drawings. Recurring failures, temporary repairs and vendor callouts often reveal where the operation is unstable.
The baseline does not need to be perfect before FM begins. It needs to be structured enough that missing information and unresolved risks are visible.
Build the core registers before information spreads across emails and messages.
An asset register should identify major equipment, location, criticality and responsible service party. A PPM planner should show required recurring tasks and due dates. An open-issues register should capture faults, actions and closure.
Vendor information, warranties, manuals and statutory or specialist records should also have defined locations. The objective is not bureaucracy; it is to prevent the operating team from rediscovering the same information every time an issue occurs.
Where the asset has just been handed over, the FM team should connect these registers to the construction closeout information while it is still accessible.
Planned maintenance should reflect the real asset, not a generic checklist.
Maintenance frequencies should be based on installed equipment, manufacturer requirements, operating conditions and criticality. A generic schedule can create activity without protecting performance.
The team should also distinguish between routine maintenance and condition-driven intervention. Some systems need fixed periodic tasks; others benefit from inspection trends or operating data.
Missed PPM should remain visible. Closing the month by moving overdue tasks forward without explanation only hides operating risk.
Service providers need measurable responsibilities.
Outsourced FM can involve cleaning, MEP maintenance, lifts, fire systems, generators, water treatment, security and other specialists. The client needs one view of what each provider is expected to do and whether it is happening.
Service visits should be linked to scope, evidence and outstanding findings. If a vendor identifies a defect, the issue should enter the operating register rather than remain buried in a service report.
Contract renewal becomes easier when performance has been documented throughout the year instead of reconstructed at the end.
Asset visibility
Know what is installed, where it is and who is responsible.
Planned before reactive
Routine maintenance should be scheduled before faults dictate the agenda.
Issue ownership
Every open technical issue needs a priority, owner and closure path.
Management visibility
FM reporting should highlight risk and required decisions, not just activity.
FM reporting should show operating risk, not only completed tasks.
Management does not need every maintenance detail. It needs visibility over critical overdue work, recurring faults, unresolved vendor issues, major expenditure needs and decisions that affect continuity.
A concise dashboard can therefore show PPM completion, high-priority open issues, repeat failures, warranty exposure and important upcoming maintenance.
That view also helps distinguish a building that is genuinely stable from one that looks quiet because problems are being handled informally.
Mobilisation is complete when routine operation no longer depends on individual memory.
A stable FM system should continue working when one technician, property manager or vendor representative is absent. That requires records, responsibilities and escalation routes to exist outside personal chat histories.
Once the core controls are established, the team can improve them: refine criticality, adjust maintenance frequencies, consolidate vendors, improve spare-parts planning and identify recurring technical weaknesses.
The first objective is control. Optimisation comes after the asset is visible.
Use the first 90 days to move from mobilisation to stable operation.
The first month should focus on visibility: asset information, open defects, providers, maintenance obligations, critical systems and immediate risks. The next phase should test whether the planned routines actually work in the building rather than only on paper.
PPM tasks may need adjustment once access requirements and operating hours are understood. Vendor scopes may contain gaps or overlaps. Asset data may require correction. Some handover defects may prove to be operational issues, while other apparent maintenance problems may still belong to construction closeout.
Separate inherited issues from normal operations.
At mobilisation, the FM team should identify defects, incomplete documentation and outstanding project items that existed before normal operation began. Keeping these visible as a separate transition list prevents them from disappearing into routine maintenance where responsibility becomes harder to establish.
By the end of the early operating period, the building should have repeatable workflows for planned work, reactive issues, vendor visits, approvals, emergency escalation and management reporting.
What should building management be able to see every month?
A useful FM dashboard should answer a limited number of management questions. Are critical maintenance tasks being completed? Which high-priority issues remain open? Are the same faults repeating? Are service providers meeting their obligations? Are warranties or statutory requirements approaching key dates? What expenditure or technical decision requires approval?
Trend information matters more than isolated numbers. A building may report high maintenance completion while repeat failures increase. Another may have several open issues but all be low priority and properly controlled. Context is necessary before management interprets a percentage as performance.
Use operational data to improve the asset, not only report it.
Once recurring information is reliable, the FM team can identify systems that consume disproportionate maintenance effort, vendors that repeatedly fail to close issues and equipment that may justify replacement rather than repeated repair.
This is the point where facility management begins contributing to asset decisions rather than simply administering maintenance. The operating record becomes evidence for budgeting, upgrades, refurbishment and future procurement.
Yehya Group viewpoint
FM mobilisation should turn building information into an operating system.
Yehya Group structures facility management around asset registers, planned maintenance, issue control, service-provider coordination and management reporting.
The aim is to move from reactive follow-up toward stable operation where recurring work and technical risk remain visible.