What is an Electronic Document Management System?

What an EDMS is

An Electronic Document Management System (EDMS) is software that captures, stores, organises, secures and tracks an organisation's documents across their entire life — from the moment they are created or scanned to the moment they are archived or destroyed.

That definition sounds like file storage, and this is where most evaluations go wrong. A shared drive stores documents too. What separates an EDMS is that it makes documents accountable: each one has a type, a set of attributes describing it, a controlled version history, an explicit list of who may see it, a record of everyone who has, and a defined point at which it must be reviewed for destruction.

A useful test: for any document in the organisation, can you say what it is, who has seen it, which version is authoritative, and how long it has to be kept? Four questions. A system that cannot answer all four is storage.

EDMS, DMS, EDRMS and ECM

Tenders use these terms interchangeably, which causes real problems at evaluation because they describe different scopes.

• DMS — document management system. The general term for storing, organising and retrieving documents.
• EDMS — electronic document management system. Adds electronic capture, workflow and lifecycle control to the above.
• EDRMS — electronic document and records management system. Explicitly adds records management: retention schedules, record declaration, disposition and archival transfer. If your organisation has statutory retention obligations, this is what you actually need, whatever the tender calls it.
• ECM — enterprise content management. The broadest term, extending beyond documents to web content, media and other unstructured content.

The practical advice: do not argue about the acronym. Specify the capability. If retention, legal hold and evidenced disposal matter to you, write them into the requirements schedule explicitly, because a system marketed as an EDMS may not include any of them.

The eight components every EDMS needs

Whatever the product, an EDMS is assembled from the same eight components. Use them as the structure for a requirements schedule — grouping requirements this way makes bids comparable and lets you weight evaluation by what actually matters to your organisation.

Who needs an EDMS

The common factor is not size or sector. It is whether the organisation has to prove something about its documents to somebody else — a regulator, an auditor, a donor, a court, or a citizen exercising a right to information.

In practice that means government ministries, county governments, state corporations and regulators; banks, SACCOs, microfinance institutions and insurers; hospitals and health institutions; law firms and professional practices; universities and colleges; NGOs and development programmes with donor audit obligations; and energy, manufacturing and utility operators with engineering document control requirements. Each has a sector page setting out the specific record types and obligations involved.

Signals you have outgrown shared drives

Most organisations do not decide to buy an EDMS. They reach a point where the absence of one starts costing visible money or visible embarrassment. These are the usual signals:

• Someone regularly asks the whole office whether anyone has the latest version of a document.
• A file has to be physically located before a decision can be made or a query answered.
• Approvals are tracked in a spreadsheet, or not tracked at all.
• Nobody can say how long the organisation keeps a given class of record, or who decided.
• An audit or information request triggers a search exercise rather than a report.
• Documents containing personal data sit in shared folders whose permissions nobody has reviewed.
• Staff email attachments to each other because filing them properly takes too long.
• A departing employee takes institutional knowledge with them because it was never in a shared file.

Two or three of these is normal. Five or more and the organisation is carrying a cost it has stopped noticing, paid in staff time, delayed decisions and audit findings rather than on an invoice anyone can point at.

What an EDMS costs

There are two pricing models, and the difference between them matters more than the headline number.

Per-user subscription. Standalone EDMS products are typically licensed per user per month, commonly in the range of USD 10 to 60 depending on the product and the capability tier. This is predictable, scales with headcount, and never stops.

Deployment pricing. Where the system is built on a platform you already license — Microsoft 365, for instance — you pay for the deployment rather than for seats. EDMS by Sibasi is priced this way: from USD 5,000 for a Basic Deployment, USD 25,000 for a Standard Deployment with workflow automation, and USD 65,000 for a Premium Deployment with AI processing, records management and integrations. The pricing page sets out what is included at each tier and the six variables that move a quote.

Whichever model you are considering, model five years. A subscription that looks modest in year one is frequently the larger number by year three, and it scales with every user you add. Budget separately for digitisation of existing paper, which is usually the largest single line in a first deployment and should never be priced without a sample survey.

Seven questions that separate the bids

Feature checklists stop being useful once every vendor has answered "yes" to all of them. These questions produce answers that actually differ.

Where implementations fail

Failed EDMS projects rarely fail on technology. They fail in four recognisable ways, and all four are avoidable at specification stage.

• Adoption. The system works, and staff carry on emailing attachments, because filing properly means leaving the application they are working in. Insist on seeing filing done from inside Outlook and Teams before you buy.
• A vendor-designed file plan. A classification scheme your records officers did not shape will be worked around within a month. The file plan must be designed with them and signed off before configuration starts.
• Digitisation priced on a guess. The largest line in most first deployments, and the most commonly revised upward after award. Require a sample survey before accepting a number.
• Records management left out of scope. The organisation procures storage, then discovers at audit that retention, disposal and legal hold were never included and must be bought again.

Our implementation methodology sets out how a deployment is structured to make each of these harder, and the tenders page covers what a workable EDMS specification needs to contain.

Where to go next

If you are specifying a system, the capability matrix is organised the way a requirements schedule should be. If you are building a business case, the pricing page is published rather than gated. If you want to see whether any of this survives contact with your own documents, book a demo and bring one.