It is possible for three different documents to share almost the same words but perform entirely different functions. One may be a draft, one may be a copy, and the last may be the official record of the final decision or event. How do you tell them apart? It often requires looking at more than just the content. You need to check their status, versioning information, proof of approval, filename, metadata, and their position in the lifecycle of the document.
A draft is a document that is currently being developed. There could be annotations, track changes, blank fields, placeholders, or open questions in it. While drafts can tell us something about how a document evolved, they should not be mistaken for a final version. Consider the file name Report_final_new.docx; it does not provide much information about its status. A better file name would include the content, subject, date, and version, such as Inspection_Report_2026-08-05_v03_Draft. However, the presence of the word “draft” is only one factor among others, including the version number and date.
A copy is a reproduction of a document that does not inherently make it the authoritative record. It could be a scan, a downloaded PDF, a photocopy for reference, or a backup copy in a different folder. Copies can be useful for accessing or distributing the information but cause confusion when no one knows where the original or approved version is located. A copy can be identified by the filename, metadata, label, or register. If there are multiple copies, compare the content of all copies to see if they are identical. Look for any signatures or approvals on one of the copies. Check if there is an organizational policy that specifies the authoritative location of the approved document.
An authoritative record is a version of the document that serves as evidence of the completion of a process or decision. Depending on the document type, it could be a signed document, an approved document, a document with an issue date, a document with a reference number, a document with a complete registration entry, or a document with some other clear indication that it has reached the end of its lifecycle. Note that having a signature on a document does not mean that it is the authoritative record. The signature might be on a copy of the document. An approved document can also be superseded by a later version that has been formally revised. Thus, it is safer to use multiple indicators to determine the status rather than focusing on a single feature.
As a learning exercise, gather 5 to 6 documents that relate to one process, for example, a meeting. Include an early draft of the agenda, an updated agenda, the approved agenda, a scanned copy of the approved agenda, the minutes, and a duplicate copy of the minutes. Identify the status of each document and then explain why you chose that status. What was the basis of your decision? Was it the filename, the date, the version number, the approval stamp, the registration data, the signature, the folder location, or some other factor? If the available information is insufficient to confirm the status of the document, then you should classify its status as ‘uncertain’ instead of making assumptions. This exercise will highlight the importance of documenting version control and metadata even before filing documents.
Once you have determined the status of each document, store them in a simple folder structure or document register. Do not mix drafts with approved versions, and label the copies appropriately. Your register could include fields for the title, document type, date, version, status, reference number, and location. You do not need to add unnecessary columns that do not help in identifying or retrieving the document. The aim is not to create a complex system for tracking documents but to ensure that someone else can find the approved version and know why that version is the authoritative record.
As a final test, pretend you cannot see the actual content of the documents. Can you still identify the current draft, the duplicate copy, and the authoritative record based solely on the filename, metadata, register entry, or location? If you can, then you have successfully documented the document status in a way that is both effective and repeatable.
