Document management is the controlled capture, classification, storage, retrieval, sharing, retention, and disposal of business records, not a digital filing cabinet.
You're preparing a client file, but the signed engagement letter isn't where it should be. There's an unsigned copy on the shared drive, a scan in someone's inbox, and a document named “final revised” on a former employee's desktop. Finding a file is only part of the problem. You also need to know which copy counts, whether you must keep it, and whether you could recover it after a server failure.
Document management controls information throughout its working life. That includes Word documents, spreadsheets, emails and attachments, database exports, digital photographs, scanned invoices, contracts, and supporting evidence. The file format doesn't determine whether something needs control, its business purpose does.
A shared drive gives employees somewhere to put files. A document management system adds rules: unique identifiers, required descriptive fields, assigned permissions, version histories, and retention instructions. You can configure some controls around a shared drive, but folders alone don't provide them.
The scale can be enormous. In 2024, the U.S. National Archives and Records Administration accessioned 463 terabytes of electronic records into its permanent archival collection, according to its agency financial report. A small firm faces a smaller volume, but still needs to preserve context, identify authoritative copies, and keep information usable.
The everyday activities fit together like this:
For a more operational view, NARA's Universal Electronic Records Management Requirements organize requirements into six lifecycle functions: capture, maintenance and use, disposal, transfer, metadata, and reporting. These functions help you evaluate what happens before and after someone clicks Save.
Six functions of document management
| Function | What it controls | What fails without it |
|---|---|---|
| Capture | Intake into a controlled system with a unique identifier | Files stay in email and scanner folders |
| Maintenance and use | Finding, sharing, and working on the current copy | Staff edit obsolete duplicates |
| Disposal | Approved decision to keep or destroy | Hoarded files or premature deletion |
| Transfer | Move to another custodian, archive, or system | Context is lost in a migration |
| Metadata | Descriptive, technical, and provenance fields | Search and retention cannot be trusted |
| Reporting | Exceptions such as uncategorized files and access violations | Problems show up only as complaints |
Say a tax firm can't locate last year's signed engagement letter. The receptionist scanned it, the preparer received an attachment, and the partner saved another copy in a personal folder. Buying a better search tool might locate those copies, but it won't establish which one the firm should trust.
The intake process needs an owner. That person confirms the signature, associates the document with the client and engagement, and files it in the approved location. An exception report should flag documents that arrive without the information needed to place them correctly.
Practical rule: If nobody owns the step between receiving a document and filing it correctly, the office hasn't finished designing its document process.
When someone asks “what is document management?”, the useful answer is a set of controlled decisions, not just a software category. Pick a document your office regularly loses, then identify the missing lifecycle function. Start fixing that failure before reorganizing every folder.
A document management system provides the machinery behind those controls. To evaluate it, follow a document through ordinary office work: someone creates it, another person reviews it, a client signs it, and an employee retrieves it later.
Versioning keeps related revisions in an understandable chain. A draft fee schedule, its reviewed revision, and its approved release shouldn't appear as unrelated files that employees must compare manually. Staff should see which revision is current without opening each attachment.
Version history also needs meaningful status. “Most recently uploaded” doesn't necessarily mean “approved,” and a signed PDF shouldn't replace the editable source document.
These controls perform different jobs:
Indexing means assigning structured information to a document so staff can sort, locate, and track it. A scanner-generated filename tells you very little; a unique record ID linked to a client, document type, and reporting period gives the scan a business identity.
NARA's metadata guidance says metadata should remain accurate and consistent whether it's captured in the recordkeeping system, embedded in the file, or both. In practice, distinguish these categories:
Use controlled selections for client IDs and document categories rather than letting employees invent spellings. During migration, export the identifying information with the files so a scan doesn't become disconnected from its matter.
Search should combine document text with structured filters. Optical character recognition, which converts scanned text into searchable text, helps employees find words inside a PDF. Filters then narrow the result to signed engagement letters for a particular client and year.
Access control determines which results a person may see and what they may do with them. A partner, preparer, and client portal user need different permissions; an audit trail should record relevant viewing and editing activity. Use a user access controls review to examine those boundaries rather than assuming that successful login means appropriate access.
For firms coordinating permissions across hosted applications, IT Cloud Global, LLC's resource on how to manage cloud access and spending provides broader governance context. Keep document permissions connected to named responsibilities, including who approves access and removes it.
Before evaluating a tool, write down the required fields for your most common document. Test whether employees can leave them blank, bypass them during bulk imports, or select an inactive client without a warning.
The easiest way to make document management concrete is to follow a familiar file. Different offices organize their work differently, but each needs employees to recognize the authoritative copy without relying on someone else's memory.
Say an accounting practice stores source documents, workpapers, returns, invoices, and engagement letters by client and tax year. Before the process is controlled, a preparer starts work using an unsigned letter from the shared drive because the signed attachment remains in a partner's inbox.
Afterward, the signed letter appears in the client-year workspace with a clear status and assigned owner. The preparer can verify the agreed scope before opening the workpapers, and the reviewer doesn't have to reconstruct the agreement from an email chain.
The improvement isn't just tidiness. The firm has made an important work decision, whether the engagement is authorized, easier to verify.
For a law firm, the organizing unit is usually the matter. Contracts, correspondence, evidence, pleadings, and billing records need that context because a client may have unrelated matters with different teams and obligations.
Before control, an associate finds a pleading in a folder but can't tell whether it's the filed document or a draft prepared before the final amendments. After control, the filed copy has a recognizable status and its filing confirmation stays with the matter.
A client-facing workspace should expose the intended document, not the firm's entire internal working set. That distinction matters even when everyone involved works on the same matter.
Say a nonprofit's grant writer keeps an award agreement on a laptop, with reporting instructions buried in email. When that employee leaves, the successor has the application but not the signed terms explaining what the organization promised.
After control, the award agreement belongs to the grant file rather than to the employee's desktop. The successor can locate the executed agreement, its reporting conditions, and related correspondence without accessing a former employee's personal working folders.
A useful handover transfers responsibility for the file, not just access to a computer.
Nonprofits should apply the same care to donor information, board minutes, and supporting material for organizational filings. These documents have different audiences, so placing them together in a broadly accessible administrative folder isn't a sufficient classification scheme.
Use a data classification framework to assign business categories and sensitivity labels before moving files. Across these offices, success means employees know which copy counts, who owns it, and which obligation determines its treatment. A departed employee shouldn't take the only usable copy with them.
Must we keep this, or may we delete it? Uploading a file doesn't answer that question. For practical business purposes, treat a record as evidence of an action, decision, transaction, or obligation that the organization needs to preserve.
A signed contract is an obvious example. An email can be equally important if it contains the client's approval of a change, while an unused draft may have little continuing value. Don't assume that every draft is disposable, though: its content, use, applicable rules, and any legal hold still matter.
AI-generated content needs the same examination. NARA's guidance on federal records and AI explains that outputs saved in agency systems and used for official business may qualify as federal records, and some scheduled transitory records may be retained for fewer than 180 days. That federal example isn't a general deletion deadline for private firms.
If an employee uses an AI summary to support a client decision, assess the summary and any necessary supporting context under your records policy. Don't classify it as disposable merely because software generated it.
What to keep and what you may delete
| Item | Record status | Handling |
|---|---|---|
| Unused working draft | Usually not the record copy if nobody relied on it and no other duty applies | Supersede when the final exists, subject to policy and holds |
| Signed letter, contract, or filed return | Record | Keep for the applicable legal, tax, contractual, or operational period |
| Email that records a client decision | Often a record | File it with the matter, not only the inbox |
| Scan that replaces paper | Copy of record once replacement is authorized | Give it an ID tied to client and year |
| AI summary used in the file | Can be a record | Apply the approved schedule before deletion |
| Transitory note | Short-lived record when classified that way | Use the authorized transitory schedule, not a blanket deadline |
| Anything under legal hold | Subject to preservation | No disposal until the hold is lifted |
A scan doesn't automatically authorize shredding the original. Confirm applicable original-document requirements and verify that the image is complete, legible, and correctly associated before treating it as the replacement.
Build a repeatable habit around the decision:
Keeping everything forever isn't a substitute for a policy. Neither is deleting files because the folder looks old. Have the responsible legal, tax, or compliance adviser approve schedules, then retain evidence of authorized disposal.
Verizon's 2025 Data Breach Investigations Report presentation reports ransomware in 44% of reviewed breaches and 88% of breaches involving small and medium-sized businesses. A searchable repository doesn't protect a firm from losing access to its records.
Centralization can concentrate damage when an attacker gains powerful credentials or exploits vulnerable software. Scanning the paper is an intake improvement, not proof that the digital archive can survive an incident.
Physical and digital protection need to work together:
Ask operational questions that require evidence rather than reassurance:
Understand the distinction between cloud storage and cloud backup. A synchronized deletion can spread to another device; that isn't the same as recovering an independent historical copy.
Use least-privilege access, which means granting only the permissions a person needs, and multifactor authentication for user and administrator accounts. Separate routine work from administrative access so an ordinary compromised account can't readily dismantle recovery protections.
Use this accompanying video as a prompt for a practical continuity discussion:
Assign an owner to restoration tests and record elapsed time, missing items, and corrective actions. Set a recurring test interval that reflects how long your firm can operate without its records.
A backup job that reports success proves that a job ran. A completed restore test provides evidence that your team can recover.
If nobody can demonstrate recovery of a complete client file, treat the system as unfinished, however convenient its search box may be.
The document rules stay the same, but who runs the server changes. An on-premise system runs on hardware the firm owns, maintained by internal IT or a local consultant. A cloud-hosted system runs offsite, with the hosting provider managing the infrastructure covered by its service agreement.
Cloud-hosted DMS versus an on-premise server
| Criterion | Cloud-hosted DMS | On-premise server |
|---|---|---|
| Where files live | Provider data center | Office server room |
| Who patches and maintains | Hosting provider, within the agreed scope | In-house IT or a local consultant |
| Day-to-day access | Any adequate internet connection, with authorized access | Office network or a configured VPN |
| Upfront spend | Subscription and less local server hardware | Servers, storage, and licenses |
| Adding users or storage | Adjust the hosted environment and licensing | Expand existing capacity or install hardware |
| Who owns backups | Provider performs agreed duties; the firm retains oversight | The firm arranges and oversees backups |
| Best fit | Multi-site firms with little IT staff | Firms that require physical custody and can run hardware |
Neither choice automatically fixes scattered repositories. In NARA's 2024 annual performance report, 71% of reporting U.S. federal agencies said they had met the goal of managing all temporary records electronically. Electronic handling is a meaningful step, but it doesn't by itself establish where authoritative information lives or how it should be governed.
The hosting distinction is straightforward:
A firm with several offices, remote staff, and limited IT capacity will often find managed hosting a practical fit. Employees can use the hosted application without the firm maintaining a server room, but internet reliability and local scanning arrangements still need testing.
On-premise operation can suit a firm with a genuine physical-custody requirement and staff able to maintain hardware. Ownership brings responsibility for patches, storage capacity, hardware replacement, monitoring, and recovery arrangements. A server in the office isn't safer just because someone can see it.
For either model, list who performs each task and who checks completion. Separate application administration from infrastructure maintenance: a hosting team may maintain the server while your office still decides document categories, user roles, and disposal approvals.
Use the cloud versus on-premise comparison to structure that operational decision. Compare the full working arrangement, including support, connectivity, application licensing, migration, and the staff time required to run it.
Before committing, select a representative matter or tax-year archive that contains more than clean PDFs. Include scans, email attachments, editable workpapers, signed documents, and the identifying fields employees use.
Run an acceptance exercise:
Include an export test too. Your firm should understand how to retrieve files and their associated information if it changes applications or hosting arrangements. A successful demonstration using a sample document isn't enough if your actual email attachments or scanned bundles behave differently.
We host FileMaker Pro, eFileCabinet, and FileCenter DMS. Our Workgroup Server is a fully managed IT environment that includes 24×7 support, server maintenance, and daily data backups. Those services address infrastructure work, while your firm remains responsible for deciding which information counts as a record and how employees should handle it.
For a proposed hosted deployment with us, bring the representative working set and request access-control and restoration evidence before committing. Confirm the scope of backup coverage and how recovery requests will be handled rather than inferring those details from the word “managed.”
Choose the arrangement your firm can operate and verify. The deciding evidence should be a usable restored file, correct access boundaries, and clear responsibilities, not the length of a feature tour.
Cloudvara offers managed hosting for document management applications so your team can use a controlled workspace without maintaining the underlying office server. Visit Cloudvara to discuss your existing application, scanning workflow, and recovery requirements, and bring a representative client file to ground the conversation in how your firm works.
