Document and policy management: making sure the current version is read
What is a document management system? Publish policies and procedures with version control, select the audience, and track read status and digital confirmation.
The returns procedure was updated last month, but the field team’s phones still hold the old PDF. Knowing who is working with which version is harder than companies think. A document management system is software that keeps policies, procedures and corporate documents in one place with version control, publishes the right version to the right people and records that it has been read. In YazSis KurumsalPortal, the Document & Policy Management module handles this.
Why are e-mail attachments and shared folders not enough?
Sending a policy by e-mail does not mean publishing it; it only shows that it was sent. A shared folder is a place that everyone can reach but where nobody knows who has read what. And as updates become more frequent, remembering which file was published on which date is left to people’s memory. Similar gaps appear with both methods:
- Several versions of the same document circulate, and which one is valid differs from person to person.
- The update is announced but the old file stays where it was, so employees keep using the old one.
- The document goes to people who do not need it and does not reach those who do.
- When an employee says “nobody told me this”, there is no record to answer with.
A document’s life cycle: five steps
In the module, a policy or procedure moves through a single flow from preparation to archiving. Because each new version is approved before publication, a draft text cannot reach employees by mistake. And because every stage is recorded, the answer is ready when someone later asks, “when was this document published, and with whose approval?”
- Prepare the document: The document is stored in one place and its version is tracked.
- Approve the version: The new version goes through approval before publication.
- Publish to the audience: The approved version is published to the selected audience.
- Track reading: Who has read the document and the digital confirmation status are followed.
- Archive the old version: When a new version is published, the previous one moves to the archive; the version history stays on record.
Example: when the returns procedure is updated
The quality department prepares the new version of the returns procedure and sends it for approval. Once approved, the procedure is published only to the teams involved in returns. A few days later, human resources checks the read list, sees who has not opened it yet and sends them a separate reminder. Because the new version is live, the old version has moved to the archive; so two different procedures do not circulate at the same time, and the date of the old version can be found in the record when needed. In other words, what changes is not the work itself but that the work is tied to a single flow and a record.
Target audience: not everyone has to read everything
Not every document concerns every employee. Sending an accounting procedure to the field team, or a field instruction to the office team, distracts people and turns announcements into noise. Publishing to a selected audience delivers to each employee only the documents that concern them. Because read status is also tracked against this audience, the question “who needed to be informed, and who was?” is answered with a clear list. Access is also limited by authorization; not every document has to be open to everyone. A procedure with sensitive content is opened only to the relevant team, while a general code-of-conduct policy is published to all employees.
A policy’s effect lies not in its being written, but in its reaching the right person and being read.
What does read status show, and what does it not show?
Honesty matters here: read status shows that the employee opened and confirmed the document, not that they understood the subject. That is why, for important policies, it is good practice to complement the read record with a short briefing or a Q&A session. The record is still valuable: when a problem arises, which version the employee was informed of and their confirmation status can be shown from the record rather than guessed. Tracking read status also gives managers a practical advantage; since those who have not yet read are visible, reminders can go only to those who are missing rather than to everyone. This also reduces announcement fatigue.
Three decisions before you start
However good the software is, a document routine rests on a few company decisions. Settling them in advance reduces the confusion in the first week of setup. These decisions can be written down as a two-page note; what matters is that everyone knows the same rule.
- Ownership: Give every document a responsible owner; that person starts the update and sends it for approval.
- Version rule: Decide up front which changes count as a new version and which stay as a mere correction.
- Audience: Agree on who receives which document before you publish it.
As important as setting up a system is that the teams take ownership of the routine you set up. That is why, when choosing the first documents, we suggest picking ones that are widely used, change often and have a clear owner. If you want to manage your documents through a single valid version, see the Document & Policy Management page, and for the platform’s other modules, the KurumsalPortal page.
Frequently asked questions
What is a document management system?
It is software that keeps policies, procedures and corporate documents in one place with version control, publishes the right version to the right people and records that it has been read. In YazSis KurumsalPortal, the Document & Policy Management module handles this.
Can it be recorded that an employee has read a policy?
Yes. The module tracks read status and digital confirmation for published policies and procedures. That way you can see which employees have read the current version.
What happens to the old version when a document is updated?
Documents are managed with version control: the new version is prepared, approved, published to the audience and archived. Employees work with the single valid document, while the version history stays on record in the archive.
Can a document be published only to the relevant employees?
Yes. The approved document is published to the selected audience, and access is limited by authorization. Read status is also tracked against this audience.
More articles
What is XML integration? How to import supplier product and stock feeds into your store
Your supplier publishes a new XML file every morning, and you are still typing prices in by hand. XML integration reads that file, applies your rules, passes the data to your online store and stops faulty data.
November 23, 2026 · 8 min readMaintenance tracking software vs Excel: when to switch for preventive maintenance
Tracking maintenance in Excel works for a while, but it breaks down at reminders, assignments, history and parts costs. We compare maintenance software with Excel, give seven criteria for switching and explain how to move your spreadsheet.
November 23, 2026 · 8 min readField visit planning: comparing what was planned with what happened
Tracking a field team does not have to mean watching every minute of an employee. Putting the weekly plan, the location match at the moment of action and the visit evidence side by side can be enough.
November 23, 2026 · 5 min read