Document management: definition, examples and good practice

Definition

Document management covers everything a team does with its documents after creating them: where they are saved, how folders are organised, how versions are tracked, who can open them and how people find them later. It applies to written documents, spreadsheets, designs, contracts, scans and any other file the work depends on.

Large organisations sometimes use dedicated document management systems with formal approval flows. Most teams simply need a shared, well-organised place for files that sits close to the work.

Why it matters

Documents carry decisions, agreements and deliverables. When they are poorly managed, teams send the wrong version to a client, lose a signed contract, or spend time recreating something that already exists.

Good document management matters because it gives:

• One current version, so nobody works from an outdated copy.
• Findability, so a file can be located in seconds rather than minutes.
• Control, so sensitive files are only seen by the right people.
• Continuity, so knowledge stays when people leave.

How it works

A typical document management approach includes:

1. A shared storage location, rather than personal drives or email attachments.
2. A folder structure that mirrors how the team works, often by client or project.
3. Naming conventions that make files easy to scan and sort.
4. Version history, so earlier versions can be recovered and the latest is obvious.
5. Access control, deciding who can view or edit each area.
6. Search and tags to find files across folders.

Examples

• An architecture firm keeps drawings, site notes and client decisions in one folder per project, uploading a new version of each drawing rather than a new file.
• An agency stores each client's brand guidelines, briefs and approved assets together.
• An accounting firm keeps each client's documents for a financial year in a dedicated folder with clear names.

Common problems

• Files in email. Attachments get forwarded and edited, creating many conflicting copies.
• Personal drives. Important files live in one person's account and disappear when they leave.
• "Final_v3_really_final". Without version history, file names become the version system.
• Documents far from the work. Files sit in a drive with no link to the project or task they belong to.
• Folder chaos. Every person invents their own structure.

Best practices

• Store project files with the project, not in personal locations.
• Agree a simple folder structure and naming convention, and write it down.
• Upload new versions instead of new copies.
• Link or reference documents from the tasks that use them.
• Review access when a project ends or a person leaves.
• Archive finished projects rather than deleting them.

Our guide on how to organise company documents sets out a practical structure you can copy. Keeping files next to the work is part of connected work.

How Emitii approaches it

In Emitii, each space can turn on Docs & Files. It holds folders, docs written in a Markdown editor, uploaded files and links. You can rename, move, colour and tag items, search within them and navigate by folder tree. Uploaded files support versions through "Upload new version" with a version picker, docs can be downloaded as PDF, and PDFs preview in the app. Docs have comments like the rest of the space.

Read more on the document management feature page.