You Can't Hand Over What You Don't Know
Why facilities transitions fail on day one, and how to sequence them so nothing critical drops
By Rashid Masood Rizvi, Founder, AM Masons Advisory
Day three of a new facilities contract. 2am. A pipe lets go above the sixth floor.
The new vendor's night technician gets there quickly. The drawings show the isolation valve on level four. It was moved during a fit-out six years ago. The outgoing team knew that. Nobody wrote it down, and they handed back their keys on Friday.
By the time someone finds the valve, two floors of ceiling tiles are on the carpet.
The new vendor did what it was asked. The old vendor did what it was asked. The knowledge that mattered lived in a person, not in a record, and it left with the contract.
Emergencies are not scheduled. They don't wait for the transition plan to finish.
The premise: own your site, even if someone else runs it
Most companies that outsource facilities let the vendor hold the site knowledge. Where the critical plant is, how it's maintained, who to call, what the workarounds are. It works, quietly, for years.
Until the vendor changes. Then the company discovers it can't hand over what it never knew.
This isn't about distrusting vendors. A good vendor runs your site well. But the knowledge belongs to the building, not to the contract. You don't need to run the site yourself. You need to own the record of it: the asset register, the critical plant list, the SOPs, the emergency and business continuity plans, the access rights and the subcontracts. And someone on your side needs to own keeping them current, with a regular review that doesn't depend on the vendor deciding to raise it.
That's what governance means here. Not more meetings. A clear owner for the knowledge, and a rhythm for checking it.
A company that does this before a transition finds the transition is mostly logistics. A company that doesn't finds the transition is where every assumption gets tested at once.
A transition is two plans, run as one
A vendor change sits between two companies with very different incentives. The outgoing vendor is winding down. Its best people are often being redeployed, and its attention is moving to the next contract. The incoming vendor wants to impress, but it hasn't seen the site and doesn't know what it doesn't know.
So treat it as two plans. An offboarding plan for the vendor leaving, and an onboarding plan for the vendor arriving. Then run them as one programme, with one owner on your side.
The most useful thing you can do is bring the incoming vendor into the offboarding. Have its site lead and key technicians walk the building with the outgoing team before they leave. Plant rooms, risers, roofs, the odd corners only one technician ever visits. Ask the outgoing team what breaks, what they keep an eye on, and what they'd warn their replacement about. The incoming team learns more in that week than in its first three months alone.
Critical elements first
Not everything needs to be perfect on day one. Some things do. Sequence by consequence: what hurts people or stops the business if it fails at 2am.
Life safety and emergency response. The emergency response plan and business continuity plan should be updated with the new vendor's names, numbers and roles before day one, not after. Who responds to a fire alarm, a flood, a power loss or a lift entrapment, who makes the call to evacuate, who tells the business. Walk it through with the people who will actually be on shift.
Access. Every key, access card, alarm code, plant room lock, building management system login, maintenance system account and landlord portal. Grant the incoming team what it needs on day one and revoke the outgoing team's on the same day. Access that lingers is a security risk. Access that's missing turns a small fault into a long one.
Critical plant and the subcontracts behind it. Lifts, fire systems, generators, cooling and the specialist contractors who maintain them. Review each subcontract and decide deliberately whether to novate it or put a new one in place. Check warranty terms before you re-tender. Some equipment warranties depend on an approved service provider, and switching casually can void them. Whatever you decide, the contract should be live before day one. Otherwise the first lift breakdown lands in a gap where nobody has a contract to call.
Escalation contacts. Including the landlord's property manager and building engineer. The new team should know who owns base building plant before they need to.
Then validate, don't inherit
Once the critical elements are covered, the next job is validation. Not accepting the outgoing vendor's records, but checking them.
Walk the asset register. Registers drift. Equipment gets replaced, moved, added in a fit-out or removed without the record catching up. A register nobody has walked in years is a description of the past.
Test the SOPs in the new structure. An SOP written for the old team may reference roles, shift patterns or reporting lines that no longer exist. It can look complete on paper and fail the first time someone tries to follow it. Run the important ones with the new team and fix what breaks.
Check what's open. Outstanding work orders, deferred maintenance, known defects and anything promised to the business but not yet delivered. These should transfer as a list, not as a surprise.
Sign off last
Tie formal acceptance of the handover to validated deliverables, not to a date on the calendar. The asset register has been walked. The critical SOPs have been tested. Access has been reconciled. Subcontracts are live. The emergency plans have been exercised with the new team.
Then sign off. Once the outgoing team is gone, the chance to ask them anything goes with them.
Put simply
A vendor transition doesn't create gaps in your site knowledge. It reveals them.
Own the record of your site, even if someone else runs it. Run offboarding and onboarding as one programme, with the incoming vendor in the room before the outgoing one leaves. Secure the critical elements first, because emergencies are not scheduled. Validate everything else rather than inheriting it. And sign off only when the work is actually done.
If you're planning a facilities transition, I'm happy to walk you through how to sequence it for your site.
Frequently asked questions
What should be in place on day one of a new facilities contract?
Updated emergency response and business continuity plans, working access for the new team with the outgoing team's access revoked, live contracts for critical plant such as lifts, fire systems, generators and cooling, and clear escalation contacts including the landlord.
What is the difference between an offboarding plan and an onboarding plan?
An offboarding plan covers what the outgoing vendor must hand back and how its knowledge is captured before it leaves. An onboarding plan covers how the incoming vendor gets access, learns the site and takes over services. They work best run as a single programme with one owner on the client side.
Should the incoming vendor be involved before the contract starts?
Yes, wherever the contracts allow it. Having the incoming team walk the site with the outgoing team captures knowledge that is rarely written down, such as known faults, workarounds and equipment locations that differ from the drawings.
Should you novate subcontracts or put new ones in place?
It depends on each subcontract's performance, pricing and terms. Check warranty conditions first, because some equipment warranties require an approved service provider. Whichever route you choose, the contract should be live before the new vendor's first day.
How do you validate an asset register during a facilities transition?
Walk it. Check that each listed asset exists, is where the register says it is, and is in the condition recorded. Add anything missing and remove anything that no longer exists, so the incoming vendor starts from an accurate record.
Who should own site knowledge when facilities are outsourced?
The client. The vendor can maintain the records day to day, but someone on the client side should own the asset register, critical plant list, SOPs, emergency plans and access records, and review them regularly.
Rashid Masood Rizvi is the founder of AM Masons Advisory, an independent corporate real estate and workplace advisory firm. He spent 18 years leading global workplace services at a Fortune 50 company, where he was responsible for 180 sites and worked across more than 20 markets. AM Masons is vendor-agnostic and takes no vendor referral fees or commissions.