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

Timestamp, GPS, heading, device ID. What it takes to stop a defect photo being waved off as taken anywhere, anytime, by anyone.

7 min