
Records management: what you keep, for how long, and where
Records management sounds like something for councils and the NHS. Yet every business holds documents it may be held to later: an employment contract, a quote that became an order, an inspection report. This article covers the arrangement around them: which documents they are, how long they stay, where they live and how they are disposed of in a way you can prove.
A record is a document that captures something you may be held to later. Records management is the arrangement for which documents those are, who owns them, how long they stay and how they go.
At its heart is a retention schedule per document type, with an owner, a trigger, a period and an end action. The periods come from your accountant or solicitor, not from IT.
A schedule only works when systems carry it out: one agreed location per type, a retention label that expires on its own, and a disposal log you can show.
What records management is, and what it is not
Not every file is a record. A draft, a note or a copy you forward is working material. A record is the document that captures what was agreed, decided or done, and that someone may come back to: a customer, an employee, HMRC, a court or an auditor. The signed contract, not its tenth draft.
Records management is the arrangement around those documents. Which types exist, who is responsible for each, how long they stay, where they are held and what happens when the period ends. It is a policy with an implementation, not a product.
Two things sit outside it, each with its own question. Making an archive technically unalterable is a storage question. How confidential something is, is a classification question. Records management is about the life of a document: from the moment it becomes a record to the moment it may go.
Start with document types, not with files
Anyone who starts by trawling the file server drowns. Start with your processes and ask, for each, which documents come out of it that you must be able to produce. In an ordinary business that gives you a few dozen types:
- People: employment contracts, payslips, right to work checks, absence records, applications from candidates you did not hire.
- Finance: invoices, bank statements, annual accounts, VAT and tax returns.
- Customers and suppliers: contracts, signed quotes, handover reports, complaints.
- Quality and safety: inspections, audit reports, incident logs, certificates.
- Governance: board minutes, resolutions, powers of attorney.
For each type, note the system it is created in: the payroll package, the accounts software, an account manager’s mailbox, a SharePoint folder. That column is the most useful part of the exercise for IT, because it shows where one type lives in four places at once.
The retention schedule: five columns per type
A document retention policy usually comes down to one table, the retention schedule. For each document type it records five things:
- Owner. The role that decides about this type: HR for personnel files, finance for the accounts. Not IT, which carries it out.
- Trigger. When the period starts to run. More on that below, because that is where it usually goes wrong.
- Period. The minimum time the record stays, and for personal data also the maximum. HMRC generally expects company records to be kept for six years from the end of the accounting period, but some records need longer and personnel data has its own rules. Have your accountant or solicitor fill in this column.
- End action. Destroy, review first, or keep longer with a stated reason.
- Location. The one system where the record is held.
A two page schedule that is right is worth more than a manual nobody opens. Start with the types that carry the risk, people and finance, and work outwards.
The trigger is harder than the period
“Six years” sounds clear until you ask: six years from when? For an invoice it is roughly the year it was issued. For an employment contract it is the end of employment, which may be twenty years after the file was created. For a customer contract it is the end of that contract.
Systems only know the creation date by themselves. Set a rule to “six years after creation” and you delete the contract of someone who still works for you. The answer is event based retention: the file gets an end date when someone leaves or a contract expires, and the clock starts from there.
That needs an integration or a fixed step in the process: whoever processes the leaver form also sets the end date on the file. Agree who does it, or it will not happen.
One place per type, and what to do with copies
A record exists once, in an agreed place. Copies always appear around it: the email attachment, the download on a laptop, the file shared in a chat. Those copies are outside the schedule, and everyone should know it: keeping the copy keeps nothing that counts, and deleting the copy deletes nothing that counts.
In Microsoft 365 you carry out the schedule with retention labels in Microsoft Purview. One label per type, applied to the library where that type belongs, with the period and the end action. A label can mark an item as a record so it cannot be changed or deleted until the period ends. Which labels and features your licence includes varies by plan; check that before you design the schedule.
Email is a special case, because a mailbox mixes records and noise. Our article on email archiving covers it.
Disposal, with evidence
Disposal is as much part of records management as retention. UK GDPR requires that you do not keep personal data longer than necessary, and the ICO expects you to be able to explain your retention periods. A file left years too long turns a data breach into a bigger problem than it needed to be.
Do not dispose silently; dispose with a review and a log. Let the system report which items have reached the end of their period, let the owner review that list, and keep the list itself: which type, which period, who approved, when. That disposal log is the evidence that you follow your own policy.
Do not forget backups. A deleted item stays in the backup until that backup expires. That is normal, but write down how long it takes, so you can explain it when someone asks whether their data is gone. For paper and retired devices, see data destruction and wiping.
When a dispute arises: pausing the schedule
There will be a moment when a document must not go, even though its period has ended: a customer claim, an employment tribunal, an investigation. You then need to pause disposal for those items without switching off the whole schedule.
Agree beforehand who takes that decision (a director or your solicitor, not IT), how the request arrives and how the hold is lifted. Technically it is usually possible: a hold on a mailbox, a site or a selection of items that overrides any label. The problem is almost always organisational: nobody knows it exists, or nobody removes the hold once the matter is over.
Where our work stops
We are not solicitors, tax advisers or archivists, and we do not set retention periods. How long a document type must stay, and which originals must be kept on paper, is for your accountant, your solicitor or the rules of your sector.
What we do is the IT side: mapping where each document type actually lives, translating the schedule into retention labels and settings in Microsoft 365 and other systems, lining up backup retention alongside it, and making sure disposal produces a log you can show.
Questions we get about this
The five that come up most often.
What is records management?
Records management is the arrangement for the documents you may be held to later: which types exist, who owns each, how long they stay, where they are held and how they are disposed of. It is a policy carried out in your systems, not a separate product.
What is the difference between a document and a record?
A document is any file you work on, such as a draft or a note. A record is the document that captures what was agreed, decided or done, such as the signed contract. Records get a fixed location and a retention period; working documents do not.
What should a document retention policy include?
A retention schedule listing, for each document type, an owner, the trigger that starts the period, the period itself, the end action and the system where the record is held. Add who may pause disposal during a dispute, and how disposal is logged.
How long should a business keep its records?
It depends on the type of record. HMRC generally expects company records to be kept for six years from the end of the accounting period, but some records need longer and personal data should not be kept longer than necessary. Have your accountant or solicitor set the periods per type.
Do you decide how long we must keep our documents?
No. We are not solicitors or tax advisers and we do not set retention periods. We make sure the periods your adviser sets are carried out in your systems, with labels, backup retention and a disposal log you can produce.
Further reading
What records management connects to.
Make your retention schedule actually work?
Send us the retention schedule your accountant or solicitor has drawn up, or the list of document types you already have. We will show you where those records live today and how to carry out the schedule in your systems.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.