Estate snagging and defects tracking should begin before a new estate is handed over and continue until every agreed defect has either been corrected, formally accepted or transferred into the estate's normal maintenance process. A snagging list that is written once and forgotten is not enough.
The useful part is the tracking: what is wrong, where it is, who is responsible, when it was reported, when it should be repaired and what evidence confirms that the work was actually completed.
What is estate snagging and defects tracking?
Snagging is the structured inspection of completed or nearly completed construction to identify incomplete work, poor workmanship, damaged items and other visible defects.
For an estate, the inspection should go beyond individual houses.
Common infrastructure may include:
- roads;
- drainage;
- streetlights;
- gates;
- perimeter walls;
- boreholes;
- pumps;
- water tanks;
- electrical installations;
- generators;
- CCTV;
- access control;
- landscaping;
- recreational areas;
- sewage systems;
- and other shared facilities.
RICS distinguishes defects that are apparent around completion from latent defects, which are hidden at that time and become apparent later. Its current defects guidance also recognises that defective work may emerge during construction, during a contractual rectification or liability period, or afterwards.
That distinction matters.
A cracked drain cover visible during inspection should go onto the snag list immediately.
A concealed waterproofing defect that becomes apparent months later may need to be handled differently under the construction contract, warranty or applicable legal rights.
For the wider transition into occupation, use the new estate handover checklist alongside the defect register.
What should be included in a snagging inspection?
Inspect the estate systematically.
Do not walk around casually and depend on memory.
Break the property into areas.
For example:
Gate and security
Check barriers, sliding gates, readers, guardhouse fittings, intercoms, CCTV and security lighting.
Roads and drainage
Look for:
- cracks;
- settlement;
- standing water;
- damaged kerbs;
- blocked drains;
- poorly finished channels;
- broken covers;
- and incorrect slopes.
Water infrastructure
Check:
- boreholes;
- pumps;
- treatment equipment;
- pipework;
- tanks;
- valves;
- leaks;
- and pressure.
Electrical infrastructure
Check:
- streetlights;
- common-area distribution;
- external sockets;
- generator connections;
- earthing;
- damaged fittings;
- and exposed cables.
Electrical defects should be assessed by competent electrical professionals rather than simply judged visually.
Buildings and common facilities
Inspect finishes, doors, windows, ceilings, plumbing, sanitary fittings, roofing and shared facilities where relevant.
RICS's current new-build survey guidance says snagging reports should be property-specific, factual, unambiguous and logically presented, with issues clearly described rather than relying on vague comments.
That is a useful principle for an estate too.
Avoid:
> Drainage problem.
Record:
> Standing water remains in the drain opposite House 27 approximately two hours after rainfall; outlet appears higher than the channel invert.
Before residents move in, this process should form part of setting up estate services before first occupancy.
How should each defect be recorded?
Every defect should become an individual trackable item.
A useful defect record includes:
Unique reference
Example:
`DEF-0042`
Location
Be precise.
Not:
> Main road.
But:
> Eastern drain beside House 18.
Category
For example:
- electrical;
- plumbing;
- drainage;
- civil works;
- security;
- landscaping;
- water;
- building finish;
- or mechanical.
Description
Explain what is actually wrong.
Photograph
Include enough surrounding context to identify the location.
Date reported
This establishes when the problem entered the register.
Priority
A practical classification might be:
Critical — immediate safety, security or major-service problem.
High — serious operational problem requiring prompt action.
Normal — requires repair but does not prevent normal occupation.
Minor — cosmetic or low-impact issue.
Responsible party
Developer, main contractor, subcontractor, installer or estate maintenance team.
Target date
There should be an agreed expectation for action.
Status
For example:
- Open;
- Assigned;
- In progress;
- Awaiting parts;
- Ready for inspection;
- Closed.
Closure evidence
Photograph, inspection note or other confirmation that the work has actually been completed.
Do not mark something closed merely because the contractor says:
> Done.
Inspect it.
Facility-management systems use the same principle for work orders: requests enter a queue, are assigned, tracked and closed with a completion record, creating usable maintenance history instead of isolated messages.
Once the estate is operational, the same discipline should feed into your facility manager reporting pack.
What happens during the defects liability or rectification period?
Do not assume there is one universal period that applies to every Nigerian estate.
The relevant period and responsibilities depend on the actual construction contract, warranties and other applicable legal arrangements.
RICS notes that construction contracts commonly contain a defects rectification or liability period during which identified defective work can be notified and corrected. Its guidance also emphasises checking the actual contract because the procedures, time periods and responsibilities differ.
For the estate, maintain a register containing:
| Defect | Reported | Responsible | Deadline | Status | |---|---|---|---|---| | Drain beside House 14 | 4 Oct | Civil contractor | 12 Oct | In progress | | Gate photocell | 5 Oct | Access installer | 7 Oct | Closed | | Pump 2 leak | 7 Oct | Plumbing contractor | 10 Oct | Assigned |
Do not let this information exist only in meeting minutes.
Also record which defects were present at handover.
RICS completion guidance notes that when possession occurs while remedial work remains outstanding, the remaining work, conditions and required timescales should be clearly documented.
That protects everyone.
The developer can see exactly what residents are expecting.
Residents can distinguish an agreed construction defect from a maintenance problem caused months later.
And the facility manager knows which contractor should be called.
Contractor responsibility should also connect to the wider contractor management process.
How do you stop defects from disappearing after handover?
Handover is where many defect registers fail.
The construction team has one spreadsheet.
The developer has another list.
Residents send photographs into WhatsApp.
The facility manager maintains a notebook.
Then nobody knows which version is current.
IFMA highlighted this problem in its 2026 construction-handover guidance, noting that operational teams often receive incomplete documentation, unclear asset information and defects whose ownership is uncertain.
Use one master register.
For every item, there should be one current:
- status;
- responsible party;
- target date;
- comment history;
- and closure record.
At handover, review open items one by one.
Each should be classified as:
Remain with developer/contractor
Construction defect still requiring rectification.
Transfer to facility management
Normal operational maintenance item.
Accepted
Issue has been inspected and closed.
Further investigation required
The cause is not yet clear.
Do not quietly move every unresolved construction problem into the new estate maintenance budget.
Equally, do not continue blaming the developer for routine wear or damage that occurred after occupation.
A proper record helps distinguish the two.
Once the development moves fully into operations, recurring maintenance should then follow the estate maintenance schedule.
What should residents and the EXCO be able to see?
Residents do not need unrestricted access to every technical or contractual detail.
But they should be able to report genuine problems and understand whether management is acting on them.
A useful workflow is:
Resident reports issue
Photo, description and location.
Management reviews
Is it a defect, normal maintenance problem or resident responsibility?
Issue is assigned
Developer, contractor, facility team or another responsible party.
Work takes place
Progress is recorded.
Management verifies
Someone confirms the repair.
Issue closes
The resident or management can see that it has been resolved.
The EXCO should receive higher-level information such as:
- open defects;
- critical defects;
- overdue items;
- recently closed defects;
- recurring problems;
- contractor performance;
- and items approaching important contractual or warranty deadlines.
That creates accountability without flooding committee meetings with every loose door handle.
Common-area responsibility should also be clear. Use the estate common areas maintenance guide to distinguish collective infrastructure from items belonging to individual properties.
How does Kompound improve estate snagging and defects tracking?
This is where estate snagging and defects tracking can move away from spreadsheets and WhatsApp entirely.
Kompound already allows residents and estate management to create structured issue reports.
A problem such as:
- broken streetlight;
- blocked drain;
- damaged fence;
- faulty gate;
- water issue;
- or common-area defect
can be reported with a photograph and location and placed into one management queue. Kompound documents the issue through its status until resolution rather than allowing it to disappear inside group chat.
That same workflow can be particularly useful during the first months of a new estate.
Instead of:
> Resident sends defect to developer on WhatsApp > Developer forwards it to contractor > Facility manager keeps separate spreadsheet > Nobody knows whether it was fixed
the workflow can become:
> issue reported → location recorded → photo attached → responsibility assigned → action tracked → repair verified → issue closed.
Kompound also keeps the wider estate context around that issue.
Management already knows:
- the resident;
- the unit;
- the estate location;
- other open issues;
- notices;
- gate operations;
- and the wider administrative record.
The platform's current issue-management system specifically provides photo reporting, location information, status tracking and a single queue of unresolved issues for management.
That becomes even more useful after the developer hands the estate to residents.
Kompound states that estate records belong to the community and remain available through management handovers, so the operational history does not have to disappear when the developer, facility manager or EXCO changes.
The result should be a clean transition:
construction snag → tracked defect → verified repair → normal estate maintenance history.
That is far stronger than handing the new EXCO a spreadsheet called:
`FINAL SNAG LIST UPDATED 3.xlsx`
and hoping somebody remembers what happened next.