Featured on this episode:

• Join The Designers Edge here
• Grab Your Free Script Guide here
• Access the full video interview with Elana Steele of Steele Appliance here

What you will learn from this episode:

• The four real reasons contractors go quiet
• Why your usual go-to responses (the soft ask, the follow-up chain, waiting it out) are making it worse
• Exactly what to say when you have the conversation

---

Let me start with a scenario.

Things started well. The contractor was responsive, the rhythm was good, and it felt like you were actually working as a team. And then somewhere around week four or five, something shifted. The communication slowed down. Not stopped — just slower. A text takes two or three days to get a response. You ask for an update and get two words back. You show up for a site visit and no one told you the schedule had changed.

And you start doing what most of us do. You fill in the silence with stories. He’s probably just busy. Maybe I’m being too demanding. Maybe I should wait a few more days before following up again.

Here’s what I want to say right up front: silence is not neutral. It’s telling you something. And the longer you manage around it instead of addressing it directly, the more it costs you — in time, in money, in your relationship with your client, and in the authority you’ve worked hard to build.

So let’s talk about what’s actually happening, why it happens, and what to do about it.

Why Contractors Go Quiet

Before we talk about what to do, it’s worth understanding why this happens. Because when you understand the reason, you stop taking it personally and start responding strategically. That shift alone changes the outcome of the conversation.

The first reason is overwhelm.

Contractors are almost always running multiple projects at once. When something goes sideways on another job, an inspection that doesn’t pass, a subcontractor who falls through, or materials that arrive damaged, your project can temporarily fall to the bottom of the priority list. Nothing personal. Nothing intentional. Just triage.

The second reason is avoidance.

Sometimes a contractor goes quiet because there’s a problem he doesn’t want to tell you about yet. He’s still trying to figure it out himself. Maybe something’s behind schedule. Maybe there was an error on site. Maybe a sub he was counting on became unavailable, and he’s scrambling to find a fix. Instead of coming to you with bad news, he goes quiet, hoping to resolve it before he has to say anything.

Honestly, I’ve done a version of this myself — I don’t like bringing a client a problem unless I have at least a couple of solutions ready. But the tell-tale sign with a contractor is that when you do finally get him on the phone, something comes out within the first thirty seconds that he clearly needed to share. The avoidance was temporary. The problem was real.

The third reason is a shift in the dynamic.

This one requires the most honest self-reflection. If a contractor has decided, whether consciously or not, that you’re not an equal, that you’re not someone he has to answer to or keep in the loop, the communication starts to reflect it.

The fourth reason is that you may have accidentally trained him to go quiet.

If you’ve consistently accepted late responses, worked around his silence, or made decisions without the information you actually needed from him, you’ve inadvertently shown him that you’ll manage your work around his availability. And so he keeps operating that way, because you’ve allowed it to work.

None of those reasons are your fault. But all of them are your problem to solve.

What This Is Actually Costing You

I think we sometimes minimize how much a communication breakdown actually costs. When a contractor isn’t communicating, you’re spending hours filling that gap, chasing, following up, restructuring timelines, driving to site visits just to gather information that should have been in your inbox on Monday. Those are hours you didn’t account for when you built your fee. You have buffer built in, yes. But you may be burning through it, absorbing a problem that should have been addressed weeks ago.

And then there’s the client. The client hired you because they didn’t want to deal with this chaos themselves. When communication breaks down between you and the contractor, you become the person absorbing that confusion and holding the illusion of control together. At some point, you either have to tell your client something’s wrong, or you take on the stress of keeping it from them. Neither is a good place to be.

I remember being on a project where I was covering for a contractor’s communication failures for about three weeks. My client finally looked at me during a site visit and said, I feel like I don’t know what’s happening on my own house. Nothing had gone terribly wrong yet. But I had let it get to a point where my client felt that way. That was the moment I decided I would never again manage around a contractor’s silence. I would address it directly.

The Responses That Don’t Work

Before we get to what does work, let’s name the patterns most of us default to, because I’ve been in all of them.

The follow-up chain. You text, then email, then call. You’re not being unreasonable; there is urgency. But what you’re communicating is urgency without expectation. And urgency without expectation just trains people to respond when they feel like it.

The soft ask. Instead of saying I need an update by Thursday end of day, you say Hey, when you get a chance, could you let me know where we are? That phrasing is a gift to someone who’s avoiding you. You’ve just given them an indefinite timeline and zero accountability. I know this because it was my go-to for years. I wanted to be accommodating. I didn’t want to come across as demanding. But what I was actually doing was making it easy for the silence to continue.

Looping in the client. There are times when the client absolutely needs to know what’s happening. But if you go to the client before you’ve addressed the contractor directly, you’ve created a triangle. And you’ve told the contractor that you’ll go around him when you’re frustrated, which does not build the dynamic you want going forward.

Waiting and hoping. The silence will sort itself out. He’s just having a bad week. It won’t. Every week you wait, the pattern gets more entrenched and harder to reverse.

How to Actually Address It

This isn’t just a script, it’s a process. The words matter, but only inside the right approach.

Step one: Decide to address it.

This sounds obvious, but a lot of designers skip it. They tell themselves it’s not worth the conflict, or that the contractor will come around, or that they don’t want to damage the relationship. I understand all of that. But not addressing it is what damages the relationship. Silence rewards silence. Naming what isn’t working is what resets the standard.

Step two: Choose the right medium.

That means a phone call or a face-to-face conversation on site. Not a text. Not an email. Texts are easy to ignore, and both are easy to misread, and they create a written record of a dynamic you don’t need documented. A real conversation gives you tone, gives you real-time feedback, and gives you a chance to actually hear what’s going on.

Step three: Lead with what you’re observing, not what you’re feeling.

This is where most designers go wrong. When frustration leads, the contractor gets defensive, and nothing changes.

Instead of: I feel like you’ve been ignoring me.

Try: Hey, I’ve noticed our communication has slowed down over the last couple of weeks. I’m not getting the updates I need, and it’s making it hard for me to stay ahead of things on my end. I want to make sure we’re back on the same page.

That’s an observation, not an accusation. It opens a door instead of starting a fight.

Step four: Ask a direct question.

Is there something going on with the project I should know about? Is there something you need from me?

That one question gives the contractor an opening to tell you what’s actually happening. More often than you’d expect, that’s exactly what comes out. You find out about a problem that’s been sitting there unspoken, and suddenly you can solve something together instead of just chasing updates.

Step five: Re-establish the expectation clearly.

Not harshly, but specifically. Something like: Going forward, I need a project update every Friday — even just two lines. Where did we land this week, and what’s happening next week? That’s what I need to do my job and keep supporting you, the client, the budget, and the timeline.

That’s not asking for more than any reasonable project partner should provide. You’re just making it explicit so there’s no ambiguity.

Step six: Document it.

After the call or the on-site conversation, send a brief follow-up email. Nothing formal. Just: Thanks for the conversation, wanted to confirm we’re going to [restate what you agreed to]. Looking forward to getting back on track.

That creates shared accountability. When an expectation is in writing, it’s much harder to unhear.

What Happens Next

Sometimes you have that conversation, reset the expectation, and the contractor responds well. Things improve. That’s worth celebrating, and it happens more often than you’d expect. A lot of contractors aren’t deliberately blowing you off. They just haven’t been held to a clear standard. Once they know what you need, they typically rise to it. I have seen relationships completely turn around after one direct conversation. It can feel almost startling how simple it is once you’ve done it a few times.

But sometimes you have the conversation and nothing changes. The next week looks exactly the same. At that point, you have a decision to make.

If you’ve addressed it clearly and directly, and this contractor still cannot meet basic communication expectations, you now have a management problem, and it’s not going to resolve itself. That’s when you involve your client. Not to vent, not to blow things up, but because your client is a party to this project. They have a right to know there’s an issue. You also need to think honestly about whether this is someone you’ll work with again. Your reputation is attached to every person you recommend. If the dynamic has fundamentally shifted, you need to take stock of that.

And depending on what your contract allows, you may need to look at your options. The direct conversation is usually all it takes. But if it isn’t, you need to know what tools you have, and using them isn’t overreacting. It’s doing your job.

The Bigger Picture

You are not a visitor on that job site. You are not there to manage around the contractor, soften your needs so nobody gets uncomfortable, or absorb the cost of someone else’s disorganization. You are there as an equal team member and a project leader. Part of what that looks like is holding your team — including the contractor — to the standard the project requires.

It doesn’t mean being difficult. It means being clear, consistent, and willing to name what isn’t working in the moment.

Most designers who struggle with contractor communication aren’t struggling because they don’t know what they need. They’re struggling because somewhere along the way, they decided that asking for it clearly would make them seem too demanding, or damage the relationship, or start a conflict they didn’t want.

Consider the opposite. Clarity is what builds respect. Naming the problem early is what saves the relationship. The contractor who actually respects you is the one who knows exactly what to expect from you.

That’s the project dynamic you deserve to have. And it almost always starts with one direct conversation.

Like This Episode?

Be sure to check out Episode #215: Why Designers Struggle with Trades—and How to Fix It

Be sure to check out Episode #252: What Contractors Know That Designers Don’t

Be sure to check out Episode #266: The 5 Construction Conversations That Prevent Chaos on Projects