Skip to content

Guide · DMS

How to organise a company document management system

How do you structure a document management system so that it is adopted, maintained and useful every day?

A successful DMS is a governed DMS

A document management system (DMS) is not a remote hard drive. It is a system: who uploads, how things are filed, who approves, how long documents are kept, how they are found. This guide proposes a realistic organisation for a small or mid-sized company — without a two-year project.

DMS organisation framework

Think light governance + living content. The tool follows; it does not replace the rules.

Named governance

A business owner (often admin / legal / a small IT team) and champions in each department. Without an owner, the DMS decays.

A short taxonomy

A list of document types and controlled tags. 20 well-used types are better than 200 phantom ones.

An explicit lifecycle

Draft → under review → published / signed → archived. Each state has its own rights and actions.

Quality at the point of entry

OCR, type and key fields on upload. Fixing things at entry costs less than cleaning up three years of archives.

Steps

An actionable sequence, from diagnosis to follow-up.

  1. Set business objectives

    E.g. find a contract in under 2 minutes, approve an invoice within 48 hours, prepare for an audit without panic. Three objectives at most.

  2. Define taxonomy v1

    Types (contract, invoice, Kbis company registration extract, payslip…), departments, business tags. Have them validated by the pilot teams.

  3. Set access rights

    Who reads, who uploads, who approves, who administers. Clearly separate HR / finance / legal where needed.

  4. Choose the priority workflows

    One or two flows (contracts, invoices). A DMS without workflows stays a storage place; with too many workflows, it becomes an overengineered monster.

  5. Roll out the pilot

    One department, a short training session, hands-on support for 4 to 6 weeks.

  6. Expand and clean up

    Add departments and types gradually. Schedule a quarterly review: dead tags, duplicates, outdated access rights.

Mistakes to avoid

The pitfalls that derail most document projects.

The “big bang” project

Migrate everything, for everyone, right away. Prefer pilot → expansion. A big bang produces phantom folders.

Folder trees as the only compass

Eight-level folder structures don’t survive reorganisations. Types, tags and search hold up better.

Nobody responsible for quality

Without a metadata review, the DMS fills up with “miscellaneous” and badly named PDFs.

Forgetting the exit

Archiving and retention periods are part of the organisation. Otherwise the repository turns into a dump.

DMS organisation checklist

  • Business objectives stated (≤ 3)
  • DMS owner and department champions named
  • Taxonomy v1 (types + tags) published
  • Access rights matrix approved
  • 1–2 priority workflows defined
  • Pilot launched with training
  • Entry rule for new documents enforced
  • Quarterly review scheduled (quality + access rights)

DocPilot as an operational DMS

DocPilot combines a document repository, OCR, workflows and search — without imposing a fixed folder tree.

Types, tags, departments, domains

Organise by metadata and by how your company really works, not by a mandatory folder tree.

Multi-channel ingestion

Inbound e-mail, web, photo, mobile: the DMS is fed where documents are created.

Built-in workflows

Approvals and tasks in the same tool as storage — no more PDFs “pending” outside the system.

Workspace administration

Organisation profile, users, departments, workflows and subscription managed from the company / team area.

FAQ

Frequently asked questions

DMS or Drive: do you have to choose?

Drive remains useful for light collaboration. The DMS holds documents that have a lifecycle (contracts, official records, approvals). Many companies use both — with a clear rule about what must go into the DMS.

How many document types to start with?

Aim for around twenty at most, grouped into families. Refine them after real-world use rather than freezing a theoretical encyclopaedia.

Who administers the DMS day to day?

An owner (often administration or legal operations) with workspace admin rights, plus business champions responsible for upload quality in their department.

How do you handle multiple sites?

Keep a common taxonomy and differentiate using departments / domains / site tags. Avoid a separate folder tree for each site that ends up duplicated.

Take action

Structure your DMS without overengineering

Roll out DocPilot on a pilot: types, access rights, one workflow — then expand department by department.