Switching Building Management Companies in 90 Days — Documents, Continuity and Knowledge

Replacing a management company looks on paper like a simple contractual matter — you end things with one and start with another. In practice, this is one of the most dangerous moments in the life of an office building. All the operational knowledge, the maintenance history, the statutory approvals and the contacts sit with the party you are leaving — and if the transition is not managed properly, they simply vanish. I wrote this guide after taking over buildings that the previous management company had left "in a single day" — and I can tell you what you find in the field when there is no orderly handover. The goal: to get you through these 90 days as a controlled process, not a gamble.

Why the Transition Itself Is the Point of Failure

In Israel's construction culture, it is customary to act only when something forces us to — a regulator, an inspection, a failure. Switching between management companies is exactly the moment when "nothing is forcing anything": the outgoing management company is no longer really committed, the new one has not yet had time to get to know the building, and the owner assumes everything will "work itself out." This is a management vacuum.

During this period, statutory inspections are postponed because no one scheduled them, approvals expire without anyone noticing, and open defects from previous inspections stay open because the knowledge of them was never passed on. I saw a building that discovered — six weeks after switching management companies — that its fire-suppression approval had expired three weeks earlier. There was no one to schedule its renewal, and both sides assumed the "other" was handling it.

The exposure is not theoretical. If, during the transition period, an incident occurs — an elevator failure, a fire-suppression system failure, a power outage — and it turns out that an inspection had expired or a known defect was not addressed, the liability falls on the building owner, regardless of which management company "was supposed to" handle it. Israeli Standard (SI) 1525 for building maintenance requires a continuous, documented maintenance log — and continuity should not break just because a vendor was replaced.

What Really Transfers in a Handover — Three Layers

A common mistake is to think that a handover is the transfer of a folder of documents. In practice there are three separate layers, and each requires different handling:

• Documents and digital assets: the building file, valid statutory approvals, vendor contracts, maintenance logs, as-made drawings, manufacturer warranties and system manuals.
• Access and operational control: passwords for building management systems (BMS), cameras, access control, the CMMS if one exists, vendor accounts and access codes for equipment rooms.
• Tacit knowledge: what "behaves strangely" in the building, which vendor is reliable and which is not, who the sensitive tenants are, where a recurring fault hides, and which equipment is waiting for budget.

The third layer is the one that is almost always lost. You can compel the transfer of documents in a contract, but tacit knowledge transfers only if you deliberately plan an overlap between the outgoing and incoming teams. Without such an overlap, the new company "discovers" the building anew — the hard way, through failures.

A field example: I once took over a building where the air conditioning on the 7th floor "worked," but only if you remembered to perform a manual restart on the unit every morning. That was the knowledge of one technician. He left with the previous company, and a week after the transition, tenants of that floor came to me with complaints about heat — without anyone knowing the cause.

The 90-Day Plan — Three Stages

Why 90 days? Because it is the minimum period that allows a real overlap without staying too long in a double-cost situation. I divide it into three stages of about 30 days.

Stage 1 (Days 1–30): Mapping and Situational Assessment

Before you transfer anything, you need to know what exists. In this stage the incoming company (or the owner) performs a full inventory:

• A list of all systems — their age, condition and date of last inspection
• A list of all statutory approvals and their expiry dates
• A list of all active vendors, the type of agreement and renewal dates
• A list of open defects — findings from inspections that have not yet been closed

This is the "snapshot" of the starting point. Without such a snapshot, it is impossible to even know what is missing after the transition — and impossible to assign responsibility for gaps that are discovered.

Stage 2 (Days 31–60): Controlled Transfer and Overlap

This is the heart of the transition. The outgoing company transfers all the documents and access, and in parallel an active overlap takes place: joint walkthroughs of the building, meetings with the outgoing team, and an orderly transfer of "field knowledge." This is also where a cross-check is performed — do the documents received match the inventory from Stage 1?

An example of a red flag: if the field file was submitted with drawings from 2019 and systems have been renovated since, the data is out of date. This must be reflected in the handover checklist as an open item that the outgoing company is responsible for closing, not passed on to the incoming company as "your problem."

Stage 3 (Days 61–90): Stabilization and Control

The new company is already operating, but still in a heightened state of attention. Here you close all the defects identified during the transition, reschedule all the statutory inspections for the coming year, and set up the monthly control board. At the end of the 90 days you should have a building with a full file, a budgeted schedule for the year, and zero expired approvals.

The Handover Checklist — What to Demand from the Outgoing Company

This is the part you must not give up on. Every item that is not received in writing and in full is a gap you will pay for later. Demand, in an orderly and documented form:

• A full building file: as-made drawings, building permits, an up-to-date field file and equipment files for the systems.
• All valid statutory approvals: fire-suppression approval (Fire and Rescue Authority), licensed-inspector elevator inspections under the occupational safety regulations, grounding inspection, fire-detection approvals, air-conditioning approvals — with expiry dates for all of them.
• Maintenance logs: the service history of every system, including recurring faults and treatments performed.
• A list of open defects: every inspection finding that was not closed — this is critical, because an unknown defect is a defect that will not be addressed.
• Vendor contracts and contacts: every active vendor, the contract terms, the service level agreement (SLA), renewal dates and contact details.
• Access and digital control: passwords and access for every system — BMS, cameras, access control, CMMS and vendor accounts.
• Tenant data and accounts: active leases, collection status and any open obligation toward a tenant.
• Building-specific knowledge: a map of the service rooms, access codes for restricted areas, emergency procedures and contacts for incidents.

The guiding rule: if it did not transfer in writing — it did not transfer. Relying on "they know and will pass it on" is exactly where knowledge falls between the cracks.

Maintenance Continuity — How Not to Fall Between the Cracks

The critical systems do not know that a management company is being replaced, and they will continue to require inspections precisely on schedule. The greatest risk in a transition is a statutory inspection whose expiry date falls within the vacuum period.

Imagine an elevator whose licensed-inspector inspection expires on day 40 of the transition. The occupational safety regulations (elevators) require a periodic inspection without exception — if no one scheduled it, the elevator is operating unlawfully, and the building owner is exposed to full criminal and civil liability, regardless of who "was supposed to" handle it. This is not a theoretical possibility — this is what happens when there is no agreed expiry table with clear owners for every row.

That is why the first step in Stage 2 is mapping all the expiry dates for the coming 12 months, and explicitly determining who is responsible for each inspection. Inspections that expire in the first 90 days get a clear owner and are scheduled immediately. At this point it is very helpful to work against the annual preventive maintenance checklist — it provides the framework of inspections and frequencies to which you should map the specific building's expiry dates.

Another point: don't assume the outgoing company will deliberately neglect. Usually the problem is not malice but a disconnect of motivation — the moment they know they are leaving, the urgency drops. That is why it is better to anchor in the termination contract that the outgoing company is responsible for every inspection due before the official disconnection date, and not before the termination notice.

Knowledge Transfer — The Layer You Cannot Write into a Contract

You can demand documents, but you cannot demand "remember to tell us that the left chiller vibrates on startup." That knowledge transfers only through human contact. The only way I have found that works is a physical overlap: at least one joint handover walkthrough of the building, in which the outgoing team hands over the building system by system, room by room, and explains the "character" of each system. Such a walkthrough reveals more in two hours than ten documents reveal.

In complex buildings, with multiple tenants and systems, the overlap is even more important. The dynamics between the tenants, the history of recurring complaints, the unwritten agreements — all of these are critical operational knowledge. I have expanded on this complexity in the challenges of managing a multi-tenant building. The more complex the building, the greater the need to document this knowledge during the overlap — and not settle for a verbal transfer that will be forgotten.

A tool I recommend: an "overlap log" — a shared document built during the handover walkthroughs, in which every field finding is recorded in real time, including camera photos and direct observations. It turns the informal knowledge into documentation that can be verified.

A Digital Building File — The Insurance Against a Painful Transition

Everything I have described so far is many times easier when the building is managed in an orderly digital building file. When all the approvals, logs, contracts and expiry dates sit in one structured system — the handover turns from "digging in the archive" into an orderly export. And vice versa: a building managed in physical binders and in the memory of a single manager is a building in which every transition is a crisis.

This is one of the reasons I recommend that owners choose a management company that works with a transparent digital file — not only because of the ongoing advantage, but because that is exactly what protects you the day you want to replace it. A digital file belongs to the building, not to the company. When these considerations already come up at the stage of choosing the company, it is worth reading how to choose a management company — file transparency and handover capability are criteria you should check in advance, not in hindsight.

The Common Mistakes in a Transition — and How to Avoid Them

• A "single-day" transition without an overlap: immediate disconnection with no overlap period. The tacit knowledge vanishes, and the new company learns through failures — usually at the tenants' expense.
• Relying on a verbal handover: "it was agreed they would pass it on." Anything not in writing and not verified — does not exist. Demand documentation and verify it against the inventory.
• Ignoring expiry dates: a statutory inspection that expires in the vacuum period with no one responsible for it — the most concrete danger in a transition.
• Not obtaining a list of open defects: a known defect that was not passed on becomes a "new" defect discovered only when something breaks.
• Forgetting digital access: documents transferred, but the BMS password stayed with the outgoing company. Partial control is no control — and restoring access after disconnection can take weeks.
• Transitioning at bad timing: a transition planned to coincide with an annual fire inspection, a concentrated renewal of approvals, or a peak season (summer, holidays) — unnecessary pressure on both sides.
• Closing the account before the handover is complete: the moment you have settled the financial account with the outgoing company, your leverage is zero. Keep it until every item in the checklist has been verified.

Contractual Aspects Worth Anchoring in Advance

Much of the pain of a transition can be prevented back in the original management contract. When you sign with a company — even if you are happy with it — anchor exit clauses that protect the building:

• An obligation of an orderly handover within a defined period (recommended: no less than 60 days)
• The building's ownership of all documents, digital data and approvals — from the start of the engagement
• An obligation of overlap with the incoming party — at least one documented handover walkthrough
• Continuation of the outgoing company's responsibility for every inspection due before the official disconnection date
• A mechanism to withhold final payment until the handover is complete and confirmed

The distinction between facility management (FM) and property management (PM) is important here, because the scope of the handover differs from model to model — whoever also maintains the physical systems holds more operational knowledge that needs to transfer, and this should be anchored in a separate checklist for each model.

At Domera Hub we take over buildings from previous management companies with a structured 90-day handover plan, and manage them in a digital building file that always belongs to the building. See comprehensive property management or get a quote for a review of your handover situation.