Version Control Policy

Version Control Policy

Version Control Policy


The purpose of this is maintaining a version control procedure is to define the system used to:

  • assure the integrity, accuracy and currency of all documents used by the College
  • Ensure that documents are approved by the appropriate personnel before becoming active
  • Ensure replaced documents are archived for continuous improvement records
  • Ensure all stakeholders are using current documentation
  • Maintain a version history of the documents at all times
  • Maintain registers of documents that relate to the Scope of Registration
  • Manage recordkeeping requirements for students as required by the VET Quality Framework


The Administration team is responsible for the implementation of this procedure and to ensure that all staff members are aware of its application and that staff implement its requirements.


  • Records maintained by the College support the continuous improvement of its operations and provide evidence of compliance with the VET Quality Framework.
  • The College uses a systematic approach that ensures it maintains all records relevant to its operations as a College, including the continuous improvement of its operations.
  • Records are systematically managed.
  • Records of demonstrating compliance with the VET quality Framework are maintained.
  • Staff meet their responsibilities for records management.
  • The effectiveness of records management is monitored and reviewed.
  • The continuous improvement of record management system is demonstrated.


Types of Documents for version control

the following documents need to be maintained as part of Version Control Procedure:

  • Applications and all Forms.
  • All College Policies and Procedures
  • All agreements related to students, college and agents, Sample Letter, Formats, and Certificates, staff documents such as position descriptions.

Version Control Process

  1. Documents are reviewed, amended by College staff. Documents must be created and amended by appropriate personnel in compliance with relevant legislation and be suitable for their intended purpose
  2. Numbering version control
    1. When a new document is under development it should have version 0.1, 0.2, 0.3,
    2. When it is at a point where it is ready to be presented to students this should be regarded as the final version and should change to version 1.
    3. Any further minor changes to the manual should have version 1.1, 1.2, 1.3, etc.
    4. If a major change is done on the manual, it should be changed to 2, 3,4, etc.
  3. Version control numbering is shown by the way the document is saved if it has been changed.
  4. Ensure to save the document with the filename and the version number at the end of the filename (e.g. Student Manual_v1.1).
  5. Responsible parties (All staff involved in the creation, review and modification of a document)
  6. All documents that are being reviewed must be marked with a document number. Upon updating the version of the reviewed document, the version number too needs to be updated in the document itself.
  7. The reviewed documents are then approved by the Chief Executive Officer who ensures that Administration team undertakes whatever consultation and checking they consider advisable on a case-by-case basis. Once all checking has been completed the document must be approved by the Chief Executive Officer who enters their name in the “Approved by” field in the Version Control Register.
  8. Upon approval, and electronic version of the document is then passed to administration team for Version Control processing and publishing.
  9. The administration team updates the version control register for version number, date of version change/review, and notes the actual change/review done in a specific document.
  10. The administration Manager must only accept documents into the Version Control system that have been checked by relevant staff and approved by the Chief Executive Officer.
  11. The administration Manager must check and, if necessary, update the following information in the Version Control Register:
    1. Document title
    2. Version number
    3. Document changes
    4. Checked by
    5. Approved by
    6. Published date
  12. A protected electronic version of the document is then placed relevantly marked folders on the College network in PDF format. The location of the updated PDF documents is then hyper-linked in the Version Control Register for easy access by staff members for viewing and printing.
  13. Electronic versions of the replaced documents are then placed in the archived documents folder.
  14. The Administration team then ensures that the college staff members are made aware of the new version by the means of an email. The reviewed document information is shared at the monthly staff meetings as well.
    The approved footer for all GCLC files is:
Document Date:00/00/0000Document Version0000Form Number: 000
Document Owner:DOCUMENT OWNERFile Name/Location:FILE LOCATIONPage 0 of 0