Build an Evidence Schedule Into the FM Tender

Why this matters

FM tenders describe activities, frequencies and reports in detail, yet often leave evidence until mobilisation.

That creates a predictable conflict: the client expects proof that can support assurance and decisions, while the provider prices the work using whatever records its operating model normally creates. An evidence schedule closes this gap before bidders commit to scope, systems and resources.

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,

summary paras. 11, 19; paras. 1.17–1.18]

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. [3, pp. 108–114]

Osmos Global analysis

Treat evidence as part of the deliverable rather than an administrative by-product. The practical consequence is that a reported result must be interpreted in the operating context that produced it.

Specify the decision the evidence must support, because a completion record, compliance record and capital-planning record require different content. This changes the management question from whether an activity occurred to whether the agreed condition was achieved and can be demonstrated.

Keep evidence requirements proportionate. Requiring photographs for every routine task may create volume without assurance. The control should create enough traceability for another competent reviewer to reproduce the decision without relying on memory.

Define ownership, access, retention and export so that verification does not depend on one supplier platform or individual. 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. List material obligations and the consequence of non-delivery. Write the purpose and boundary first so the record does not become a generic administrative form. 2. Define the minimum acceptable evidence for each obligation. Use information already created by operations where it is reliable, and identify any new collection burden explicitly. 3. Name the evidence creator, custodian and acceptance authority. Give the action to a named role with authority to resolve the exception or escalate it. 4. Set submission timing, format, retention and access rules. Test the step on a difficult real example before making it part of routine governance. 5. Ask bidders to price and demonstrate the proposed evidence workflow. Retain the outcome and the evidence used so that later review can distinguish improvement from a change in reporting.

Illustrative application

A tender requires monthly inspection of fire doors but says nothing about asset identity, exceptions or corrective-action linkage. One bidder prices a checklist total; another prices tagged asset-level records. Their prices are not comparable because the evidence obligation differs. Publishing the evidence schedule makes the commercial comparison more honest. 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 list material obligations and the consequence of non-delivery 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 tender design 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 evidence schedule should distinguish common fields from service-specific proof. Asset identifier, event date, responsible role and exception status may be common; the technical acceptance evidence should follow the obligation. Asking every provider for identical files can conceal important differences between cleaning, engineering, security and workplace support. The schedule should therefore explain why each record exists and who will use it.

For GCC tenders, test the exchange between the provider’s system and the client’s retained records before assuming that an export clause will work. Ask bidders to demonstrate a small, anonymised example containing an open action and its history, not just a polished completed task. Evaluate whether identifiers, attachments and status changes remain intelligible after export. This is a capability test, not a request for another client’s confidential data.

Separate mandatory evidence from optional analytical enhancements. Bidders should price the mandatory baseline consistently, while additional dashboards or predictive features can be assessed as alternatives. If the client later adds a substantial reporting burden, handle it through the applicable change process. The tender should make assurance affordable and operationally useful, rather than reward a promise of unlimited reporting that neither party can sustain.

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

Procurement should evaluate evidence capability alongside technical method and price. FM should avoid specifying data that nobody will review or act upon. IT and security should confirm that evidence exchange, retention and access are workable. 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

The schedule is not a substitute for clear scope or professional specification. It can also become bureaucratic if every low-risk task receives the same proof burden. Apply risk tiers and explain where sampling is acceptable. 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 [3] 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.