
Choosing a document management system: what the IT side has to sort out before you sign
A document management demo shows how neatly a file moves through a workflow. What it does not show is whether that file ever gets in: from the scanner, from Outlook, from the finance system, with the right permissions and without someone saving it to their desktop first. This is the list the IT side should go through before you choose a DMS.
A document management system solves the problem of files nobody can find or that exist in five versions. If you do not have that problem, you probably need a better folder structure rather than a DMS.
Whether people use it depends on the integrations: scanner, email, finance and signing in with the same account. A document that does not arrive on its own does not arrive.
Before you sign, ask how you get out: in what format your documents and their metadata come with you. That decides whether you can still choose freely in ten years.
What document management does that a file share does not
A document management system stores documents not in folders but with attributes: client, case, document type, date, status. You search for what something is rather than where it lives. On top of that come a few things a file share or an ordinary cloud folder does badly or not at all:
- Versions. One document with a history, instead of “quote-final-2-new.docx” next to three others.
- Workflow. A supplier invoice that reaches the budget holder after scanning, gets approved and then moves to finance, with a record of who did what.
- Permissions per case. HR files, contracts and client documents each with their own circle, without building a ten-level folder tree to get there.
- Retention and deletion. A period per document type, and a prompt when it runs out.
So the honest question is: which of these four are you missing today? If the problem is only findability, a tidied folder structure in the platform you already have is often enough. If it is workflow, or files that belong to several departments, a DMS starts to earn its keep.
Start with the documents, not the product
Most DMS projects begin with a comparison of vendors. Turn it round and begin with a list of the documents the system has to carry. For each document type, four questions:
- Where does it come from? Paper in the post, a PDF by email, an export from the ERP, something a colleague writes.
- Who needs to act on it? Read it, add to it, approve it, or send it out.
- Which attributes does it need? Client number, case number, invoice number: anything you will want to search on later. What you do not capture when filing, you will not find later.
- How long must it be kept? That period is set by your accountant or legal adviser, not by IT; IT makes sure the system can enforce it.
Then start with one process, usually supplier invoices or HR files, not with “everything”. A DMS that works in one department sells itself to the next. One that is half introduced everywhere at once becomes a second file share.
Integrations decide whether it gets used
A document management system stands or falls on how little effort it takes to get something into it. Do not ask each vendor whether an integration exists; ask how it works and who maintains it.
- Scanners and multifunction printers. Can the device scan straight into the DMS, with text recognition and a fixed destination per button, or does it go through a holding folder? Every holding folder is a place where documents pile up. How printers and scanners fit into that flow is on our page about printing and document flows.
- Email. An attachment filed into the right case from Outlook in one click, with sender and date as attributes.
- Finance and ERP. Who sends which data to whom, and what happens when one system is updated and the other is not yet.
- Microsoft 365 or your office software. Opening and editing without downloading first, or everyone ends up working in a local copy anyway.
Also ask what happens to an integration during an update. A connector built by a vendor’s partner often falls outside the maintenance of both. Agree who fixes it when it stops.
Access, sign-in and people who leave
A DMS with its own usernames and passwords is one more place where a leaver still has access. Require it to sign in with the same account as the rest of the workplace (single sign-on, with Microsoft 365 through Entra ID), so that disabling one account closes everything.
- Permissions through groups, not individuals. Someone who changes department changes group, and with it their access. Individual permissions are no longer understood after a year.
- External sharing. Can a client or accountant see a case, and if so: with their own account, with a link that expires, and is it recorded what they opened?
- Admin rights. Who may change attributes, workflows and retention periods. That is a different role from IT administration and should not sit with everyone who has an admin account.
- Logging. Who opened, changed or deleted what, and how long that log is kept.
Personal data will almost always end up in it, so a cloud service needs a data processing agreement with the vendor under UK GDPR or the GDPR.
Cloud or your own server, and how you get out again
Most document management systems are now bought as a service, and for most organisations that is the sensible choice: no server to patch, updates handled by the vendor. Your own installation still makes sense when the DMS has to reach deep into on-site software, or when there is a requirement about where data is held. The trade-off itself is in our article on own servers or the cloud.
Whichever way you go, three questions belong in the quote:
- Where the data is held, in which country and data centre, and who can reach it for support.
- What is backed up, and by whom. A cloud vendor protects against its own failures; a deleted folder or a user who wipes a case by mistake is often your problem.
- How you get out. Not just the files, but the attributes, versions and audit log, in an open format. An export that only produces PDFs in a zip file throws away exactly what you bought the DMS for.
What drives the price is usually the number of users, the amount of storage, the number of workflows and what is added for integrations and configuration. Ask for those last two separately; that is where quotes differ.
Moving off the file share
Filling a DMS with the contents of a file share is not a copy job. The folder structure holds information the DMS wants as attributes, and it has to be translated somewhere. A workable order:
- Clean up first. Duplicates, expired drafts and folders of people who left years ago. What you do not bring, you do not have to migrate or secure.
- Then translate. Record for each folder which attributes its files get: “Clients/1043 Smith/Contracts” becomes client number 1043, type contract.
- Pilot with one case, and have the people who use it find things in it. Only when they can do you carry on.
- A fixed cut-over day, after which the old share is read-only. Two places to save to means two versions within a month.
How to prove nothing was lost in such a move is covered in our article on data migration without loss.
Who looks after it once it is live
After go-live a DMS needs two kinds of administration, and they often get mixed up. Functional administration is about content: which attributes exist, how a workflow runs, who may add a new document type. That belongs with someone in the organisation who knows the processes. Technical administration is everything around it: accounts, integrations, scanners, the workplace, backup and updates.
Agree before go-live who holds which role, and who calls the vendor when a workflow gets stuck. Without that, every question lands with IT, including questions about configuration that only the vendor can answer.
And plan a short check once a year: are the groups still right, are retention periods running out as intended, and does the export still work. Everyone forgets that last one until the day it is needed.
Where our work stops
What we do. We handle the IT around a document management system: the workplace and Microsoft 365, sign-in with one account, groups and permissions, scanners and multifunction printers, the network, backup, and cleaning up and moving the file share. We also help you put the questions in this article to a vendor.
What we do not do. We do not sell or implement DMS software. The product belongs to a third party, and configuring workflows and document types is done by the vendor or its implementation partner. We are not lawyers or tax advisers either: which retention period applies to which document is for your accountant or legal adviser to decide. We make sure the system can carry out what they decide.
Questions we get about this
The five that come up most often.
What is a document management system?
A document management system stores documents with attributes such as client, case and document type, rather than only in folders. It keeps versions, can route documents to people through a workflow, handles permissions per case and can enforce retention periods. You search for what a document is, not where it is stored.
Do I need a DMS or is a good folder structure enough?
If the only problem is finding things, a tidied folder structure is often enough. A DMS pays off when you need workflows, such as invoice approval, or files that belong to several departments each with their own access. So start by asking which of those functions you are actually missing.
What should I look for when choosing a DMS?
The integrations with scanner, email and finance, sign-in with the same account as the workplace, permissions through groups, and where the data is held. Also ask how you get out: whether you can export documents with their attributes, versions and audit log in an open format. That decides whether you can still choose freely later.
How do you move files from a file share into a DMS?
Clean up first, then record for each folder which attributes its files get, then run a pilot with one case that users search themselves. After that comes a fixed cut-over day, after which the old share is read-only. That stops two places to save from existing side by side.
Do you supply and implement DMS software?
No. The product comes from a software vendor, and the vendor or its implementation partner configures the workflows and document types. We handle the IT around it: accounts and permissions, the workplace, scanners, the network, backup and migrating existing files. Which retention periods apply is decided by your accountant or legal adviser.
Further reading
What a DMS connects to.
Choosing a DMS and getting the IT around it right?
Send us your list of document types and the products you are considering. We will tell you what each one asks of integrations, permissions and migration; the choice of product stays with you.
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.