1. Introduction

Failure to enforce version control on documents is an important issue in contract administration, construction projects, infrastructure development, banking, financial institutions, procurement, project management, legal proceedings and corporate governance.

Document version control refers to the systematic process of creating, identifying, reviewing, approving, issuing, modifying, storing and maintaining different versions of documents so that all concerned persons use only the correct, authorised and latest applicable version.

Failure to enforce version control occurs when an organisation does not maintain proper control over different versions of documents, resulting in the use, circulation or implementation of outdated, unauthorised, modified or inconsistent documents.

This may lead to serious contractual, financial, operational and legal consequences.

For example, in a construction project, an engineer may issue a revised structural drawing changing the foundation specifications. However, due to the absence of proper version control, the contractor continues construction using the earlier drawing.

This may result in:

Execution of work according to outdated specifications.

Structural defects or quality problems.

Additional expenditure and rework.

Disputes regarding contractual responsibility.

Delay in project completion.

Difficulty in determining which document was officially approved.

Disputes concerning liability for defective work.

The fundamental legal principle is that contractual and operational decisions must be based on authentic, authorised and applicable documents. An organisation must maintain adequate systems to establish the authenticity, approval status, revision history and effective date of documents relied upon for official purposes.

The following discussion is primarily based on Indian law.

2. Meaning of Document Version Control

Document version control is a formal mechanism through which every document is assigned a unique identification number, revision number, date and approval status.

It ensures that any amendment or modification is properly recorded and that the latest approved document is made available to the concerned persons.

A properly controlled document generally contains:

Document identification number.

Document title.

Revision or version number.

Date of preparation.

Date of approval.

Name of the person preparing the document.

Name of the reviewing authority.

Name of the approving authority.

Description of modifications.

Effective date of the revised version.

Distribution and circulation details.

Record of superseded versions.

Example

Suppose a government department issues a construction drawing for a bridge project.

The original drawing is identified as:

Drawing No. BR-102

Revision 00

Issued: 1 January 2026

Original foundation design.

Drawing No. BR-102

Revision 01

Issued: 15 February 2026

Revised foundation design approved by the competent authority.

Drawing No. BR-102

Revision 00 – Superseded

The original drawing must no longer be used for construction after the revised drawing becomes effective.

If the contractor continues using Revision 00 after Revision 01 has been formally approved and issued, it may result in defective execution and contractual disputes.

The issue is not simply that two documents exist. The real problem is the failure to establish which document is authoritative and applicable.

3. Meaning of Failure to Enforce Version Control

Failure to enforce version control means that the organisation does not effectively regulate the creation, modification, approval, circulation and use of documents.

It may occur in the following circumstances:

Different departments use different versions of the same document.

Revised drawings are circulated without formal approval.

Outdated documents are not withdrawn or marked as superseded.

Changes are made without recording the revision history.

Unauthorised persons modify official documents.

The date and authority of approval are not recorded.

Original documents are overwritten without preserving earlier versions.

Electronic files are circulated through email or messaging applications without proper identification.

The organisation cannot establish which version was actually relied upon for a decision.

There is no centralised document management system.

The central concern is the inability to establish the authenticity, authority and applicability of the document at the relevant point in time.

4. Importance of Document Version Control

A. Ensuring authenticity

Version control helps establish whether a document is genuine, approved and issued by the competent authority.

B. Preventing unauthorised modifications

It prevents employees, contractors or other persons from making changes without the necessary approval.

C. Maintaining contractual compliance

It ensures that parties execute their contractual obligations according to the applicable approved documents.

D. Avoiding financial losses

It prevents unnecessary expenditure arising from rework, incorrect instructions, outdated drawings and inconsistent specifications.

E. Establishing accountability

Revision histories help identify who prepared, reviewed, approved and circulated a particular document.

F. Maintaining audit trails

It provides evidence of the sequence of modifications and decisions.

G. Supporting legal proceedings

Proper version control helps establish which document was operative when a particular contractual decision or activity occurred.

5. Legal Framework Governing Document Version Control in India

There is no single Indian statute that imposes a universal document-version-control procedure on every organisation. However, several statutory provisions govern document authenticity, execution, electronic records, contractual compliance and evidentiary reliability.

A. Section 37 of the Indian Contract Act, 1872 – Obligation to Perform Contractual Promises

Section 37 requires parties to perform their contractual promises unless performance is dispensed with or excused under the law.

Application:

Where a contract incorporates approved drawings, specifications, technical schedules or revised instructions, the parties must comply with the applicable contractual documents.

If an organisation fails to communicate an approved revision and continues to rely upon an outdated version, disputes may arise regarding the performance of contractual obligations.

B. Section 73 of the Indian Contract Act, 1872 – Compensation for Loss or Damage

Section 73 provides compensation for loss or damage arising naturally from a contractual breach or which the parties knew was likely to result from the breach.

Application:

Where failure to communicate or enforce a revised document causes defective execution, additional expenditure, delay or rework, the affected party may claim compensation if it establishes:

The contractual breach.

The actual loss suffered.

The causal connection between the breach and the loss.

The recoverability of the loss under applicable law.

C. Sections 61, 62 and 63 of the Bharatiya Sakshya Adhiniyam, 2023 – Electronic and Digital Records

The Bharatiya Sakshya Adhiniyam, 2023 recognises electronic and digital records as documents and provides the framework for proving their contents.

These provisions are important where documents are maintained electronically, including:

PDF drawings.

Digital contracts.

Electronic correspondence.

Document management system records.

Revision histories.

Electronic approval records.

Digital project files.

Application:

An organisation relying on electronic documents should maintain appropriate records establishing their origin, integrity, modification history and authenticity.

D. Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 – Admissibility of Electronic Records

Section 63 deals with the admissibility of electronic records and prescribes conditions for proving computer output and electronic evidence.

It is particularly relevant where a party relies upon:

Email communications.

Electronic approval records.

Digital drawings.

Document management system extracts.

Electronic revision histories.

Computer-generated audit trails.

The statutory requirements concerning certificates and electronic evidence must be followed where applicable.

E. Section 5 of the Information Technology Act, 2000 – Legal Recognition of Electronic Signatures

Section 5 provides legal recognition to electronic signatures, subject to the prescribed requirements.

Application:

Where electronic documents require formal approval, an appropriately authenticated electronic signature can help establish the identity of the approving authority and the authenticity of the approval.

However, merely inserting a scanned signature into a document does not automatically establish a valid electronic signature under the Act.

F. Section 7 of the Information Technology Act, 2000 – Retention of Electronic Records

Section 7 deals with the retention of electronic records where any law requires documents, records or information to be retained.

It recognises electronic retention where prescribed conditions are satisfied, including accessibility, preservation of the original format or an accurately representable format, and availability of relevant particulars.

Application:

Organisations maintaining electronic records should ensure that approved documents and their relevant revision histories remain accessible and capable of verification.

G. Section 21 of the General Clauses Act, 1897

Section 21 provides that the power to issue notifications, orders, rules or bye-laws includes the power to add to, amend, vary or rescind them, subject to the statutory context.

This provision may be relevant when examining amendments to formal government orders or notifications.

It does not, by itself, establish a universal document revision procedure for private contractual documents.

6. Detailed Explanation of Common Failures in Document Version Control

6.1 Use of Outdated Documents

One of the most common failures occurs when employees, contractors or departments continue using documents that have already been revised or superseded.

Example:

A department approves a revised technical specification for a project.

However, the procurement department continues issuing purchase orders based on the earlier specification.

This may result in:

Procurement of incorrect materials.

Rejection of supplied materials.

Additional expenditure.

Delay in execution.

Disputes regarding responsibility.

Legal implication: The organisation may face contractual disputes if the use of outdated documents results in non-compliance with approved specifications or contractual obligations.

6.2 Unauthorised Modification of Documents

Documents may be altered without approval from the competent authority.

For example:

Modification of contractual payment terms.

Changes in technical specifications.

Alteration of quantities.

Changes in approved drawings.

Modification of delivery schedules.

Changes in financial calculations.

Such modifications may create disputes regarding the validity and enforceability of the altered document.

An unauthorised revision does not automatically become contractually binding merely because it has been circulated or implemented internally.

6.3 Failure to Maintain Revision History

Every material modification should be recorded in a revision history.

A revision register should ordinarily contain:

If the revision history is not maintained, it may become difficult to determine which version was applicable when a particular decision was made.

6.4 Failure to Withdraw Superseded Documents

When a new version is approved, the earlier version should be appropriately marked as superseded and withdrawn from active use.

Failure to do so may result in different departments using different versions simultaneously.

This creates inconsistency and increases the possibility of operational and contractual errors.

6.5 Failure to Obtain Proper Approval

A revised document should be approved by the person or authority empowered under the relevant delegation of powers or contractual arrangement.

For example, a site engineer may be authorised to recommend a change but may not have authority to approve a variation in the contract price.

If the change is implemented without the required approval, the organisation may face disputes regarding the validity of the instruction and liability for resulting expenditure.

6.6 Failure to Maintain Electronic Audit Trails

In electronic document management systems, modifications should be traceable.

An effective audit trail should record:

Identity of the person making the change.

Date and time of modification.

Previous version.

Revised version.

Nature of the change.

Approval details.

Date and time of issue.

Persons to whom the revised document was circulated.

Without such records, it may be difficult to establish whether an electronic document was altered, when it was altered and by whom.

6.7 Failure to Control Document Circulation

A document may be properly revised and approved but may not reach all the concerned departments.

For example, the engineering department may receive the revised drawing while the contractor and quality-control department continue using the earlier drawing.

This indicates a failure in document distribution and communication controls.

6.8 Failure to Preserve Original Documents

Replacing an earlier version with a revised file without retaining the original creates difficulties in establishing the sequence of decisions.

Organisations should preserve both superseded and current versions, with clear status identification and access restrictions.

This is particularly important where documents may be required for audit, arbitration, litigation or investigation.

7. Important Indian Supreme Court Case Laws

The following judgments are relevant to document authenticity, proof of documents, electronic records, unauthorised changes and evidentiary reliability.

There is an important distinction: Indian courts have not laid down one universal rule specifically titled "document version control". The following decisions establish legal principles that apply to disputes involving conflicting versions, modified documents, missing originals and electronic revision histories.

Case 1. Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020)

SUPREME COURT OF INDIA · (2020) 7 SCC 1

Facts of the case:

The dispute arose from an election petition involving the admissibility of electronic records.

The parties relied upon electronic evidence, including video recordings and other electronic material.

The question before the Supreme Court was whether electronic records could be admitted in evidence without satisfying the statutory requirements prescribed under Section 65B of the Indian Evidence Act, 1872.

Judgment:

The Supreme Court held that a certificate under Section 65B(4) was generally a mandatory condition for admitting secondary electronic evidence under the applicable provisions of the old Evidence Act.

The Court explained the importance of establishing the source and authenticity of electronic records.

It also clarified that the certificate could be produced subsequently in appropriate circumstances, subject to the court's directions.

Important legal principles:

Electronic records must satisfy applicable statutory requirements for admissibility.

The authenticity and source of electronic records are important.

Electronic evidence must be capable of verification.

The integrity of electronic records is essential in legal proceedings.

Relevance to failure to enforce version control:

This judgment is particularly relevant where an organisation maintains documents electronically and different versions are circulated through email, document management systems or other electronic platforms.

For example, if a contractor relies upon a revised drawing stored in an electronic system, the organisation should be able to establish:

The original electronic file.

The date of revision.

The identity of the person who made the change.

The approval of the revised document.

The authenticity of the version produced in evidence.

Failure to maintain such information may create difficulties in proving which version was authentic and operative.

Significance: This is an important authority for maintaining the integrity and authenticity of electronic documents.

Note: The Bharatiya Sakshya Adhiniyam, 2023 now governs applicable proceedings instituted under the new law. The decision remains relevant to understanding electronic evidence under the former Section 65B framework.

Case 2. Anvar P.V. v. P.K. Basheer (2014)

SUPREME COURT OF INDIA · (2014) 10 SCC 473

Facts of the case:

The matter concerned the admissibility of electronic evidence in an election dispute.

The parties sought to rely upon electronic records without complying with the special statutory requirements governing electronic evidence.

Judgment:

The Supreme Court held that Section 65B of the Indian Evidence Act was a special provision governing the admissibility of electronic records.

The Court explained that electronic records produced as computer output must comply with the statutory requirements prescribed under that provision.

Legal principle:

The source and authenticity of electronic records must be established in accordance with the applicable evidentiary law.

Relevance to document version control:

Where an organisation relies upon different electronic versions of a contract, drawing, approval or instruction, it must be able to establish the authenticity of the electronic records.

For example, if two versions of a contract contain different payment terms, the organisation should maintain reliable records establishing which version was executed and approved.

An unauthenticated electronic copy may face evidentiary objections.

Case 3. H. Siddiqui (Dead) by LRs v. A. Ramalingam (2011)

SUPREME COURT OF INDIA · (2011) 4 SCC 240

Facts of the case:

The dispute involved the production and proof of documentary evidence in a property-related matter.

A party relied upon a copy of a document rather than producing the original document.

The question concerned the circumstances in which secondary evidence could be admitted.

Judgment:

The Supreme Court explained that secondary evidence cannot be admitted unless the conditions prescribed under the Evidence Act are satisfied.

The party seeking to rely upon secondary evidence must establish the factual foundation for its admissibility.

The Court also clarified that merely marking a document as an exhibit does not automatically prove its contents.

Legal principle:

Documents must be proved in accordance with the applicable rules of evidence.

Relevance to version control:

Suppose an organisation produces a photocopy or scanned copy of an approved contract but cannot produce the executed original or explain the origin of the copy.

If multiple versions of the document exist, the organisation may face difficulty in establishing which version is authentic.

This judgment reinforces the importance of preserving original documents and maintaining reliable records of subsequent modifications.

Case 4. Shalimar Chemical Works Ltd. v. Surendra Oil & Dal Mills (Refineries) (2010)

SUPREME COURT OF INDIA · (2010) 8 SCC 423

Facts of the case:

The dispute concerned the admissibility of documentary evidence and the production of copies instead of original documents.

The Supreme Court considered whether secondary evidence could be admitted without satisfying the statutory conditions.

Judgment:

The Court emphasised that admissibility of documentary evidence should be decided at the appropriate stage.

It held that the requirements governing secondary evidence cannot be bypassed merely by marking a document as an exhibit.

Legal principle:

The authenticity and admissibility of documents must be examined in accordance with law.

Relevance to version control:

Where an organisation maintains multiple copies of the same document, it must establish which copy represents the approved and operative version.

An uncontrolled photocopy or scanned document cannot automatically be treated as the authoritative version merely because it is available in the project file.

Case 5. LIC of India v. Ram Pal Singh Bisen (2010)

SUPREME COURT OF INDIA · (2010) 4 SCC 491

Facts of the case:

The dispute involved documentary evidence produced in proceedings relating to an employment dispute.

The Supreme Court examined the evidentiary value of documents that had been produced and marked without proper proof.

Judgment:

The Court explained that mere production or marking of a document as an exhibit does not automatically establish its contents or authenticity.

The party relying upon a document must prove it in accordance with the applicable rules of evidence.

Legal principle:

Admission of a document as an exhibit and proof of its contents are distinct legal requirements.

Relevance to version control:

This principle is important where an organisation produces several versions of:

Contracts.

Financial statements.

Technical specifications.

Administrative approvals.

Project drawings.

Internal instructions.

The organisation must establish not merely that the documents exist, but also that the particular version relied upon was properly approved and applicable.

Case 6. Sait Tarajee Khimchand v. Yelamarti Satyam (1972)

SUPREME COURT OF INDIA · (1972) 4 SCC 562

Facts of the case:

The dispute involved documentary evidence and the question whether mere production of documents was sufficient to prove their contents.

Judgment:

The Supreme Court explained that merely producing a document and assigning it an exhibit number does not establish its contents.

The document must be proved in accordance with law.

Legal principle:

Production, marking and proof of a document are different matters.

Relevance to version control:

This judgment is useful where an organisation relies upon a particular version of a document without establishing its approval, authenticity or applicability.

For example, merely producing a revised drawing does not necessarily establish that the drawing was formally approved or issued for execution.

Case 7. State of Maharashtra v. Dr. Praful B. Desai (2003)

SUPREME COURT OF INDIA · (2003) 4 SCC 601

Facts of the case:

The matter concerned the use of video conferencing for recording evidence.

The question was whether evidence could be recorded through video conferencing under the applicable procedural law.

Judgment:

The Supreme Court recognised the use of video conferencing as a permissible method of recording evidence.

The Court adopted an interpretation of procedural provisions that accommodated technological developments.

Relevance to document version control:

This decision provides broader support for the recognition of technology-based procedures in legal processes.

In modern organisations, electronic document management systems, digital approvals and electronic audit trails play an important role in establishing the authenticity and history of documents.

However, the case does not directly prescribe version-control requirements.

8. Practical Illustration: Failure to Enforce Version Control in a Construction Contract

Consider the following hypothetical situation.

A government department awards a construction contract for ₹50 crore.

The original approved drawing is issued on 1 January 2026.

Subsequently, due to a change in structural design, the competent authority approves a revised drawing on 1 March 2026.

However, the revised drawing is not properly circulated to the contractor and site engineers.

The contractor continues construction using the original drawing.

After completion of a portion of the work, the department identifies deviations from the revised design.

The department alleges that the contractor has executed defective work.

The contractor, however, claims that it followed the drawing originally supplied by the department.

Documents available

Legal and contractual consequences

The department may face difficulty proving that the revised drawing was properly communicated.

The contractor may argue that it acted on the basis of the officially supplied document.

The department may face claims for additional expenditure and extension of time.

The responsibility for defective execution may become disputed.

The absence of a proper revision register may complicate the determination of liability.

The court or arbitral tribunal may examine the approval records, correspondence, contractual provisions and conduct of the parties.

Legal conclusion: Failure to maintain document version control may create uncertainty regarding the applicable contractual instructions and may substantially complicate the determination of responsibility for defective work.

9. Legal and Financial Consequences of Failure to Enforce Version Control

10. Documents and Records Required for Effective Version Control

The following records should be maintained by an organisation:

11. Preventive Measures and Best Practices

The following measures should be implemented to prevent failure of document version control:

1. Centralised document management: Maintain a centralised document repository accessible to authorised personnel.

2. Unique document identification: Assign a unique number to every important document.

3. Revision numbering: Every modification should carry a distinct revision number.

4. Approval mechanism: No revised document should be implemented without approval from the competent authority.

5. Revision history: Maintain a record of all modifications, including reasons and dates.

6. Withdrawal of outdated versions: Immediately withdraw or mark superseded documents to prevent their further use.

7. Controlled circulation: Ensure that revised documents are communicated to all concerned departments, contractors and stakeholders.

8. Access restrictions: Restrict modification rights to authorised personnel.

9. Electronic audit trails: Maintain logs of document creation, modification, approval and circulation.

10. Periodic verification: Conduct periodic checks to ensure that departments are using the latest approved versions.

11. Preservation of original documents: Retain original documents and historical versions for audit and legal purposes.

12. Staff training: Train employees and project personnel regarding document control procedures.

12. Consolidated Legal Position Emerging from the Case Laws

13. Conclusion

Failure to enforce version control on documents represents a significant weakness in an organisation's internal control system, contractual administration and document management practices.

When proper version control is not maintained, outdated, unauthorised or inconsistent documents may be used for official decisions, financial transactions, procurement, construction activities and contractual performance.

This may result in defective execution, financial losses, contractual disputes, delays, difficulties in establishing accountability and complications in legal proceedings.

The Supreme Court's decision in Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal (2020) is particularly relevant because it emphasises the importance of authenticity and integrity of electronic records.

Similarly, H. Siddiqui v. A. Ramalingam (2011) and LIC of India v. Ram Pal Singh Bisen (2010) reinforce the principle that documentary evidence must be properly established and proved in accordance with law.

Accordingly, organisations should implement a formal document control system that ensures every document is uniquely identified, properly reviewed, approved, revised, circulated and preserved.

Ultimately, document version control is not merely an administrative formality. It is an essential internal control mechanism for ensuring document authenticity, contractual compliance, operational consistency, financial accountability and legal defensibility.

14. Suggested Wording for an Internal Audit / Inspection Report

The following paragraph may be used in an internal audit report, departmental inspection report, project audit or compliance review.

Writing

Failure to Enforce Version Control on Documents

It was observed that adequate controls were not established to ensure systematic version control of important documents. Different versions of documents, including contractual records, technical specifications, drawings, approvals and other official communications, were maintained and circulated without an effective mechanism to identify the latest approved version.

Further, proper records of document revisions, approval dates, authorisation details, modification history and withdrawal of superseded documents were not adequately maintained.

The absence of an effective document version control mechanism creates a risk of reliance on outdated, unauthorised or inconsistent documents, which may result in incorrect execution of work, contractual disputes, avoidable expenditure, delays and difficulties in establishing accountability.

The matter assumes significance in view of the principles laid down by the Supreme Court in Arjun Panditrao Khotkar v. Kailash Kushanrao Gorantyal, (2020) 7 SCC 1, concerning the authenticity and admissibility of electronic records, and H. Siddiqui v. A. Ramalingam, (2011) 4 SCC 240, concerning proper proof and admissibility of documentary evidence.

Accordingly, the organisation should establish a centralised document management system, maintain a document master register and revision history, ensure approval by competent authorities, withdraw superseded versions and maintain appropriate electronic audit trails to ensure that only authentic, approved and current documents are used for official and contractual purposes.

15. Important Legal Qualification

The above judgments deal primarily with authenticity, admissibility and proof of documents. They do not establish that every failure to maintain a revision register automatically constitutes a statutory violation.

Whether the failure amounts to contractual breach, negligence, misconduct or regulatory non-compliance depends on:

The applicable contract or document-control policy.

The authority responsible for approval and circulation.

The nature of the document.

Whether the incorrect version was actually used.

The financial or operational consequences.

The applicable statutory record-keeping requirements.

This distinction is important when framing an audit objection or fixing responsibility on a particular officer or department.