Building Maintenance Contract Dubai

Everything else in a building contract is downstream of one document, and a surprising number of buildings do not have it.

An asset register lists every item of plant the association is responsible for: each pump with its duty, each tank, each board, each fan, each unit, where it is, roughly how old it is and what condition it was in when somebody last looked. It sounds administrative. It is the difference between a maintained building and a building that gets attended.

Without it, three things go wrong predictably. Scope becomes a description rather than a list, so "maintain the common area MEP" means whatever the attending technician interprets it to mean. Pricing becomes guesswork, and the gap between the guess and the building always resolves in the same direction. And nobody can tell whether the planned work actually happened, because there is nothing to check it against.

With one, the ordinary questions become answerable. Which pumps were serviced this quarter. How old the transfer pumps are. What failed twice last year. What the building should be putting aside for. None of those can be answered from invoices, and all of them get asked eventually.

The register belongs to the building, not to the contractor. Any contract should say so explicitly, because a register that leaves with a departing contractor takes the building back to the start — and the next contractor will charge to rebuild it.

Building it is not glamorous work. It means opening every plant room, walking every riser, going onto the roof, into the basement, and writing down what is actually there rather than what the drawings say is there. Buildings routinely discover equipment nobody knew about and equipment that has not worked for years.

This section exists because the alternative is a contract that quietly implies competence it does not have.

Lifts are a certified specialist trade with their own regime, their own engineers and their own statutory inspection arrangements. A general maintenance contractor does not maintain lifts. What it can do is hold the coordination — logging faults, chasing attendance, keeping the records with everything else — and that is worth having, but it is a different thing and should be written as one.

Fire detection and suppression are the same and more serious. Detection systems, sprinklers, pumps, extinguishers and the associated certification are the domain of contractors approved for that work and subject to inspection requirements set by the authorities. Requirements change, so the current position is a question for your certified fire contractor and the authority rather than for a web page. What we will not do is imply that a maintenance visit covers any of it.

Water tank cleaning and disinfection is approved-contractor work with its own documentation. A general contract should inspect tanks, flag when cleaning is due, and hold the certificates — not perform the cleaning under cover of a general scope.

Facade, rope access and anything structural are specialist and safety-critical.

And high-voltage or substation-side work is a utility matter rather than a maintenance one.

The reason to insist on this list is not caution for its own sake. A contract that absorbs specialist scope into a general fee produces a building where somebody believes an obligation is being met and no certified party has attended. That is a worse position than having no contract, because the gap is invisible.

Buildings that get into trouble almost always did it the same way, and it is visible in the accounts a year before it is visible in the building.

Planned preventive maintenance is scheduled work against the register: it happens whether or not anything is wrong, and its output is mostly the absence of events. Reactive maintenance is attendance when something has failed. Both are legitimate and every building needs both.

The failure mode is that reactive work grows and planned work is quietly deferred to pay for it. Each individual decision looks reasonable — a pump has failed, it must be fixed, the quarterly servicing can wait a month. Repeat that for two years and the building has stopped doing preventive work entirely, while spending more than it did before, because deferred maintenance surfaces as breakdowns.

The protection is bookkeeping rather than engineering: separate the two lines in the budget, report them separately, and treat a rising reactive proportion as the warning it is. A committee that can see planned spend falling and reactive spend rising has the information to act. One that sees a single maintenance figure does not.

It also changes procurement. Planned work is genuinely comparable between contractors, because the schedule defines it. Reactive work is not comparable in advance, and should be governed by an agreed rate structure and an authorisation threshold rather than by quoting each job while the building waits.

A sensible threshold — below which the contractor simply proceeds and reports, above which the manager approves — is one of the most useful clauses in a building contract. Set too low it produces delay on trivial work; set too high it removes control. It is worth arguing about at signing rather than during a failure.

From the point of view of the residents, a small number of items cause almost all the incidents.

Water pumping is first. A building depends on transfer and booster pumps, and when they fail the entire property has no usable supply within hours. Most buildings have duty and standby sets, which is the correct arrangement — and the standard failure is that the standby has not run in months and does not start when it is finally needed. Exercising the standby and proving the changeover is the single most valuable recurring item on a building schedule, and it is exactly the sort of task that looks pointless right up to the day it is not.

Sump pumps in basements and car parks are second, and they fail the same way: unattended, in a pit, until there is water where cars are. Float switches foul, non-return valves stick, and nobody knows because the pump was never asked to run.

Drainage is third and it is seasonal. Roof outlets, podium drains and car park gullies silt up steadily through a dry year, and Dubai then delivers its rain in a small number of heavy events. A building that clears its outlets before that is doing fifteen minutes of work; one that does not is dealing with water in a lift pit.

Common electrical distribution is fourth. Loose terminations heat up, and the progression from warm to failed is slow and invisible until it is neither. Boards in plant rooms and risers accumulate dust and heat, and the labelling drifts out of date until an isolation becomes a guess. The same discipline described on electrical inspection Dubai applies here, at greater consequence.

And ventilation is fifth, particularly extract in basements and car parks, which is a safety system as much as a comfort one and which nobody notices has stopped.

The commercial context is different from every other page in this category, because the buyer is spending money that belongs to the owners and was approved in advance.

That has three practical consequences. The contract has to be explicable — a scope that cannot be summarised in a paragraph will be attacked at a general meeting whatever its technical merits. It has to be predictable, because a budget overrun is a governance problem rather than an inconvenience. And it has to be documented, because the manager may be asked to justify any line of it.

Which is why the annual figure matters less than its structure. A contract with a clear planned scope, an agreed reactive rate structure and an authorisation threshold produces a maintenance line that behaves. A cheaper contract with a vague scope produces variation orders all year, which is how a maintenance budget overruns while the building gets less work.

The second issue is the reserve fund, and it is where a good contract earns its place. Plant has a finite life: pumps, boards, fans, tanks and cooling equipment all reach a point where replacement rather than repair is the honest answer. A building that discovers this when something fails is making a capital decision under pressure, usually at the worst price. A building whose annual report lists assets approaching end of life has a planned conversation instead.

That report is the deliverable a committee should ask for by name: not a list of visits, but a statement of condition — what is fine, what is being watched, what will need replacing in the next few years and roughly in what order.

And the third: continuity. Managers change, committees change, and buildings lose institutional memory faster than almost any other kind of property. The register and the reporting are what survives that, provided the contract states that both belong to the building.

A building recently handed over by a developer is a specific case and it is worth handling deliberately.

New buildings typically carry a defect liability period during which the developer remains responsible for putting defects right. Maintenance during that window is not the same conversation as maintenance afterwards, because a proportion of what goes wrong is somebody else's obligation.

The mistake is to treat every failure in that period as maintenance, fix it, and pay for it out of service charge. Doing so quietly discharges the developer of things they should have addressed, and the money does not come back.

So the useful contract in a handover building does something slightly different: it identifies and documents defects distinctly from wear, so that the association can pursue what belongs to the developer while genuinely maintaining what belongs to the building. That distinction is a documentation exercise as much as a technical one, and it needs to happen while the period is still open.

The other handover issue is information. New buildings arrive with drawings, manuals and commissioning records of extremely variable quality, and the association frequently receives less than it should. Establishing what exists — and building a register from the plant itself where documentation is missing — is a first-year task rather than something to discover in year three.

It is also the ideal moment to start a maintenance record, because everything is at a known state. A building whose history begins at handover is in a materially better position than one whose history begins whenever somebody finally started writing things down.

Associations usually tender this work, and tenders in this market are frequently not comparable with each other. A few things make them so.

Issue the asset register with the tender. If each contractor prices their own idea of the scope, the returns cannot be compared and the cheapest one is simply the one that assumed least. This single step does more for a tender than anything else.

Specify frequencies per asset rather than a total number of visits. "Monthly attendance" tells you nothing about what happens to the pumps.

Ask for the reactive rate structure separately: labour rates by trade, out-of-hours arrangement, and how parts are charged. A low planned price with an undefined reactive arrangement is not a low price.

Ask what specialist scope is excluded, and treat a tender that appears to include lifts or fire certification as a warning rather than as good value.

Ask what reporting looks like, and ask to see an example. This is the deliverable the manager lives with every month.

Ask about mobilisation: what happens in the first sixty days, whether a register is being produced, and what the building is left with if the contract is not renewed.

And read the exit terms. Notice periods, handover of records and the register, and what happens to any equipment installed. A contract that is hard to leave gets renewed on the contractor's terms rather than the building's.

None of this is about finding the cheapest tender. It is about being able to tell what the tenders actually say, which in this market is most of the work. The same discipline applied to a single property is on annual maintenance contract Dubai.