Haverstock Logistics - 138 Findings and Nine Months
Haverstock Logistics runs four distribution centres (DC1–DC4) with 61,000 pallet positions and an associated fleet operation. FM is delivered by a single integrated provider under a five-year contract, overseen by an in-house team of three. In January the board committed to ISO 41001 certification within nine months because a major retail client's tender in November awards 20% of the score to 'certified FM'. A consultant's gap analysis returned 138 findings across all clauses and produced a 40-document toolkit, including an FM manual, which the operations director has asked the team to 'implement by June'. DC4 is leased with 14 months left on the lease and a board decision pending on whether to exit; it currently handles 18% of throughput. The head of FM wants to include all four DCs to make the certificate look stronger. No FM objectives exist, and the provider's monthly report is the only performance data available.
1. Advise on whether DC4 should be inside the certification scope, and how to document the decision.
Read the worked answer
Clause 4.3 requires the organisation to determine the boundaries and applicability of the FM system, informed by the issues in 4.1 and the requirements of interested parties in 4.2. The test is not 'which answer looks better on a tender' but 'can the system genuinely be applied and controlled across these boundaries'.
Arguments for inclusion: DC4 is 18% of throughput, it is operationally significant, and excluding it creates an artificial boundary that the system's interfaces (transport, labour, stock cover during any closure) would still have to manage. Arguments against: the board may exit within 14 months, so the scope could become partly inapplicable during the certification cycle, forcing a scope change and certificate amendment, and the system would be applied to a site whose future is undecided.
A defensible resolution: include DC4 while it operates, and state the scope as activities and FM services rather than as a fixed list of buildings, with the site referenced in the scope description. If the site closes or transfers, handle it through the system's change management and inform the certification body, which will assess whether scope amendment is needed. If the board decides to exclude it now, the exclusion must be justified in the scope statement and the interfaces (shared fleet, labour pooling, emergency cover) defined - clause 4.3 does not permit excluding something that undermines the system's ability to achieve its intended outcomes.
Record the rationale, the decision-maker and the date, so the auditor sees a reasoned boundary rather than an omission.
2. With 138 findings, 40 consultant documents and a nine-month window, how should the programme be sequenced?
Read the worked answer
138 findings is a gap register, not a plan. Convert it into a risk-based programme using 6.1: for each finding, score the consequence if unaddressed (statutory breach, safety, service failure to the retail client, tender disqualification) against the effort and dependency to fix it. That typically produces four groups:
- Foundational decisions that everything else depends on - context (4.1), interested parties (4.2), scope (4.3), FM policy (5.2), the demand/supply operating model, and roles and authorities (5.3). Do these first; they determine what the rest of the documents must say.
- Risks, opportunities and objectives (6.1, 6.2) - including the risk of the DC4 decision and dependence on a single provider.
- Operational control (8.1) - service specification, contract management, escalation, contractor control, change control. This is where the tender evidence will actually come from.
- Evaluation and improvement (9.1–9.3, 10) - indicators, audit programme, management review, corrective action.
Treat the 40-document toolkit with suspicion. Clause 7.5 requires documented information only where the standard requires it or where the organisation determines it is necessary for the system's effectiveness. Forty documents written by someone else is a maintenance burden, and a system nobody uses fails at stage 2. Keep what the operation needs, delete the rest, and let the in-house team own each document.
Set gate reviews at months 3, 5 and 7, and start internal audit no later than month 6 so findings can be corrected before the certification audit.
3. The CEO has signed the policy but attends no implementation meetings. What evidence of leadership would an auditor look for, and how should the head of FM secure it?
Read the worked answer
Clause 5.1 requires top management to demonstrate leadership and commitment by taking accountability for the system's effectiveness, ensuring the policy and objectives are compatible with strategic direction and context, integrating the system into business processes, ensuring resources, communicating importance, ensuring the system achieves its intended results, directing and supporting people, promoting improvement, and supporting other management roles in their areas of responsibility.
A signed policy is evidence of one bullet, not of leadership. An auditor will look for decisions traceable to top management: the FM objectives appearing in the board pack; resource approvals (staff, CAFM data, the permit system); minutes where the CEO challenged FM performance; a management review at which decisions were made and resourced; and whether the CEO can explain, unprompted, how FM risk affects the retail tender and the DC4 decision.
The head of FM's practical move is to change the forum rather than add one. Put a standing FM item on the monthly executive meeting with three inputs - performance against objectives, top FM risks, and decisions required. That creates the record, forces 9.3 inputs to be produced monthly rather than annually, and makes the CEO's accountability real. Also secure a written statement of delegated authority under 5.3 so the FM lead can act on behalf of top management.
If leadership commitment remains nominal at month 4, the honest recommendation is to delay certification rather than manufacture evidence; an auditor interviewing the CEO will detect a system that exists only on paper.