Agree a Defect Disposition Record at Mobilisation

Why this matters

Mobilisation surveys often produce a long defect list and an equally long debate about responsibility. The urgent operational question is different: what must happen now to keep people, service and assets safe while ownership is resolved? A defect disposition record separates the immediate risk decision from the later commercial allocation.

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

Identify the asset and condition with enough precision for another person to find and verify it. The practical consequence is that a reported result must be interpreted in the operating context that produced it.

Record consequence, interim control and inspection frequency rather than relying on a red status alone. This changes the management question from whether an activity occurred to whether the agreed condition was achieved and can be demonstrated.

Distinguish maintenance execution, lifecycle replacement, design deficiency and client-authorised risk acceptance. The control should create enough traceability for another competent reviewer to reproduce the decision without relying on memory.

Preserve the disputed commercial position without allowing disagreement to suspend necessary mitigation.

Where evidence is incomplete, the honest result is an exception with an owner—not a confident conclusion assembled from assumptions.

Figure 1. The obligation-to-proof model Original Osmos Global conceptual framework, 2026. No measured dataset. Prepared 1 September 2026.

What this means: A reported result becomes decision-ready only when the proof and acceptance route are explicit.

The practical tool

1. Verify the defect jointly and record data confidence. Write the purpose and boundary first so the record does not become a generic administrative form. 2. Assess immediate safety, compliance, continuity and asset consequences. Use information already created by operations where it is reliable, and identify any new collection burden explicitly. 3. Choose mitigation, maintenance, investigation, capital action or monitored acceptance. Give the action to a named role with authority to resolve the exception or escalate it. 4. Assign operational and commercial owners separately. Test the step on a difficult real example before making it part of routine governance. 5. Set the next verification date and evidence required to close the disposition. Retain the outcome and the evidence used so that later review can distinguish improvement from a change in reporting.

Illustrative application

A pump is operational but has recurring seal leakage and no reliable maintenance history. The provider disputes that replacement belongs in its fixed-price scope. The disposition record can still require containment, inspection and a replacement decision by a named date while preserving the contract question for commercial resolution. 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 verify the defect jointly and record data confidence 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 asset baseline 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

A portfolio defect register should preserve the local condition rather than replace it with a generic label.

Similar assets can have different consequences, access restrictions and available redundancy. For each inherited issue, record what is known, what remains untested and what evidence would change the disposition. An uncertain condition should not be presented as a confirmed defect merely to transfer responsibility.

In a leased GCC workplace, the immediate mitigation may belong to the FM provider while investigation or replacement depends on the landlord or client. Name both routes. The record should show the operating restriction, who accepted it and when it must be reconsidered. A disputed cost allocation can remain open without leaving the day-to-day control ambiguous.

Revisit the disposition after an incident, material change in use or failure of the temporary control. Avoid automatically carrying mobilisation exceptions into successive reporting periods. Equally, do not close an issue merely because it has been transferred to a capital plan. Closure should identify the evidence of correction, or clearly document the authorised long-term treatment and the continuing monitoring obligation. The register is a decision history, not simply a list of liabilities.

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

FM leaders should prevent unresolved ownership from becoming unmanaged risk. Finance and capital teams need visibility where maintenance cannot economically restore asset condition. Providers should not be held accountable for unknown inherited conditions without a documented baseline and discovery mechanism.

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 disposition record does not determine legal liability or technical fitness by itself. Safety-critical decisions require competent assessment, and the register must not become a holding area for actions that are continually deferred. 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.