“Done, sir”: why done on site rarely means done

It is 7:40 on a Thursday evening. Arjun, a project manager at a twelve-person design-build firm in Pune, is driving home from a client meeting in Baner. He has four live sites and one of them, a 3BHK in Wakad, is supposed to have its kitchen finished today. He calls Ravi, the site engineer.

“Ravi, kitchen ho gaya?”

“Done, sir. All shutters fixed. Imran’s team is leaving now.”

Arjun thanks him, hangs up, and sends a message to the accounts person: the carpentry stage for Wakad can be released. Imran has been asking for it since Monday. It is a fair ask. The work is done.

On Monday the client walks through with her husband. The hinges on the tall unit have not been adjusted, so two shutters rub. The profile handle on the corner unit is missing. The sink cut-out has not been sealed. There is no skirting behind the fridge space, because the fridge space was “not in the drawing” according to someone. Every one of these is a small job. Together they make the client say a sentence that Arjun will remember for weeks: “If this is done, what does finished look like?”

Imran’s team is now at a site in Hinjewadi. He has been paid. He will come back, he says, on Saturday, maybe.

Nobody lied

The first thing to understand about “done, sir” is that it is usually not a lie. Ravi was not hiding anything. From where he stood, the kitchen was done: the carcasses were in, the shutters were hung, the countertop was on, and the carpenters had packed up. That is what done looks like at 7:30 PM after a twelve-hour day.

The problem is that the word “done” carries no evidence. It is a feeling, reported over the phone, by the person who has the most reason to want the task off his list. It answers the question “did the main work happen?” when the owner thinks it answers “is this ready for the client and ready to be paid?”

On a site, done has at least three meanings, and most firms collapse them into one:

• Reported done: someone on site says the work is finished. This is a claim.
• Checked done: someone other than the doer has looked at it against a list, with photos and measurements where they matter. This is evidence.
• Payable done: the checked work is good enough that a named person is willing to release money against it. This is a decision.

When these three are the same word, money moves on a claim. And claims are always more optimistic than evidence.

“Done” is a claim. “Checked” is evidence. “Payable” is a decision. Most firms let all three travel in one word over the phone.

Why the gap stays hidden until handover

If done-but-not-done showed up the next morning, it would be cheap to fix. The carpenter is still nearby, the materials are still on site, and the PM can walk the room with the engineer. The reason it hurts is that it rarely shows up the next morning. It shows up weeks later, when the client walks the flat.

A few things keep it hidden. The next trade arrives and works around the gap: the painter paints around the missing skirting, the electrician fixes the light above a shutter that does not close. Nobody owns the leftover because the task is closed. And the PM, who has four sites and a phone that does not stop, has no reason to go back to something that was reported finished.

Then handover comes, and every small leftover arrives at once, in front of the client, at the moment the firm most needs her to feel good about the last instalment.

What it really costs

The obvious cost is the rework itself. The less obvious costs are bigger. Once a vendor is paid, your leverage to bring him back is gone, so you wait on his schedule, not yours. The PM spends time on site that was meant for the next project. The handover date slips, and with it the client’s final payment. And the client, who was happy for three months, now remembers the project as the one where nothing was finished.

Here is how one kitchen can add up. The figures are invented for the example, but the pattern will be familiar.

Eleven or twelve thousand rupees is not what ruins a project. What hurts is doing this on every room, on every site, every month, and then wondering why handovers always take three extra weeks.

What good firms do instead

The firms that have this under control do not have better engineers. They have a simple discipline that separates the three meanings of done, and they stick to it even when everyone is tired. You can run this on paper, on a spreadsheet, or in a tool. The habit matters more than the medium.

1. Write down what done means for each task. A wardrobe is not done when the shutters are hung. It is done when the shutters are aligned, the hinges adjusted, handles fixed, edges banded, the inside cleaned and the protective film off. A ten-line checklist per item, written once, used on every project.
2. Make the engineer confirm, not just say. A confirmation is a specific act: this task, this room, this time, with a photo. Not “kitchen done” on a call, but “kitchen base units, all checklist items done” with three photos.
3. Have someone else check. QC is done by a person who did not do the work. On a small team, that might be the PM or a senior engineer from another site. The doer and the checker should never be the same person.
4. Fail things on purpose. A QC that never fails is not a QC. When something fails, it becomes a snag with an owner and a date, not a comment in a group.
5. Tie money to the check, not the claim. A vendor stage is payable when QC passes, and a named person approves the release. Ideally the person who raises the payment is not the one who approves it.
6. Close it the same week. The cheapest time to fix a leftover is while the team is still on site. A short Friday walk of everything marked done that week catches most of it.

None of this is complicated. The hard part is that it slows down the moment of saying “done”, and everyone on site, including the PM, wants that moment to be fast. The trick is to make confirmation quick and checking routine, so the discipline does not feel like punishment.

How to talk about it with your vendors

Vendors sometimes hear this as distrust. It helps to put it the other way round. A clear checklist protects them too: when QC passes, there is no argument about the stage payment, and they are not called back three weeks later for something nobody wrote down. Good carpenters like Imran usually prefer a fair, clear check to a vague promise and a late surprise.

Say it at the start of the project, put it in the vendor contract if you can, and then apply it to everyone the same way. The first time a stage is paid promptly because QC passed with photos, the conversation changes.

How Pakka handles it

Pakka is built around this exact gap. On the Ops Desk, site engineers work from WhatsApp. Nothing is marked done without the engineer’s own tap, so a voice note saying “kitchen done” becomes a suggestion until he confirms it. When all the tasks in a phase are confirmed, the phase waits for QC, and QC checklists ask for photo, measurement and document evidence.

A failed QC creates snags and rework tasks, each with an owner, and open snags hold the handover. A QC pass is what makes a vendor payment eligible on the Money Desk, and even then a named person approves the release, and the person who raised it cannot approve it. Pakka never pays anyone on its own and never holds your funds. It simply keeps reported, checked and payable as three separate steps.

Arjun’s Thursday call would still happen. It would just end with “ready for QC”, and the money would wait until someone had actually looked.