Document control log template for Word (free download)
Document control log template for Word (free download)
Every company produces documents: policies, procedures, forms, work instructions, minutes, reports. While there are only a few, everybody knows which one is the good one. Once they pass a dozen, and there are two warehouses, three shifts or people coming and going, the classic problem shows up: two versions of the same procedure are in circulation, somebody printed a copy that is no longer valid and taped it next to the workstation, and on the day a decision has to be explained nobody knows which document was in force at that date.
Document control is the part of the internal management system that answers those questions: which documents exist, which version they are on, who approves them, where the original is kept, who holds a copy, what happened to the old ones and when they are due for review. It does not call for new software or a separate department: it calls for an honest list, a version rule and the discipline to keep it updated when something changes.
This Word template brings that control already built. It includes the control table with the code [CD-___], the purpose and scope, the prefix scheme for identifying each type of document, the master list with rows ready to fill in, the version history table with its initial version row, the distribution and controlled copy fields, the paragraph on obsolete documents and archiving, the periodic review with its next date, the three signatures for prepared, reviewed and approved, and the closing notice. All it takes is replacing the bracketed fields, changing the company name in the header and in the footer, and starting to fill the master list with what the company already has.
⬇ Download document control log (.docx)What it is, and who should approve it
A document control log is, at bottom, an orderly inventory of the paperwork the company works with, plus the rules that keep that inventory true over time. It has two halves that work together: the master list, which says what exists and in which version, and the control rules, which say how a document is created, changed, approved, distributed, archived and withdrawn.
Because it is an internal control document, it is best approved by management or by whoever is responsible for the company's management system, and its day-to-day administration should sit with one single person: the one who updates the list, assigns codes and receives new versions. When three people do that job at once with no written rules, two codes end up being used for the same form, and the control stops doing exactly what it was created for.
There is one detail almost everyone overlooks: the document control log is itself a document and has to appear in its own master list, with its code, its current version, its owner and its date. If the document that governs all the others is missing from the list, the rest of the list loses credibility at the first review.
One thing is worth saying from the start: this template is a general guide for internal use. Each company decides its own codes, its review frequency and who signs; it is not legal or certification advice, and if the company already runs a formal management system, it is best reviewed together with whoever leads it.
What it is for
- Knowing which version of each document is current, without asking anyone or digging through email.
- Keeping two areas from working with two different versions of the same procedure.
- Leaving a trail: who changed what, when, and with whose approval.
- Having orderly evidence ready for an internal audit, a customer or an inspection visit.
- Controlling printed copies: which ones are controlled, who received them and when they get replaced.
- Withdrawing what is obsolete and archiving the original, instead of keeping it around just in case.
What the template includes
These are the sections of the file as they come, with what goes in each one:
| Section | What goes in there |
|---|---|
| Control table | Code [CD-___], document version, date and the name of the person who administers the control. It sits at the top of the first page, so any printed copy shows which version it came from. |
| 1. Purpose and scope | Why this control exists and which documents it covers. It pays to be explicit about what is left out: accounting records, commercial correspondence and third-party documents are usually handled separately. |
| 2. How documents are identified | The code scheme by type of document, with the prefix the company chooses and the running number assigned in order of creation. |
| 3. Master document list | The main table, one row per document: code, name, current version, date, owner, medium, where the original is kept and status (current or obsolete). |
| 4. Version history | The log of each document: version, date, description of the change, who prepared it and who approved it. The first row is the initial version. |
| 5. Distribution and copies | Whether controlled copies are printed, how each copy is identified and who receives it. If the company works only in digital form, that is written down too. |
| 6. Obsolete documents and archiving | What happens to the previous version: mark it obsolete, withdraw it from circulation and keep the original for as long as the company decides. |
| 7. Periodic review | How often the whole set is reviewed and the date of the next review, so the control does not depend on anybody's memory. |
| Signatures | Prepared, reviewed and approved, with name, position and date. Those are three different signatures: the person who writes the document should not be the one who approves it. |
How documents are identified
The code is the backbone of the control: a document with no code cannot be cited in another document, cannot be asked for by name during a review, and there is no way to tell whether the copy in circulation is current. That is why the template asks you to define the scheme before assigning the first code, and not the other way round. The file comes with the table of document types and suggested prefixes, which the company can adjust to taste as long as it is written down:
| Type of document | Suggested prefix | What it groups |
|---|---|---|
| Policy | POL | The company's general rules on a subject: what is allowed and what is not, and how far each area goes. |
| Procedure or SOP | SOP | The step by step of an activity, with the person responsible and the record left at each step. |
| Form or record | FRM | The sheets that get filled in and remain as evidence that an activity took place. |
| Work instruction | WI | Short directions for operating a piece of equipment or carrying out one specific task. |
Two practical rules prevent half of the trouble: a running number is never reused, not even when a document is withdrawn, and a document whose content changes gets a new version, even when the change looks small. If the company wants, it can add one prefix for third-party documents and another for minutes, but the scheme should fit on one page and nobody should have to look it up to remember what their own form is called.
How to use it, step by step
- Open the file and complete the control table on the first page: the code [CD-___], the initial version, the issue date and the name of the person who will administer the control.
- Replace the company name in the header and in the footer, and delete the sample data that does not apply to your operation.
- Define the prefixes the company will use for policies, procedures, forms and work instructions, and write them into the identification section before assigning the first code.
- Walk the company and build the master list with what already exists, even if sections or signatures are missing. Do not write what ought to exist: write what is used today.
- Give every document its code, its current version and its date. If you find two versions in circulation, leave only one as current and mark the other as obsolete.
- Open the version history of every important document and write the initial version row, with the date and the name of the person who approved it.
- Decide whether you will print controlled copies. If the answer is yes, define how the copy is identified and who receives it; if it is no, write that down anyway, so nobody prints one just in case.
- Sign the three boxes, keep the original in the location you declared in the list, and publish only the current version in the shared folder.
What to check before signing
- That the document control log itself appears in the master list, with its code and its version.
- That two codes are not being used for the same form, or the same code for two different documents.
- That the versions on the list match the ones published in the shared folder.
- That it is clear where the original sits, on paper and digitally, and who answers for each one.
- That obsolete documents have been withdrawn from circulation and marked, not simply left lying around.
- That the next review date is written down and somebody has it in their calendar.
How it stays alive
A document control log does not fall apart for lack of a template, it falls apart for lack of upkeep. If the master list is filled in once and never touched again, within a few months it will say things that are no longer true and people will stop consulting it. The way to avoid that is to treat it like any other task in the operation: with an owner, a frequency and evidence.
Three moments trigger an update: when a new document is created, when an existing one changes its content, and when one is withdrawn. If those three moments are written down and somebody knows them, the rest is routine. The full periodic review serves a different purpose: it looks at the set as a whole, dusting off documents nobody uses any more, fixing repeated codes and confirming that what the list says matches what is in the folders.
| Activity | Suggested frequency | Evidence it leaves |
|---|---|---|
| Update the master list | Every time a document is created, changed or withdrawn | A new or edited row, with the date of that update. |
| Review the content of each document | Every [number] months, or sooner if the process changes | A new row in the version history, with the approval signature. |
| Review the list as a whole | Once every [number] months | A signed note recording that the review took place. |
| Withdraw old printed copies | Every time a new version is published | A record of controlled copies handed out and returned. |
| Clean up the archive | Every [number] years, according to the retention the company set | A note of what is kept and what leaves the archive. |
When it pays to move to a system
A document control log in Word works well while the volume is manageable: one person administers it, the list fits on a sheet and versions are published in a shared folder everybody respects. The breaking point arrives when there are several administrators, when the list grows into the dozens of rows, or when somebody needs to know without calling anyone which version is current and which document backs a specific inventory movement. That is where an inventory system such as Kardex Tauro earns its place: it does not replace the master list, it feeds it with data already recorded in the operation, so that the current version and the record of the movement come from the same place. Until that point arrives, the Word template is enough and is honest: what matters is not the tool, but that the list is true on the day somebody consults it.
⬇ Download document control log (.docx)This template is a general guide for internal use: have it reviewed with your adviser before adopting it as an official company document.
