Picture handover on a 200-dwelling tower. You are not walking one building, you are walking level 14, then 15, then 16, each with a dozen units, each unit with a bathroom, a kitchen, a balcony, two bedrooms. The tiler is on level 9 still. The waterproofer swears he closed out the ensuites on 11. The strata manager wants to know what is outstanding on the units settling next Friday, and the builder's PM has a list that does not match the one the certifier is holding.
No single defect on that job is hard. A cracked tile is a cracked tile. What kills a multi-res handover is that the defects stop living on one list.
The real failure is drift, not defects
At three units, everyone can hold the whole job in their head. At two hundred, nobody can. So the lists multiply. The builder's super has a spreadsheet. The waterproofing sub keeps his own on his phone. The developer's client-side rep walks with a clipboard. The certifier builds a third list off his own inspection. Four records of the same building, and the moment two of them disagree, you are in a meeting about the meeting.
I have watched a fit-out PM spend a full day reconciling two spreadsheets that were the same list a fortnight earlier. Not fixing anything. Just working out which version was true. That day is the tax you pay for letting the list split.
One list, keyed by where the defect is
The fix is boring and it is the whole game: one defect list for the project, and every defect hangs off a location, not a person's memory. Building, level, unit, room. Unit 1508, ensuite, cracked floor tile. Level 12 lobby, paint damage to the architrave.
When the address is the spine, the list does things a pile of spreadsheets never can. It groups by building and rolls up by level, so you can hand the settling agent exactly the units closing next week and nothing else. It never invents two names for the same room, because there is one location tree and everyone logs against it. A defect captured by the sub, the super, and the client rep is the same defect, in the same place, seen three times, not three defects in three systems.
That structure is what stops 200 dwellings from becoming a spreadsheet swamp.
Assignment keeps the one list from becoming a bottleneck
A single list only works if the trades can act off it without a gatekeeper. So the defect carries its own trade. Log the cracked tile in unit 1508, assign it to the tiler, and it is his, with the location already attached from when the photo was taken. The tiler sees his units across the whole tower. The super sees what is outstanding on level 15. The developer sees the totals. Same list, different reads of it, nobody maintaining a private copy.
This is the part developers underrate. You are not buying a defect logger. You are buying the thing that stops fourteen subbies and three stakeholders from each maintaining their own truth.
What the developer actually hands over
At the end, the developer does not want a spreadsheet. They want a report per building or per level that a certifier, a purchaser's solicitor, or a tribunal can read cold: what was wrong, where, who closed it, and when, with the photo evidence and the audit trail sitting under each line. That report only exists because the data underneath it was one structured list the whole way through. You cannot assemble it on the Friday from four disagreeing spreadsheets. The shape of the handover is decided months earlier, on the day you choose to keep one list instead of letting it split.
Two hundred dwellings is not two hundred small problems. It is one problem, which is keeping every one of them on the same list, in the same place, all the way to close-out.