Tips For Written Communication In Construction

Written Communication in Construction: Seven Practices That Keep You Out of Trouble and In Flow

The legal counsel who came to do a training at Hensel Phelps made a joke that was not entirely a joke. If they could get rid of email entirely, they would because it gets companies in so much trouble. The examples they showed the room were not of fraud or malicious intent. They were superintendents writing things in an email that they never would have said the same way face to face. Frustrated tones. Dismissive phrasing. “Try again.” Words that looked fine in the heat of a difficult moment and looked catastrophic in a conference room or a courtroom.

That training delivered a principle that shapes everything about how written communication in construction should be approached: never write anything in an email or text that you would not feel comfortable saying in court. That single standard eliminates most of the written communication problems that construction teams create for themselves. It does not eliminate email. It changes what goes into it.

The Philosophy: Less Documentation, Done Better

There is a spectrum in how construction professionals approach documentation. At one end are the professional documenters everything goes in writing, every interaction becomes a record, every conversation spawns a follow-up email. At the other end are the teams that document almost nothing, relying on relationships and verbal communication to carry the project. Neither extreme serves the project or the people on it.

The right position is closer to the less documentation end but with a critical qualifier. Some things must be documented, and when they are, they must be done professionally, accurately, and completely. The documentation that exists on a well-run project is sharp. It is precise. It does exactly what it was designed to do and nothing else.

The principle for internal communication is direct: default to no email. Teams, WhatsApp, Asana, Monday, ClickUp, meetings, verbal, text whatever platform the team has standardized on for quick internal exchange. Fast, direct, low friction. If an email must be sent, it is external only. The belief that everything must be documented for legal protection is not entirely true and the defensive documentation spiral it produces often does more damage than it prevents.

What does deserve documentation? The trade partner preparation sequence: contract execution, pre-mobilization meetings, pre-construction meetings, follow-up inspections, final inspections, quality sign-offs. Anything that touches the contractual agreement, establishes expectations, or creates a record of shared understanding. These get documented well. Everything else gets communicated effectively.

Here is the diagnostic that reveals how a project is actually running: if the job is going well, there will be fewer RFIs, fewer reworked submittals, and less administrative overhead. The documentation that exists will be accurate and professional. A project drowning in defensive documentation has problems and the documentation is usually making those problems worse, not better.

Eight Practices for Written Communication That Actually Works

The first practice is knowing why something is going in writing before writing a word. Every written communication serves one of two purposes: to clearly communicate, or to clearly document from a risk standpoint. Both have legitimate value. Confusing them produces documents that do neither well communication written so defensively it fails to communicate, and documentation so casual it provides no protection. Know which one you are doing. Then do it cleanly.

The second practice is stating the purpose immediately. The first line of any written communication should tell the reader exactly what this document is and why it exists. “This email documents the installation requirements for the overhead MEP in zones three through six.” Or: “This email confirms the conditions needed for your crew to mobilize Monday morning.” The reader should know within five seconds what this is, why it was sent, and what they need to do with it. If they have to read three paragraphs to figure that out, the communication has already failed.

The third practice is maintaining tone discipline under all circumstances. Emotions do not belong in written construction communication. Not urgency, not frustration, not sarcasm none of it. AI tools are genuinely useful here. Draft the substance, use an AI assistant to check the tone, and send something that reads professionally regardless of how the situation feels. The test is not whether the email accurately reflects your frustration. The test is whether you would be comfortable reading it aloud in a formal setting.

The fourth practice is treating RFIs, submittals, and meeting minutes with the seriousness they carry. These documents have contractual weight. RFIs must be precise not vague requests that invite misinterpretation or that are actually doing design work that belongs elsewhere. Submittals must follow the proper process and must not become a vehicle for redesigning through the submittal cycle. Meeting minutes and daily reports must be accurate, complete, and written without language that would be damaging if read back to the people who were in the room.

These four practices address what to write and how to write it. The next four address the system around the writing.

The fifth practice is building communication around the goal of preventing claims, not winning arguments. The point is not to pin something on somebody. The point is to communicate so clearly and so early that there is nothing to pin. Ask of every written communication: is it effective? Is it visual? Is it clear? Is it accessible to the person who needs to act on it? Not: did I send it? Not: is it buried in one of thirty-five folders in the project management application? Is it working?

Here are the don’ts that consistently make written construction communication worse rather than better:

• Emotional tone in any form it converts professional documentation into evidence of a broken culture
• Vague language “can you put that wall up Tuesday?” communicates nothing, creates confusion, and generates the RFIs you were trying to avoid
• Missing context assuming the recipient knows what you are referring to without establishing the reference produces misunderstandings that cost more time and money to unwind than the original communication would have taken to write clearly

The sixth practice which is closely related is understanding that the communication system on a construction project is its nervous system. Text, radio, meetings, field coordination, office alignment: when these channels are functioning, information reaches the right people at the right time in the right form. When they break down through adversarial documentation, siloed platforms, or teams that have stopped trusting each other enough to communicate directly the project loses the coordination it needs to flow.

A military principle applies directly: the first objective in defeating an enemy is to shut down their communications. Construction teams should not do this to themselves by turning their internal communication into a legal exercise. Embrace the communication system. Protect it. Make it strong enough that no disconnect is possible between the field and the office.

The seventh practice is establishing standard work for written communication. Set up templates for RFIs, meeting minutes, pre-mobilization documentation, and the other recurring written communication forms. Set those standards not just for yourself but for every person on the team. When the whole team writes from the same standards and the same habits, the quality of the documentation rises and the individual burden of producing it well falls.

Here are the signals that written communication is supporting the project rather than complicating it:

• Every external email states its purpose in the first sentence
• Internal communication flows through fast, direct tools rather than email chains
• RFIs are clear, specific, and traceable back to a genuine information need
• Meeting minutes and daily reports are accurate and professionally written
• The team can locate every relevant document without hunting through multiple systems

Connecting to the Mission

The connection between written communication and production flow is direct and underappreciated. A project that generates fewer RFIs is a project where the design was coordinated, the trades were prepared, and the pre-construction process was done well. A project with professional, accurate meeting minutes is a project where decisions are made clearly and commitments are tracked honestly. Written communication is not a separate administrative function it is the information layer that either supports or undermines the production system running in the field.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Take thirty minutes this week and audit one category of written communication on your project RFIs, meeting minutes, or your internal email volume. Ask honestly: is this communication serving the project, or is it protecting individual positions? If it is the latter, the production system has a problem the documentation is hiding rather than solving. Find it. Fix the system. Reduce the paper.

Jason Schroeder said, “The goal is not to be excellent at documenting problems. The goal is to build systems good enough that the problems don’t happen.”

On we go.

Frequently Asked Questions

Why is the internal default for communication “no email” on a well-run project?

Because email is slow, creates adversarial documentation culture, and generates communication overhead that fast, direct tools eliminate. Internal communication needs to be immediate and frictionless. Email is for external communication and for formal documentation that needs to exist as a retrievable professional record.

What categories of communication always deserve formal documentation?

The trade partner preparation sequence: contracts, pre-mobilization meetings, pre-construction meetings, follow-up inspections, final inspections, and quality sign-offs. Anything that establishes contractual expectations or creates a record of shared understanding deserves to be documented professionally.

Why do projects with more documentation often have more problems?

A well-run project generates less documentation because the conditions that produce RFIs, change orders, and claims are being managed proactively through strong planning and clear communication.

What is the most damaging type of written communication error in construction?

Emotional tone. It converts professional documentation into evidence of a problematic culture, creates legal exposure, and damages the relationships that collaborative production depends on. Once it is in writing, it exists permanently, discoverably, and exactly as damaging in a conference room as it was intended in a frustrated moment.

How does standard work apply to written communication?

By establishing templates and consistent practices for recurring document types RFIs, meeting minutes, pre-mobilization checklists, daily reports so that every person on the team produces documents to the same quality standard.