A new home can look finished while still containing defects that are difficult to describe from memory. Snagging is the practical inspection and recording step at handover: identify a problem, locate it precisely, photograph it and confirm how it will be handled. A good list is useful whether the item is corrected immediately or requires follow-up after the owner moves in.
ADREC's developer journey describes a completion certificate, snagging with buyers, title deed issuance and a post-handover defects liability stage. This public overview does not specify what every buyer must sign, whether a particular defect justifies withholding acceptance, or the warranty terms for a specific unit. Read your SPA and handover documents alongside it.
Before the appointment
Ask for the unit number and approved layout, the handover notice, the inspection procedure, the defect reporting channel, the current account statement and the documents you will be asked to sign. Confirm whether a representative or independent inspector may attend and whether utilities will be working for a functional check. If access or services are unavailable, record what could not be tested rather than ticking it off as passed.
Bring a copy of the agreed specification, a phone or camera, charger, measuring tape, small flashlight and a written room list. Create a defect log with five fields: room, precise location, observation, photo reference and response or proposed resolution. Use one entry per issue. A statement such as "bathroom leaks" is less actionable than "water appears under the guest bathroom vanity after running the basin tap for two minutes."
Do not confuse this walkthrough with an engineering inspection of concealed structure, wiring or fire systems. If a visible sign suggests a serious issue, stop the relevant test, document the symptom and ask a qualified professional to assess it.
Work room by room, then system by system
Begin with the entrance and proceed in a fixed order through every room, balcony and accessible external area. Check against the contracted layout and finish schedule, not only against the show unit or promotional images. Record absent items separately from damaged items.
| Area | Safe owner checks | What to record |
|---|---|---|
| Walls and ceilings | Visible finish, stains, cracks and uneven transitions | Room and wall, size or position, photo |
| Floors and skirting | Alignment, chips, loose edges and transitions | Exact tile or board location |
| Doors and windows | Opening, closing, visible seal and lock operation | Which leaf, hinge, handle or frame |
| Cabinets and counters | Doors, drawers, chips, joints and sealant | Cabinet identifier and symptom |
| Kitchens and bathrooms | Taps, visible leaks, drainage and water damage | Fixture, test performed and result |
| Cooling and ventilation | Thermostat response, airflow and visible condensate | Room, setting and observed response |
| Power and lighting | Ordinary switch, socket and fitted appliance operation only | Which point failed and under what condition |
| Balcony or garden | Accessible finishes, drainage outlets and rails | Location and visible issue |
Only perform tests that are safe and permitted by the handover team. Do not remove covers, open a distribution board, test polarity or climb to reach equipment. Ask a licensed specialist to investigate suspected electrical or structural defects. If an appliance or air-conditioning unit cannot be demonstrated because a service is disconnected, mark it untested and agree a follow-up date.
Take both an overview photo and a close-up for each issue. Keep the original image files with timestamps. If video demonstrates an intermittent fault, save a short clip and note the conditions that triggered it. This is more useful than a large folder of unlabeled photographs.
Close the inspection with a reconciled record
Before leaving, compare your list with the developer representative's list or portal entries. Keep copies or reference numbers for every submitted item. Record which defects are acknowledged, which are disputed, which could not be inspected and the next response date. If a representative promises a repair verbally, ask for the promise and timing in the official channel.
Read the acceptance document before signing. Does it say the unit is defect-free? Does it incorporate the snag list? Does it set a later inspection or rectification route? The legal effect depends on its wording and the governing documents. This article cannot tell a buyer to sign "subject to rectification" as if that phrase automatically preserves every right. Where a material defect or disputed clause is involved, obtain advice on the actual documents before signing.
ADREC's registration rules describe the completion and final-register process. That process is separate from a casual walk-through and may depend on project documents, final plans and the buyer's obligations. Do not assume a key handover proves every registration step is complete.
Track unresolved items after handover
Create a follow-up table with the submitted date, reference, owner, proposed remedy, scheduled visit and closure evidence. Photograph the completed repair from the same angle as the original defect. Test the affected function again where safe. Do not close an item merely because a contractor attended.
If a new fault appears later, report it promptly through the contractually specified route and retain the correspondence. ADREC's developer journey describes a defects liability stage, while the detailed rights and time limits for a particular issue require the contract and applicable law. The developer's own published process may help with logistics. For example, Aldar's handover guidance describes a walkthrough with a handover agent and reporting finish or condition snags. That is an Aldar example, not a rule for every developer.
A useful handover file ends with three folders: what the contract promised, what the buyer observed, and what the developer acknowledged or repaired. That record helps resolve ordinary defects and makes any later specialist or legal review more precise.
Sources and limits
The official ADREC developer-journey and registration pages and Aldar's own handover guidance were checked on 2 October 2026. The ADREC overview is a developer-process summary, not a unit-specific warranty certificate. Aldar's process applies to its customers, not automatically to another project. No universal acceptance rule, repair deadline or waiver is asserted here. This is not legal or technical safety advice; a serious defect or disputed acceptance document needs a qualified professional's review.