Blog / Information Management
Email remains one of the most important systems in any architecture, engineering, and construction project. It holds design discussions, client direction, consultant coordination, approvals, risks, and the small decisions that shape the outcome.
For many firms, the first step toward better project information management is email capture. It is a worthwhile step. Filing project emails consistently improves visibility, helps preserve the record, and reduces the risk of critical communication disappearing into personal inboxes.
But email alone does not tell the full story.
AEC teams do not deliver projects through email. They deliver them through a continuous chain of conversations, assignments, documents, drawings, models, approvals, and formal workflows. A project decision often starts in an instant message, gains detail in an email, refers to a drawing or model element, becomes an RFI response, and ultimately affects a submittal, change request, schedule, or budget.
When those elements sit apart, teams still spend time reconstructing the story. The emails are there. The context is not.
An email management solution creates a better record of correspondence. It organizes messages by project, folder, sender, or subject. It helps teams find what was said.
Yet project teams often need to answer a more demanding question: why was a decision made, who approved it, what information informed it, and what happened next?
Consider a common project scenario. A contractor identifies a conflict in the field. The issue is discussed in a Teams conversation. A project architect sends a follow-up email with an initial recommendation. The team reviews revised drawings and a model view. A formal RFI records the question and response. A submittal later reflects the approved approach. A change document captures the commercial effect.
Each item matters. None tells the whole story alone. 
A future project manager, owner, or legal reviewer should not need to search five systems, read dozens of messages, and ask former team members to piece together
the sequence. They need a connected view of the project record, where the related correspondence, files, decisions, and workflow documents are easy to see together.
That is the difference between information storage and project understanding.
Most AEC firms already have document repositories. They store files, drawings, specifications, meeting minutes, reports, photos, and contracts. The issue is rarely a lack of files.
The issue is knowing which files matter to a specific question.
A document repository might show every version of a drawing. A project team still needs to identify the version reviewed during a decision, the emails discussing it, the model issue behind it, and the resulting RFI or submittal action. 
This is especially important when teams revisit decisions months or years later. People move roles. Consultants change. Project memories fade with impressive speed. The person who “knows the history” becomes unavailable, and the organization is left with disconnected artifacts.
Connected information preserves institutional knowledge. It helps the firm retain the reasoning behind a project decision, not only the final document.
RFIs, submittals, and change management documents provide essential structure. They create accountability, establish dates, record responsibilities, and support auditable project workflows.
But formal workflows do not exist in isolation.
An RFI response often relies on prior correspondence, reference documents, design discussions, photos, and related model issues. A submittal review might depend on specifications, product data, revised drawings, and earlier clarification. A change document might trace back to a field condition, an owner decision, and several coordination exchanges.
When workflow documents are separated from the supporting information, teams see the outcome without the full reasoning behind it. That creates delays, weakens accountability, and makes disputes harder to resolve.
The best project record connects formal workflow documents to the real-world context surrounding them. It gives teams one place to understand the decision, the evidence, the people involved, and the downstream impact.
A connected project record improves more than search. It strengthens how teams work.
Project teams respond faster because they spend less time hunting for the right information. New team members ramp up faster because the history is visible. Leaders gain greater confidence in project status and accountability. Firms reduce dependence on individual memory.
Most importantly, teams are better prepared when questions arise.
A client asks why a design decision changed. A contractor challenges an interpretation. An owner requests support for a change. A dispute emerges years after project completion. In each case, a folder of emails is helpful. A connected record of communications, documents, plans, models, workflow actions, and decisions is far more valuable.
Email management should therefore be treated as a foundation, not the finish line.
AEC firms need technology built around the reality of project delivery. Email matters. So do instant messages, documents, files, plans, models, assignments, RFIs, submittals, and change management records. Their value grows when they are connected in context.
Newforma helps firms move beyond email management toward a complete, searchable, and defensible view of project information. It brings the communications and content teams already use into closer connection with the workflows and decisions that drive project delivery.
Because a better project record is not simply a cleaner inbox. It is the ability to understand the full story when it matters most.
