Turn the Monthly FM Review Into a Decision Record

Why this matters

Monthly FM reviews can consume substantial time while producing little more than a presentation history.

The same metrics reappear, actions remain open and important trade-offs move to separate conversations. A decision record changes the unit of governance from “topics discussed” to “exceptions resolved or deliberately accepted”.

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 Australian National Audit Office published Auditor-General Report No. 25 of 2025–26 on 18 March 2026.

It tested 14 engagements in a diplomatic Security Enhancement Program using records, contract data and procurement information. Four achieved the original scope, timeframe and estimated cost together. The sample is a bounded audit case involving mixed works and services, not an FM-sector benchmark. [2,

Osmos Global analysis

Begin with material exceptions and decisions required, not a tour of every green measure. The practical consequence is that a reported result must be interpreted in the operating context that produced it.

Show the evidence, uncertainty and business consequence behind each exception. This changes the management question from whether an activity occurred to whether the agreed condition was achieved and can be demonstrated.

Record the decision-maker, chosen action, due date and verification test. The control should create enough traceability for another competent reviewer to reproduce the decision without relying on memory.

Carry unresolved items forward with ageing and escalation rather than rewriting the narrative each month.

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

Figure 1. Keep the contract baseline traceable Original Osmos Global conceptual framework, 2026. No empirical measurements. Prepared 1 September 2026.

What this means: An authorised change is incomplete until evidence and reporting reflect the new baseline.

The practical tool

1. Issue a concise exception pack before the meeting. Write the purpose and boundary first so the record does not become a generic administrative form. 2. Validate which decisions and authorities are required. Use information already created by operations where it is reliable, and identify any new collection burden explicitly. 3. Record options, assumptions and the decision taken. Give the action to a named role with authority to resolve the exception or escalate it. 4. Track implementation and evidence of effect. Test the step on a difficult real example before making it part of routine governance. 5. Close only after the agreed verification test is met. Retain the outcome and the evidence used so that later review can distinguish improvement from a change in reporting.

Illustrative application

A recurring lift fault appears each month with improving response times. The review records good SLA performance but no decision on component replacement. A decision-led agenda would present recurrence, disruption, repair history, options and capital implication, then record the authorised path and verification date. 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 issue a concise exception pack before the meeting 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 performance governance 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 review should distinguish decisions that belong locally from those requiring central approval. Site teams may resolve routine operational matters, while changes in budget, contractual scope or accepted risk require different authority. The meeting pack should identify that distinction before discussion so material issues are not repeatedly deferred to people who are not present.

For GCC leadership, summarise the business consequence and the choice required, then link to the supporting record. A long chronology can obscure the decision. State the available options, significant uncertainty and the consequence of waiting. Where no decision is made, record why, who must supply the missing information and when the matter returns. Silence should not be interpreted as acceptance.

Begin the next meeting by checking a small number of prior decisions against their verification tests. An action marked complete may have produced a document without changing the operating condition. Preserve disagreements and the basis of the chosen action so a new manager can understand it later. The decision record should be concise enough to use, but complete enough to distinguish a deliberate trade-off from an issue that simply disappeared from the agenda.

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

Senior leaders should attend for decisions that require their authority, not for ceremonial review. Providers should bring evidence and options rather than defensive explanations. Finance and procurement should see when apparent savings create backlog or repeated operating cost. 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

Not every operational issue belongs at the senior review. Poor filtering can overload decision-makers, while excessive filtering can hide risk. Define escalation thresholds and allow urgent matters to bypass the monthly cycle. 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] Australian National Audit Office. Procurement and Contract Management by the Department of Foreign Affairs and Trade for its Security Enhancement Program. Australian National Audit Office, 2026-03-18. Auditor-General Report No.25 of 2025–26. Summary paras.11, 19; audit scope/method paras.1.17–1.18; recommendation6; chapter4. Accessed 1 September 2026. https://www.anao.gov.au/work/performance-audit/procurement-and-contract-management-by-dfat-for-security-enhancement-program

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.