Imran is one of the best carpenters the firm works with. On a Friday afternoon at a 4BHK in Kharadi, Pune, he finishes the master bedroom wardrobe: eight feet wide, floor to loft, four hinged shutters in a beautiful matte laminate. He sends a photo to the site group. It looks great.
On Saturday morning the client visits. She stands in front of the wardrobe for a long moment, then opens WhatsApp on her phone and scrolls back to a message from two weeks ago, where she wrote: “Make this sliding, the bed is too close.” Underneath it, the designer had replied: “Done, Rev 2 updated.”
Rev 2 was updated. It was uploaded to the shared drive and sent to the PM. But the drawing Imran had been working from was the PDF in the site group, posted a month earlier. Rev 1. Hinged shutters. Nobody had sent Rev 2 to the group, and nobody had told the group Rev 1 was dead.
Four shutters, the hardware, the track that now needs a different loft detail, and two days of Imran’s time go into the rework. The client is polite about it. She also asks, carefully, whether the kitchen is being built from the right drawing.
Every drawing is correct, until it is not
The cruel thing about revision mistakes is that the person on site did nothing wrong. Imran built exactly what the drawing in front of him said, and he built it well. The drawing was correct the day it was made. It simply stopped being correct, and nobody told the people holding it.
In interiors, drawings change constantly, and they should. Clients see a render and change their mind. A site measurement reveals a beam. A material is out of stock. Each change is reasonable. The danger is not the change itself. It is that the old version stays alive in places nobody controls.
A drawing is never wrong on the day it is made. It becomes wrong quietly, in a phone, in a site group, in a printout taped to a wall, the day after something changes.
Where old drawings hide
If you walked through any active site today and asked to see the drawings people are working from, you would probably find several versions. Here are the usual hiding places:
- The site WhatsApp group, where Rev 1 was posted and never replaced or deleted.
- The carpenter’s phone, where he saved the PDF a month ago and opens it from his downloads.
- A printout taped to a wall, which nobody re-prints when a revision comes.
- A vendor’s inbox, where the shop drawing was made from an earlier version.
- The designer’s laptop, where “final”, “final_2” and “final_revised_new” all exist side by side.
None of these are marked as old. A PDF does not know it has been replaced. That is the heart of the problem: unless someone actively kills the old version, it looks exactly as valid as the new one.
What a wrong revision costs
Revision mistakes tend to be expensive because they are discovered late. By the time someone notices, the work is finished, the material is cut, and the client is standing in front of it.
| Four shutters in matte laminate, remade | ₹22,000 |
|---|---|
| Sliding track and hardware (new purchase) | ₹9,500 |
| Loft detail rework to take the track | ₹3,500 |
| Carpenter and helper, 2 extra days | ₹7,000 |
| Hinged hardware already fitted, mostly wasted | ₹3,200 |
| Delay to the room’s handover | 5 days |
| Direct cost of one old PDF | ₹45,200 |
Every figure is an illustrative example, not real project data. Laminate, hardware and labour rates vary widely by city and specification.
Forty-five thousand rupees for a single message that was not forwarded. And that is before the cost you cannot put in a table: a client who now wonders what else is being built from the wrong drawing.
There is also an argument waiting at the end. Who pays for the remade shutters? The designer says the revision was issued. The PM says it never reached site. The carpenter says he built to the drawing he was given, and he is right. Without a clear record of which version went where and when, the firm usually ends up paying, and the team ends up blaming each other.
The discipline that prevents it
Good firms do not avoid revisions. They make each revision unmistakable, and they make old versions visibly dead. Most of this can be done with simple habits, even before you use any software.
- Nothing goes to site before GFC. Good for construction means the design manager and the client have approved the set for building. Concept drawings, working drawings and renders are for discussion. Only GFC drawings go to the people with saws.
- Every revision gets a change note. Not just “Rev 2”. A one-line note on what changed: “Master wardrobe: hinged to sliding, loft detail revised.” The note travels with the drawing and goes to site.
- Mark old versions superseded. When Rev 2 is issued, Rev 1 is stamped SUPERSEDED, everywhere you control. Keep it for history, but nobody should be able to mistake it for the current one.
- One place for current drawings. Site should know exactly where to find the current set, and only the current set. If it is a folder, the folder holds only current GFC drawings, with old ones moved to an archive.
- Tell site when it changes. A revision is not issued until the people building it know. A short message to the engineer and the vendor, with the change note, is part of issuing the drawing.
- Ask site to confirm the revision. Before a big item is fabricated, the engineer confirms the revision number he is working from. Ten seconds. It would have saved Imran two days.
- Clean the group. When a new revision goes out, delete the old PDF from the site group, or reply to it clearly: “This is superseded, use Rev 2.”
Sharing drawings without losing them
There is a second risk with drawings that float around on WhatsApp: they leave. A detailed set of drawings is your design work. Forwarded to a contractor or another studio, it can be priced against you or simply copied.
Two simple protections help. Share drawings as images or watermarked files rather than editable originals. And put the name of the person you sent it to on the watermark. People are much less likely to forward a drawing with their own name across it.
When the client changes their mind on site
Clients often ask for changes directly on site, to the engineer or the carpenter. “Can we make this drawer deeper?” A helpful carpenter says yes. Now the built item matches neither drawing.
Agree a simple rule at the start of every project: changes requested on site are welcome, and they go back through the designer as a revision, with a note, before they are built. It protects the client too, because their change is recorded and priced instead of being a favour nobody remembers at the final bill.
How Pakka handles it
Pakka’s Design Desk was built for Imran’s Friday. Every revision needs a note on what changed, the note goes to site, and older versions are kept with full history and clearly marked superseded. The door to production stays shut until the design manager and the client approve the GFC set, and on the Ops Desk, site works only from drawings that have been pushed to production.
The client marks up drawings on her phone, so “make this sliding” is a tracked change request, not a WhatsApp message two weeks deep. Shared drawings are watermarked with the viewer’s identity and the original file is never sent. And when an engineer is unsure, he can ask the drawings a question on WhatsApp and get the answer with the drawing page attached, from the current set.
Imran would still have built a beautiful wardrobe. It would just have had sliding shutters.