<img src="https://i.canddi.com/i.gif?A=f0f63a3d3d2d596f1b8c53b1e727e618">

What is Document Version Control?

Author: Ruban Rajasooriyar

Good Practice Guidance - Document Version Control
What is Document Version Control?

Document Version Control is the process by which different drafts and versions of a document or record are managed. It is a tool which tracks a series of draft documents, culminating in a final version. It provides an audit trail for the revision and update of these finalised versions.

Document Management solutions can automatically track and update records so users know exactly which is the latest version of any document. For group manuals for example, email alerts can be automatically sent out to notify of an update.

Why do we need document version control?

When drafting a new policy, new procedures, or a new publication (or updating an existing one) version control clearly identifies the development of the document. For example, it allows you to retain and identify the first draft that was submitted to a group for comment, the draft which was generated as a result of these comments, the versions that went back and forth for further comment, and the final version which was endorsed by the Senior Management Group, signed off by Head of Department, or made available to the public. This tool is also useful when working on a document with others; with version control, changes made by different individuals at different times can be clearly identified.

How do I use document version control?

Version control should be used where more than one version of a document exists, or where this is likely to be the case in the future.
Version control can be achieved by adding a number at the end of a file title. Each successive draft of a document is numbered sequentially from 0.1, 0.2, 0.3… until a finalised version is complete. This would be titled version 1.0. If version 1.0 is to be revised, drafts would be  numbered as 1.1, 1.2, etc. until version 2.0 is complete.

In addition to adding the version number to the end of the file title, it should also be displayed within the document. The version number should appear on any document title page, and also in the header or footer of each page.

Document Version Control Table

In some cases it may also be appropriate to use a version control table. This is done automatically within our solutions.  The table provides further details of what changes were made to a document, when, and by whom. A version control table is only required with formal University procedures, policies, strategies and project documentation. It can be added at the beginning or end of the document itself, or created as a separate document, and stored in the paper or electronic folder.

The version control table (see example below) must be updated each time a change
is made to the document. It details:
The new version number;
The purpose of the change or the change itself;
The person making the change;
The date of the change.
Version Number Purpose/Change Author Date

0.1 Initial draft – to line manager   James Smith, Personnel Officer

0.2 Consultation draft – to working group James Smith, Personnel Officer

0.3 Second consultation draft – to working group James Smith, Personnel Officer

1.0 Final version – approved by CMT James Smith, Personnel Officer

1.1 Revision of paragraph 12 to clarify procedure Elaine Brown, Personnel Officer

1.2 Update of contact details Mark Campbell, Personnel Assistant

Microsoft Versioning Tool

Microsoft Word also offers a versioning tool. However, it is not advisable to use this function as it substantially increases the size of your document, which in turn wastes valuable server space.

Document Version Control -Further Advice

Contact DocTech to see how our solutions could improve your document version control 0161 647 7040.

Original Post by
Records & Information Management Service
tel: +44 (0)141 330 6494 or 5146
email: recman@glasgow.ac.uk

Contact us now for more information 0161 647 7040