written by: Sidharth Thakur
• edited by: Jean Scheid
• updated: 12/28/2010
Are you finding it difficult to manage the multiple versions of documents that are being used by your project team? If so, then setting up a document version control can cut-out the confusion. Read on to find out how to set up a version control policy for documents used in a project.
slide 1 of 2
The importance of document version control stems from the fact that most documents go through a lot of revisions and editing, especially digital documents in which revisions are difficult to track. Whether for projects or for businesses, it’s critical that the user knows which version of the document he is looking at. Also, in projects where a number of team members are contributing toward developing a collaborative document, which may have to undergo a lot of revisions before getting finalized, it will be easier to mange if the document’s versions are controlled using a proper policy.
Tips for Setting up a Document Version Control Policy
Ideally, a document version control policy should be in place before the project goes into execution. Failing to do so when multiple versions of the same master documents exist with different team members could result in utter chaos.
At any point of time during the project execution, there must be only one version of the document in use. As and when the document is edited or revised, the revised version of the document must be made available to all the concerned team members.
Every document must have clear details about which team members are allowed to edit the contents of the document and to what extent. Also, the document must have some place to add in information about the edits such as the name of the person, the version code and the date of editing.
As far a possible a team member who will be responsible for handling documents, they must be identified and every version of each document must pass through this person. Following this protocol will ensure that all team members have the latest version of the document. Also, this central channel will ensure that there are no different versions of the document being used by different team members. This person will also be required to maintain a detailed log of the different versions of the documents that pass through him.
The document version control policy must be applicable for both physical as well as digital documents. Also the same methods of coding the different document versions should be followed for both the document types.
A unique version coding method must be set up and communicated to all team members who are involved with creating, editing, reviewing or revising the documents. They must all clearly explain how the version code must be changed when submitting the edited or revised versions. It is best to use the coding either in the header or the footer of the document. The coding policy must also mention how reviewed and finalized documents must be coded distinctly.