An email document management system captures emails and their attachments as managed records. Each message is filed against a client, matter or project. Its sender, recipients and date are kept as metadata you can search. Retention rules decide how long it stays, and an audit trail shows who opened, changed or deleted it. Some products call this an email content management system. The job is the same.
Most small firms meet this question from the other side. They already have years of client mail in Gmail or Outlook, and they want to know if it counts as a record. They want to know if they have to copy it all somewhere else to keep it properly. Often they don’t. The mailbox can be the record, if it does a short list of things well.
This page covers when an email is a record, what a kept copy has to carry, and the two ways to keep one. Then it shows how to make the mailbox itself the record, so you aren’t running a second filing system beside it.
What an email document management system does with a message
The system takes a message out of one person’s inbox and gives it a place the firm controls. That happens in five steps:
- Capture. The email and its attachments go in, by a button, a rule or a drag.
- Classify. It’s tied to a client or matter, and its header fields become searchable metadata.
- Protect. Permissions decide who can open it, and a declared record can’t be quietly edited or deleted.
- Keep. A retention rule holds it for a set period, and a hold stops the clock when a dispute appears.
- Dispose. When the period ends, it’s deleted on purpose, with a note that it was.
Software built to do this has its own standard, ISO 16175-2:2011. It covers products “often termed” electronic records or enterprise content management systems. The vendors, their add-ins and their 2026 prices are in software for document and email management, along with the free options. This page is about the record itself.
When an email counts as a record
An email is a business record when it’s part of how the firm does its work. A client’s approval is a record. So is the advice you gave, the fee you quoted and the deadline you agreed. A newsletter you skimmed isn’t.
US courts use a test for this. Federal Rule of Evidence 803(6) lets a business record in as evidence when these conditions hold:
(A) the record was made at or near the time by … someone with knowledge; (B) the record was kept in the course of a regularly conducted activity of a business, organization, occupation, or calling, whether or not for profit; (C) making the record was a regular practice of that activity
So an email earns its weight from how it was made and kept. It was written at the time, by someone who knew, as part of the normal run of work. A message that sits untouched in the mailbox where it arrived fits that well.
How long each kind of record has to be kept is a separate question. The tax, law, health and advisory periods are in how long to keep emails, with a schedule you can write in an afternoon.
What a kept email has to carry
The clearest US rule on this is written for federal agencies, not for private firms. It’s still the best plain list of what makes a kept email whole. 36 CFR 1236.22(a) asks agencies to preserve these:
(1) The names of sender and all addressee(s) and date the message was sent must be preserved
(2) Attachments to electronic mail messages that are an integral part of the record must be preserved as part of the electronic mail record.
In other words, the text alone isn’t the record. Who sent it, who got it, when, and what was attached are part of it too. The way you save a message decides how much of that survives:
| How the email is kept | Sender, recipients, date | Attachments | Full headers | Still part of the thread |
|---|---|---|---|---|
| Left in the mailbox | Yes | Yes | Yes | Yes |
| Saved as an .eml or .msg file | Yes | Yes, inside the file | Yes | No |
| Filed by a DMS add-in | Yes, as metadata fields | Usually, filed with it | Depends on the product | Linked, if the product does it |
| Printed to PDF | As printed on the page | No, saved separately if at all | No | No |
| Printed on paper | As printed on the page | Only if printed too | No | No |
Print-to-PDF is the most common habit, and it keeps the least. It’s fine for a copy to hand someone. As the firm’s only copy, it drops the attachments and the routing data a dispute might turn on.
Two ways to keep email as a record
There are two ways to keep email as a record. One files a copy somewhere else. The other keeps the original where it already sits and puts rules on that place.
| File a copy | Keep it in place | |
|---|---|---|
| Where the record lives | A DMS, a practice system or a shared drive | The Gmail or Outlook mailbox |
| Who does the work | Each person, message by message, or a filing rule | An admin, once, through retention settings |
| What it’s good at | Gathering one matter’s mail beside its documents | Keeping everything, with nothing missed |
| Where it slips | Mail nobody filed. Copies filed twice. | Mail anyone can delete, until rules are set |
| What you pay | A DMS seat or add-in, plus everyone’s time | Often nothing extra, depending on your plan |
Filing a copy feels like the careful choice. Here’s the catch, and it’s the one place on this page where a common belief costs real money. The filed copy doesn’t replace the mailbox copy. Both are now records.
A discovery request reaches whatever is in your “possession, custody, or control”, in the words of Federal Rule of Civil Procedure 34(a)(1). That’s the DMS and the mailbox. A hold has to cover both. Your retention schedule has to delete from both, or one of them keeps everything by accident. Two filing systems mean two places to search, hold and clean, and one of them depends on people remembering to file.
The mailbox as the record: what it has to do
A mailbox can be the record. It just has to do the jobs a records system does. The federal rules give a useful checklist here as well. 36 CFR 1236.22(d)(1) says an agency’s email system can hold the record copy only if it has every feature in 36 CFR 1236.20(b). In plain terms, those are:
- Declare. Mark something as a record, with its own identity.
- Capture. Take records in.
- Organize. Tie each record to a retention schedule.
- Secure. Prevent unauthorized changes or deletion, with an audit trail of use.
- Retrieve. Control who can see records and let them search.
- Preserve. Keep records readable for as long as they’re kept.
- Dispose. Delete what’s eligible, on schedule.
A small firm isn’t bound by this rule. It’s still a fair test of whether your mailbox is a records system or just a big folder. Here’s how the two big suites line up against it. Plans and licensing vary, so check yours before you count on a row.
| Job | A mailbox with no settings | Google Workspace with Vault | Microsoft 365 with Purview |
|---|---|---|---|
| Capture | Every message, as it lands | The same | The same |
| Organize by schedule | No | Retention rules by organizational unit, date range and search terms | Retention policies and labels, including a file plan |
| Declare and lock | No | Retention rules and holds keep mail, without a per-message record mark | A retention label can mark an email as a record, which blocks editing and deletion |
| Audit trail | Limited | A Vault log of rule changes, searches and exports | “Labeled message as a record” appears in the audit log |
| Holds | No | “Holds take precedence over retention rules.” | Litigation Hold and retention policies |
| Dispose | Whatever people delete | Expired data “is removed from user accounts and purged from all Google systems”, except under hold | Disposition reviews, with proof of deletion |
Two details matter more than the rest. Google says that, by default, “Google Workspace data stays in user accounts until the user or admin deletes it.” So an untouched Workspace mailbox keeps everything, and anyone can delete anything. Microsoft goes further for the strictest case. Once a regulatory record label is on an item, Microsoft says “nobody, not even a global administrator, can remove the label.” That suits a firm with a regulator demanding it. Most small firms want the ordinary record label, or just a retention policy.
Which plans include Vault, Purview retention and holds is set out in what email compliance software a small firm needs.
Keep by mailbox, not by message
The hardest part of any records system is the person who has to file each message. NARA, the federal archive, met this problem across the whole government. Its answer was to stop asking.
NARA Bulletin 2013-02 set out the Capstone approach:
Using this approach, an agency can categorize and schedule email based on the work and/or position of the email account owner.
That lets an agency keep a senior official’s whole mailbox permanently and keep everyone else’s for a set period. NARA says it “cuts down reliance on print-and-file, click-and-file drag and drop, or other user-dependent policies.”
Capstone governs federal agencies. It places no duty on a private firm. The idea carries over well, though. Instead of asking each person to decide about each email, set the rule once per mailbox:
- Client-facing mailboxes are kept for your longest client period, counted from the end of the work.
- The shared office address is kept on the same schedule, since clients write to it.
- Mail tied to a dispute goes under a hold, whatever the mailbox.
- A departing employee’s mailbox is converted or archived on purpose, and kept on the same schedule.
Nobody has to file anything for the record to be whole. The mailbox is complete because nobody took anything out of it.
The few messages that also go in the client file
Keeping the record in place doesn’t mean nothing ever leaves the inbox. A small set of messages are worth a copy in the client file as well:
- the signed engagement letter and the email that sent it
- the client’s written approval of a scope change or a fee
- advice that a later decision rests on
- anything you’d attach to a filing, a claim or an audit response
This is a copy for convenience. The mailbox original stays where it is, under the same retention. Which files belong in a shared drive or DMS, and which can stay attached, is set out in where a file belongs in a small firm.
One firm, worked through
Elena runs a five-person landscape architecture firm on Google Workspace. Client mail goes to each designer and to a shared studio address. A client dispute two years ago took her a week of searching, and she asked whether she needed a document management system.
She decided she didn’t. Here’s what she set up instead, in one afternoon:
- One retention rule for everyone. Mail is kept for seven years, which covers her longest client period. Vault applies it to the whole organization.
- A hold, ready to use. She knows where the hold setting is and who places it: she does, the day a demand letter arrives.
- One label per client. Each project thread carries the client’s name, so one search gathers a project’s mail.
- A short list for the project folder. Signed contracts, approved drawing sets and change orders get a copy in the shared drive.
- A rule for leavers. A departing designer’s mailbox is kept, not deleted, and stays under the seven-year rule.
Her records live where her mail already lives. There’s no second system to feed. The next time a client asks what was agreed, the answer is one search away, with its date, its sender and its attachment intact.
Point and the mailbox you keep
Point sorts and files mail in the Gmail or Outlook account you already have. The record never leaves the place your retention settings reach.
Mail is read and sorted as it lands. What needs you sits at the top, and the rest waits. In Gmail, each triaged message carries a Now, Later or Other label. In Outlook it’s a category with the same names. Filing a thread in Point archives it in your own mailbox as well. It isn’t deleted, so it’s still there for the next search and still under your rules. Attachments that matter land in a Documents list, named and dated. Each one opens back onto the thread it came in, so the file and the conversation stay together.
Point isn’t a records system. It doesn’t declare, lock or dispose of anything. Your Vault rules or Purview policies do that, inside your suite. To do its work, Point keeps its own working copy of your correspondence and the summaries and search index built from it. The privacy policy sets out how long each one lives. If you’re checking any AI tool against a mailbox you have to keep, what to check before you connect your inbox has the questions. The rest of a working day with Point is laid out in what Point does for a small firm.
Common questions
What is an email document management system?
It’s software that captures emails and attachments as managed documents. Each message is filed against a client, matter or project, with its sender, recipients and date stored as searchable metadata. The system adds permissions, retention rules, holds and an audit trail. M-Files, NetDocuments and iManage are examples.
What is an email content management system?
It’s another name for the same kind of product. “Content management” is the wider term and covers documents, images and web content as well as email. When the subject is email, both names mean capturing and governing messages as records.
Is an email a business record?
Usually, yes, when it’s part of how the firm does its work. Federal Rule of Evidence 803(6) treats a record as reliable when it was made at the time by someone with knowledge, kept in the regular course of business, and made as a regular practice. Client approvals, advice and agreed deadlines fit that. Newsletters and routine notices don’t.
Can my Gmail or Outlook mailbox be my records system?
It can, once retention settings are in place. A mailbox with no settings keeps mail until someone deletes it, so anyone can remove a record. With Google Vault or Microsoft Purview retention, mail is kept for a set period, held during a dispute and deleted on schedule. Check that your plan includes those features.
Is a PDF of an email good enough as a record?
It’s a reasonable copy to share, but a weak only copy. A PDF keeps what was printed on the page. It drops the full headers, and attachments aren’t inside it unless you save them separately. The original in the mailbox, or an .eml or .msg file, keeps all of that.
Do I need to save emails to a DMS if my mailbox has retention?
Not for the record itself. Retention in the mailbox keeps the whole correspondence. A DMS helps when several people work the same client’s documents and need versions and permissions beside the mail. If you do file copies, the mailbox originals are still records, so your holds and deletion schedule have to cover both.