A construction counteroffer usually succeeds in the gap between verbal acceptance and the first day. It works because the pull is operational rather than financial: a project manager mid-job is leaving a live schedule, a sub base, and a team. Money is the excuse the conversation uses, not the reason it works.

The offer was accepted on a Tuesday. By Friday the candidate had “decided to stay and see the project through,” and you were three months into a search that is now starting again.

Most hiring managers file this under bad luck or a candidate who was never serious. It is neither. It is a process failure with a predictable location, and it happens in the same place almost every time.

Why do counteroffers work so well in construction?

Because the ties are operational, not financial. A project manager mid-job has subcontractor relationships they built, a schedule they own, and a superintendent who depends on them. Leaving reads as abandoning a job rather than changing employer, and that pull is stronger than a raise.

Consider what the current employer can actually say in that conversation, because it is more persuasive than a number:

  • “Finish this job and then we will talk about the promotion.” A deadline the candidate already feels responsible for.
  • “Who is going to run the buyout on the medical center?” Naming the specific people affected.
  • “We were already planning to move you up after this cycle.” Unfalsifiable, and it costs the employer nothing to say.
  • “You are going to a firm you do not know, mid-project, and you will be the new person.” A real risk, honestly stated.

Only the last of those is about the new job at all. This is the part that makes construction different from most white-collar hiring: the industry runs on projects with visible completion dates, and there is always a reason to stay until the current one is done. There is always another one after it.

Workforce conditions make the employer’s incentive to counter stronger still. In a tight regional market, whether that is Dallas, Austin or Atlanta, a firm losing a project manager knows the replacement pool by name. The AGC has reported for years that United States contractors struggle to fill salaried positions, and the BLS job openings and turnover series tracks the same pressure across the sector. A firm losing an experienced project manager knows exactly how long and how expensive the replacement will be. Countering is rational for them.

When is a construction counteroffer most likely to land?

At resignation, in the gap between verbal acceptance and the start date. That is the only window where the current employer gets to respond, and it is where a candidate who has not thought past “I accept” is most persuadable.

Map the sequence and the vulnerable point is obvious:

StageCandidate stateCounteroffer risk
InterviewingExploring, low commitmentLow, employer does not know
Verbal acceptanceCommitted in principleLow, still private
Resignation conversationPublicly leaving, under pressureHighest
Notice periodBeing worked on dailyHigh
First dayCommitted in practiceLow

The risk is not spread across the process. It concentrates in two stages, and both of them happen after you think you have hired someone. Everything you do before those stages either prepares the candidate for that conversation or leaves them to improvise in it.

Most hiring processes leave them to improvise.

What stops a construction counteroffer working?

Surfacing the real reason for leaving before offer stage, and testing whether money could fix it. If the answer is yes, the candidate is not moving, and you would rather discover that in week two than after you have made an offer.

Five steps, in order:

  • Ask what would have to change for them to stay. Early, directly. If the honest answer is a raise and a title, their current employer can supply both, and this search is a negotiation lever rather than a hire.
  • Separate the push from the pull. A candidate leaving because of one specific person or one specific project is solving a temporary problem. A candidate leaving because the firm has no path to project executive is solving a structural one. Structural reasons survive a counteroffer.
  • Name the counteroffer before it happens. Tell the candidate their employer will very likely counter, and what it will sound like. A predicted move loses most of its force.
  • Rehearse the resignation. What they will say, to whom, and what they will do when the response is “finish the job first.” This sounds excessive until you have lost a placement at exactly that sentence.
  • Compress the gap. Every additional week between acceptance and start is a week of daily persuasion. Fast paperwork is not administrative tidiness. It is risk management.

None of that is about paying more. A candidate who takes the counteroffer for money was usually going to, and the standard industry observation is that most people who accept a counteroffer are gone within a year anyway. We cannot source that number to a primary body, so treat it as the widely held view among people who hire rather than as a measured fact, and note that it does not help you either way: whether they leave in ten months or stay, you still do not have a project manager. Restrictive covenants complicate the same conversation, which is why we treat non-compete terms as a screening question rather than a closing one.

When to surface the real reason for leaving Statistic, When to surface the real reason for leaving: 2 weeks in: test whether money fixes it. When to surface the real reason for leaving Before offer stage, not after a verbal acceptance 2 weeks in: test whether money fixes it Source: Process steps in this section
If a raise and a title would keep them, the current employer can supply both and the search is a negotiation lever, not a hire; learn that in week two, not after the offer.

Why does this keep happening to the same firms?

Because a process built for speed treats verbal acceptance as the finish line. The firms that lose candidates at resignation are usually the ones that ran a fast, clean, entirely transactional process, and never asked the one uncomfortable question.

There is a structural version of this problem too. A recruiter paid on placement has every incentive to reach an accepted offer quickly and no incentive to interrogate whether the candidate is genuinely leaving. The conflict is built into the model rather than into the individual, and it shows up precisely here: the questions that most reduce counteroffer risk are the ones most likely to slow or kill the deal. This is one of the practical differences between a headhunter and a recruiter working a volume desk. Selah runs confidential searches for a senior project manager.

It is also why the roles that matter most are usually approached confidentially. A candidate who applied to a posting is, by definition, actively looking, and an active looker often has their current employer’s attention already. A candidate approached directly for a role that was never advertised has had no such conversation, which is one practical benefit of confidential executive search for mandates that cannot be publicly posted.

This does not apply everywhere. If you are hiring someone who is unemployed, relocating for family reasons, or leaving a firm that is visibly contracting, counteroffer risk is low and the five steps above are overhead. Skip them. The trap is specific to hiring a performing person out of a stable firm mid-project, which happens to be most senior construction hiring.

The lesson is not that candidates are unreliable. It is that a verbal acceptance is a statement of intent made before the hardest conversation, and if you have not prepared the person for that conversation, you have not finished hiring them.

Losing candidates at resignation more than once? Let us look at the process.

Sources and further reading

  • AGC workforce survey reporting on salaried hiring difficulty
  • BLS job openings and labor turnover survey
  • BLS occupational data for construction managers
  • ABC construction workforce data