Document management

The client record, not the folder tree

The shift a document system makes is from folders to records: every file attached to the client, the entity, the year and the job it belongs to, so the file is found by asking who and when rather than by remembering where. That is what lets a second person pick up a client, what makes the busy season survivable, and what an inspector or an insurer expects to see. A folder tree in a shared drive can imitate it for a while; it stops working at the first departure.

What to look for

Integration with the practice system as the client record, so a new client creates the structure and a job knows its documents. Capture from email without leaving the inbox, because correspondence is most of the file. A filing convention the tool enforces rather than suggests. Full-text search across everything. Retention and deletion rules that match the firm's obligations. Version history and an audit trail of who did what.

Then the client side: a portal or request tool through which clients send documents against a list, sign what needs signing, and find what the firm sent them, without email attachments in either direction. The request list is the feature that ends the year-end chase.

Collection as a process

Firms that run document collection well build a standard request list per job type, send it from the document system on a schedule, let the tool remind the client, and see at a glance which clients have sent what. The bookkeeper stops asking for the bank statement; the tool asks, and the client uploads from a phone. That single change is where most of the category's value sits for a small firm.

The failure mode is a portal the client does not use because email is easier. Mobile capture, a single sign-in and reminders the client expects are what make the portal the easier path.

Pricing and how firms recover it

Vendors price per user for the firm's staff, sometimes with storage bands, and client portals may add a per-client element. The directory records what vendors publish; it does not say what a firm should charge for document handling, and nothing here is fee advice. Firms describe treating the document system as overhead inside every fee rather than a line the client sees.

Migration and the first ninety days

The move is the hard part: years of shared-drive folders, several naming conventions, and an email archive. Firms that do it well migrate the active clients first with the new convention, leave the archive searchable where it is, and set a date after which nothing new goes to the old place. The convention should be written before the migration, not discovered during it.

What to avoid

A document system without a practice-system link. Any convention the tool does not enforce. A portal without mobile capture. Migrating the archive before the active clients. And email attachments continuing after go-live: the day a partner emails a client a PDF instead of using the portal is the day the team follows.