Resolve the Client–Landlord–Provider Responsibility Gap

Why this matters

Many workplace failures sit between contracts. A landlord controls base-building systems, an FM provider manages occupied space and the client retains business decisions. Each party can perform its own obligation while the overall service remains unresolved. An interface record makes the handoffs and authority visible before an incident tests them.

Evidence context

The UK Cabinet Office’s Contract Management Playbook, published 25 March 2026, is government practice guidance. It supports proportionate governance, responsibility mapping, obligation tracking, accurate records, multi-source performance information, change control and planned exit. It does not measure the impact of those practices, and its public-sector rules should not be treated as universal law. [1, pp. 45–49,

53–55, 67]

The Planning Malaysia study published 3 June 2026 analysed PWD FMM 2016 and interviewed six purposively selected practitioners: five FM contractors and one public client. It reports challenges involving tender information, contract clauses, variations, specifications, work orders and asset data. The small contractor-heavy sample is indicative rather than generalisable; unexplained participant codes also limit respondent-level interpretation. [2, pp. 108–114]

Osmos Global analysis

Define the service outcome across organisational boundaries, not only each party’s activity. The practical consequence is that a reported result must be interpreted in the operating context that produced it.

Name who detects, reports, grants access, investigates, authorises cost, communicates and verifies restoration. This changes the management question from whether an activity occurred to whether the agreed condition was achieved and can be demonstrated.

Provide a fallback when the normal decision-maker or landlord contact is unavailable. The control should create enough traceability for another competent reviewer to reproduce the decision without relying on memory.

Track the whole incident even when work transfers to another party’s system. Where evidence is incomplete, the honest result is an exception with an owner—not a confident conclusion assembled from assumptions.

Figure 1. A mobilisation or recovery decision gate Original Osmos Global conceptual framework, 2026. Not a validated scoring model. Prepared 1 September 2026.

What this means: Calendar pressure does not remove the need to own unresolved risk.

The practical tool

1. Select shared-asset and access scenarios with material consequence. Write the purpose and boundary first so the record does not become a generic administrative form. 2. Map responsibilities, authority and evidence across all parties. Use information already created by operations where it is reliable, and identify any new collection burden explicitly. 3. Identify gaps, duplicated tasks and incompatible service clocks. Give the action to a named role with authority to resolve the exception or escalate it. 4. Agree escalation and fallback arrangements. Test the step on a difficult real example before making it part of routine governance. 5. Test the interface and update records after actual incidents. Retain the outcome and the evidence used so that later review can distinguish improvement from a change in reporting.

Illustrative application

A base-building water leak affects tenant equipment after hours. The landlord owns repair, the FM provider controls local isolation and the client decides whether business operations continue. Without an interface plan, each party may wait for another to authorise action. The record should show who can isolate, communicate, preserve evidence and declare the area usable. This example is an Osmos Global illustration, not a reported case from the cited sources. Its purpose is to test the decision logic and reveal what evidence would be required.

Questions for the review

• Can the parties demonstrate how they will select shared-asset and access scenarios with material consequence using a current operating record? • Which evidence would cause the acceptance owner to reject the reported result or impose a condition? • Who has authority to resolve the most consequential exception raised by this interface management control? • How will the workflow distinguish a provider-controlled gap from a client, asset, landlord or third-party dependency? • What will be rechecked to establish that the corrective action changed the operational outcome rather than only the report?

Portfolio and GCC application

Create the interface record around an event, not around a static organisation chart. For a shared building service, name who detects the condition, reports it, grants access, investigates, authorises intervention and confirms restoration. Where a role depends on the lease or management agreement, identify the relevant document and keep the unresolved interpretation visible for the appropriate professional review.

In a GCC occupying several floors of a multi-tenant building, the workplace team may receive complaints while the landlord controls the central plant. The FM provider may be able to verify local conditions but lack authority to change the shared equipment. Give users a communication owner even when technical resolution sits elsewhere. Otherwise each organisation can complete its own task while nobody owns the explanation to the affected business.

Test an after-hours handoff using the actual escalation route. Confirm that the receiving person can recognise the site, access the relevant record and contact someone authorised to act. An interface matrix becomes stale when people, management companies or building systems change. Review it after those changes and after a failed handoff. This operating record helps reveal gaps; it does not itself modify contractual or statutory responsibilities.

Implementation-quality indicators

• Selected records can be reproduced from source evidence without reconstructing the story after the review starts. • Exceptions carry a named owner, decision route, due date and explicit consequence of delay. • Temporary controls and permanent resolution remain distinguishable in both the operating record and the governance pack. • A later reviewer can see which baseline and definitions applied when the decision was made.

Leadership implications

CRE leaders should include operating interfaces in lease and property-management discussions. FM providers need clear authority limits and reliable landlord contacts. Workplace and business teams should know who communicates operational impact while technical ownership is resolved. The roles should be adapted to the organisation’s retained capability, site risks and contractual authority.

Practical recommendations

• Start with one service where the current evidence can be reconstructed and where a better decision would matter. • Pilot the tool with client and provider teams, record disagreements in definitions and revise the workflow before scaling. • Report exceptions, uncertainty and overdue verification alongside compliance results. • Review the control after a material incident, portfolio change, system migration or contract variation.

Risks, limitations and unresolved questions

A responsibility map is an operating aid, not a legal interpretation of the lease or service contract. It should be reviewed against the actual agreements and local requirements. The article provides an operational framework rather than contract wording, legal advice or a site-specific technical standard.

Source notes

[1] Cabinet Office. The Contract Management Playbook. UK Government, 2026-03-25. March 2026 edition. Printed pp.45–49, 50–55 and 67; PDF page index = printed page + 3. Accessed 1 September 2026. https://www.gov.uk/government/publications/the-contract-management-playbook Contains public sector information licensed under the Open Government Licence v3.0. https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/ [2] Syarifah Nur Shaqina Syed Shabahar; Haryati Mohd Isa; Nor Suzila Lop; Hussain Ismail. THE CHALLENGES OF FACILITIES MANAGEMENT AND MAINTENANCE CONTRACT DOCUMENT IMPLEMENTATION FOR OFFICE BUILDINGS IN MALAYSIA. Planning Malaysia / Malaysian Institute of Planners, 2026-06-03. DOI 10.21837/pm.v24i42.2033; volume24 issue3, pp.102–116. Methodology pp.108–109; Table2 p.109; findings pp.110– 113; limitations p.114. Accessed 1 September 2026.

Editorial and visual note

This publication is original Osmos Global analysis informed by the cited sources. Reported findings are distinguished from Osmos recommendations and illustrations. Source findings and trademarks remain attributable to their owners. The content is general research and does not replace contract-specific, legal, engineering, safety or other professional advice.