How to choose document management software

Most document management projects that disappoint were chosen from a feature grid. Every vendor ticks most of the boxes, so the grid says little about whether the system will handle your invoices, your personnel files or your contracts the way your people work. This guide takes the other route: start from your documents, decide what really matters, and make vendors prove it on your own files.

Ademero sells document management, so read this with that in mind. The advice is meant to work whichever system you pick.

Start from your documents and processes, not features

Before you look at any product, spend an afternoon writing down what you have. For each kind of document, note:

Five or six document types usually cover most of the pain. Rank them by how much time they waste today, and you have the core of your requirements in words your staff will recognize.

Must-haves vs nice-to-haves

A must-have is something you would walk away over. Keep the list short; if everything is a must-have, nothing is. A typical split for a mid-sized organization:

Move items between the columns to fit your organization. What matters is deciding before the demos, not during them.

Capture and indexing

Capture is how documents get in, and indexing is how they get the fields people search by. It is where most of the daily labor lives, so test it hardest. Ask how each arrival route works: scanning (including stacks of mixed documents), email attachments, watched folders that other systems drop files into, and forms. Then ask which fields fill in without typing: barcodes, fixed zones on a form, values read by AI, lookups from your own database.

Two details separate good systems from tiring ones. First, what happens to a document the system cannot index on its own: there should be a clear queue where a person finishes it. Second, whether duplicates are caught while indexing rather than months later.

Click to enlarge

Search

People search by what they know: a word on the page, a vendor, a date range, an employee ID. Insist on both full-text search of scanned pages (which needs OCR at capture) and field filters, combined in one search. Then check the details that save time every day: saved searches, highlighted hits on the page, exporting results to a spreadsheet, and links that open a document or a search straight from another application.

Most important: results must respect permissions. A search should never reveal that a document exists to someone who cannot open it.

Click to enlarge

Security and permissions

Ask how access is controlled at each level, and test the answers with real roles during the proof of concept:

• Sign-in

  Your directory or single sign-on, multi-factor authentication that an admin can require for everyone, password policy and lockout.

• By document type

  Separate rights to view, search, add, edit, download, share and delete.

• By field and by value

  Hiding a salary field, or letting a branch manager see only that branch’s documents.

• Outside people

  How a document is shared outside the organization, whether the share expires, and what the recipient can reach.

• Other systems

  API keys that can be limited to certain areas, expire and be revoked.

Ask too which of the vendor's own staff can reach your documents, and how that access is recorded. For hosted systems, ask exactly where documents are stored.

Audit trail, retention and legal holds

An audit trail should record sign-ins, searches, views, downloads, changes, deletions, approvals and emails, with who and when, and it should not be something a user can switch off. Each document should also keep its own version history.

Retention is the other half of records control. Look for retention periods set per document type and applied automatically, a scheduled destruction process, and a way to keep a specific document indefinitely when it is under a legal hold, with a record of who made that override. If you do not yet have a written schedule, start with our records retention policy template.

Workflow, approvals, e-signatures and forms

Workflow is where a document system pays for itself, because it stops people chasing paper. Check that an administrator can build rules without code; that approvals support groups, voting rules, deadlines, escalation and substitutes during absences; and that every decision lands in the audit trail. Our workflow automation guide covers what good looks like in detail.

For signatures, ask who can sign (staff only, or anyone with an email address), whether you can set a signing order, and what the finished document looks like. If you need signatures to meet a particular legal standard, have your own counsel review how each vendor signs; do not rely on a marketing page. For forms, ask whether a submitted form is filed with its data in one step, or whether someone retypes it.

Integrations with accounting and ERP

The usual target is accounting: approved invoices should reach your accounting system or ERP without retyping. Ask which systems the vendor exports to today, out of the box; whether lists like vendors and GL accounts can come from the accounting system; how duplicates and failed exports are flagged; and whether fields can be looked up from your own databases. Ask to see the export in the demo, not a slide about it.

For anything else, ask what the API does and, just as important, what it does not cover.

Cloud, on-premises or hybrid

Where the system runs decides who maintains it, who can reach the documents and how it connects to systems on your own network. Cloud means nothing to install and easy access from anywhere. On-premises means documents stay on servers you control and your IT team runs them. Hybrid setups mix the two, for example capturing and filing on-premises while sharing selected documents outside.

We cover this in two places: the cloud vs on-premises comparison lays the two models side by side, and the on-premises guide explains who still needs their own servers, the trade-offs and hybrid patterns.

Migration from shared drives or an old system

Migration is usually the most underestimated part of the project. Plan it before you sign:

1. 01

   Decide what moves

   Old files past their retention period may be better destroyed under your policy than migrated.
2. 02

   Mine the folder structure

   On a shared drive, folder and file names often hold the index data, such as vendor or year. Ask whether the import can turn them into fields.
3. 03

   Get the old index data out

   From an old system, ask for documents and their index data together, plus version history and audit data if you must keep them.
4. 04

   Clean up naming first

   A consistent naming standard makes import mapping easier. Our file naming convention template helps.
5. 05

   Migrate in waves

   One department or document type at a time, checking counts and spot-checking documents after each wave.

Ask the same question in reverse: how would you get everything out of this new system if you left?

Total cost questions

The license is one line of several. Before comparing quotes, make sure each vendor has answered the same questions:

• What is priced

  Users, concurrent users, servers, storage, modules, scanning stations or document volume.

• Setup and migration

  Who configures it, how many days it takes, and what would make it take longer.

• Support and upgrades

  What maintenance includes, response times, and whether new versions are included.

• Your own costs

  Servers, database licenses and backup for on-premises; staff time for administration in either model.

• Growth and renewal

  What happens to the price when you add users or departments, and at renewal.

Compare over several years rather than on the first invoice, and include the hours your staff spend today.

How to run a proof of concept on your own documents

A short proof of concept with your own files is worth more than a polished demo. Keep it tight:

1. 01

   Pick two processes

   One high-volume (such as invoices) and one with records rules (such as personnel files or contracts).
2. 02

   Gather real samples

   A few dozen real documents per type, including the messy ones: poor scans, multi-page, handwritten notes, odd layouts. Remove or mask anything you cannot share.
3. 03

   Write success criteria first

   Which fields must fill in, how a person fixes what is missed, what an approver sees, what reaches accounting.
4. 04

   Use real roles

   Have an AP clerk, an approver and an auditor-minded person each try their own tasks, signed in with their own permissions.
5. 05

   Try to break it

   Search for a document you should not see. Reject an approval. Let a deadline pass. Export a duplicate. Check the audit trail afterwards.
6. 06

   Score it the same way for every vendor

   Against the criteria you wrote, not against the demo script.

Red flags

• Demos only on the vendor’s sample documents

  You learn how the product handles their files, not yours.

• Vague answers about exit

  If getting your documents and index data out is unclear before you buy, it will be worse after.

• “Integrates with everything”

  Ask which systems, out of the box, and to see one working.

• Audit logging that can be switched off

  An audit trail anyone can disable is not one an auditor will trust.

• Every answer is “custom development”

  Fine for rare needs; a warning sign for approvals, retention or accounting exports.

• Prices that depend on features you have not chosen yet

  Ask for a quote against your written requirements.

Vendor question list

Send the same questions to every vendor on your shortlist before the demos, and ask for written answers. Copy the list into an email or document and add your own.

Where Ademero fits

Ademero makes the pieces most buyers end up needing, so you can start with one and add the rest:

• CapturePoint 6 is the scanning and capture station: it splits stacks, recognizes document types and reads fields on the PC, then files to folders, Content Central, SharePoint or OneDrive, Google Drive, Dropbox or Nucleus One.
• Content Central is document management on your own servers: capture, full-text search, permissions down to field level, audit trail, retention and legal holds, no-code workflow and approvals, e-signatures, and exports to QuickBooks, Sage 50, Sage X3, Workday and Epicor. People work in a web browser. See the Content Central help library.
• Nucleus One is our cloud document system, with workflows, tasks, forms, e-signatures, client portals, Zapier, a REST API and iOS and Android apps.

To see how the products fit together, read document management solutions. Comparing us with other vendors? Our comparison hub is a fair place to start.

Questions