Journal/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.

A two-colour risograph poster of a gloved hand holding a phone crowded with site photos and chat messages
JW
Justin WilliamsCo-founder
13 July 2026·6 min read

A cracked tile gets spotted on level six. Someone shoots a photo, drops it in the site WhatsApp with "this needs sorting before the client walk", and three people react with a thumbs up. Good. It is on the record. Except it is not. Two weeks later the tiler swears he was never told, and now you are scrolling upward through four hundred messages, past a lunch order and someone's photo of a parking fine, trying to find one tile you know you saw.

You will not find it. Or you will find it at 10pm the night before handover, which is the same as not finding it.

The problem is not the people. It is that nobody owns the list.

Everyone assumes the list exists somewhere. The super thinks it is in the group chat. The PM thinks it is in the spreadsheet. The QA lead has their own version on a clipboard from Tuesday. Three lists, and the thing they all have in common is that no single person can point at one and say "this is the defect register, and it is complete". When something falls through, and it will, there is no one place it was supposed to be, so there is no one to say it went missing.

Scattered tracking fails in a specific order, and I have watched it happen the same way on job after job.

First the evidence and the record split up. The photo is in one person's camera roll, the description is in the chat, the status is in someone's head. Nothing links them, so reconciling the three is a job someone has to do at night, and mostly nobody does.

Then ownership goes fuzzy. A defect posted in a group of twelve is assigned to everyone, which means it is assigned to no one. "Someone should look at that" is not an instruction. It is a hope.

Then it gets raised twice, because the QA lead and the super both walked the same corridor and neither could see the other's list. Now you are arguing about whether it is one crack or two.

And then the dispute. "We never agreed that." With a chat thread and a camera roll, settling it is archaeology, and the loudest person in the meeting wins. That is not a records problem you can fix with a better group chat. It is a records problem you fix by having records.

What one owned list looks like

Not a fourth WhatsApp group. One register that everyone captures into and everyone reads from, where each item has a name against it and a status that moves.

The capture and the record have to be the same act. You are standing in front of the cracked tile: you take the photo, mark the location, say what is wrong, and it is logged, in one go, right there. No posting it somewhere and writing it up later. The evidence lands stamped with when and where it was taken, so the photo and the defect cannot drift apart. That timestamp and GPS is what ends the "we never agreed that" argument, because the record is not somebody's memory, it is a defect with a photo and a location and a name on it.

Then it goes to one trade, not a group of twelve. Two taps, assigned, and now there is exactly one person who owns that item until it is closed. The status is not a vibe. It is open, assigned, fixed, verified, closed, and a trade cannot quietly tick off their own work because each step is gated against a name.

And the list is the source of truth even when the signal is not. Half the defects on a build are found in a basement or a lift core or the back of a block before the comms riser is live. If the tool needs a bar of 4G to save anything, people go back to the group chat, and you are back where you started. It has to work offline, phone as the source of truth, syncing later when the signal turns up.

There is nothing clever about this. It is the boring truth that a list only works if one person owns it and everyone else can see it. WhatsApp is a great way to tell someone something. It is a terrible way to remember it. The camera roll is a great place to keep photos of your kids. It is a terrible defect register.

You already have three lists. The fix is not a better one of those. It is one list, owned, that the whole team writes into and no one has to go digging for. When the tiler says he was never told, you open one screen instead of scrolling for twenty minutes, and the argument is over before it starts.