Small business document management system: file by client

What a simple document management system for a small business must do: filing by client, fast search, access by client, and where Standards stops.

The Standards team

In short

A simple document management system for a small business files each client document on the client it concerns, where the people who handle that client find it by name and nobody else sees it. You set one up by choosing where files live and giving each client the same folders, then you move inboxes and desktops into it.

What is a document management system for a small business?

A document management system (DMS) for a small business is one shared place where your team stores, files, finds and controls access to business documents, in place of desktops, email attachments and a shared drive nobody tidies. For a firm that works on client files, such as an advisory practice or a brokerage, most documents belong to one client: an ID scan, a signed engagement letter, a tax return. Vendor guides such as Docupile and Cloudvara (both read October 2026) describe a central repository with folders, search, permissions and version control, and treat the client as one more folder name. When work is organized by client, a simple system files each document on the client record itself, so finding the client finds its files. Standards, an AI-native CRM, works this way, with a drive on every client record.

What must a simple document management system do?

A simple document management system must do six things well for a business drowning in client files. It keeps files in one place, files them by client, shows which documents a client still owes, finds files fast, limits who sees them and recovers what someone removed by mistake. Standards covers those six. Standards searches file names rather than the words inside scans, and the table names the three jobs it leaves to other tools.

Need

What it means for client files

How Standards handles it

One place

No more desktops, inbox attachments and personal drives

Every client record has its own drive: folders, drag-and-drop upload, sort by name or date

Filing by client

Each document sits with the client it concerns

The drive belongs to the record; a record's Documents tab also shows the drives of related records

Required documents

You know which client still owes an ID or a signed agreement

A document field can be Required and limit its file types; a record still missing one shows a warning

Search

Find a file without knowing its folder

Search each client's drive by file name; find any client from one bar, typos included

Text inside scans

Find a figure in a scanned statement

Standards reads PDFs and images with OCR and agents answer from that text; no search bar matches the words inside a scan

Access

Staff see only the clients they handle

A private record's drive follows the record's sharing: Can view or Can edit

Recovery

Undo a mistaken removal

Archived documents stay listed and can be restored

Version history

Go back to last month's draft of a file

Standards keeps no version history of a file

Approval and signature

Route a draft to a reviewer, collect a client's signature

Standards has no approval workflow on documents and no electronic signature; file the signed PDF on the record

Why file documents on the client record instead of in folders?

Filing documents on the client record means the client is the index: you open the client and see its files, instead of guessing which folder a colleague used. A folder tree on a shared drive depends on everyone following the same naming rules, and the Cloudvara guide (read October 2026) spends a whole section on naming conventions for that reason. In Standards, each client record carries its own drive, so a passport scan uploaded to a client's record stays with that client instead of landing in a colleague's folder. The same record holds the client's emails and meetings, matched by the participants' email addresses, so the signed letter and the mail that asked for it sit side by side. When a file belongs to a related record, such as a household member or a company the client owns, the Documents tab lists that drive too, and you drag the file across. Firm-wide files such as policies go in a drive of their own, listed under Drives in the sidebar.

How to set up document management by client in five steps

You set up a client-based document system in five steps: decide what each client file must contain, set the folders every client gets, create the clients, move existing files in, and route new files as they arrive. The first step is a decision for the partners; the fourth, moving the files, takes the longest.

  1. The partners list the documents every client file must hold (ID, signed engagement letter, latest statement) and the folders the rest goes into, such as Onboarding, Planning and Correspondence.

  2. Your developer or the Standards team declares the folders once as the preset for your client records, so every new client's drive opens with them.

  3. Your team drops the client spreadsheet, or an export of your old tool, into a conversation with an agent, which creates the client records; the required documents show on each record as fields to fill.

  4. Each person drags the files from their desktop and the shared drive into the matching client's drive, and archives what no longer applies.

  5. An agent, when you ask it, copies the attachments of a client's email into Standards and files them on that client's record, then reads a scan and fills the record's fields from it.

If your clients still live in a spreadsheet, step three starts with our guide to building a customer database from your client spreadsheet.

How do you find a client document in seconds?

You find a client document in seconds by searching for the client first, then for the file inside that client's drive. In Standards, the search bar finds any client record from a few letters, even with a typo. Inside the record, the search icon of the Documents tab searches every folder of the drive by file name, up to five levels deep, and shows each match with its folder path. Open a digital PDF in the viewer and you can search for a word inside it. Standards does not search the words inside scanned files across all your clients: it reads PDFs and images with OCR, and agents use that text, but the search bar matches records, and each drive's search matches file names. Name files for what they are, such as "Passport, client surname, 2026", and ask an agent when you need what a scan says. An agent reads the document and answers, or copies the values into the record's fields.

Who should see which client's files?

Each person should see the files of the clients they handle, and no more. In Standards, access to documents follows access to the client record. A role grants read, create, update and delete per object, so you can let an assistant view client records without deleting them. A record can also be private to its owner, then shared with named colleagues as Can view or Can edit. Its drive follows those shares: a viewer lists and downloads the documents, and an editor also adds, renames and moves them and decides who has access. Someone who cannot see the client record cannot see its drive at all. Agents follow the same rules: an agent acts within the permissions of the person it works for. In Auto mode, the default, it files and edits without asking; before it deletes anything or sends anything outside the firm, it shows you what will change and waits for your approval.

What a CRM-based document system does not do

A document system built into Standards covers filing, finding and sharing client files, and leaves three jobs to other tools: version history, electronic signature and approval workflows. If your firm's work turns on contract drafts reviewed in rounds, a dedicated DMS such as SharePoint fits those jobs better. SharePoint numbers each version of a document and lets approvers control when content is published (Microsoft Learn, read October 2026). For a small firm whose files are mostly received, scanned and signed elsewhere, those three gaps matter less than knowing every client's file is complete.

  • Version history: Standards keeps no version history of a file, so keep dated copies when the history of a draft matters.

  • Electronic signature: clients still sign in your signature tool, and you file the signed PDF on their record.

  • Approval workflow: Standards does not move a document through stages such as Draft, Reviewed and Approved, the workflow Docupile describes for document control (read October 2026).

The full behaviour of files, drives and uploads is in the Standards documentation on files and documents.

Example: a fictional advisory firm moves its client files

Juniper Ridge Wealth is a fictional nine-person financial advisory firm, used here as an example. Its client files live in three places: a shared drive with one folder per adviser, each adviser's inbox, and a scanner folder nobody empties. The partners decide that every household file holds a photo ID, a signed advisory agreement and the latest account statement, and that the rest goes into Onboarding, Planning and Correspondence. With the three folders declared as the household preset, an agent creates the households from their client spreadsheet, and each drive opens with those folders. Over the following weeks, each adviser drags their households' files across, and the Required marks show which households still owe a signed agreement. When a client emails a new statement, the adviser asks an agent to save the attachment to that household; the agent files it and copies the account value into the record. A new hire covering for an adviser opens the household and sees its documents next to the client's mail and meetings.

Questions

Before you switch tools.

Three kinds compete: a shared drive such as Google Drive or Dropbox, a standalone DMS such as SharePoint or DocuWare, and a CRM that files documents on client records, such as Standards. A shared drive is the quickest to start and keeps recent versions, 30 days on Dropbox Basic (read October 2026). A standalone DMS adds approval workflows, and SharePoint numbers every version of a document. A CRM ties each file to its client and to the client's mail.

A free shared drive such as Google Drive is enough while one or two people file documents and follow the same naming rules. It breaks down when several people file for one client, when access must differ by client, or when you must know which client still owes a document. Then a system that files on the client record saves the hunt. Standards is billed per person per month, setup included, and the price is given at the first meeting.

A CRM with a drive on each client record can replace a document management system for client files: storage, filing, search by name, access by client and restoring archived files. It does not replace one for version history, approval workflows or electronic signature: those stay in your signature or drafting tool, and the final files come back to the client record.

  1. Move client by client, starting with the clients you work on this month, and leave the old shared drive read-only until the last folder is moved. In Standards, each file you drag into a client's drive is filed from that moment. Standards checks each file's type against its content when you upload it, and a single file can be up to 50 MiB.

File every client document on the client

Standards gives each client record its own drive, marks the documents a client still owes, and lets agents file mail attachments and read scans for you.