The carpenter rings at 7:15. Item 118, the door to 4.02 catching on the carpet, is not his. The door was hung fine; the carpet is 2 mm thicker than the spec and the flooring contractor should trim it or the architect should have picked a thinner carpet. He is not attending.
He is probably right. He is also now one phone call that nobody wrote down, against an item that says Assigned: carpenter and will say that until somebody remembers the call. In three weeks the client walks 4.02, the door still catches, and the register says the carpenter has had it for three weeks.
The dispute is part of the record, or it is a reason the record is wrong
Here is the opinion. A trade saying "not mine" is one of the most useful things that can happen to a defect, and most registers treat it as noise. It is the moment the item gets correctly classified, correctly costed and correctly routed, if someone writes it down. If nobody does, it is the moment the item starts lying.
So the question is not how to stop trades disputing items. It is how to make the dispute land on the item instead of on your voicemail.
Four things a trade means by "it's not a defect"
They sound the same on the phone and they are four different items.
It is not mine. The door is fine, the carpet is wrong. Right trade, wrong defect, or right defect, wrong trade. The item needs re-issuing, and whoever caused it may need to wear the cost even if someone else does the work.
It is not a defect, it is incomplete. The architrave is not missing, it is not installed yet, because the painter has not finished the wall behind it. True on most jobs for about a third of what gets raised at the first inspection. It needs a different type on the record, because counting it as a defect against the carpenter's name is unfair and counting it in your defect numbers is wrong.
It is a variation. The client asked for the door swing changed on site and now it catches. Somebody is paying for this and it is not the carpenter, and the record needs to say that before the invoice arrives.
It is a defect, and I cannot get to it. The unit is locked, the owner has moved in, the scaffold is down. The trade is not refusing. They are blocked, and the block is yours to clear.
A register with one status for all four, Assigned, will produce one outcome for all four: the item sits.
Give the trade a button, and make it leave a mark
In IssuesId a trade has three actions on an assignment, and Dispute is one of them, next to I'm on it and Mark as Complete. They can press it from the email link with no login. It asks for the reason and puts it in the defect's conversation thread where the project team can see it, and the defect's status shows it is in dispute. The item does not quietly stall. It is loudly paused, with the carpenter's words on it, at 7:16, which is one minute after he would otherwise have rung.
Then somebody on your side adjudicates. Not the trade. The dispute is a claim, the ruling is a decision, and both stay on the file: what the carpenter said, what the site manager decided, when. If the ruling goes against him he can see why. If it goes for him, item 118 is re-issued to the flooring contractor and the record shows it was the carpenter's for eleven minutes, not three weeks.
A workflow rule on the disputed trigger can tell the site manager the moment it happens, which is the right speed for a dispute. An item in dispute that nobody has looked at for a week is the worst of both worlds.
Type, classification, cost: three fields that sound alike
This is where the four phone calls go on the record, and it is worth being precise because the fields get confused.
Type says what the record is. Defect, Incomplete Works, Variation, Warranty, Safety and a few others. The architrave that is not installed yet is Incomplete Works, and once it is typed that way it stops counting against your defect numbers and stops looking like a carpentry failure.
Classification says what is wrong and whose trade it is, from your organisation's own list. The door is Carpentry until the ruling, then Flooring.
Cost category says who pays. Defect, variation or backcharge. And the cost-to contractor is set separately from who is issued the work, which is the field that handles "the flooring contractor trims the carpet, the carpet supplier wears it". Trade A does the rework, Trade B is backcharged, and the accounts team reads it off the record instead of off a conversation.
Three fields, three different readers. The carpenter reads the first. The site manager reads the second. The accounts team reads the third, months later, and the dispute thread tells them why it says what it says.
The blocked one is yours
The fourth call, "I cannot get in", is the one where the trade is right and the register still blames them. The owner of 4.02 has moved in and is not answering. The scaffold came down last week. The unit is a show suite on Saturdays.
Outstanding exists for this: a state outside the normal path, for an item that cannot progress and should not be read as the trade's delay. Put it there, with the reason, and it drops out of the overdue list without dropping out of the register. The overdue rule stops shouting at the carpenter about a locked door, and the Monday digest shows the site manager three items in Outstanding that are his to unblock.
What the file says afterwards
Item 118, run badly: Assigned, carpenter, three weeks, no notes, client walks it, door still catches, everyone remembers a different phone call.
Item 118, run on the record: raised Tuesday 09:40 with a photo of the door and the carpet edge; issued to the carpenter 09:55; disputed 07:16 Wednesday, "door hung to spec, carpet over thickness, see flooring"; adjudicated 08:30, agreed; re-typed as a variation against the carpet substitution, cost to the supplier; re-issued to the flooring contractor, due Friday; marked complete Thursday with a photo of the trimmed edge; closed Friday by the site manager after walking it.
The carpenter was on that item for eleven minutes and the record says so. That is the point of letting him dispute it. The full lifecycle those states belong to is at the construction defect lifecycle, and the three fields are explained once, properly, in the defects documentation.
