Field Notes: Bad News Doesn’t Age Well

Written by Juan Garza, Superintendent at RO

There are very few problems in construction that improve when nobody talks about them.

A missed delivery does not fix itself. A coordination issue does not disappear above the ceiling. A trade partner struggling with manpower does not suddenly catch up because the schedule still shows them finishing on Friday.

Bad news does not age well.

The longer an issue sits, the fewer options we have, the more expensive the solution becomes, and the harder it is to maintain trust. What may have started as a manageable problem on Monday can become a full project crisis by Friday. As the general contractor, I believe one of our most important responsibilities is creating an environment where problems are communicated early, honestly, and to the people who need to know.

Have the Tough Conversation Early

No superintendent or project manager enjoys calling an owner or owner’s representative with bad news. Maybe the schedule is slipping. Maybe unexpected conditions were uncovered. Maybe a long-lead item is arriving later than promised. Those conversations are uncomfortable.

Avoiding problems does not protect the relationship, it damages it.

When I need to deliver bad news, I try to come prepared with a plan based on these questions.

• What happened?
• Why did it happen?
• What is the actual impact?
• What are we doing about it?
• What decisions are needed, and when do we need them?

Sometimes the full solution is not available yet, and that’s okay. The owner still deserves to know that an issue exists, that we are actively working through it, and when they can expect the next update.

There is a big difference between saying, “We have a problem and do not know what to do.” And saying, “We identified an issue, here is what we know, here are the options we are evaluating, and here is our immediate plan.”

Honesty paired with accountability builds credibility.

After the conversation, document it. Send a follow-up email, record any decisions, include the responsible parties, and the next steps. Documentation doesn’t need to be seen as a weapon, it should provide clarity and keep everyone aligned.

Owners can handle bad news. What they struggle to accept are surprises. Especially when they find out the project team knew about the issue days or weeks earlier. Even when the news is difficult, people remember who told them the truth and who gave them enough time to make an informed decision.

Make It Safe for Trade Partners to Speak Up

Trade partners are an extension of the project team, and are often the first ones to recognize that something is wrong. That makes their willingness to speak up critical.

A trade partner may realize they cannot meet a scheduled activity. They may discover a conflict in the drawings, or made a mistake in the field or dealing with procurement issues. I need them to tell me immediately.

But I also have to recognize that my response determines whether they will bring me bad news the next time.

If my first reaction is yelling, embarrassment, or blame…the message is clear: “Keep quiet until you have no other choice.” That does not help the project. Anger is not a recovery plan.

A strong GC creates an environment where trade partners know they will be treated fairly, expected to perform, and supported in working through legitimate problems. When that trust exists, information moves faster. When information moves faster, the team has more options.

Build a Team Where Surprises Are Rare

A healthy project team should communicate often enough that very few things come as a complete surprise. The field team should understand what the office is tracking. The office should know what is happening in the field. The Superintendent, Project Manager, Assistant Project Manager, Project Engineer, and trade partners should not be operating from separate versions of reality.

That requires honest conversations during meetings; communication that reflects what is actually happening. Even with strong communication, mistakes will happen.

Construction involves thousands of decisions, hundreds of people, changing conditions, incomplete information, and constant pressure. Expecting perfection is unrealistic. What matters is how the team responds.

When someone makes a mistake, I want the conversation to focus on a few things:

• What do we need to do right now?
• Who needs to be informed?
• How do we limit the impact?
• What can we learn from this?
• How do we keep it from happening again?

The team is watching how leadership behaves under pressure and I want the lesson learned to be bigger than the technical mistake.

If every problem creates panic, blame, and overreaction, people will spend their energy protecting themselves. They will hesitate to make decisions, raise concerns, or admit when something has gone wrong. If leadership stays calm, gathers the facts, and moves the team toward a solution, that behavior becomes part of the project culture.

Bad News Is Part of the Job

Every project will have problems; materials will arrive late, drawings will conflict or work will be installed incorrectly. People will make mistakes.

The goal is not to create a project where nothing ever goes wrong. The goal is to create a team that identifies problems early and handles them well. That requires trust, accountability, and direct communication at every level.

Tell the owner what they need to know before they hear it from someone else. Make it safe for trade partners to raise their hands before an issue becomes a crisis. Teach the internal team to respond with facts, urgency, and a plan instead of panic and blame.

Bad news may be uncomfortable when it is delivered early, but it becomes far more painful after it has been sitting unnoticed, unspoken, or intentionally hidden. Speak up early. Own the issue. Bring a plan. Protect the project.

Because, bad news does not age well.