Discussing Equipment Installation Before a Renovation Is Ready

A facilities manager calls to pin down an installation date before the renovation that will house the equipment is even close to finished. The room hasn't passed electrical inspection, the shutdown window hasn't been approved by anyone above the manager, and the IT review hasn't started. This conversation comes up on nearly every capital project, and how you handle it decides whether you end up coordinating a plan with the customer or defending a promise you never should have made.

Why this conversation goes wrong

Facilities managers are usually under pressure from their own leadership to lock in a shutdown window and show progress. An installation date feels like one more item they can check off early, so they push for it before the dependencies are actually resolved. You want to be responsive, so you give a date that sounds reasonable given the project timeline. The problem is that once you say a date out loud, it becomes the plan in the customer's mind, caveats or not. Renovations slip constantly, electrical inspections get rescheduled, and IT reviews take longer than anyone expects. When the date moves, you are the one who "missed it," even though the actual cause was a contractor delay or an inspection failure that had nothing to do with you.

The fix isn't to avoid the conversation. It's to have it in a way that gives the manager real information without putting a date on anything you don't control.

How to prepare before the call

Get the approved site requirements from the project manager or your own applications team before you talk to the facilities manager. You need to know what has to happen before installation can even be scheduled, not guessed at. That includes electrical inspection status, remaining construction milestones, access and security restrictions for the install crew, the network and IT review, and the shutdown window the facility is actually requesting.

For each of those items, identify the owner. Electrical inspection usually sits with the contractor or a city inspector, not the facilities manager. IT review sits with the hospital's IT department. Service scheduling sits with your own service team, not with sales. Walk into the call with a list of open questions and named owners, not a date. If someone tells you a task is "almost done," ask what specifically is left and who confirmed it. Vague status updates are how false dates get created.

What to say

Start by acknowledging the urgency, then separate the schedule mapping from the schedule commitment.

The facilities manager says, "We need to lock in installation during the shutdown window. Can you guarantee that date?"

You say, "I can map out the dates and dependencies with you right now, but I can't commit to an installation date until site readiness and scheduling are confirmed by the teams that own them. Has the electrical work passed final inspection yet, and who owns the IT and service reviews on your side? Once I have that, I'll bring those owners into a feasibility discussion and come back with a verified path instead of a guess."

The manager pushes back. "The shutdown window is already set. We can't move it, so we need the equipment in by then."

You say, "Understood, and that's exactly why we should get the real owners talking now instead of waiting. I'll set up a short feasibility review with your electrical contractor, your IT lead, and our service team this week. I'll come back to you with confirmed status on each dependency and the earliest date that actually works, not an estimate."

This keeps you useful without putting your name on a date that depends on three other departments finishing their work on time. It also puts the responsibility for the missing information where it actually belongs, on the people who own it, not on you.

Mistakes to avoid

The most common mistake is giving a specific date just to keep the conversation friendly. It feels helpful in the moment and creates a real problem two months later. A second mistake is assuming the facilities manager speaks for IT and the service team. They usually don't, and treating their word as confirmation on those items sets up a conflict later when the actual owners haven't agreed to anything. A third mistake is skipping a written readiness check and relying on a verbal "we're on track." Verbal status changes depending on who you ask and when. A fourth mistake is proposing a feasibility review and then letting it happen without the right people in the room. If the electrical contractor or IT lead doesn't actually show up, you've scheduled a meeting instead of solving the problem.

None of these mistakes come from bad intent. They come from wanting to sound confident and helpful on a call where the honest answer is "I don't know yet, and here's how we find out."

How to practice and score it

This conversation is hard to get right the first time because the pressure to commit is real and immediate. Run it as a practice scenario before you're on the call with an actual customer. A manager or the rep can score the exchange on a few concrete things, whether the rep avoided naming a specific installation date, whether the rep named the actual dependency owners instead of treating the facilities manager as the sole authority, whether the rep proposed a concrete next step like a feasibility review instead of a vague reassurance, and whether the rep's tone stayed collaborative instead of defensive when pushed on the shutdown window.

DealSpeak's Medical Devices practice conversations include this exact scenario along with related ones, so you can rehearse the pushback before it happens with a real customer. If you want to see how the same discipline applies when an executive asks for a performance guarantee instead of a date, read Answering an Executive Request for an Equipment Outcome Guarantee. And if procurement is the one applying pressure, this time on pricing instead of scheduling, Handling a Procurement Request for a Capital Pricing Deadline covers the same core skill, giving a straight answer without a commitment you can't back.

Practicing this exchange out loud, with someone pushing back the way a real facilities manager will, is what makes the difference between freezing up and giving a calm, specific answer. Once you can name the dependencies and owners without hesitating, the pressure to promise a date mostly goes away on its own.