A structural engineer's guide to never losing a project email

Why does email risk hit structural engineers differently?

Structural engineering carries a specific kind of exposure: defects claims that surface years after a building is handed over, long after the calculations were signed off and the site team has moved on. When a crack appears, a load behaves unexpectedly, or a client questions a design choice, the question that follows is almost always the same - what was specified, what was approved, and on what basis.

That question gets answered by correspondence, not just by drawings and calculation packs. The email where a load assumption was confirmed, where a client accepted a design risk, or where a site query was answered is often the only record of reasoning that the formal documents don't capture.

What does a senior engineer's inbox actually contain?

Brian Falconer at Severud Associates - the New York structural engineering firm behind Moynihan Station and the WTC Path Station - described what email management looked like before a proper system was in place: "Just archiving and managing my emails was taking me over an hour a day."

An hour a day spent managing correspondence is an hour not spent on engineering work. But the bigger risk isn't the time lost - it's what happens to that correspondence once it's buried in a personal inbox rather than filed against the project it relates to. A senior engineer's inbox typically holds exactly the kind of detail a defects claim would need: design rationale, client sign-offs, site clarifications, and the reasoning behind decisions that aren't fully captured anywhere else.

Calculation packs and drawings alone don't answer "why"

A calculation pack shows the final answer. It rarely shows the conversation that led to a particular assumption, or the client instruction that changed a specification midway through a project. When a dispute or defects claim asks "why was it designed this way," the formal documents often can't answer that question on their own. The email thread usually can.

This is exactly why professional indemnity exposure in structural engineering tends to outlast the project team. The person who made the original judgement call may have moved firms by the time a claim surfaces, and if the correspondence explaining that judgement was never filed anywhere beyond their personal inbox, the explanation leaves with them.

What should structural engineers do differently with project email?

The fix isn't asking engineers to spend more time managing email - that approach already failed, which is exactly what cost Brian Falconer over an hour a day. The fix is removing the manual effort entirely. Ideagen Mail Manager files project emails from Outlook to the correct project folder automatically, with a single click, so the design rationale and client correspondence that explain an engineer's decisions are preserved against the project rather than trapped in a personal inbox.

For a structural engineer, that means the one email that would settle a defects claim years from now is already exactly where it needs to be, rather than depending on memory or a departed colleague's goodwill.

Ideagen Mail Manager supports over 50,000 users across 2,500+ firms worldwide.

Frequently asked questions

Why is email retention particularly important for structural engineers?

Structural defects claims can surface years after handover, often long after the people involved have moved on. The email correspondence explaining a design decision is frequently the only record of the reasoning behind it, since calculation packs and drawings show the outcome but not the discussion that led to it.

What kind of correspondence matters most for a structural engineer to keep?

Anything that explains design rationale, client sign-offs on risk or scope, and site clarifications - the detail that a calculation pack or drawing set doesn't capture on its own.

Why do engineers struggle to manage this correspondence manually?

Manually archiving and filing email takes significant time away from engineering work. One senior engineer at Severud Associates described losing over an hour a day to email management before switching to one-click filing with machine learning suggestions.

What happens if the original engineer has left the firm when a claim arises?

If their correspondence was never filed against the project, the reasoning behind their decisions effectively leaves with them, making it far harder to defend a claim years later.

How does one-click filing change this risk?

It removes the dependency on an individual engineer's memory or ongoing availability by filing every project email to the correct folder at the point it's sent or received, so the record exists independently of who wrote it.