Handing a building over to a facility management provider

A completed building changes hands twice. First from the contractor to the developer, when the completion certificate is issued. Then from the developer to whoever will run the place afterwards: an Owners Committee's appointed manager, a Master Developer's contracted operator, or a facility management company brought in for exactly this purpose. Dubai Law No. (6) of 2019 Concerning Ownership of Jointly Owned Real Property calls that second party a Management Entity, sorts the project into a category, and lists what it must do once it holds the keys. It says far less about what it must be given on the way in.

Six things move, or should move, at that point: the asset register, the operation and maintenance manuals, the outstanding warranties, the snag list, the utility accounts, and a mobilisation period for the new manager to get up to speed. Only two of those six carry a number fixed by Dubai statute. The rest are professional practice, filled in by contract, worth naming precisely because the law leaves them unnamed.

Three categories, three routes to a manager

Article 18 of Law No. (6) of 2019 sorts every project into one of three categories for managing its Common Parts. A Major Project leaves the Developer responsible for management, operation, maintenance and repair of Common Parts and Utility Services, with an Owners Committee of RERA-selected owners sitting alongside it. A Hotel Project has its Common Parts outsourced to a Hotel Project Management Company under rules the Director General approves. Everything else, Category 3, gets a specialised management company that RERA itself selects and contracts.

The Developer in a Major Project is not stuck running the building forever. Article 18(c) lets it outsource that duty to a Management Company, for fees both sides agree, provided RERA approves the arrangement. That is the route most Dubai facility management contracts actually travel: a commercial handover the Developer chooses, checked by RERA rather than forced by it.

What the manager is on the hook for from day one

Article 34 requires the Management Entity to conclude contracts with maintenance, security, cleaning and insurance companies, and to report on that work to RERA every six months. Article 41 goes further on insurance. The Management Entity must insure the property against fire, damage or destruction, naming itself as beneficiary, and separately insure against liability for injury to occupants or third parties.

That cannot be done by guesswork. A manager cannot insure a chiller plant it cannot describe, or price a lift maintenance contract it cannot count. Law No. (6) of 2019 never uses the words asset register. It creates the obligations that make one necessary and leaves the document to whoever is left holding the building.

The paperwork that is named, and the paperwork that is not

Some of the handover package does have a legal home. Article 6 requires the Developer, once it holds a completion certificate, to file the Plans, the Master Community Declaration, the Statute and the Building Management Regulation with the Dubai Land Department within sixty days, extendable by thirty more where DLD accepts the reasons. Those four documents then form part of the title deed, and DLD keeps an original of each. Miss the deadline, and DLD can appoint another party to file them, at the Developer's expense.

Operation and maintenance manuals sit outside that list entirely. No provision of the Law names such a document, and the Dubai Development Authority's checklist for a Building Completion Certificate does not either; it asks for a Civil Defence certificate, sewerage approval, a compliance certificate from the main consultant, and confirmation that approved drawings are on site. What it confirms is timing. Those approvals, and the manufacturer's own literature for the lifts, generators, fire pumps and chillers being signed off, exist at completion, while the installing contractor is still reachable. Ask for it during mobilisation and it already exists somewhere. Ask eighteen months later, and someone has to reconstruct it from memory.

The register DLD keeps, and the one no authority keeps

Article 4 gives Dubai one statutory register for jointly owned property, held by DLD. It records land plots, units and owners, Owners Committee members, Building Management Regulations, Plans, and the details of Management Entities and their management contracts. It does not record a single lift, chiller, fire pump or generator. That inventory, an asset register in the ordinary sense, is nobody's statutory product. It is worth little if it moves on as a conversation rather than a spreadsheet: serial numbers, installation dates, warranty end dates, one line per asset.

Warranties belong to the building, not to whoever is managing it

Article 40 fixes two liability periods on the original Developer, and both run regardless of who is managing the building when a defect turns up. Structural defects carry a ten-year liability from the completion certificate. Mechanical, electrical, sanitary and sewerage installations carry one year from unit handover, or from the completion certificate if the owner never takes possession. A facility manager who does not know which of those two dates applies to a failed pump cannot tell an owner whether the Developer still owes anything.

Article 40(d) closes an obvious loophole. Any agreement made after the Law came into force that contradicts these periods is void. The dates cannot be negotiated away in a management contract.

The snag list moves from the flat to the plant room

A unit owner's snag list covers paint, tiling and door alignment. The equivalent exercise on Common Parts, the one a facility manager inherits, covers the pumps, the fire alarm panel, the generator and the building management system. Nothing in the Law prescribes that inspection either. But the one-year clock on installations in Article 40(b) runs from the first unit handover, not from whenever the incoming manager walks the plant rooms. A defect logged in month eleven is still the Developer's to fix. One found in month thirteen, on a shared chiller nobody snagged, usually is not.

Utility accounts move too, and not always together

Dubai Electricity and Water Authority runs a Transfer of Electricity/Water, or Move-to, service that shifts an account between premises through a digital link with the Dubai Land Department, working through real estate management companies once an Ejari tenancy contract has been issued, and it moves the security deposit from the old account to the new one in the same transaction. Before an account closes, DEWA issues a Clearance Certificate once outstanding bills are settled, valid for one month from the date it is issued.

That machinery is built around a tenancy changing hands, one unit at a time. It says nothing about the building's own accounts, the lobby lighting, the irrigation, the shared pumps, moving from the Developer's name into the Owners Association's or the facility manager's. Nothing published by DEWA sets that step out as its own procedure. It gets handled case by case, which is why it is worth confirming in writing, before mobilisation, whose name sits on every common-area meter.

The only mobilisation clock the Law actually sets

For an ordinary handover, a Developer outsourcing under Article 18(c) or a Master Developer appointing its first manager under Article 19, Dubai legislation sets no mobilisation deadline. How many weeks a new provider gets to review documents, walk the site and take over service contracts is whatever the management agreement says.

There is one handover the Law does time, and it is narrower. Where RERA decides a Category 3 management company is incompetent, Article 38 sets four steps: notify the Owners Committee and seek its opinion; serve a written warning, answerable within fourteen days; have a certified audit firm check the Service Charges account against the RERA-approved budget; then set a deadline to hand over.

Thirty days. That is the only mobilisation figure the Law itself sets, and it applies to a company being removed for cause, not to a building completing on schedule.

A Management Entity also stands behind its own work. Article 36 requires it to hold a bank guarantee, in favour of DLD and in an amount DLD sets, against damage its own negligence causes to Common Parts. That has nothing to do with the Developer's defects liability under Article 40. It secures the manager's conduct, not the Developer's.

Before mobilisation starts, ask the outgoing party for two things in writing: the completion certificate, with its date, and the current name on every common-area DEWA account. Everything else in a handover can be renegotiated later. Those two facts cannot be reconstructed once the developer's team has moved to the next project.