Start by reading your report
Your Fedari report lists every finding with photographs, a room-by-room location and a severity label — Critical, Major, Minor or Advisory. Before you send anything, read it once end to end. The severity labels are practical prioritisation tools: Critical and Major items are the ones to put first in your communication, while Minor and Advisory items round out the complete picture.
Keep the original PDF unchanged. It is your dated, independent record of the property's condition on the inspection day — everything you send or discuss later traces back to it.
Submit through the developer's own channel
Most Dubai developers have a defined channel for defect reporting: a customer-care portal, a handover app, or a dedicated email address for after-sales service. Use that channel — it routes your report to the team that can act on it and creates a reference number automatically.
When you submit, attach the full report and ask for written confirmation of receipt with a reference number. That confirmation, plus the date, is the anchor for every follow-up conversation afterwards.
What to include when you submit
A complete, easy-to-process submission typically contains:
- The full inspection report PDF, unedited
- Your unit details: building, unit number, community and handover date
- Your contact details and preferred response channel
- A short covering note highlighting the Critical and Major items by their report reference
- A polite, clear request: review, confirm which items are accepted, and share the rectification plan and timeline
Following up professionally
Give the developer's team a reasonable window to respond, then follow up in writing against your reference number. Written follow-ups — email or portal messages — create a record that phone calls do not. If an item is repaired, note the date; if an item is disputed, note the reason given.
Stay factual. The report does the arguing for you: photographs, locations and severity labels are difficult to dismiss, and a calm paper trail keeps the conversation moving.
If items are disputed or refused
Developers sometimes decline items — for example as 'within tolerance' or outside the applicable warranty. What is accepted, rejected or rectified is governed by your contract and the developer's process; Fedari documents the condition and does not promise that any party will accept or repair a reported item.
If a significant item is disputed, you can request the specific basis for the rejection in writing and, where needed, seek advice from an appropriately qualified specialist or legal adviser about your contract position. Nothing in this guide is legal advice — it is practical process guidance from an inspector's perspective.
After the fixes: the reinspection
When the developer reports the items as rectified, a reinspection visually reviews the apparent status of the previously reported findings. Reinspections start from AED 399. You receive an updated, documented view of what is resolved and what still needs attention — so the loop closes with evidence, not assumptions.
