Skip to content
Interface language: English
Imperium / Signal

Archiving company knowledge: retiring an instruction that still looks right

Retire outdated instructions from daily use. Check their status, successors, copies and search paths for people and AI tools.

Article language: English

A woman holds a sheet of paper beside an ornate red cabinet of drawers.
In this article

The instruction looks polished, the screenshots are clear, and it ends with the signature of someone who left the company two years ago. The document still comes first in search results. Retiring an instruction takes more than moving a file into an Archive folder. You need to mark its status, point to the current way of working and check the places where people and tools still retrieve the old content.

Start by deciding why the material is no longer suitable for current work. It may have been superseded, retained as history, found to be wrong or related to a process that has ended. Each reason calls for a different action. Archiving to preserve necessary history and deleting an unnecessary copy are not the same operation. Choose an approach that fits the information and the company's retention rules.

Establish the document's role in the process

Imagine a manufacturer whose sales team uses instructions for preparing spare-parts quotations. The document describes an outdated form and points to an old price list. The technical team already has a new procedure, but sales still opens the old PDF from a welcome email. For one team the matter is closed; for the other the problem is only beginning.

Check which task the material was meant to support, who used it and what replaces that help today. Do not judge its currency by file age alone. An old drawing may still describe a part correctly, while an instruction written yesterday may describe the wrong access permissions. Compare it with how the work actually happens.

If the owners and connections between materials are unclear, return to the company's knowledge architecture (in Polish). You do not have to organise the whole drive first. Start with one process and the documents that actually take the people doing the work from a question to a result.

Separate history from instructions to follow

Keeping a document can help reconstruct an earlier decision, but it should not suggest that people must still follow it. A "historical" status needs to explain the period or scope the material covers. A "superseded" status should point to its successor. "Withdrawn because of an error" needs a clear warning and the correct route to follow.

GOV.UK publishing guidance for standard content types distinguishes withdrawal with a visible notice from unpublishing. For withdrawal it calls for an explanation to readers and markings on attachments. This is a procedure for a particular government publishing system. The useful distinction is between keeping material and allowing it to remain an instruction for current use.

In our example, the old quotation instruction can remain as a record of the earlier process if it is needed to reconstruct what happened. It should not remain the default answer to "How do I prepare a quotation now?" Address those needs separately: use a marked archive and point to the current instruction where the work begins.

Assign an owner for the status decision

The author cannot always decide alone whether a document has ceased to apply. It may be used in several processes and by teams other than the one that created it. Bring together the content owner, the process owner and someone who uses the instruction. Agree what scope is being withdrawn and from when.

The role described in the process owner (in Polish) connects the status of knowledge with responsibility for carrying out a task. A library manager can make the technical change, but needs substantive confirmation that the new material really replaces the old one for the specified use.

Do not close the matter with "nobody raised an objection" if it is unclear who was supposed to assess it. When use is uncertain, mark the material for review and state the limitation. A lack of comments proves neither that it is current nor that it is unnecessary. Silence in a folder can simply be silence in a folder.

Find copies and entry points

List the document's main page, downloads, attachments, links in training and materials sent to new starters. Check message templates, instructions in the ticketing system and company search as well. You do not have to prove that nobody ever downloaded the file. You do need to identify the known paths by which it can still be distributed.

In the manufacturer's example, changing the library page will not automatically update a PDF attached to the onboarding pack. Update the pack and tell its owner. For quotation materials, the principles of versioning a multilingual offer (in Polish) are useful. One correct version does not remove discrepancies in other channels.

Record where copies are and who can change them. If you lack access, send a specific task with the link and expected result. "Please use current documents" is too weak when the reader still receives an outdated file as the first result. The message should accompany a fix to the route, not replace it.

Provide a successor or say honestly that there is none

A new instruction must support the same task or clearly explain how the process has changed. Do not mechanically redirect people to a general department page where they have to start searching again. Give them the specific material, its scope, the date from which it applies and a contact for exceptions.

If there is no successor yet, name the temporary route. In the fictional company, this might mean preparing a quotation with an approved form and having a named person review it. Agree who maintains that arrangement and when the decision on the final instruction will be revisited. A temporary status without an owner can easily become a permanent way of working. When a document describes a service the company is ending for customers, a service wind-down plan (in Polish) is also needed. The instruction's status and the next route for existing customers should fit together.

Do not copy the old text merely to give it a new date. Work through the actual task, confirm the inputs and check the result. For the successor, choose an example, instruction or independent exercise (in Polish) according to what the reader cannot yet do. A new document status will not teach it by itself. When onboarding new people, use tasks that check independent use of company knowledge (in Polish). Trying the action reveals gaps that reading alone cannot show.

Mark the material where readers will see it

A withdrawal notice should appear before content that leads people to act. Give the reason, date, scope and a link to current help. A download may also need a notice inside the document itself. A folder name will not help someone who opens an attachment saved on their computer months ago.

Aeneia conceptual photography

A historical version should retain information about its original scope. Do not silently edit it so that current content looks like an old record. If a correction is necessary, mark it and preserve the required change trail. History should explain what the company knew at a given time, not offer a smoothed-over biography of an instruction.

Record the decision in a project decision log (in Polish). Not every minor typo needs a separate resolution. Retiring material that directs the work of several teams should, however, have a reason and a responsible person so the status change can later be explained.

Check versioning and visibility separately

Microsoft's explanation of versioning in SharePoint lists and libraries describes tracking and restoring changes, alongside separate settings for draft visibility and approval. These functions depend on the library's configuration. Version history alone does not mean a reader will automatically see the right status or that the old document will disappear from every access path.

Confirm the settings and outcome in the environment you use instead of transferring behaviour from another product version. Check the material with an account corresponding to an ordinary user. Can they see the notice? Do they open the current version? Does the link work? An editor's account may show different material from a read-only account. Record the result with the role, date and specific entry path.

Do not set deletion rules merely to make the library easier to manage. Material may be subject to company retention rules, relevant to an open case or contain information needing restricted access. Resolve those decisions with the appropriate people. For AI data, a plan for retention and deletion of copies (in Polish) covers a separate scope.

Account for tools that use the document

If the instruction feeds a search engine or an AI assistant, changing the library may be only one step. Establish where the tool gets its data, how it receives updates and whether it keeps copies of its own. Assume neither immediate refresh nor permanent retention of the old content. Check the particular setup.

Use an AI data-flow register (in Polish) to find the source and subsequent places where it is processed. Then ask test questions that previously led to the withdrawn instruction. Check both the answer and the cited source. A generally correct answer may still rely on an outdated document.

After a larger change to the material, AI answer regression checks (in Polish) can help. The point is to check behaviour after the change, not merely a system message saying indexing has finished. Confirmation that a technical operation ran and confirmation of a useful result are two different forms of evidence.

Example: one instruction, three outcomes

The manufacturer divides the old document into parts. The description of the old form is withdrawn from current use, information about earlier product variants is kept in marked historical documentation, and a still-correct description of a customer conversation is assessed and used in the new instruction. There is no need either to keep the entire PDF as current or to delete everything with it.

For each part, the team identifies the audience and the reason. The salesperson receives a new route, the person analysing an earlier quotation retains access to the record they need, and the AI knowledge-base owner receives a task to check the current source. This division takes work, but reflects actual uses. The file's age alone could not distinguish those needs.

In a glossary of company terms (in Polish), agree what statuses mean: current, under review, superseded and historical. If every team understands them differently, a coloured label will not help. A status should say whether the material can be used to act, not merely look good in a legend.

Record the outcome for one instruction

For the fictional document "Preparing a spare-parts quotation", the note might state that the old form description has been replaced by a new instruction. The reason is a change in required inputs and the way prices are approved. The process owner confirms the scope, the library owner adds the notice, and the person responsible for employee onboarding updates the starter pack. Each task points to a specific place of use, so completion can be checked later.

Add the routes by which people reach the material: a search result, a link from an internal form and the file in the training pack. For each route, record what a user should see after the change. Outcomes may differ: the current instruction, marked history or an explanation of where to raise an unusual case. Not every old route has to disappear, but none should lead to outdated action without a warning.

If the company uses AI-generated summaries, also check the answer to a question about preparing a quotation in this particular process. Record the material cited by the tool and the passage that needs assessment. If uncertain, return to the owner of the source or integration. Do not treat a tidy library as proof that every downstream copy is current just because the main page now looks right.

This record allows an honest close: the team knows which known places have been corrected and which still need checking. It does not promise to find every copy downloaded in the past. It does direct attention to routes that matter to the work. At the next review, the team can start with a specific list of dependencies instead of rediscovering where the salesperson found that reliable old PDF.

Check the withdrawal with a real task

Ask someone who did not take part in the clean-up to find the instruction and prepare one step of a quotation. Start from the search tool or onboarding pack that people actually use. Check whether they reach current material and understand the archive notice. If they return to the old file, fix the route that took them there.

Record remaining limitations, owners and a date to check again. Repeat the archive review when the process, offer or tool sources change. The point is not to move every date forward each year. It is to stop documentation directing work once it no longer describes that work correctly.

If you want to organise the knowledge used by your team and AI, see the scope of Aeneia Audit services.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear