RERA India and Common Area Handover: The Records Associations Should Demand

Operational control map

Use this map when translating the guide into system configuration or procedure. Replace every placeholder and add jurisdiction-specific rows before approval.

Control area	Minimum requirement	Owner	Evidence
Scope and applicability	Confirm entity, jurisdiction, activity and effective date.	[ASSIGN]	[EVIDENCE LINK]
Authoritative requirement	Link the current source from RERA.	[ASSIGN]	[EVIDENCE LINK]
Master data	Define fields, identifiers and ownership.	[ASSIGN]	[EVIDENCE LINK]
Workflow control	Record submission, approval, rejection and correction states.	[ASSIGN]	[EVIDENCE LINK]
Evidence	Retain source documents, acknowledgements and versions.	[ASSIGN]	[EVIDENCE LINK]
Exception handling	Assign escalation, resolution target and authority.	[ASSIGN]	[EVIDENCE LINK]
Periodic review	Set an owner and regulatory review date.	[ASSIGN]	[EVIDENCE LINK]

Treat this as a maintained record. Store source publication, internal approval and next review dates, and preserve prior versions whenever a rule or workflow changes.

Treat handover as operational acceptance, not a document transfer. Build a requirements register before practical completion, assign each item an owner and acceptance test, sample critical assets in the field and preserve unresolved gaps in a dated action log. The receiving FM team should be able to identify an asset, understand how it operates, see its commissioning baseline, find its warranty, generate its maintenance plan and trace its cost without returning to the developer's project team.

A handover folder can be complete on paper and useless in practice

The contract says quarterly preventive maintenance. The vendor uploads four generic reports on the final day of the quarter. The asset history shows no readings, parts or defects. The invoice is paid because the contract value matches the purchase order.

That is not maintenance assurance. It is document matching.

Annual maintenance contracts cover lifts, HVAC, generators, fire systems, UPS, water treatment, building automation, security equipment and many other facility services. Their risks differ, but the governance principle is the same: scope, performance, evidence, payment and transition must connect.

The Government of Dubai's Manual for Procurement of Non-Consultancy Services 2025 explains that input-based contracts require vigilant monitoring of deployed resources and service quality. It emphasises the importance of service-level agreements, performance standards and acceptability evidence. Private facilities are not necessarily governed by this public-procurement manual, but its contract-management disciplines are useful.

This article provides operating guidance, not legal advice. Draft penalties, termination, labour compliance, tax treatment and liability with qualified Dubain legal, tax and procurement professionals.

1. Start with the verified asset and space baseline

A handover package cannot be governed if neither party agrees what is covered. Attach a controlled asset schedule containing:

• unique asset ID and location;
• description, manufacturer, model and serial;
• capacity and criticality;
• installation and warranty status;
• condition at contract start;
• operating hours and duty;
• included assemblies and exclusions;
• maintenance strategy and frequency;
• statutory inspection or certification needs;
• opening defects and pending projects;
• ownership of specialist software, tools and access.

Physically verify a risk-based sample before commencement. A legacy list can include removed equipment, duplicate tags and assets maintained by another vendor.

Use a variation process for additions, removals and major upgrades. Do not let the invoice asset count drift through email approvals.

2. Collect as-built drawings and system schematics

“Comprehensive” is not a complete scope. Clarify whether the fee includes:

• preventive and corrective labour;
• emergency attendance;
• consumables;
• routine and major spares;
• refrigerant, oil, filters or batteries;
• specialist software and licences;
• testing instruments and access equipment;
• statutory tests and certificates;
• transport and freight;
• standby equipment;
• after-hours work;
• damage from misuse or third parties;
• obsolescence and replacement;
• taxes and price adjustment.

For labour-only contracts, define client-supplied spares and approval lead time. For comprehensive contracts, list excluded capital components and price mechanism. An undefined exclusion becomes a dispute during failure.

Separate scheduled service from projects. Replacing an entire chiller may fall outside the handover package while compressor repair may be included. Set decision and quotation rules.

3. Demand commissioning and performance evidence

The SLA should distinguish:

• acknowledgement;
• competent remote response;
• physical attendance;
• safe containment;
• temporary restoration;
• permanent resolution;
• root-cause report;
• closure evidence.

Define priority by consequence:

Priority	Example impact	Control focus
Critical	life safety, total critical-service loss, severe operational risk	immediate escalation and continuity
High	major area or business function unavailable	rapid attendance and restoration
Medium	limited service degradation with workaround	planned resolution
Routine	cosmetic or non-urgent request	scheduled completion

Use asset criticality and affected service, not requester's designation. Include clock start, operating calendar, permitted pause reasons, client dependencies and escalation.

The Department of Expenditure manual describes SLA service elements and management elements: services, availability, standards, responsibilities, tracking, reporting, dispute and revision. That is a stronger model than a single response-time promise.

4. Convert O&M manuals into maintainable task plans

A PM report saying “checked and found OK” does not prove the contracted work.

Each job plan should include:

• asset and maintenance basis;
• safety and permit controls;
• task steps;
• readings and acceptable ranges;
• condition observations;
• consumables and parts;
• defects and follow-on work;
• technician identity and competence;
• start, finish and interruption;
• client verification where required;
• attachment or instrument evidence appropriate to risk.

Schedule from statutory, manufacturer, warranty, condition, duty and risk requirements. Vendor convenience should not determine frequency.

Late PM should remain visible. Do not reschedule after the due date to make compliance green. Record deferment authority, risk and revised date.

Measure PM quality through sampling, repeat failure, reading completeness and defect detection—not completion percentage alone.

5. Transfer warranties, guarantees and defect ownership

Where payment or service depends on deployed manpower, maintain a roster by role, shift, site and required competence. Verify attendance through appropriate controls without replacing supervision with biometric data alone.

Track:

• approved person and employer;
• qualification and licence;
• induction and site access;
• medical or safety requirement where applicable;
• shift and relief coverage;
• absence and substitution;
• overtime and fatigue risk;
• training and authorisation expiry.

Substitution must meet the contracted competence, not merely headcount. A technician present without authorisation for the relevant work does not fulfil capability.

Review applicable labour, wage, social-security, safety and contractor obligations with specialist advisers. Store vendor declarations and evidence, but do not assume a certificate automatically proves site-level compliance.

6. Control spares, tools, keys and access credentials

For every spare request, link:

1. fault and diagnosis;
2. covered asset and contract clause;
3. included or excluded responsibility;
4. part number, quantity and compatibility;
5. approval and quotation where needed;
6. issue or purchase;
7. installation and testing;
8. removed part disposition;
9. warranty and inventory update.

Comprehensive handover package vendors may hold critical stock. Agree minimum quantities, storage, shelf life, ownership, inspection and replenishment. Physically verify high-risk spares.

Serialised components and batteries need traceability. Prevent invoicing a new part while the old part remains unaccounted.

Track lead time and downtime caused by spare unavailability. A low handover package price can transfer inventory risk back to the client.

7. Transfer statutory certificates and compliance calendars

Identify applicable inspections, licences, tests and records by asset, site and jurisdiction. Assign responsibility for arranging, witnessing, correcting and retaining evidence.

The calendar should show:

• requirement and source;
• asset or system;
• due and internal preparation dates;
• competent person or authority;
• prerequisite maintenance;
• certificate or report;
• finding and closure;
• validity and next due;
• escalation owner.

Do not rely on the vendor to interpret every obligation. The facility owner or operator retains governance responsibility according to applicable arrangements.

A visit booked before expiry is not completion. Track valid evidence and findings.

8. Reconcile service-charge budgets and commitments

Penalty clauses that say “up to 10% at management discretion” are difficult to administer consistently. Define the event, data source, calculation, cap, exclusions, notice, vendor representation, approval and appeal process.

Examples can include:

• missed planned maintenance;
• late attendance or restoration;
• absent contracted staff;
• incomplete compliance evidence;
• repeat failure attributable to poor work;
• non-availability of included spare;
• reporting delay;
• safety or access breach.

Avoid double counting the same consequence under several clauses unless the contract clearly intends distinct remedies. A service deduction should not become a substitute for corrective action.

Use workflow:

potential breach → evidence review → client dependency check → vendor response → authorised decision → invoice deduction → corrective action → trend

Preserve original timestamps and clock-pause reasons. Manual editing of SLA time destroys trust.

Measure client-caused delay too

Vendor performance can be affected by denied access, delayed purchase approval, unavailable shutdown, missing client spare or unsafe work condition. Record these dependencies transparently.

Pause the SLA only for contractually valid reasons and while the dependency genuinely prevents progress. Assign an internal owner and escalation. A paused ticket should not disappear from service-risk reporting.

Balanced evidence improves vendor relationships and makes transition decisions defensible.

9. Transfer active contracts only after scope verification

Three-way matching purchase order, service entry and invoice is not enough if service entry is a monthly rubber stamp.

Build certification from:

• active contract and period;
• verified covered assets;
• PM and reactive performance;
• deployed resources where applicable;
• included spares and consumables;
• approved variations;
• open deductions and credits;
• statutory and reporting deliverables;
• taxes and price adjustment;
• authorised acceptance.

Separate undisputed and disputed invoice amounts. Resolve deductions under the contract rather than withholding the entire payment without workflow.

Accrue service received but not invoiced at period end under accounting policy. Late vendor invoices should not distort contract cost or asset decisions.

10. Preserve operating history and performance baselines

A useful scorecard contains:

• critical-service availability;
• response, attendance and restoration by priority;
• PM timeliness and task quality;
• repeat failure and first-time fix;
• statutory evidence;
• safety events and permit compliance;
• staffing and competence;
• spares lead time and availability;
• energy or condition outcomes where in scope;
• reporting and data quality;
• commercial accuracy and deduction rate;
• improvement actions and recurrence;
• user or stakeholder impact.

Do not average a serious safety breach with good paperwork. Use gates for critical non-conformance.

Normalise by asset base and service volume, and show data confidence. A vendor with few tickets may have better reliability—or poor reporting.

11. Establish owners-association governance and reporting

Monthly operational review

Review failures, SLA exceptions, PM, statutory items, spares, staffing, invoices and immediate actions. Keep it evidence-led and asset-specific.

Quarterly business review

Review trends, asset health, lifecycle risk, cost, energy, user outcomes, improvements, contract interpretation and future demand. Discuss whether the service model remains fit.

Record decisions with owner and due date. Slide decks are not action registers.

12. Start transition before practical completion

Waiting until the final month gives the incumbent negotiation leverage and makes a safe transition impossible.

At 180 days:

• confirm expiry, notice and extension provisions;
• review asset and scope change;
• assess performance and unresolved breaches;
• inspect high-risk assets;
• identify market alternatives;
• decide sourcing strategy and timeline;
• validate budget and commercial model;
• begin data and document cleanup.

At 120 days:

• approve renew, compete, restructure or insource decision;
• issue procurement documents if required;
• address transition and employee/vendor dependencies;
• freeze baseline asset and service data.

At 60 days:

• finalise award or authorised extension;
• agree mobilisation, spares, access and system transfer;
• plan joint condition and inventory verification;
• communicate service continuity.

Transition is not a reward for SLA compliance alone

Ask:

• Are critical assets more reliable and maintainable?
• Has the vendor prevented failure or merely closed tickets?
• Are lifecycle risks visible early?
• Is statutory evidence trustworthy?
• Are recurring defects reducing?
• Is cost predictable and commercially accurate?
• Does the vendor share useful data and challenge?
• Can the market provide better capability or value?
• What is the transition risk and cost?
• Has scope changed enough to redesign the contract?

Transition may be sensible despite some deductions if the vendor is improving and transition risk is high. Competition may be necessary despite high SLA percentages if the relationship hides risk or capability has stagnated. Document the total decision.

Plan developer exit from day one

The contract should require return of:

• complete maintenance history;
• asset and condition updates;
• open work and defects;
• certificates and statutory records;
• warranties and vendor contacts;
• spares, tools and client property;
• software configuration and credentials;
• drawings, job plans and reports;
• keys, access cards and permits;
• knowledge-transfer sessions.

Define format, timing and acceptance. Client data should remain accessible throughout, not be released only after final payment dispute.

Conduct joint condition survey and inventory. Separate incumbent liability, inherited defects and new-provider responsibility.

Common developer-handover failure patterns

• asset schedules attached without physical verification;
• generic PM checklists for unlike equipment;
• SLA clocks paused without reason;
• penalties calculated manually at year end;
• invoices paid before performance evidence;
• compliance certificates stored outside asset records;
• vendor-reported closure without user or technical verification;
• open defects reset at transition;
• critical spares promised but not inspected;
• transition approved because procurement started late.

Use asset condition to challenge the contract model

A handover package can become uneconomic when the covered asset base ages beyond the assumptions used for pricing. Failure frequency rises, parts become obsolete and both parties argue whether repeated replacement is maintenance or capital work.

Review condition, criticality, remaining life and support status before every transition. Group assets into maintain, overhaul, replace, run-to-failure under controlled risk, and specialist review. Then decide whether each group belongs in comprehensive coverage, labour-only support, call-off repair or a replacement project.

Do not reward a vendor for keeping obsolete equipment alive if lifecycle replacement is the better client decision. Equally, do not penalise the vendor for failures caused by a documented capital decision the client deferred. The contract scorecard should show the dependency and interim risk.

Link transition pricing to the verified asset schedule and expected duty. If quantities or operating hours change materially, use the agreed remeasurement or variation method. A flat annual percentage increase cannot correct a scope whose physical basis is wrong.

Protect operational data in vendor-operated systems

Some vendors use their own maintenance portal. The client still needs timely access, exportable history and audit rights. Define required fields, attachment standards, identifiers, interface frequency, retention and exit format.

Test the export before transition or termination. A PDF summary is not a usable asset history. The transition pack should preserve work events, readings, parts, defects, warranties and open actions in a structured form that the incoming model can load and verify.

A controlled handover sequence

Weeks 1–2

Load contracts, vendors, sites, covered assets, expiry, scope and owners. Identify missing schedules and urgent compliance.

Weeks 3–4

Configure service levels, priority, PM job plans, statutory calendar, staffing and spares responsibilities.

Weeks 5–6

Connect work orders, attendance, evidence, service entry, invoice and deduction workflow. Pilot with one major handover package.

Weeks 7–8

Launch scorecards, governance and 180-day transition pipeline. Close duplicate spreadsheets after reconciliation.

FAQ

What is the difference between handover package and CMC? Terminology varies. The contract must state whether labour, consumables, spares and major components are included rather than relying on the title.

Should every SLA breach create a penalty? Only according to the agreed formula and evidence. Some breaches may require corrective action or escalation without a financial deduction.

Can an invoice be paid when performance data is incomplete? Follow the contract and authorised process. Service acceptance should be evidence-based; disputed and undisputed amounts should be handled transparently.

When should transition planning start? About six months before expiry for material contracts, earlier where procurement, mobilisation or statutory transition is complex.

Is the lowest-price handover package best value? Not necessarily. Compare coverage, capability, spares, exclusions, risk, lifecycle outcome and transition—not fee alone.

Where a system helps

A facility-management platform can link every contract clause to assets, PM, tickets, attendance, statutory evidence, spares, invoices, deductions and transition workflow. It creates a shared record for facility, procurement, finance and vendor teams while preserving a complete exit pack.

Explore FaciOS for facility management.

Related reading: The FM KPIs That Predict a Failed Contract Transition (KB-440) and Facility Management in Giga-Projects (KB-437).

Sources

• Dubai Land Department, Service Charge FAQs
• RERA Circular 2021/03, Verification of Owner Balance
• Dubai Land Department, Service Charge Index