Email is Not a Contract

“Per my last email…” — famous last words.  Brian and Alex break down how projects go sideways when emails replace actual documentation. From silent approvals and missing threads to field decisions made over text, this episode dives into why inboxes are not contracts, and how those messages can still come back to bite you. Leave feedback for Brian and Alex ⁠⁠⁠⁠⁠[email protected]⁠⁠⁠⁠⁠ LINKS: Website: ⁠⁠⁠⁠⁠https://buildableish.com/⁠⁠⁠⁠⁠Instagram: ⁠⁠⁠⁠⁠https://www.instagram.com/buildableish⁠⁠⁠⁠⁠X: ⁠⁠⁠⁠⁠https://x.com/Buildableish⁠⁠⁠⁠⁠LinkedIn: ⁠⁠⁠⁠⁠https://www.linkedin.com/company/buildable-ish/⁠Show Notes Chapter 1 – When Email Becomes Design Design decisions made without drawings or documentation. Missing stakeholders and uncoordinated changes. Decisions made via email instead of formal RFIs or meetings.  Chapter 2 – Procurement by Inbox Misinterpreting “go ahead” vs actual authorization to proceed. Unclear vendor scope and inconsistent pricing assumptions. Risks of proceeding without contracts or purchase orders.  Chapter 3 – Field Direction vs Reality Crews working from emails, texts, and verbal approvals. Conflicts between drawings and unofficial field direction. Need for clear yes/no responses and formal documentation.  Chapter 4 – Closeout and the Email Black Hole Lost warranty info and O&M manuals buried in inboxes. Confusion over final versions and responsibility at turnover. Payment delays tied to missing or undocumented approvals.  Key Takeaways Emails are not contracts. Formal documentation (RFIs, drawings, contracts) is required for decisions. Lack of clarity leads to rework and risk. Assume every email could be read in court. Link to Brian’s article for Steel Erector’s Association of America https://issuu.com/seaa_admin/docs/connector-2010-edition  on pg 58-59