# Automatic email filing for construction projects: an Outlook-first guide

Canonical: https://cogram.com/guides/automatic-email-filing-construction-projects
Publisher: Cogram — AI tools for architects and engineers (https://cogram.com)

---
{/* Reviewed 2026-07-30 (Soumaya) — source checks resolved, internal links live. Panel ids: [15, 16, 33, 48, 64, 65] · gtm-inbound source: posts/articles/automatic-email-filing-construction-projects.md */}

On a construction project, email is the record. RFIs, submittal correspondence, owner directives and half the design decisions live in individual inboxes, and when a claim arrives two years later, the project record is whatever got filed. Firms we've spoken with describe the same pattern. A filing policy exists on paper, and actual filing falls far short of it because the people with the most valuable email have the least time to file.

This guide covers why filing fails, the four approaches available to an Outlook-based firm, what keeping Outlook while fixing filing looks like, and retrieval across historical project email.

## Why project email filing fails

Filing fails for behavioral reasons before it fails for tooling reasons. Filing each message means deciding which project it belongs to, which folder within that project, and whether the attachments need separate handling. Each decision is small. Multiplied across a day's inbox on several jobs at once, it is a task that competes directly with billable work, and it loses.

Three consequences follow.

First, the record fragments. Each person files their own slice, differently, or files nothing. The project's correspondence exists in aggregate across a dozen mailboxes and nowhere in particular.

Second, the record leaves with people. When a PM changes firms, their mailbox is archived or deleted on IT's schedule, and the unfiled portion of the project record goes with it.

Third, retrieval breaks at the worst moment. A firm most needs a complete correspondence trail during a dispute, a claim, or a fee negotiation, which is when reconstructing it from individual mailboxes is slowest and least defensible.

Any fix has to remove the per-message decision from the person, or reduce it to something that survives a busy week. Tooling that still depends on individual discipline inherits the original problem.

## What to evaluate in any approach

Fix the criteria before comparing options. Five questions separate the approaches:

1. **Who does the work per message?** Does each email require a human decision, a one-time rule, or nothing?
2. **Is the filed record shared?** Filing into a personal folder structure solves retention but not fragmentation. The record needs to be visible to the project team.
3. **Does filing preserve searchability?** A filed email that cannot be found by sender, date, project, or content is stored rather than filed.
4. **What happens to attachments?** Drawings and PDFs carried in email are often the substantive record. Check whether they are extracted, indexed, and openable.
5. **What does it cost to leave?** If the tool holds the filed record in a proprietary store, confirm the export path before you commit.

## The four approaches

### 1. Manual folders in Outlook

The default. Each person maintains project folders in their own mailbox and drags messages in. It costs nothing and requires no IT involvement. It also fails every shared-record criterion above: the work is per-message and per-person, the record is private, and it disappears with the mailbox. The failure mode described in the previous section is this approach operating as designed.

### 2. Outlook rules

Rules move messages automatically based on sender, subject keywords, or recipient address. For a small number of stable patterns, such as a project-specific distribution address, they remove the per-message decision. They do not scale to project work. Correspondents change over a project's life, subject lines rarely carry reliable project identifiers, and one message can concern two projects. There is also a hard ceiling. Exchange Online allots 256 KB total for a mailbox's inbox rules, a quota Microsoft states cannot be increased ([Microsoft documentation](https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/outlook-on-the-web/increase-the-space-used-by-inbox-rules)). Rules also file into the same private mailbox folders as approach 1, so the shared-record problem remains untouched.

### 3. SharePoint drag-to-library

Dragging email from Outlook into a SharePoint document library puts the message in shared, IT-governed storage, which fixes the fragmentation and retention problems. The mechanics undercut it. The email lands as a .msg or .eml file whose metadata (sender, recipients, sent date) is not extracted into library columns without third-party add-ins. Filtering the correspondence record therefore degrades to filename search ([Microsoft Q&A](https://learn.microsoft.com/en-us/answers/questions/981585/storing-emails(drag-and-drop)-in-sharepoint-online)). Attachments inside a filed .msg cannot be opened from the browser preview without downloading the file into a desktop client ([Microsoft Tech Community](https://techcommunity.microsoft.com/t5/sharepoint/drag-drop-msg-into-document-library-cannot-open-attachments-nor/td-p/449949)). And the new Outlook for Windows does not support dragging messages to SharePoint at all, which breaks the workflow as Microsoft migrates users off classic Outlook ([Microsoft Q&A](https://learn.microsoft.com/en-us/answers/questions/1643734/saving-an-email-to-sharepoint-in-new-outlook-versi)). Most important, the per-message human decision survives intact. Drag-to-library is manual filing with a shared destination.

### 4. Dedicated email filing tools

A category of tools exists for exactly this problem, most of it built in and for the AEC industry.

**Ideagen Mail Manager** is an Outlook add-in originally built inside Arup and sold to Ideagen in 2022 ([Oaklins deal record](https://www.oaklins.com/baltics/en/deals/107934/)). It prompts for a filing location at the point of sending and uses machine learning to suggest the destination, filing into your existing storage: SharePoint, network drives, ProjectWise, or similar ([Mail Manager](https://www.mailmanager.com/product/features)). The filing decision is reduced to confirming a suggestion rather than eliminated.

**Newforma Project Center** files email through an Outlook add-in with a File in Project button, or via "Items to File" folders in Outlook that a synchronize action sweeps into the project record as .msg files ([Newforma documentation](https://projectcenter.help.newforma.com/learning/how-tos/synchronize_outlook_and_proj_cent/)). It is a full PIM suite, and email filing arrives bundled with the wider platform. Firms we've spoken with who run it describe the filing step as still manual in practice, and adoption across a project team as the recurring struggle.

**TonicDM** files email from Outlook to a shared project email box through a sidebar add-in, drop folders named with the project number, or a project-specific CC address ([TonicDM documentation](https://help.tonicdm.com/en/articles/892253-filing-project-email)). It requires Microsoft 365 and runs on PC, Mac, and Outlook on the web. AECbytes reviewed it as a deliberately lean PIM option ([AECbytes review](https://www.aecbytes.com/review/2024/TonicDM.html)).

**Cogram** (our product) connects to Outlook and files email and attachments to the appropriate project automatically, using AI to read the message rather than asking the user to choose a destination. Filed correspondence sits in shared project folders searchable by the whole team, and projects can sync from Deltek Vantagepoint, Vision, or Ajera so filing targets stay current ([cogram.com/email-management](/email-management)). The design goal is criterion 1 at zero decisions per message. Email filing requires Outlook / Microsoft 365 today. On security: no training on customer data, SOC 2 Type II, SSO (SAML 2.0), TLS 1.3 / AES-256 encryption, customer-controlled storage.

Within this category, the difference to evaluate is where each tool sits on the automation spectrum, from prompt-assisted manual filing to fully automatic classification. If your concern is misfiled email, test the classification accuracy of any automatic tool on a live project during a pilot before trusting it with the record.

## Comparison at a glance

| Approach | Work per message | Shared record | Metadata searchable | Attachments handled | New cost |
|---|---|---|---|---|---|
| Manual Outlook folders | Human decision, every message | No | Within one mailbox only | Stay inside the message | None |
| Outlook rules | One-time setup, breaks as projects evolve | No | Within one mailbox only | Stay inside the message | None |
| SharePoint drag-to-library | Human decision, every message | Yes | .msg metadata not extracted natively | Not openable from browser preview | None (M365) |
| Dedicated filing tools | Confirm-a-suggestion down to zero, by tool | Yes | Yes, by design | Extracted or indexed, by tool | Per-seat licence |

## Keeping Outlook while fixing filing

None of the dedicated tools above replaces Outlook, and that is the correct shape of the fix. Firms we've spoken with are consistent here: PMs will not change where they read and write email, so the filing layer has to attach to Outlook rather than compete with it. In practice "keep Outlook, improve filing" means four things:

1. Email is read, written, and sent in Outlook exactly as before.
2. A connected service or add-in captures project correspondence into a shared record, with the per-message burden as close to zero as the tool allows.
3. The shared record is where the team searches, so retrieval no longer depends on who filed what.
4. IT retains normal Microsoft 365 governance, since nothing about the mailbox itself changes.

A pilot should measure, above everything else, the fraction of a live project's correspondence that ends up in the shared record without anyone being chased. That is the number manual policies fail on, and the number that predicts whether the record will be there in two years.

## Search and retrieval across historical project email

Filing exists so that retrieval works. Evaluate retrieval as three separate capabilities, because tools differ on each:

- **Scoped search.** Search within one project's correspondence across every participant's filed email, by sender, date range, and content. This is the baseline a shared record buys, and what individual mailbox search cannot do.
- **Attachment search.** The approval often lives in a PDF or a marked-up drawing carried by an unremarkable email. If attachments are not indexed, the search misses the substance.
- **Question-shaped search.** Newer AI search finds "the email where the structural engineer approved the transfer beam change" without the searcher knowing sender or date. Cogram's search works this way over filed correspondence (our product claim). Whatever tool you evaluate, test retrieval with your own historical questions during the pilot, since marketing pages all describe search the same way.

One boundary condition matters for historical email. A filing tool captures the record from deployment forward. Ask every vendor what back-filing an existing project's mailbox archive involves, because answers range from bulk import to not supported.

## FAQ

### What is automatic email filing for construction projects?

Automatic email filing captures project correspondence from individual Outlook inboxes into a shared, searchable project record without requiring each person to file messages by hand. Tools range from add-ins that suggest a filing location at the point of sending to AI systems that classify and file email with no per-message action.

### What software stops project managers drowning in email filing?

Dedicated AEC email management tools remove or shrink the per-message filing decision. Ideagen Mail Manager and Newforma prompt-assist filing from Outlook, TonicDM files via sidebar, drop folders, or a CC address, and Cogram files automatically using AI classification. The differentiator to test is how much work each message still requires from the PM.

### How do I stop losing project emails in Outlook?

Move the project record out of individual mailboxes into a shared store. Manual folders and Outlook rules keep email private to one mailbox, so departures and archive policies destroy the record. A filing tool attached to Outlook, or a disciplined shared-mailbox convention, ensures correspondence survives independent of any one person's inbox.

### Is there automatic email filing for Outlook?

Yes. Outlook's native rules can auto-move messages but are capped at 256 KB of rules per mailbox and depend on stable senders and subjects. Add-in tools built for project work go further: Mail Manager suggests destinations with machine learning, and Cogram files Outlook email and attachments to the correct project automatically.

### What is the best project email management software for architecture firms?

It depends on how much filing work your PMs will tolerate. Newforma bundles filing into a full PIM platform, Ideagen Mail Manager and TonicDM are focused filing-and-search tools, and Cogram automates the filing decision itself. Shortlist on per-message effort, shared searchability, and attachment handling, then pilot on one live project.

### Can we keep Outlook and still improve project email filing?

Yes. The options discussed here all assume it: the AEC filing tools are Outlook add-ins or connected services, so PMs keep reading and writing email in Outlook while the tool captures correspondence into a shared project record. Nothing about the mailbox or Microsoft 365 governance changes.

## Where to start

Pick one live project and run a four-week pilot of whichever approach fits your tolerance for per-message work. Measure the fraction of correspondence that reaches the shared record unprompted, then try to answer three historical questions from the record alone. If you want a second opinion on the pilot design, or a mapping of automatic filing against your current folder structure, we are happy to [walk through it](/get-demo).