1. Describe the observation before assigning its cause
DR recommends opening a record for the particular condition: its location, when it appeared, how it affects use and what can be observed safely. A description such as water staining below the bathroom ceiling is more useful than an unsupported conclusion that a pipe or waterproofing system has failed.
Give the issue a stable reference. Add dated photographs showing both the location and detail, retain the originals, and distinguish your observation from a contractor’s explanation. If the condition returns, append the new occurrence to the same history while allowing a specialist to determine whether the cause is the same.
For jointly owned property, DLD identifies the management company as responsible for building management, common-facility maintenance and receiving owners’ enquiries and complaints. Identify the relevant management and developer contact channels, while keeping their roles distinct. The organisation receiving a message is not necessarily the party ultimately responsible for the defect.
Where there is an immediate safety concern, seek the appropriate urgent response. Do not delay it to finish photographs or a spreadsheet, or enter an unsafe area to collect evidence.
References: DLD — Jointly owned property management responsibilities; reporting method is DR analysis
2. Preserve the dates behind the liability question
For jointly owned real property governed by Dubai Law No. 6 of 2019, Article 40 sets out the developer’s obligations. It provides for remedying structural defects for ten years from obtaining the project completion certificate, and repairing or replacing defective mechanical, electrical, sanitary, sewerage and similar installations for one year from unit handover. Where the owner declines possession for any reason, the latter period starts from obtaining the project completion certificate. The provision contains qualifications and preserves other statutory rights. These periods should not be assumed to apply to every Dubai property, defect or responsible party.
Create separate fields for the completion certificate, handover notice, actual handover, first observation and first notification. Attach the supporting record to each. If a date is disputed or unavailable, retain that uncertainty rather than substituting the date of an email or your purchase.
The published Dubai provision refers to the earlier federal Civil Code. Dubai’s official legal-training material identifies the replacement Civil Transactions Law as effective from 1 June 2026. Have a qualified lawyer check the applicable framework and transition where relevant; this guide does not determine individual applicability, contractor claims or filing deadlines.
References: Dubai Law No. 6 of 2019 — Article 40, original Arabic · Dubai Law No. 6 of 2019 — Published English text, Article 40 · Dubai Legal Affairs Department — Civil Transactions Law training descriptions
3. Agree what an inspection is expected to establish
Before commissioning a visit, DR suggests defining the question in writing. Are you requesting a record of visible conditions, diagnosis of a recurring problem, a proposed repair scope or verification of work already reported complete? Ask the professional to state the limits of the assignment.
Request a report that identifies the inspected location, date, accessible areas, methods used, findings and further investigation required. Keep an inaccessible area distinct from an inspected area where no issue was observed. Ask who will decide which tests are appropriate and how access will be arranged.
These inspection questions are DR’s proposed method for organising a private assignment. The working register records evidence and follow-up; it does not replace the professional’s inspection, findings or stated limitations.
- Identify the precise issue and intended output before comparing inspection quotations.
- Ask about exclusions, access restrictions and whether a return visit is included.
- Request separation of observed facts, possible causes and confirmed findings.
- Keep the signed report and its limitations together.
4. Use one register from notification to verification
The following is DR’s suggested working register, not an official form. Use one issue reference across the original report, appointment, work record and follow-up. This allows another reviewer to follow the sequence without searching several message threads.
Describe status precisely: reported, acknowledged, inspection arranged, diagnosis received, work proposed, work reported complete, or verification recorded. Keep the technical and liability questions open where the evidence does not resolve them.
Preserve each party’s explanation. If management believes a problem concerns a private installation and the developer believes it concerns a shared system, record both positions and the technical evidence needed to distinguish them.
| Field | What to preserve | Purpose |
|---|---|---|
| Issue identity | Reference, unit, room and precise location. | Connect every later record to the same observation. |
| First observation | Date, description and original photographs. | Preserve what was known before investigation. |
| Notification | Recipient, delivery evidence and request reference. | Identify what was reported and when. |
| Inspection | Appointment, access record, report and limitations. | Separate a visit from a supported finding. |
| Proposed action | Scope, exclusions, responsible party and proposed date. | Make the intended work reviewable. |
| Work record | Attendance, work description and relevant attachments. | Identify what is reported to have been done. |
| Verification | Reviewer, date, method, result and exceptions. | Explain the basis for closing or retaining the issue. |
| Recurrence | New observation linked to the earlier history. | Preserve continuity without assuming the cause. |
References: DLD — Enquiry and maintenance context; register is original DR analysis
5. Separate a reported repair from its verification
As a practical workflow based on DR analysis, ask for a short description of the completed work, its date and any follow-up required. A message stating done should be connected to the issue reference and the work actually performed. Avoid silently converting an appointment or material delivery into completion.
Ask the appropriate professional what would demonstrate that the repair addresses the recorded issue. The answer may involve a return inspection or another suitable check. The professional should determine the method and conditions; this guide provides no instructions for testing building systems.
Where an item cannot yet be verified, record the reason and next step. Access unavailable, conditions not reproduced and further observation requested are more informative than an unexplained closed label.
Keep access arrangements and missed appointments in the chronology without assigning blame. Distinguish acknowledgement of attendance from acceptance of the work; obtain advice before signing wording that could affect your legal position.
6. Worked example: ten reported repairs, seven verified closures
This example is original DR analysis using entirely invented inputs. Consider a register containing 12 separate issues. Assume the service team reports work complete on ten. A subsequent review supports closure of seven; two require further work and one could not be checked. The other two issues remain awaiting work.
The reported-work completion rate is 10 ÷ 12, or 83.33%. The verified-closure rate is 7 ÷ 12, or 58.33%. Both calculations can be accurate when labelled correctly. Calling the file 83.33% resolved would obscure the five issues without verified closure.
This is a count of issues, not a measure of safety, cost or severity. Several minor finish items should not outweigh one serious unresolved concern. Keep priority and technical significance in separate fields, and have them assessed appropriately.
If a closed issue recurs, retain its earlier closure evidence and record the new event. Do not erase the history to make the current percentage appear consistent.
| Invented position | Issue count |
|---|---|
| Work reported complete and closure verified | 7 |
| Work reported complete; further work needed | 2 |
| Work reported complete; verification unavailable | 1 |
| Still awaiting work | 2 |
| Total | 12 |
7. Route the unresolved question to the appropriate party
For complaints about service and maintenance standards, DLD’s FAQ identifies Dubai REST’s Real Estate Violations System. Its general complaints guidance distinguishes regulatory violations from contractual claims. Do not assume one complaint channel decides every repair, compensation or liability question.
Prepare a concise request stating the unresolved issue, previous references, relevant response and next action sought. Ask whether the receiving channel can address that question. Preserve the acknowledgement and any direction to another procedure.
For a possible shared-system issue, DR recommends linking the unit observation to management’s investigation reference. Other residents’ observations may help identify questions, but they do not establish a common technical cause.
Where a formal claim, contested responsibility or time limit is involved, obtain qualified legal advice on the actual documents. An open service ticket should not be treated as confirmation that a legal deadline is protected.
References: DLD — Maintenance complaints and scope of real-estate complaints
8. Keep the history usable through occupation or resale
DR recommends preserving the original handover record alongside later repair documents. If the property is occupied by a tenant, agree a practical way to report observations and arrange access, while keeping contractual responsibilities available for review.
For a resale review, organise the unresolved issues, completed-work records and available warranties with appropriate permission. Do not fill an unknown original date with the resale date or assume that a change of owner creates a new period. Ask the relevant adviser to establish the applicable position.
For a previously delayed development, retain the earlier project chronology as well. The defect file should explain what happened after possession without rewriting the preceding completion and handover history.
Share only the material needed for the review. Remove unrelated identity, banking and other occupants’ information from general summaries.
9. Finish with a clear next action
A useful summary states the observation, current explanation, latest action and evidence still required. For each open item, identify who is expected to provide the next record and the proposed follow-up date. Keep that working date separate from any contractual or legal deadline.
Public sources were reviewed for this guide on 16 October 2026. No unit, inspection report, private account or individual complaint was examined. Detailed federal contractor-liability and transition analysis is outside this guide.
Development Resolution organises evidence for delayed or distressed project assessments. If post-handover issues form part of that wider situation, a structured file can support the assessment. DR does not certify repairs, determine liability or guarantee a remedy.
References: DLD — Public guidance used within the stated review limits
Questions about reporting and tracking post-handover defects
What should I include in the first defect report?
Identify the unit, precise location, first observation date, visible condition and effect on use. Add relevant photographs and request a reference and next step. Keep your observation separate from an unconfirmed diagnosis.
Does a closed service ticket prove the repair worked?
Check what the closure records. DR recommends preserving the work description and separate verification evidence, including any limits or unresolved observations.
Can I use one warranty date for every issue?
Do not assume that. Preserve the completion and handover records separately and obtain advice on the applicable property, responsible party, defect category, starting event and deadlines.
Does this register replace a technical inspection?
No. It organises evidence and follow-up. A qualified professional must determine the necessary investigation, findings and verification method.
Are the repair percentages actual Dubai performance data?
No. The twelve-issue example is entirely hypothetical DR analysis and demonstrates the difference between reported work and verified closure.
Primary and official sources
Project status and procedures can change. When a decision depends on current information, verify the live primary source rather than relying only on a secondary summary.