New files should use the name format:

{Client name} {file name} – {Draft/Final} {Version} {Date}

Example: Oracle Opinion HealthIT – Draft v0.1 10-09-23

Version control #

• Always start with version v0.1.
• Keep the client name consistent across all files. For example, always use ‘Prescribe Digital’, rather than ‘Prescribe’.
• When collaborating on a document in MSTeams there’s no need to increase the version number internally – work within the same file. You have the flexibility to increase the version number if you need to retain milestone changes. Only increase the minor number for internal revisions (ie v0.1, v0.2)
• Once a revised document has been signed off by the client, increase the file version to the next major number (ie v1.0, v2.0).
• Once a revised document has been signed off by the client, adapt the file name to the next major number (ie v1.0, v2.0), and adjust the word draft to FINAL.

Examples
Oracle Opinion HealthIT – Draft v0.1 10-09-23	Internal draft
Oracle Opinion HealthIT – Draft v0.2 12-09-23	Internal draft
Oracle Opinion HealthIT – Draft v1.0 12-09-23	Sent to client for review
Oracle Opinion HealthIT – Draft v1.1 14-09-23	Further amends from client
Oracle Opinion HealthIT – Draft v1.2 15-09-23	Further amends from client
Oracle Opinion HealthIT – FINAL v2.0 20-09-23	Signed off by client

Things not to do #

Here is a list of things not to do when naming documents:

• Do not add you initials or any other descriptors to the file name
• No underscores
• Do not save a copy onto your own laptop, always open in MS Teams app then make the changes there