Ask a compliance team to talk you through how a policy is managed and you will usually get a confident, detailed account of everything up to publication - how it is drafted, who reviews it, who signs it off, how people are asked to attest to it, and how the review date is tracked. But there tends to be far less attention given to what happens at the other end, when a policy stops applying and needs to be retired. Of course, that is understandable, because withdrawing a document feels like the moment the work finishes rather than the moment it matters. But in the organisations we work with, the end of a document's life is where the evidence is most often lost, and it is lost quietly, which is a problem.
In summary
Policy retirement is the controlled withdrawal of a document from circulation: it stops being something people must follow, without ceasing to be something the organisation can account for. A defensible retirement record shows why the document was withdrawn, who approved the withdrawal, the date it stopped applying, and who had attested to it before that date. ISO 9001 requires obsolete documents that are kept for any purpose to be identified clearly enough that nobody uses them by mistake. In many organisations, policy retirement is still a manual job, and that is usually where the attestation record goes missing.
What retiring a policy actually means
Retiring a policy means taking it out of circulation as a live obligation while keeping it, and its history, on record. It is not the same as deleting the document, and it is not quite the same as archiving it either, although the three get used interchangeably in conversation.
Deletion removes the document and, depending on how it was stored, often removes the evidence that it ever applied to anyone. Archiving usually describes where a document ends up such as a different library, a different site, a folder nobody browses, but a place where the document can ultimately be retrieved if necessary. Retirement is something different again. It describes a decision: this policy document no longer applies, from this date, for this reason, with the decision approved by these people. The question of where the document is stored follows from the decision.
That distinction sounds academic and not particularly important until someone asks you about a document you withdrew two years ago. At that point the useful record is not the file sitting in an archive folder. It is the answer to what applied, to whom, and until when.
Why withdrawing a document deserves the same control as approving it
You might not agree with us on this but I would argue that the decision to withdraw a policy carries the same or even more risk than the decision to approve one. When a policy is approved, a large number of people then read it, attest to it and work to it, and if something is wrong with it there is a reasonable chance somebody will notice and say so.
But when a policy is withdrawn, nobody reads it again. There is no second check. If the wrong document comes out of circulation, or the right one comes out at the wrong time, the organisation usually finds out from an incident or an audit rather than from an employee. And of course, by then it is too late to prevent the consequences of any incident.
That is why review and approval workflows became standard practice for publishing and updating documents, and why it always seems odd to me that the same discipline so rarely applies at the point of withdrawal. The same question is being answered in both cases, whether the document represents what we require of people right now. In both cases somebody with authority should be answering it on the record, and ultimately approving the publication or the retirement of the policy.
There is a second problem relating to communicating the associated change. A policy is withdrawn, the people who approved the withdrawal know it has been withdrawn, but the people who were working to the policy are never told. Where policy retirement runs as a manual job tracked on a spreadsheet, communication is usually the step that slips, because a tracker is built to record that the file has been moved rather than that anybody has been informed.
Even if a replacement policy has been communicated, employees do not go back to the library to check whether a document they read eighteen months ago still applies. They work from the copy they saved to their own machine, the version they printed, the document attached to an old email or the link they bookmarked when they attested to it. They then carry on following the policy in good faith, sometimes long after the business stopped working that way.
The consequences of this can be serious, particularly in heavily regulated industries. Take medical device manufacturing, a sector that takes policy retirement very seriously, because the consequences can be highly impactful. Its regulators have long framed the policy retirement requirement in terms of use rather than storage: the question is not whether the obsolete version has been filed somewhere sensible, but whether it has been removed from every point where the work actually happens, which includes the printed copy at the bench and the file sitting on somebody's desktop. Since February 2026 the FDA has applied this through its Quality Management System Regulation, which brings ISO 13485:2016 into 21 CFR Part 820 by reference. Very few of the organisations we work with operate under that regime. But the failure it exists to prevent with somebody following a document in good faith that the organisation withdrew months ago, is the same failure a policy library on a shared drive produces, albeit with less at stake.
What does an auditor ask for when a policy has been withdrawn?
They ask what was in force at the time, who it applied to, and how you know that detail. An auditor or investigator looking at an event from two years ago is not interested in your current policy set, because your current policy set did not govern what happened. They want the version that was live on the date in question, confirmation that the people involved had been required to read it, and evidence that they did.
Consider an incident being investigated in 2026 that relates to something that happened in March 2024. The procedure that governed it was replaced a year later and the old one was withdrawn and tidied away. The question is not whether you still have a copy of the old policy. It is whether you can show that this exact version was the one in force in March 2024, that the three people involved were assigned it, and that two of them attested to it on dates you can produce. If the withdrawal was simply a manual move of a file into an archive location, that evidence is usually sitting in a spreadsheet, an export somebody took at the time, or nowhere.
There is a standards dimension to this as well. ISO 9001:2015, at clause 7.5.3.2, requires organisations to prevent the unintended use of obsolete documented information and to identify it suitably where it is retained for any purpose; ISO 13485:2016 carries an equivalent requirement at clause 4.2.4. Neither standard tells you to delete the old document. Both assume you will keep it and expect you to make its status unmistakable.
Where does policy retirement usually break down?
The policy retirement process usually breaks down in the gap between the decision to retire the policy and the mechanics of the withdrawal, because the two are normally done by different people at different times. Someone decides a policy no longer applies, often in a meeting, and someone else moves the file, often weeks later. The audit trial for reasoning, date approved and who approved is detail between the decision and the file removal that does survive, making it hard to pinpoint and demonstrate the policy retirement decision.
For organisations managing policies on SharePoint, there is a more specific trap. Where a document management layer tracks attestations against a document in a particular library, moving that document somewhere else - including into a hidden or restricted archive library - can clear its assignments, and the live attestation record goes with them.
The workaround we have recommended to clients is to download the read report first, while the document is still live and its assignments are intact, then move the file using SharePoint's own "Move to" function so the version history is preserved, then store the report alongside the document in the archive library so the two stay together.
We have found this advice works, but it is an imperfect workaround. It is also, looking at it plainly, a sequence of manual steps where getting the order wrong destroys the evidence, and it ends with your compliance record as a downloaded file rather than a live record. We have been recommending it as a sensible way to handle a gap rather than how policy retirement should work. To be transparent, its’ the part of our own guidance I have been least comfortable with.
Another common point of failure is quieter. A policy is withdrawn and the documents that referenced it are not touched, so a procedure carries on pointing at a policy that no longer exists. Additionally, sometimes a mandatory reading task can sit in somebody's to do list when actually the document was retired months ago. Nobody is doing anything wrong. The links between documents simply have no reason to update themselves.
What a defensible retirement record contains
Whatever system you use, and this applies as much to a well-run manual process as to software, a policy retirement record that stands up to scrutiny generally needs to hold the following:
The reason for withdrawal. Superseded by a named document, process discontinued, regulation no longer applicable, duplicate removed. A reason recorded at the time is worth considerably more than one reconstructed later.
The approval. Who decided, in what role, and on what date. If a single person can withdraw a document unilaterally, your retirement control is weaker than your publishing control.
The attestation history. Who was assigned the document, who attested, to which version, and when, all preserved as a record rather than rescued as an export before the document moves.
The status of outstanding obligations. If people still had the document on their must-read list when it was withdrawn, those tasks need closing and those people need telling. Leaving them open produces overdue compliance tasks for a document that no longer applies, which erodes trust in the numbers and process.
The related documents. Anything that references the retired document should be identified so its owner can decide whether the referring document needs updating.
The retention position. This needs to cover where the retired document now lives, how long it will be kept, and what happens at the end of that period. There are two key factors here. The first is that the retired document remains retrievable with its version history intact, so that an auditor looking at a decision made three years ago can be shown the version that governed it rather than a description of it. The second is the retention schedule itself, which is usually set by legal or records management rather than by the policy owner, and will need to align with legal and regulatory requirements for keeping records.
Some people reading this might think this sounds like overkill. If you only have a handful of policies, no external auditor and one person who knows where everything is, a dated folder and a naming convention will hold this together perfectly well. The argument for a controlled retirement process gets stronger with the number of documents, the number of owners and the number of people who will be asked to account for them. There is also a risk if you are relying on one gatekeeper who knows where the documents are and the related context and nobody else does.
Where software fits, and what is changing in Xoralia
A document management system should treat document or policy retirement as an important stage of the document lifecycle. This means a withdrawal should be able to go through an approval route in the same way an update does, and the resulting record should remain readable, reportable and attributable afterwards. We wrote in our policy management eBook that obsolete policies should be archived rather than deleted so the historical record survives an audit. That advice still stands. What we did not say then, and should have, is that keeping the document is only half of it; keeping the evidence of who was bound by it is also critical as the auditors may ask about this.
For disclosure, Xoralia is built by Content Formula, a Microsoft 365 consultancy that delivers out of the box, in-a-box and custom-built solutions, which is why we are happy to talk both about the manual route and the software route to meeting a business need. Xoralia is compliance management software for Microsoft 365: it controls policies, SOPs and regulated documents, and proves every review, approval and attestation with a timestamped audit trail.
Policy retirement workflows are now available in Xoralia, bringing controlled withdrawal into the document lifecycle. The process works in the same way as the policy update workflow. A workflow administrator-a governance role rather than an IT role-configures the retirement process in advance, with one or more approval stages and all named mandatory approvers. A document owner then submits a document for retirement through that workflow, ensuring everyone who needs to approve the withdrawal is involved rather than leaving the decision to the policy or document owner alone.
When the retirement completes, the document moves to a retired state that holds both its attestation history and its retirement approval history against the document. Outstanding must-read tasks are cancelled automatically and the assignees are notified, related documents are flagged to their owners, and the read report remains exportable from the retired record. That last point is the one that matters for the problem described earlier: the evidence no longer has to be rescued before the document comes out of circulation.
The document itself goes to a retired library in your own SharePoint environment, where it keeps its full version history and stays viewable and recoverable for site owners under your existing permissions.
The retirement process results in two records which answer different questions. The library holds the document as it stood, every version of it, available to produce when somebody asks what the wording actually said. The retirement record holds the decision covering who approved the withdrawal, when it took effect, and who had attested to which version before it did. An audit usually needs both, and in a manual process they tend to end up in different places, maintained by different people, with only one of them still accurate.
The notification to related document owners is important, but it is dependent on a decision the organisation makes long before any retirement happens. A link typed into the body of a Word document is a piece of text that will carry on pointing at a policy that no longer applies. Nothing about it will tell the owner of the procedure that anything has changed. A link created as a relationship between two documents behaves differently: it is bidirectional, it belongs to the documents rather than to the wording inside them, and it already drives an email to the other document's owner when a linked policy is re-published, expires, is deleted or goes into draft. Retirement now joins that list, so the owner of the procedure that depended on a withdrawn policy hears about it and can decide whether their own document needs changing; this is a decision somebody should be making deliberately rather than discovering during an audit, which clearly is not a good look.
The caveat is that none of this works unless the relationships were recorded while the documents were being published. Linking accompanying documents as you go is a modest amount of work at the time and it is the thing that keeps a policy set in step with itself afterwards, because each relationship stays accurate as the documents around it change. Linking documents also signals a more intentional approach to managing policies and sometimes other important areas come to mind in that process.
Looking at your own policy retirement process?
If you want to work out what your current process would produce if an auditor asked about a document that you withdrew two years ago, our guide to policy lifecycle management is a reasonable place to start. If you would rather see how a controlled policy retirement route works in practice, you can start a free Xoralia trial or ask us for a walkthrough. Additionally, if you think we have missed something that belongs within a retirement record, we would be interested to hear about it.
Frequently asked questions
What is the difference between retiring, archiving and deleting a policy?
How long should a retired policy be kept?
Do attestation records still matter once a policy has been withdrawn?
Who should approve a policy retirement?
What happens to documents that reference a retired policy?
About the author

Dan Hawtrey
CEO and product lead
Dan Hawtrey is CEO of Content Formula and the driving force behind Xoralia, a policy management platform built natively on Microsoft 365. Dan writes regularly on policy management, compliance, and the evolving role of AI in how organisations manage knowledge. His articles are grounded in real conversations with the companies and teams using Xoralia day to day.
