Scope boundaries in a hospital FM system: maintenance only?
Northvale Health Group operates six hospitals (1,420 beds) and runs its facility management (FM) system from a single estates directorate. The scope statement in its FM manual reads: 'Provision of building maintenance and cleaning at the six Northvale hospital sites.' Clinical engineering, IT and networks, security, catering, space planning and capital projects are managed by other directorates and are listed as exclusions 'for clarity'. The FM director tells you during a certification audit that ISO 41001 is essentially a maintenance management standard and that the exclusion list shows what his directorate does not do. Symptoms are visible: a new outpatient wing opened four months late because room allocation was decided by the capital projects board with no FM involvement; cleaning and maintenance teams regularly block each other over room turnaround; energy spend rose 11% year on year while the energy contract sits with Finance; and there is no record of which interested parties were considered when the scope was set.
1. The FM director argues that the scope statement and exclusion list are sufficient. Assess the defensibility of that position and describe what you would examine to conclude against clause 4.
Read the worked answer
The exclusion list is not automatically wrong. ISO 41001 does not dictate which services an organisation must deliver, and clause 4.3 requires the organisation to determine the boundaries and applicability of the FM system and to make the scope available as documented information. Clauses 4.1 and 4.2 require that this determination be made against the organisation's context and the needs and expectations of interested parties. So the test is not 'are there exclusions?' but 'was the boundary drawn deliberately, on the basis of context and interested-party requirements, and does the resulting system still deliver its intended outcomes?'
ISO 41011 defines FM as the organisational function which integrates people, place and process within the built environment to improve quality of life and the productivity of the core business. A scope limited to maintenance and cleaning removes most of the 'place' and 'process' integration, and the symptoms show the consequence: no FM input to space allocation, cross-service conflict over room turnaround, and no energy accountability despite an 11% cost rise.
Lines of enquiry: the documented scope and its approval; records showing how context and interested parties were analysed; interface agreements or service level agreements with security, IT, capital projects and Finance; the post-project review of the late wing; KPI ownership for energy; and interviews with the directors holding the excluded activities. The judgement to make is whether the interfaces are identified and controlled. If they are, a narrower scope may be defensible. If they are not, the system cannot achieve its intended outcomes, and a nonconformity against 4.3, supported by 4.1 and 4.2, is the better-grounded conclusion than a general criticism of scope.
2. The FM director states that energy performance cannot be relevant to the audit because the utilities contract is managed by Finance. How do you deal with that position, and what would turn it into a finding?
Read the worked answer
I would not accept a scope label as a reason to stop testing. The question is not who signs the utility contract, but whether the FM system identifies energy as a facility performance issue, assesses the associated risk and controls the interface with the function that does hold the contract.
Clause 6.1 requires the organisation to address risks and opportunities relevant to the FM system's intended outcomes. Clause 8.1 requires operational planning and control, including control of outsourced and interfaced processes. Clause 9.1 requires monitoring, measurement, analysis and evaluation of FM performance. If energy consumption affects cost, compliance, resilience or client requirements, it is a legitimate subject for the FM system even where procurement sits elsewhere.
I would interview the Finance manager responsible for the utility contract, look for joint reporting or review of consumption data, and check whether the FM risk register or objectives mention energy. The evidence decides the outcome. If there is a documented interface, shared data and periodic joint review, the exclusion is being managed and I would note it as an observation at most. If no interface exists, no energy data reaches the FM review, and the risk is unassessed, I would raise a nonconformity against 8.1 or 6.1 - not against 'excluded activity' in the abstract, but against the failure to control an interface on which the FM system's outcomes depend.
3. At the closing meeting the estates director says the late wing and the cleaning/maintenance clashes are 'operational issues, not system issues'. Evaluate that distinction and explain how you would conclude.
Read the worked answer
The distinction is a common deflection and should be tested rather than accepted or dismissed. In a management system audit, operational symptoms are precisely the evidence from which system effectiveness is inferred. Clause 8.1 requires planned and controlled operation of FM processes; clause 9.1 requires performance to be monitored and evaluated; clause 10.2 requires nonconformities to be corrected and the effectiveness of corrective action reviewed; clause 10.3 requires continual improvement. A recurring clash that the organisation knows about and has not resolved is evidence about those requirements.
However, the reverse error is also real: not every operational problem is a nonconformity. ISO 41001 does not demand zero defects, and a one-off delay can be consistent with a functioning system if it was detected, escalated, corrected and reviewed. The auditor's task is to trace each symptom to a requirement and to evidence.
So I would ask: was the late wing delay recorded as a nonconformity? Was a corrective action raised and its effectiveness checked? Do the room-turnaround clashes appear in performance data, and did anyone analyse them? If the answer is that the issues never entered the monitoring, corrective action or improvement processes, the system is not detecting its own performance problems, and I would raise findings against 9.1 and 10.2 rather than against 'operations'. If the issues were captured and acted on, I would report them as evidence of a working system, with an observation about the pace of improvement.