When someone leaves a construction or real estate business, the organisation needs to understand what influenced the decision. A site engineer may be tired of remote postings. A crew member may have found steadier work. A sales executive may be unhappy with incentives or leads. The reasons differ across the corporate, sales and site workforces, so the conversation should too.
The purpose is to learn from their experience, respect their decision and identify what could improve for the people who remain and for the next project.
CIPD's guidance on employee turnover highlights the value of understanding why staff leave and addressing areas such as fair treatment, flexibility and employee wellbeing. Source: CIPD
Look beyond the first answer
"Better opportunity." "Project finished." "Closer to home." These may be accurate, but they may not explain the whole decision. A project finishing might mean nobody told the person what came next. A better opportunity could mean a posting nearer home, steadier work or a clearer path to site-in-charge.
Start with a simple question: "What made you start considering a change?"
Then ask what made the person decide to leave. This helps separate the circumstances that started their search from the offer that eventually attracted them.
Avoid assuming that every exit reflects a problem. Project completion, relocation and family needs are real reasons. Look for the part within the organisation's control, including whether anyone discussed what came next.
Explore the areas that shaped their experience
Use the following areas as prompts rather than assuming any one of them caused the resignation.
- Site location and postings: Was the posting location, distance from family and time between home visits manageable?
- Project schedule and workload: Did schedule pressure lead to long hours, rushed work or last-minute changes without support?
- Safety and conditions: Did the person feel safe on site? Were living arrangements, facilities and equipment adequate?
- Pay and payment timing: Were pay, overtime and any allowances clear? Was payment on time, including for contractor crews?
- What comes after the project: Was redeployment discussed before release? Did the person know whether work was coming on another phase or site?
- Sales roles: Were incentives, lead quality and targets clear and fair? Could the person check how incentives were calculated?
- Manager and site leadership: Were instructions clear? Did people feel able to raise concerns with the project manager or site in-charge?
- Growth and personal circumstances: Could engineers and supervisors see a progression path? Did family or relocation shape the decision?
Several factors may contribute to one resignation. Allow people to explain these connections in their own words.
Create a respectful exit conversation
Invite the person to a voluntary conversation during their notice period or, for crews, at release or demobilisation. Explain that the purpose is to understand their experience and improve the next project.
Where possible, choose someone sufficiently independent of the issues being discussed. For site staff, that may be HR or a manager from another project, not the project manager or site in-charge. Give the person the option to provide written feedback, or a short phone call, if a formal conversation is not practical.
Explain who will see their responses and how the information will be used. Avoid promising complete anonymity on a small site where details could identify the person.
Listen without interrupting or defending each decision. If clarification is needed, ask for a specific example respectfully. The person should not have to justify their decision to leave. For how to run the process around the conversation, see exit interviews that produce action. The general version of this guide covers the questions that apply in any business.
Ask questions that lead to useful feedback
- 1
What first made you consider leaving, or not staying on after this phase?
This finds the starting point, which is often different from the final reason.
- 2
What were the main factors in your final decision?
Let the person link the factors in their own words.
- 3
What did you value most about working here?
It shows what is worth protecting for the people who stay.
- 4
How did the role and posting compare with what you were told when you joined?
Gaps point to promises about location, duration or role that were not kept.
- 5
Was your pay, including overtime or incentives, clear and on time?
Listen for late payment and for incentive queries that went unanswered.
- 6
How manageable were the site hours, schedule pressure and living arrangements?
Listen for repeated rush periods and missing support.
- 7
How safe did you feel on site, and were your concerns heard?
This shows whether safety concerns reached someone who could act.
- 8
Did anyone discuss what would come next for you after this project or phase?
The gap here is often the real reason a person leaves at release.
- 9
Were there concerns you raised earlier? How were they handled?
This shows whether concerns reached anyone who could act.
- 10
What should we improve for the next person in this role, or the next crew on this site?
A forward-looking close that also tells you whether you would welcome them back.
Use follow-up questions where necessary, while allowing the person to skip questions they do not wish to answer.
Turn individual feedback into a pattern review
Record the main reason for leaving, any contributing factors and a brief factual summary. Separate what the person said from your interpretation. For crews, also record whether you would welcome the person back on a future project.
Review departures over time by project, site, role, contractor and length of service. Repeated concerns deserve attention, but a small number of exits should prompt further investigation rather than an immediate conclusion about a project manager or contractor. The attrition number that hides the problem explains why a single headline rate is not enough.
Compare exit feedback with attendance, schedule pressure and safety records. Keep identifiable responses restricted to those who need access, and use summaries for wider reporting.
Give each improvement an owner
An exit conversation has limited value if the feedback is simply filed away. For each issue selected for action, agree on:
- The specific change needed.
- The person responsible.
- A completion date.
- How progress will be reviewed.
For example, release without a redeployment conversation could lead to a standard check before demobilisation, owned by the project manager. Payment delays for contractor crews could lead to a review with the contractor. Sales incentive queries could lead to a published calculation.
Where appropriate, tell current employees what has changed, without revealing a departing employee's private feedback.
Start listening before people resign
Include regular conversations about what helps people work well and what makes the job difficult. Ask: "What would make you consider leaving, and what could we improve now?"
On a project, a conversation at the start of each phase can catch concerns before the phase ends and the crew disperses. Follow-through matters: asking for feedback creates an expectation that someone will act on it.
Every resignation or release deserves a respectful response. Understanding the reasons, checking the wider evidence and acting on issues within the organisation's control gives that conversation a useful purpose.
