Field notes from the defect register.

Field notes

Ten years, on a public register

A house finished in 2019 can now produce a rectification order with the builder’s name on a public register. Since July 2026 the job’s record is a ten-year asset in Victoria, and most builders are still treating it as a twelve-month one.

5 min

Field notes

The defect nobody could have seen

Month nineteen, a brown ring on the ceiling of 8.03, a DLP that closed five months ago and a membrane nobody could have inspected without lifting the floor. Both sides are right, so the argument moves to dates.

6 min

Field notes

The committee and the builder who stopped answering

Month eight, thirty-one defects, a folder of forwarded emails and a builder who has said nothing since June. The builder did not refuse. Nobody on their side was asked a question with a number on it.

6 min

Playbook

Write the defect for a stranger

Item 214 said "tiling". The tiler rang from the car park with grout, silicone and a box of tiles, which is the tiling equivalent of bringing everything. Nine words would have saved the call: what, where on the thing, how much.

6 min

Playbook

The walk before the walk

Our Tuesday list had sixty items. The client's Friday list had forty-one, and nineteen of hers we had never found because nobody ran the shower for ten minutes. A pre-completion inspection is a rehearsal for the next walk.

6 min

Field notes

When the trade says it is not a defect

The carpenter rings at 7:15: the door catching on the carpet is not his, the carpet is over thickness. He is probably right, and he is now a phone call nobody wrote down. A dispute is the most useful thing that can happen to a defect, if it lands on the record.

5 min

Playbook

The register you hand over is the one you kept

An Excel export, 2,300 photos named IMG_4471 onwards and an inspection PDF that references neither. The handover pack goes wrong because it is assembled. If the register during the build was the register, handover is a filter and a print button.

6 min

Field notes

The photo that closes a defect, and the one that does not

The painter sent a good photo of a painted ceiling. Three weeks later the water mark was back. An after photo proves the trade did something, not that the defect is gone, and a fix needs two people on the record, not one.

5 min

Playbook

Due Friday is not a plan

Forty-one defects issued on a Tuesday, all due Friday, none of them because of anything about Friday. A due date is a sorting key, not a threat. Pick the priority, let the date fall out of it, and make overdue an event rather than a colour.

5 min

Playbook

The data hall punch list is the programme

214 items from the pre-IST walk, three walkers, three ways of naming the rooms. On a data centre the punch list is not beside the programme. It is the programme, and it has to answer one question every morning.

5 min

Playbook

Object-based snagging, or snag the room

The model demo attaches a snag to a fire door and the door glows. Then the fit-out foreman has to use it on Tuesday. For most builders the snag belongs to the room, because the room is what everyone on site agrees on.

4 min

Field notes

Real-time defect tracking, three floors underground

Three items found at 10:40 in a basement with no signal. Real-time is the wrong thing to ask for. What matters is that the defect exists the moment it is found, with the right time and place on it.

5 min

Guide

Deficiency, punch, snag, defect: the word changes at the border

Same chipped tile, four captions. In Toronto it is a deficiency, in Denver a punch item, in Manchester a snag. What changes at the border is the contract moment. What breaks is identical in the photo.

4 min

Playbook

An inspection that cannot raise a defect is a form

Thirty-one crosses on a PDF checklist, retyped into the register on a Thursday night. Two never make it. The join between found and owned has to be structural: a No is a defect, or the inspection was a form.

5 min

Guide

A building issue reporting system needs a front door

Ten past ten, level three lift lobby, corridor light out and the fire door not latching. Whether the resident's scan becomes a record or a suggestion depends on the door: not bolted, not wide open, a doorman.

5 min

Playbook

Tracking DLP defects after the trades have gone

Month seven of a twelve-month defects liability period, the plumber is in Geelong and the owner's email is sitting in the info@ inbox. A DLP is a twelve-month job with no job number. Give it one and run it like a job.

5 min

Guide

Defect platform or full project-management suite?

We already pay for a platform and it has a defects module. Sometimes that is the right answer. Four questions that decide it, why dual entry always loses, and the export question to ask before you sign anything.

4 min

Playbook

What makes a construction defect management tool site-ready?

The demo is a clean project on wifi, driven by the person who built it. Your site is a basement with no signal and a plasterer who has never logged into anything. Nine tests to run during the demo, including the ones we do not pass.

5 min

Guide

The construction defect lifecycle: from open to verified close

Fixed is the most dangerous word in a defect register. It reads like an ending, and it is a claim made by the person with the strongest reason to make it. What each of the seven states is really claiming, and who is allowed to move it.

5 min

Playbook

How to set up a construction defect register that survives handover

The register you hand over is never the register you kept, and about a third of it cannot be rescued in the fortnight before practical completion. The fields, the evidence rules and the status ownership to settle in the first hour of the job.

5 min

Guide

Construction defect tracking vs defect management: what changes after capture

A tracker records that the ensuite ceiling in 1204 is stained. It cannot tell you who accepted the fix or what they looked at when they accepted it. One defect, run both ways, and the four questions worth asking before you trust a tool.

5 min

Field notes

It is not just building sites: issue tracking for warehouses and factories

A bowed racking upright, a missing machine guard, a weeping refrigerant line. The capture-assign-close-with-evidence loop we built for building defects fits all three, even if some of the labels are still construction-shaped.

4 min

Product

For trades: closing a defect without ten messages and a site visit

"Fix the thing in the bathroom" costs a trade a wasted trip. A defect that arrives with a photo, an exact spot and one line lets you turn up once, fix it, and mark it done. Good capture respects the trade's time.

4 min

Guide

Common property, and the paper trail strata actually needs

Common property defects turn into owner disputes, and the committee that cannot show a dated, photographed, assigned record loses the argument at the AGM or with the builder. A single logged, tracked list is the paper trail strata needs to hold a builder to account inside the liability period.

4 min

Guide

After the keys change hands: defects for facilities managers

A tenant reports a warm meeting room and a stained ceiling tile, and that is a defect like any other. The report discipline that ends at handover is exactly what an FM needs for the next ten years, from warranty claims to surviving staff turnover.

4 min

Guide

Fit-out runs on a two-week clock. Your defect tracking cannot lag it

Fit-out gives you two weeks a floor and three trades stacked on top of each other, so a defect you write up tomorrow morning is already behind the programme. Capture it at the wall, assign it in two taps, and close it before the next trade moves in.

4 min

Playbook

200 dwellings, one defect list: handover for developers

On a 200-dwelling tower no single defect is hard. What kills the handover is the lists splitting: the super, the subs, the client rep, and the certifier each keeping their own. One list keyed by location is what stops it becoming a spreadsheet swamp.

5 min

Playbook

Residential builders: making handover the boring day it should be

Handover goes bad the moment the owners find the benchtop scratch before you closed it. One owned defect list, captured with photos at the PCI and verified closed before the client walks, is what keeps the day uneventful.

4 min

Field notes

A defect you cannot find is one you pay for twice

A hairline crack in unit 1207, disputed at practical completion, and nobody could prove who found it or when. The tile is cheap to replace. The argument is not, and the record is the only thing that ends it.

4 min

Product

The correspondence that decides who pays

A delay notice is only worth what you can produce eleven months later, when the claim lands and it is still sitting in someone's inbox. Project correspondence puts the delays, variations and claims on the record, threaded at project level, with the other side replying by email magic-link and no login.

4 min

Guide

What IssuesId does on a live site, minus the sales pitch

No feature tour. Just what the product actually does across one job, in order: catch an issue with photo evidence, assign it in two taps, work with no signal, track it to closed, and hand over a report that holds up. Plus what it does not do.

5 min

Field notes

Your defect list is in three WhatsApp groups and nobody owns it

Most teams track defects across a group chat, a camera roll and a spreadsheet, and it fails for one reason: nobody owns the single list. Here is what one owned register actually looks like.

6 min

Guide

Snagging vs defect management: what site teams actually need

Two words that get used for the same clipboard. They are not the same job, and the difference shows up the morning someone disputes a defect and you go looking for the record.

6 min

Announcement

EOFY deal: cut costs before the financial year ticks over

$29 per project and $5 per dwelling per month, the lowest we run all year. Priced by area and dwelling, not by seat. Valid until 10 July.

3 min

Field notes

Why offline-first is the only honest promise in site software

Signal dies in basements, and that is exactly where the defects are. So the phone is the source of truth until it syncs, and sync is something you never think about.

6 min

Playbook

The anatomy of a compliance-ready defect report

What goes into a handover report that stands up to certifier scrutiny? Five sections, one audit trail, zero spreadsheets.

9 min

Product

Trade assignment: the two-tap standard

We rebuilt assignment around one question: what would a site supervisor do if they had 90 seconds between tasks?

4 min

Engineering

Photo metadata as evidence

Capture time, a named location, an untouched original. What it takes to stop a defect photo being waved off as taken anywhere, anytime, by anyone, and why the GPS pin is the weakest fact on it.

7 min