Ask any architect about their worst site disaster and the story almost always starts the same way: the site was building from the wrong drawing. A revision went out on email, the contractor's engineer had the old print, a wall came up where a niche should be, and the demolition cost more than the drawing management system that would have prevented it, which is to say, more than nothing, because there was no system. Working drawings are the legal and practical spine of your project, and most Indian practices manage them with folders, email attachments and hope. Let me lay out what proper working drawings management looks like, at the practice scale, without enterprise-software theatre.
The three failure modes of drawing chaos
Drawing problems on Indian sites cluster into three types, and it's worth naming them because each needs a different fix.
Superseded drawings in circulation. The classic. R2 is on site, R4 is current, and nobody can say who has what because issues went out over email, WhatsApp and a pen drive. The fix is an issue register: every transmission recorded, every recipient known, every old revision visibly marked superseded.
Unanswered site queries. The contractor calls with "boss, the beam is fouling the duct here, what do we do", the architect answers on the phone, nothing is written anywhere, and three weeks later the same question comes back with a different answer. The fix is queries pinned to the drawing itself, at the exact spot, answered in writing, visible to everyone thereafter.
Drawings disconnected from quantities and money. A revision changes scope, the BOQ doesn't follow, the client's budget expectation drifts from reality, and the gap lands on your fee conversation. The fix is structural: drawings, quantities and billing living in one system so a change in one visibly touches the others.
The drawing register: your single non-negotiable
If you adopt only one thing from this post, adopt a real drawing register. It's the master index of every drawing on the project, and here's the minimum structure that works:
| Column | What goes in it | Why it exists |
|---|---|---|
| Drawing number | A consistent numbering scheme per project and package | Everyone cites the same ID |
| Title and zone | What and where the drawing covers | Findable without opening files |
| Current revision | R0, R1, R2, with date | One glance answers "what's current" |
| Status | Draft, issued for approval, issued for construction, superseded | Prevents building from approval sets |
| Issued to and when | Contractor, consultants, client, with dates | Proof of transmission |
| Open queries | Count of unresolved pins on this drawing | Surfaces bottlenecks |
The "status" column deserves emphasis. Half the trouble on sites comes from a drawing that was issued for approval being treated as issued for construction. The register makes that distinction impossible to miss, and honestly, the discipline of maintaining a register changes team behaviour by itself, because issuing a drawing becomes a deliberate act instead of an email reflex.
Pins beat paragraphs
The single biggest quality-of-life upgrade in modern drawing management is the pinned comment. Instead of an email saying "in the third bedroom, near the window on the north wall, the switchboard location clashes with the wardrobe shutter swing", you drop a pin at the exact spot on the drawing and type two lines. The contractor sees the pin in context, replies in place, and the resolution stays attached to the location forever.
This matters double for site queries and snag-type observations during execution. A pinned query with a photo is unambiguous, and the thread of pins on a drawing becomes an honest history of every decision taken on that part of the building. In Designa, construction drawings live with the project and support exactly this, pins with comments and photos, so the answer to "why is the switchboard there" is one click deep, years later.
Revisions: the rules that keep sites safe
Revision discipline is procedural, and the procedure is short:
Revision rules for a safe site
- One current set per project, in the system, never "the latest is on someone's laptop"
- Every revision gets a number, a date and a one-line description of what changed
- Old revisions are marked superseded the moment the new one is issued, not eventually
- Issues are recorded: who received the revision, on which date, through the system
- Clouding or highlighting shows what changed, so the site doesn't re-read the whole sheet
- Site queries land as pins on the current revision, answered in writing
None of this needs enterprise document-control software. It needs a place where drawings, revisions and issues live together, and a team habit of using it. The habit is the hard part for about two weeks, and then it's just how the practice works.
Drawings connect to money, whether you like it or not
Here's the connection practices underrate. Working drawings drive quantities, quantities drive cost, and cost drives two money conversations: the client's budget and your own fees. A practice that bills stage fees, concept, design development, tender, construction, closes each stage with a drawing issue, which means your billing trigger is literally a drawing-management event. When the system knows the construction set was issued, raising the stage invoice should be one click, and in Designa it is, a compliant GST invoice from the agreed fee schedule, with the collection link attached. I've written the detailed billing side in billing and fee collection for architecture practices, and the invoice mechanics in how to turn a quote into a GST invoice in minutes.
The same logic runs downstream: revisions change scope, scope changes should update quantities and the client's cost plan, and the practices that keep this thread connected simply don't have the "but the drawing changed" billing dispute, because the record is continuous.
Choosing tools without over-buying
Do you need a dedicated CDE (common data environment) platform? If you're doing large institutional work with dozens of consultants, maybe. For the typical Indian practice, five to twenty people, residential, commercial, hospitality, the honest answer is that a connected workspace covering drawings with pins, specs and quantities, site updates, snags and billing does the job at a fraction of the cost and complexity, and your team will actually use it, which is the metric that matters. Registered practices working under the Council of Architecture framework, and firms straddling architecture and interiors, the community bodies like the Institute of Indian Interior Designers represent, need the drawing discipline and the studio operations in one place, because that's how their projects actually run. I've mapped the whole toolkit question in every tool a design studio needs and which you can skip, and for metro practices, the Mumbai-focused software guide adds the local context.
Frequently asked questions
What is working drawings management?
The system of registers, revisions, issue records and query handling that ensures a site always builds from the current drawing, and that every drawing decision is traceable.
How should drawing revisions be numbered?
A simple sequential scheme per drawing (R0, R1, R2) with dates and a one-line change description, plus a status marking whether the set is for approval or construction.
What is a drawing issue register?
A record of every drawing transmission: which drawing, which revision, to whom, on what date. It's your proof of what the site should have been building from.
Can Designa manage construction drawings?
Yes. Drawings live with the project, revisions supersede visibly, and site queries land as pins with comments and photos on the exact spot, connected to the same timeline as site updates, snags and billing.
Drawing chaos is one of those problems that feels cultural but is actually infrastructural, give the team one register, one current set and pins instead of paragraphs, and the culture follows in a fortnight. See drawings, pins, site updates and stage billing working as one thread at demo.designa.work, and the founding offer, one flat price for the whole practice billed in rupees, is at go.designa.work.