The inbox is the jobsite’s second set of drawings

Every decision, change and approval lives in email long before it reaches a drawing set. Here’s how to treat correspondence like the record it actually is.

On every project, the official record is supposed to live in the drawing set and the contract documents. In practice, the decisions that shape those documents happen somewhere far messier first: in email.

That thread is doing the work of a record. The problem is that it doesn’t look like one — so nobody treats it like one until it matters.

The record hides in plain sight

Correspondence accumulates faster than any other artifact on a project. A mid-sized job can generate tens of thousands of emails across its lifecycle, and each one carries a little piece of context — who knew what, and when.

If you can’t answer “when did we agree to that?” in under a minute, your inbox isn’t a tool — it’s a liability.

The fix isn’t more folders or stricter naming conventions. The fix is to let the structure form automatically from the content that’s already there.

What “good” looks like

A correspondence record you can actually rely on has three properties:

• Mapped, not filed. Every message is associated with a project, a discipline, and the items it touches — without anyone dragging it into a folder.
• Queryable in plain language. “Show me everything about the curtain-wall embed plates” should return a thread, not a search-results graveyard.
• Correctable. When the automation gets something wrong, fixing it takes one click and the system learns from it.

Get those three right and the inbox stops being a place where information goes to get lost. It becomes the second set of drawings — the living one, where the project is actually negotiated day to day.

• Correspondence
• RFI
• Project Records
• AEC