A construction candidate withdrawal in week seven was usually decided around week three and announced when it could no longer be put off. Employers control most of the causes: silence between rounds, a brief that moved, a range revealed late, a spouse never consulted, a slipped start. Ask one direct question at every stage and you see it coming.

The call starts with “I have been thinking.” You know the rest before it arrives. The finalist is grateful, the opportunity is a good one, the timing is simply not right, and they hope you will stay in touch. A candidate withdrawal always sounds like a decision made last night. It almost never was.

Ask them a month later, when nothing rides on the answer, and you hear a different date. Somewhere in the third week the interest cooled, and they kept taking your calls because nobody enjoys closing a door.

When does a candidate withdrawal actually happen?

Weeks before you hear about it. The decision forms in a quiet stretch of the process, usually after a good first round, when the candidate goes back to a live job and your firm goes silent. The phone call in week seven is the paperwork.

Nothing dramatic causes it. A senior project manager leaves your office on a Tuesday feeling better about the conversation than they expected to. They tell their spouse. Then nine days pass. Their own job has an owner meeting, a pour and a pay application in those nine days, and your firm has become a pleasant memory with no next step attached.

Each day of that silence costs you a little, and no single day costs enough to notice. The candidate does not decide against you. They stop deciding for you, and the difference only shows at the end, when you ask for a commitment and discover there is not enough left to make one.

Employers read the late withdrawal as bad luck or a counteroffer. Occasionally it is. More often the search was already failing in a way nobody was measuring, which is the pattern behind most of why searches fail. The same holds one step later, when a declined offer turns out to have been lost in week two.

Which causes of candidate withdrawal does the employer control?

Five of them, and all five are quiet. None involves an argument or a visible mistake. Each one leaves the candidate to draw a conclusion alone, and a person running a live project draws conclusions quickly.

  • Silence between rounds. No feedback and no date reads as no interest. The candidate will not chase you to find out.
  • A brief that moved. The seat described in round one reported to the president. By round three it reports to a vice president who was not in the room.
  • A range revealed late. The Bureau of Labor Statistics publishes wage data by state, Texas included, and candidates read it. Holding your number until the offer does not protect it.
  • A spouse never consulted. Asking a project executive in Atlanta to move to Austin is a decision for two people, and one of them has never heard your name.
  • A project start that slipped. The job they were hired to run moved from spring to “later this year,” and nobody called to say what they would do in the meantime.

The fix for each is a conversation that takes ten minutes and feels slightly awkward. That awkwardness is why it gets skipped. A slow internal process compounds every item on the list, and fixing a slow search is where most firms should start.

Which causes are outside your control?

Two, mainly: a counteroffer from the current employer, and a project the candidate will not walk away from. You cannot prevent either. You can learn about both early enough to plan around them, if you ask before the offer.

The counteroffer is the one employers fear and the one they prepare for least. In construction it works because of the job more than the money: the candidate is leaving a schedule, a team and an owner mid-flight, and the counteroffer trap closes in the weeks after acceptance. The Bureau of Labor Statistics reports construction quits each month in its JOLTS release, and each quit in that count is a resignation somebody had the chance to argue with.

The project is harder, because it is honorable. A superintendent or project manager who will not leave before topping out is showing you the trait you are hiring for. The answer is to ask in the first conversation which milestone they would need to reach, and to decide then whether your start date can wait for it. Bonus dates and bid seasons hold a candidate the same way, and our note on search timing maps that calendar.

What should you ask at each stage?

One direct question per stage, asked out loud, with the answer written down. The purpose is to turn a private doubt into a stated one while there is still time to answer it. A candidate who is asked will usually say.

StageWarning signWhat to do
First conversationVague about why they would leaveAsk what would have to be true for them to stay
After round oneSlow replies, no questions of their ownGive feedback and the next date within two days
Before round two”I need to check a few things at home”Offer to speak with the spouse, or host a visit
Before the offerHas not asked about pay or start dateState the range and ask about their project milestones
After acceptanceResignation date keeps movingAgree a date to resign and call the day after

The table is not a script. Its use is that it forces a named person at your firm to own each row, because the usual answer to “who called the candidate after round one?” is a look around the table.

A slow process against a tight one

Put two processes side by side as a worked example, with numbers chosen for illustration. In the slow one, feedback after the first interview takes 9 days, the second round follows 14 days later, and the offer comes 12 days after that. In the tight one the same three gaps are 2, 5 and 3 days.

Calendar days between steps, slow against tight Bar chart, Calendar days between steps, slow against tight: Slow: to feedback 9 days, Slow: to round two 14 days, Slow: to offer 12 days, Tight: to feedback 2 days, Tight: to round two 5 days, Tight: to offer 3 days. Calendar days between steps, slow against tight The slow process gives a candidate 35 quiet days to reconsider. The tight one gives 10. 0 days 5 days 10 days 15 days 20 days Slow: to feedback 9 days Slow: to round two 14 days Slow: to offer 12 days Tight: to feedback 2 days Tight: to round two 5 days Tight: to offer 3 days Source: Worked example in this section
The slow process gives a candidate 35 quiet days to reconsider. The tight one gives 10.

The slow process leaves 35 days of quiet. The tight one leaves 10. Neither firm interviewed any harder than the other, and the interviews themselves were identical. One of them simply gave a busy person five weeks to talk themselves out of a move.

The market does not reward patience here. AGC’s hiring outlook for 2025 reports on contractors across the United States and their plans to add staff in a tight labor market. Assume your finalist has other conversations running, each at its own speed.

Is the seat one you cannot advertise, so that a late withdrawal cannot be repaired by posting the job again? Selah Talent Partners runs confidential executive search for mandates that cannot be publicly posted, and employers can see how each stage above is handled.

Think of the last finalist who withdrew on you. Which week did they decide, and who at your firm would have been in a position to know?

Sources and further reading

  • BLS wage data, Texas occupational employment and wage estimates
  • BLS JOLTS, job openings and labor turnover release
  • AGC outlook, 2025 construction hiring and business outlook