Skip to content

Construction defect categories that stay useful on site

A defect category should help route work and reveal patterns. It should not try to describe the room, responsible contractor, seriousness, cause and status in one label. The most useful reporting systems keep those dimensions separate.

9 minute read. Last reviewed .

Categories are an information system, not a technical or legal conclusion. Whether work is defective or non-compliant depends on the contract, applicable law, the National Construction Code, referenced standards, manufacturer requirements and competent assessment.

What a category should do

A good category answers one stable question: what building element or work type does this observation concern? That answer helps a site team send the item to the right person, filter a report and see whether the same kind of problem is repeating.

Categories fail when they are built around a single project’s wording. “Level 3 bathroom waterproofing urgent” contains a location, system and priority. The next waterproofing defect needs a new label, and after fifty items the list is no longer filterable. “Waterproofing” as the category, with Level 3 bathroom in Location and High in Priority, remains useful.

The category also should not declare a cause too early. Staining may relate to plumbing, the weather envelope, condensation or an earlier event. Record “Water and moisture” or the affected element while cause is investigated. Update the action and assigned trade when the evidence supports it.

Use element first, then trade where helpful

For most building defect registers, a two-level model is enough. The primary category is the building element or system. An optional secondary tag identifies the work package or specialist discipline. Contractor assignment remains a separate field because the responsible business can change while the underlying category does not.

Primary category

  • Stable across projects and contractors
  • Describes an element, system or work type
  • Broad enough to avoid dozens of near-duplicates
  • Specific enough to route and analyse
  • Applied consistently by different inspectors

Separate record fields

  • Project, level, area and exact location
  • Observed condition and requested action
  • Assigned contractor or responsible person
  • Priority, due date and current status
  • Compliance reference or specialist finding

On a smaller residential project, categories may map closely to trades. On a larger or more technical project, element-based categories are usually more durable because responsibility can cross packages. A leak at a window may involve installation, membrane, flashing, sealant or adjacent cladding. The window remains the affected element while the investigation determines responsibility.

A practical starter category list

Begin with a short controlled list and add only when a new category will change routing or analysis. The following set covers common handover and building inspection work without pretending to replace a technical classification standard.

  • Site, drainage and landscaping: finished levels, paths, paving, retaining, surface water and external site elements.
  • Structure and movement: observed cracking, displacement, deflection or damage where structural review may be relevant.
  • Roof and rainwater goods: roof finishes, flashings, gutters, downpipes and related penetrations.
  • External walls and weatherproofing: masonry, render, cladding, membranes, sealants and facade junctions.
  • Windows, glazing and external doors: frames, glass, hardware, operation, seals and interfaces.
  • Internal walls, ceilings and linings: plasterboard, plaster, partitions, cornices and finish continuity.
  • Internal doors and hardware: leaves, frames, clearances, latches, locks, closers and stops.
  • Floor finishes: tile, timber, resilient, carpet, transitions, skirtings and movement joints.
  • Painting and coatings: coverage, damage, preparation, colour, texture and coating failure.
  • Joinery, fixtures and appliances: cabinets, worktops, shelving, built-in fittings and included equipment.
  • Waterproofing and wet areas: visible wet-area interfaces, sealants, drainage and observed moisture concerns.
  • Hydraulic and plumbing: water supply, sanitary fixtures, drainage, leaks, hot water and exposed pipework.
  • Electrical and communications: lighting, outlets, switchboards, controls, data and included access systems.
  • Mechanical and ventilation: heating, cooling, exhaust, grilles, controls, noise and commissioning observations.
  • Fire and life safety: fire doors, detection, emergency systems, penetrations and egress matters requiring prompt competent review.
  • Documentation and handover: certificates, manuals, warranties, keys, labels, commissioning and training not yet provided.

Add “Other, review required” as a temporary category, not a permanent dumping ground. Review those items weekly. If several describe the same element, create one controlled category and reclassify them.

Keep location, condition, cause and ownership separate

The defect title can combine element and condition for the reader: “Bedroom window does not latch”. The structured fields below it should remain atomic so they can be filtered independently.

  • Location: Building A, Level 2, Unit 204, bedroom 1, west wall. Location tells someone where to go.
  • Category: Windows, glazing and external doors. Category describes the affected element.
  • Condition: Sash contacts the frame and the latch cannot engage without force. Description records what was observed.
  • Action: Investigate alignment and adjust or rectify so the window operates and latches as required. Action gives a finish line without overstating an unproven cause.
  • Assigned to: Window contractor. Assignment routes the work and may be revised after investigation.

This separation is what makes a filtered contractor report possible. It is also what lets a project manager ask useful questions later: how many open window items remain, which areas contain them, and whether the same condition is recurring.

Priority is not a defect category

Keep priority deliberately simple. High can cover immediate safety, serious water entry, statutory barriers or anything genuinely blocking lawful handover. Medium can cover functional failures that do not stop use. Low can cover cosmetic and minor finish items. Define the levels for the project so inspectors use them consistently.

A category does not carry a fixed priority. A paint touch-up is usually low, but an unspecified coating within a fire-related system may not be. A door adjustment may be medium, while a fire door that does not close may require urgent competent review. Priority depends on the particular condition and context.

Likewise, “major defect” can be a defined legal term rather than a synonym for important. Do not use it casually as a priority label in a report that may be read as making a statutory conclusion.

Maintain one controlled taxonomy

Nominate an owner for the category list. Merge duplicates such as “electrical”, “electrics” and “power”, publish short definitions, and avoid renaming a category halfway through a project without mapping the earlier data.

Review the list after the first hundred items. Categories used once may be too specific. A category holding half the register may be too broad. The aim is not mathematical balance. It is a list that supports routing during closeout and reveals repeat conditions while there is still time to change the work.

Pair the taxonomy with strong evidence. The guides to photographing defects and writing a defect report show how to create the record that sits behind each category.

Sources and further reading