Drawing Revision Control Software: A 2026 Guide for Indian Sites

If you have ever had a bar-bending gang stop mid-shift to ask "Boss, which drawing is final?", you already know why drawing revision control software matters. On most Indian sites, drawings still travel by WhatsApp forward, email thread and rolled-up A1 print. One missed update — an opening shifted 150 mm, a revised column schedule, a plumbing shaft moved half a metre — quietly becomes hacking, rework, and a claim nobody wants to argue about eighteen months later.

This guide is deliberately narrow. It is not about where to store drawings or how to organise folders — that is the job of a broader construction drawing management system. This is about the revision layer: how revisions are numbered, how status is declared, how superseded sheets are killed off, how transmittals prove issue, and how you reconstruct months later exactly who was holding which revision on the day the wall went up.

What drawing revision control software actually controls#

Storage software answers "where is the drawing?". Revision control answers four harder questions:

1. Which revision is current, and is it executable? Not the newest upload — the newest upload with an approved status.
2. What changed since the last revision? Clouded, dated, and attributable.
3. Who was issued this revision, when, and did they confirm receipt? A distribution record, not a chat history.
4. What was the state of the drawing on a given past date? Reconstructable from an audit trail nobody can edit after the fact.

Everything else — markup, folders, search, mobile viewing — is drawing management. These four are revision control, and they are the ones that show up in a dispute.

The anatomy of a revision: what "Rev" means on an Indian drawing#

Most teams treat the revision letter as a label the consultant types. It is actually a formally specified field.

IS 962 : 1989, the Bureau of Indian Standards code of practice for architectural and building drawings, is explicit. Clause 4.2.1 requires drawings to record all alterations or revisions made from time to time, with a revision panel carrying the revision number or letter, the date, the zone or location affected, a brief record of the change, and the dated initials of the approving authority. Clause 4.2.2 says that panel must sit contiguous with the title block and read from the bottom upwards, and 4.2.4 that the number and date of revision shall be added in it. Clause 4.2.3 leaves the numbering scheme itself to each organisation — precisely why every consultant on your project uses a different one. For title block contents, clause 4.5.1 refers you onward to IS 11665 : 1985. You can read the code in full via the public copy of IS 962 : 1989.

Two things follow. A drawing without a populated revision panel is non-compliant with the Indian code of practice, not merely untidy. And because BIS deliberately does not mandate a numbering scheme, your contract has to fix one — the software will not do it for you.

Revision is not the same as version#

This trips up almost every team moving from Drive folders to a real system, and the clearest published explanation comes from Oracle Aconex, a common data environment used on large Indian infrastructure jobs.

Aconex's own help documentation on version control and the audit trail spells this out, and adds the point that actually matters for disputes: historical versions are retained and cannot be deleted, so superseded content stays viewable rather than disappearing.

The practical lesson is simple. The revision is your promise to the site. The version is the system's memory of what you did. Software that only gives you version numbers has not given you revision control.

Revision numbering conventions that survive an audit#

Pick one scheme, write it into the drawing issue protocol, and make every consultant sign up to it before the first sheet arrives.

Option A: the ISO 19650 style (preliminary and contractual)#

The ISO 19650 series is the international framework for information management on built assets. The familiar status codes — S0 to S7, A1, B1, CR — actually come from the UK National Annex to BS EN ISO 19650-2, not the ISO text itself, and are set out in the UK BIM Framework guidance on the common data environment. Revision codes pair with them: P01, P02, P03… for preliminary revisions while the container is work-in-progress or shared and non-contractual, and C01, C02, C03… for contractual revisions once information is published and authorised.

Status codes broadly run: S0 initial status; S1 suitable for coordination; S2 suitable for information; S3 suitable for review and comment; S4 suitable for stage approval; S6 and S7 for information model authorisation. A1 and An mark authorised issues carrying a contractual revision; B1 and Bn mark a partial sign-off with comments, which keeps a preliminary revision; CR marks the as-constructed record. The table has changed between National Annex editions — S5 was withdrawn, and the S4 and S5 wording differs between the earlier CDBB version and the 2021 revision — so cite the specific edition your project information standard adopts rather than an internet table.

As of mid-2026 we could not find a BIS-published Indian adoption of the ISO 19650 series. Indian projects that use it reference the ISO documents directly, usually because a client's requirements or an international consultant's execution plan demand it. Treat ISO 19650 here as a contractual obligation you may inherit, not a statutory one.

Option B: the Indian site-practice style (IFA / IFC / GFC / AFC)#

Most Indian residential, commercial and industrial jobs run on a shorter vocabulary: For Approval (IFA), Issued for Construction (IFC), Good for Construction (GFC), Approved for Construction (AFC), and As-Built. That works fine — provided you accept one uncomfortable fact: these terms have no single legal definition in India. GFC in one contract is IFC in another, and Indian contract formulations tend to define GFC drawings by reference to a notice issued under the employer's requirements rather than any universal meaning. So write the definitions into your drawing issue protocol, with a rule a site engineer can recite: only a sheet carrying an executable status may be built from; everything else may be read, commented on and planned against, but not executed.

Numbering rules that hold up#

• Choose letters (A, B, C) or numbers (01, 02, 03). Never mix, and never let a consultant restart numbering after a stage change without a documented reset rule.
• Increment the revision only when the drawing leaves your organisation. Internal iterations are versions, not revisions.
• Never reuse a code. "Rev 04 revised" is not a revision code; it is a future dispute.
• Never issue a drawing whose file name revision disagrees with its title block. If those diverge, the register is fiction.
• Start from IS 962's own discipline prefixes — clause 4.3.2 recommends A, S, C, P, E and M for architectural, structural, constructional, plumbing, electrical and mechanical series.

A file naming format you can adopt this week#

Use a fixed count of hyphen-separated fields, always in the same order, with no hyphens inside a field value:

Project - Site - Discipline - DocType - Zone - Level - Sheet - Revision - Status

Examples:

• SS-PUN-ARC-DR-TWRA-L07-101-R04-IFC.pdf
• SS-PUN-STR-DR-TWRA-B01-SLAB-R02-GFC.pdf
• SS-PUN-MEP-SHP-PODM-L02-FP03-R01-IFA.pdf

Two disciplines are non-negotiable. Every field is always present — use NA rather than dropping a field, so column positions stay stable when you split the name in Excel or sort the folder. And the status sits in the file name, so a PDF that has escaped into a WhatsApp group still declares what it is. If your project still runs on forwards, that one change buys more safety than any other, though the real fix is moving drawing issue off chat entirely.

Superseded stamp discipline: killing the old sheet properly#

Uploading a new revision does not remove the old one from site. Superseding is a physical process as much as a digital one.

In the system. The moment a new revision is published, the prior one must be automatically flagged superseded, dropped from default search and download lists, and reachable only through an explicit "show superseded" toggle. If a site engineer can accidentally open Rev 03 while Rev 04 exists, the software is not doing revision control.

On the PDF. Apply a diagonal watermark reading SUPERSEDED with the superseding revision and date — "SUPERSEDED BY R04, 12 JUN 2026" — burned into the file, not overlaid in the viewer. It has to survive a download and a reprint, because that is exactly how old sheets travel.

On paper. Indian sites will keep printing, and that is fine as long as prints are controlled:

• Print controlled copies with a stamped copy number, the issue date, and the revision in 40 mm letters at the top of the sheet.
• Log every print against the register — sheet, revision, copy number, who took it, where it went.
• Run a superseded sweep every Friday: the site engineer walks the contractor cabin, the bar-bending yard, the shuttering store and each subcontractor's cabin, physically pulls old prints, and marks the register.
• Destroy, do not archive on site. One archived paper set in a cabin drawer becomes the set someone builds from.

On the change itself. Insist consultants cloud the changed area, tag it with a revision triangle, and describe the change in one plain line in the revision panel — "Toilet shaft shifted 300 mm east, grid C4–C5" beats "Revised as per coordination".

Transmittals: the difference between sending and issuing#

Sending a drawing is an act of communication. Issuing a drawing is an act of record. A transmittal converts one into the other: a numbered instrument stating what was sent, in which revision, to whom, on what date, and why.

Aconex's documentation draws the distinction sharply. Documents attached to ordinary mail are just attachments — they never enter the recipient's document register, and none of the document details travel with them. Documents sent by transmittal are added to the recipient's register with all details, including revision and revision date, captured; the transmittal then links back into the document's event log.

Whatever tool you use, a usable transmittal has to carry:

For any package where a wrong revision costs real money — structural GFC sets, column schedules, bar bending schedules, MEP coordination sheets, shop drawings — make the transmittal mandatory and the acknowledgement a gate. No acknowledgement from the subcontractor's authorised signatory, no work front released. This is a discipline a broader document control system should enforce across drawings, specifications and correspondence alike.

Who saw which revision: the audit trail you will need#

Two years after handover, someone will ask a question you cannot answer from memory. The audit trail answers it, and at minimum needs three layers — matching the structure Aconex describes:

• Document history — every version and revision of the sheet, retained, with no deletion permitted.
• Event log — who changed what and when, including metadata changes, with links to the transmittals that distributed each revision.
• Correspondence thread — who was in the conversation, what was attached, and when.

The test to run on any product demo is not "can you show me version history?" It is: pick a date six months ago and a specific subcontractor, and tell me exactly which revision of sheet STR-101 they were holding on that date, and prove it. Most tools that market "version control" cannot answer that in under a minute. That gap is the whole product category.

Two Indian-specific reasons to care. Arbitral tribunals here take notice discipline seriously — a genuine delay caused by late or wrong drawings can still fail if the contractual notice was late or missing, and the drawing register is where the notice clock is evidenced. And HKA's CRUX Insight programme, whose eighth annual report draws on more than 2,200 distressed projects across 114 countries, publishes a dedicated India series on late approvals and design issues as recurring dispute causes — exactly the categories drawing-issue records speak to.

What wrong revisions actually cost#

The classic number comes from the 2018 PlanGrid and FMI "Construction Disconnected" study of 599 construction professionals: respondents reported spending about 5.5 hours a week hunting for project data such as revised drawings, and the study attributed roughly 48% of US rework to poor data and miscommunication (52% globally). That research is now eight years old and US-weighted, so treat it as directional rather than a benchmark.

On rework cost itself, the better-supported figures come from the Construction Industry Institute, which puts direct field rework at around 5% of total construction cost on average with a long tail — a 90th percentile above 12%. The Navigant Construction Forum's review lands near a 5% median with a likely range of roughly 4% to 6%, and argues actual costs run higher because rework is systematically under-reported.

Why this bites harder in 2026: input costs are no longer falling to absorb your mistakes. JLL's Construction Cost Guide India 2026, published in March 2026, projects that the Labour Codes brought into force in November 2025 will push labour costs up 5–12%, partly offset by 2–5% of GST savings, with steel, aluminium and copper up 2–4%. When labour is the fastest-rising line item, rework — which is almost pure labour — is the most expensive mistake on the project.

Three ways it goes wrong on Indian sites#

Residential tower, Pune — the shaft that moved. Consultant issues Rev 06 with a toilet shaft offset 300 mm to clear a beam. Site is working off a Rev 05 print pinned in the contractor cabin. Blockwork goes up across four floors before MEP sleeves fail to align. Cost: hacking, block rebuild, waterproofing redo, tiling pushed by a fortnight on those floors — plus a plumbing subcontractor with a legitimate idle-labour claim. The transmittal record decides who pays.

Warehouse, NCR — the opening nobody told the foreman about. A structural sheet relocates a services opening. The fabricator receives the revised PDF; the site foreman, who is not on the consultant's distribution list, does not. Core-cutting proceeds at the old location, main reinforcement is exposed, and a patch repair with consultant sign-off follows. The failure is not the drawing — it is a distribution list with one missing name.

Villa cluster, Hyderabad — the rebar spacing change. A staircase reinforcement detail changes spacing on a new revision; the shuttering team is working from an older print. The error surfaces at pre-pour inspection, which is the good outcome — caught after pour, it is a demolition. This is the case for wiring drawings into the task and inspection workflow instead of a separate document silo: the pre-pour checklist should show the governing revision, not just the activity.

The RERA angle most builders miss#

For residential projects, drawing revision control is not purely a productivity question.

Section 11(3) of the Real Estate (Regulation and Development) Act, 2016 requires the promoter, at the time of booking and issue of the allotment letter, to make the sanctioned plans and layout plans with approved specifications available to the allottee, by display at the site or such other place as the Authority specifies. Section 14 requires the project to be developed in accordance with those sanctioned plans; minor alterations to a particular apartment need that allottee's prior consent, and changes to the project's sanctioned plans require the written consent of at least two-thirds of the allottees.

The operational consequence is direct: you must be able to distinguish, at any point, between the sanctioned set and the working set — and show when a change crossed from one to the other. A revision log showing a design change executed on site without the corresponding sanctioned-plan amendment is a compliance problem, not just a documentation gap. As-built and completion drawing handover requirements typically sit in state RERA rules and the model agreement for sale rather than the central Act, so check your state's position. Broader obligations are covered in our guide to RERA compliance in project management.

Evaluation checklist: what to test in the demo#

Do not ask whether a feature exists. Ask the vendor to perform the task in front of you.

Revision integrity and status gating#

• Publish a new revision and show the previous one automatically flagged superseded and dropped from default lists, with the watermark surviving a download and reprint.
• Attempt to issue a sheet whose file-name revision contradicts its title block, and attempt to delete a revision. One should be flagged, the other impossible.
• Filter to executable status only, and show a site user's default view contains nothing else.

Transmittals and reconstruction#

• Issue to a subcontractor and produce the transmittal PDF with sheet, revision, revision date, status, recipient and reason. Confirm it cannot be edited or recalled after sending.
• Show a pending-acknowledgement list you could chase at Monday's meeting.
• Pick a past date and a subcontractor. Produce the revision they held and the transmittal that put it in their hands.
• Export the full register and audit trail at project close, without vendor assistance.

Site reality#

• Open a 30 MB structural PDF on a three-year-old Android phone on a slow connection, then again in basement 2 with no signal — genuine offline access is the difference between adoption and shelfware.
• Have a site engineer, not the vendor, mark up and reply to a drawing query unassisted.

One 2026 caveat on pricing research: Autodesk has folded Construction Cloud into the Autodesk Forma brand and reshuffled its document management tiers, so older comparison articles may not match your quote. Ask any vendor for a written, GST-inclusive, per-user figure against your actual user count rather than trusting aggregator listings.

A 30-day rollout that does not stop work#

Week 1 — fix the standard, not the software. Write one page: the revision scheme, the status vocabulary and which statuses are executable, the file naming format, and the drawing issue protocol. Circulate it to every consultant and subcontractor, and get the architect and structural consultant to confirm compliance in writing. Load the current register as-is.

Week 2 — one package only. Pick structural GFC for slabs and columns, or MEP coordination for a typical floor, and move it fully in, superseded flags and all. Record a baseline: "which revision?" calls per day, and how long it takes to produce the current revision of a named sheet.

Week 3 — turn on transmittals. Stop issuing that package by chat or email. Every issue goes out as a transmittal, with acknowledgement required from a named person per subcontractor. Start the Friday superseded sweep. Expect resistance in week 3; it passes.

Week 4 — enforce and extend. Make it a written site rule that only a system-hosted executable revision may be built from, and that no work front is released without an acknowledged transmittal. Then extend to the next package and re-measure. If "which revision?" calls have not roughly halved, the problem is enforcement, not tooling.

Where SiteSetu fits#

SiteSetu's drawings module is built for this workflow on Indian sites: a drawing register with revision history, controlled issue to site engineers and subcontractors, superseded handling, and offline access on ordinary Android phones — with drawings sitting alongside the tasks and quality checks they govern rather than in a separate document island. That last part matters, because the failures in this article almost always happen at the seam between the drawing and the work.

The honest answer, though, is that the tool is the smaller half. The habit is the larger one: one register, one executable revision, one transmittal per issue, one sweep a week.

FAQs#

Is Google Drive or WhatsApp enough for drawing revision control?#

They handle storage and speed, but not the two things revision control exists for: preventing execution on a non-approved status, and proving who received which revision on which date. A folder can hold a superseded file; it cannot stop someone opening it or watermark it on download. If your project has subcontractors, claims risk or RERA exposure, you need an audit trail nobody can edit after the fact.

Should we number revisions with letters or numbers?#

It matters far less than consistency. The common convention is letters (A, B, C) for pre-construction issues and numbers once the drawing is issued for construction, while ISO 19650 practice uses a letter prefix with two digits — P01 for preliminary and C01 for contractual revisions. Pick one scheme, write it into your drawing issue protocol before the first sheet arrives, and never let a consultant restart the sequence without a documented reset rule.

What is the difference between a revision and a version?#

A revision is metadata a person enters, and it should match what is printed in the title block — Oracle documents Aconex's revision field as free text the system does not validate. A version is a system-generated counter that increments on every change to the record, including a pure metadata edit, and it exists to make the audit trail complete. Site teams care about revisions; auditors and tribunals care about versions.

Is a revision panel legally required on drawings in India?#

IS 962 : 1989, the BIS code of practice for architectural and building drawings, requires drawings to record all alterations and revisions, with the revision number and date entered in a revision panel placed contiguous with the title block and read from the bottom upwards. It leaves the numbering scheme itself to each organisation, which is why your contract has to fix one. It is a code of practice rather than a penal statute, but on a disputed project it is the benchmark your drawings will be measured against.

How do we handle subcontractors who insist on paper drawings?#

Do not fight it — control it. Keep the software as the master record, print controlled copies with a stamped copy number and the revision in large type, log every print against the register, and run a physical superseded sweep every Friday across the contractor cabin, the yard and each subcontractor's cabin. Destroy old prints rather than archiving them on site.

Final takeaway#

Drawing revision control is not bureaucracy. It is the difference between finding a mistake at pre-pour inspection and finding it with a breaker in your hand.

Start with one page of standard, one package, and one rule: only the current executable revision gets built, and every issue leaves a record. Everything else can wait until that habit sticks.