5 min read · 2026-11-11
Handing over a building to a new facilities team: a checklist
What to collect, check and hand over when a tower or compound changes facilities team: documents, keys, equipment, open jobs, contracts and residents.
A handover goes well when the outgoing team leaves four things in writing: what the building has (equipment, documents, keys), what is open (jobs, quotes, complaints), who does what (contracts, contacts, staff) and how it was run (rounds, schedules, limits). Collect them in the last month of the old contract, walk the building together, and load the lists into the new team's system on day one, so nothing lives only in someone's phone.
Why handovers lose information
The outgoing team knows where the pump room key is, which lift breaks in August and which resident always calls at night. None of that is in the contract. When they leave, the WhatsApp groups, the photos and the history leave with their phones. The new team then rediscovers every problem the hard way, and residents notice.
The handover checklist
Tick each line, note who handed it over and the date.
What the building has
- [ ] Floor plans and as-built drawings, if any.
- [ ] Equipment list: AC plant, pumps, tanks, generator, lifts, fire panel, with model, location and warranty end date.
- [ ] Service records and certificates for lifts, fire systems, tank cleaning and pest control, as your local rules require.
- [ ] Keys, access cards and codes, counted and labelled (plant rooms, roof, meters, tanks, stores).
- [ ] Spare parts store: what is in it, who holds the key.
- [ ] Meter readings on handover day, photographed.
What is open
- [ ] Every open job, with unit, fault, date reported and who was on it.
- [ ] Quotes waiting for approval, and the limits agreed with owners.
- [ ] Repeat faults: machines repaired several times recently.
- [ ] Open warranty claims with suppliers.
- [ ] Complaints or disputes with residents or owners still running.
Who does what
- [ ] Contracts with outside providers (lifts, fire, pest control, cleaning, security), with end dates and contact numbers, and how each is briefed (how to brief a contractor).
- [ ] Owner or association contacts, and how each wants to be reported to.
- [ ] Staff transferring to the new team, with their skills and certificates.
- [ ] The duty manager and out-of-hours arrangement.
How it was run
- [ ] Rounds: what was checked daily, weekly, monthly, and the last records (our building rounds checklist is a starting point if there were none).
- [ ] Response times promised to residents or in contracts.
- [ ] Spending limits per owner or building.
- [ ] Resident list per unit, with move-in dates (handled under your privacy rules).
Walk it together
On the last week, walk the building with someone from each side: plant rooms, roof, tanks, car park, every common area. Photograph each plant room and machine label, and agree in writing on anything broken at handover, so the new team is not blamed for it later.
Day one in the new system
The handover lists are only useful if they become the new team's records quickly.
In UnitVO, units can be added as a range ("floors 1 to 20, 8 per floor"), a list or a file. A CSV of units, residents, equipment or staff is checked row by row and shown before anything is saved, so missing fields and bad values are flagged first. See import and export.
Equipment goes into the equipment register with model, location and warranty date; a list can be imported from a file, and each machine gets a QR code on it, so its history builds from day one (equipment warranty tracking shows why the warranty date matters). A manager enters each open job from the old team as a new request for its unit, and dispatch gives it one owner.
Several buildings can sit in one account, each with its own units, team, response times and spending limit, and the audit log shows who changed what and when. See several properties. If the outgoing team ran on a sheet, UnitVO vs spreadsheets shows how to start from it.
Plan for your own exit too
A good handover is also a good test of your records. Ask: if we left tomorrow, could the next team take over from what we have written down? In UnitVO, the organisation's data can be exported at any time as CSV files in one ZIP.
When this is not for you
If the outgoing contractor's records are in a system they own and will not export, the checklist still applies, but you will be typing much of it; ask for exports in writing before the contract ends. Legal transfer of contracts, staff and deposits follows your contracts and local law; check them. If the building has more than 300 units, the listed plans stop there; write to the team. Read who UnitVO is not for and UnitVO for owner associations and facility teams.
What it costs
In the International region: Free (5 units, USD 0), Pro USD 49, Team USD 75 and Portfolio USD 199 a month, billed yearly. Each region has its own price list in its own currency; prices are before tax, and UAE customers pay 5 % VAT at checkout. Every plan has every feature, and setup is online, by calls and online demos. The 30-day trial has Team features for up to 50 units and needs no card. See pricing.
Questions and answers
When should a facilities handover start?
In the last month of the outgoing contract, with a joint walk of the building in the final week.
What is most often missing at handover?
The equipment history and the list of open jobs and quotes. Both usually live in the old team's phones and chats.
Can we import the old team's spreadsheets?
Yes, for units, residents, equipment and staff as CSV, each row checked and shown before it is saved.
Can we take our data out if we change again?
Yes. The whole organisation can be exported as CSV files in one ZIP at any time.