Moving to New Outlook is the moment project email is most likely to scatter, with the cost landing later in disputes, audits or staff departures. The five risks to resolve first are dispute exposure, compliance failure, invisible knowledge loss, productivity degradation and an IT-driven rollout that ignores project context.
| Risk | Conseqeunce if unaddressed | How to close it |
| Dispute exposure | Contractual emails sit only in personal inboxes when a claim arrises | Automated filing to the project at point of send and receive |
| Compliance failure | A demonstratable ISO 19650 gap surfaces in audits | A consistent, auditable filing workflow that survives the swtich |
| Invisible knowledge loss | Project history leaves with the person who held it | File to the project, not the person |
| Productivity degradation | Teams rebuild decisions from manual inbox searches | Searchable project email, retrievable in seconds |
| IT rollout without project context | FIling breaks undiscovered until mid-project | Ask IT to test filing before go-live |
Switching email clients feels like an IT job. It is also a records job. Silent filing failure is when an email client migration stops project email being filed without anyone noticing, so correspondence quietly drifts into personal inboxes until a dispute or audit exposes the gap. The move to New Outlook is the most common trigger. Resolve these five risks before IT completes the rollout.
1. Dispute exposure
Construction disputes turn on documentary evidence. The Arcadis 2025 Global Construction Disputes Report puts the average North American dispute at $60.1 million and 12.5 months to resolve. If your team switches to New Outlook and filing quietly stops, months of contractual correspondence may exist only in personal inboxes, invisible to project managers, lawyers and adjudicators when it matters most.
2. Compliance failure
ISO 19650 requires organizations to manage project information systematically across its lifecycle. Email is information. A broken filing workflow creates a demonstrable gap between what the standard requires and what you can produce, and that gap surfaces during exactly the audit or client request you cannot afford to fail.
3. Invisible knowledge loss
Project managers change and teams move on. When correspondence is filed against projects rather than held in inboxes, continuity is preserved. When filing breaks, the institutional knowledge that makes handovers work disappears with the person who held it. File email to the project, not the person, and when someone leaves the knowledge stays.
4. Productivity degradation
Without a searchable record, teams fall back on manual inbox searches, chase messages and phone calls to reconstruct decisions. WSP found that project leads who once spent days locating information now retrieve it in seconds. That is time that belongs to projects, not to hunting through inboxes.
5. An IT rollout that ignores project context
IT teams rolling out New Outlook are focused on technical compatibility, not project information governance. Unless the business asks, they will not test whether email filing still works, which is how silent filing failure takes hold and leaves project teams to discover the gap mid-project. Ask IT directly: has email filing been tested in New Outlook, and does our filing backend still work?
How should AEC firms prepare for New Outlook?
New Outlook is coming whether you plan for it or not. The firms that come through it cleanly treat it as a governance review, not just a technical upgrade. Ideagen Mail Manager files email as you send and receive it, into your own infrastructure, and makes any email findable in seconds. It supports New Outlook now through the Mail Manager Desktop NOW Bridge, across SharePoint, file servers and ProjectWise.
Frequently asked questions
What is the biggest email risk when moving to New Outlook?
Silent filing failure, where filing stops during the switch without anyone noticing. Filing tools built for classic Outlook can stop working, and project correspondence scatters back into inboxes.
Does moving to New Outlook affect ISO 19650 compliance?
It can. ISO 19650 requires systematic information management, and email is information. If filing breaks during the switch, you create a demonstrable gap in your processes.
How does Mail Manager protect project email during a migration?
Ideagen Mail Manager suggests the right project location for each email and files it into your own infrastructure, across both Microsoft 365 and non-Microsoft 365 backends, so correspondence stays filed and searchable.
Should IT test email filing before the New Outlook rollout?
Yes. IT teams focus on technical compatibility, so ask explicitly for filing to be tested before the switch goes live, especially if you file to a file server or ProjectWise.