"Fix the thing in the bathroom." That is a defect that costs you a morning. You drive across town, walk the unit, and find three bathrooms and nothing obviously wrong in any of them. You ring the super. He is up a ladder on another job and does not pick up. You take a guess, regrout a joint that looked a bit rough, and leave. A week later it comes back, because the thing was a hairline crack in the hob on the ensuite, not the joint you fixed. Now you are making the same trip twice for one defect you could have closed the first time.
Compare that to a defect that turns up as a photo of the exact crack, a pin on unit 1204 ensuite, the wall you are facing, and one line: "hairline crack in hob, disputed at PC". You already know what you are walking into before you leave the yard. You bring the right gear. You fix it once.
That is the whole argument, from the trade's side. Good defect capture is not paperwork the builder makes you deal with. It is the difference between one trip and three.
What a vague defect actually costs you
A vague defect does not cost the person who wrote it anything. It costs you. Every missing detail becomes a phone call, and every phone call is you standing on site trying to reach someone who is busy doing what you were doing five minutes ago. "Which unit." "Is it the tap or the pipe behind it." "Send me a photo." By the time you have the picture in your hand you have burned half a day, and you have not touched a tool yet.
The trades I know price this in. If a builder is known for vague lists, you pad the quote, because you know a chunk of the job is chasing information that should have arrived with the defect. That padding is not you being difficult. It is the cost of the ten messages, made honest.
A good defect arrives finished
Here is what a defect should carry when it lands on your phone, and what IssuesId puts there without the super doing extra work:
- →A photo of the actual problem, marked up, so you are not guessing which crack.
- →The exact spot. Not "bathroom" but the unit, the room, and the heading the photo was taken on, so you can stand where the super stood and look at the same wall.
- →What is wrong, in one line, and who it is assigned to. You, or your trade.
None of that is extra admin for the person capturing it. The photo carries its own timestamp, GPS and device metadata from the moment it was taken. The location is already on the defect. The super taps your trade, taps your name, and moves on. Two taps for them, a defect you can actually action for you.
Marking it done is the same deal in reverse
The bit that gets skipped: closing it out. You fixed the crack. Now you want it to stay closed and never hear about it again.
So you do to the builder what a good builder does to you. You take a photo of the finished work, from the same spot, and mark the defect done. That before-and-after pair is the most persuasive thing either of you can hold. It is proof the work happened, it is dated, and it kills the "are you sure you fixed it" follow-up before it starts. If there is ever a dispute at handover, the record is already sitting in the report with your name on the close-out, not buried in a text thread nobody can find.
That is the part worth saying plainly: the same capture that respects your time protects you later. The trade that turns up once, fixes it, and photographs the result is the trade with nothing to argue about at PC.
The honest bit
None of this makes a bad list good. If the super captures "bathroom, fix it" and taps your name, you still get a vague defect, just faster. The tool cannot make someone care. What it can do is make the good version the easy version, so the super with 90 seconds and one thumb captures the crack, the spot and the line without it being a chore. When capture is that cheap, the vague defect stops being the default.
And when the defect arrives finished, so does your day. One trip. One fix. One photo. Done.