In a controls firm a resignation seldom lands on a quiet day. It tends to arrive a fortnight after a cell clears its site trial. By then the engineer has slept in a lodge near the customer's gate for weeks, eaten in their canteen and fielded two recruiter calls in the car park. The punch list closes, the invoice goes out, and the one person who knew the sequence logic is serving notice.
The resignation mail is usually brief. 'Better package.' 'Wanted something near home.' 'Joining a product company.' Each may be true. Each can also mask something fixable. A design seat was promised after 'just one more site'. The breakdown phone never rotated. Three years went by on one controller family with no route to the next.
What 'better package' tends to hide in a controls team
Pay for ladder logic, servo tuning and SCADA scripting does climb quickly, so never brush the money answer aside. Ask what the new letter actually altered. Often the fixed component rises only a little. The bigger gain is a written site allowance, fewer nights in lodges, or a title with lead in it. Once the leaver names the clause that won them over, you know which part of your own offer was thin.
A second pattern is the customer hire. An engineer who brought up a palletising cell gets approached by the plant that bought it. Their maintenance head offers one address, a general shift and no laptop bag on a night bus. The mail says 'better opportunity'. The real comparison was a settled life against a travelling one.
Pressures that pile up between kickoff and handover
- Weeks outstation: How many weeks away in the final half year? Were return dates honoured, or pushed back each time the customer's mechanical contractor slipped?
- Festival cutovers: Plants schedule changeovers in their Diwali or year-end stoppage. Did the same engineers miss the holidays every year?
- The breakdown phone: Was there a named rota for service calls, with rest next morning, or did it ring whoever wrote the program?
- Platform lock-in: Was the person kept on one controller make or one robot brand because they were fastest on it, while juniors got the newer kit?
- Five jobs in one: Did they draw, program, check ferrules, commission and answer warranty calls on the same job?
- Credit at sign-off: When the customer signed the acceptance protocol, did anyone back at the office notice who made it happen?
- The ladder: Could they see what separates a controls engineer from a senior, or a site lead, and the money attached to each rung?
- Customer temper: Were they shouted at by a production head over cycle time, and did their own manager step in?
- Home: Ageing parents, a wedding, a child starting school. These pull people toward a fixed location.
Most leavers carry three or four of these together. Ask them to rank their own list, and to name the week the thought first arrived.
Small signals usually surface in registers the firm already keeps. Did the leaver's comp-off balance balloon? Were reimbursements for guest houses and sleeper berths settled late? Did they stop volunteering for pre-sales demos or the exhibition stand? Did a customer's maintenance head start ringing their personal mobile for every glitch? Each shows up months before the resignation mail.
Choosing a listener outside the delivery chain
The project manager or technical head is usually inside the story. They set the site roster and chose who went to the difficult plant. Pick somebody with no hand in those calls: the HR lead, a purchase or accounts head the engineer trusts, or the founder if the founder does not run delivery. Book it before the final week, because the handover scramble swallows everything. Tell the leaver exactly whose desk the summary reaches.
Engineers answer precise prompts better than broad ones. 'Were you happy here?' gets a shrug. 'Which week on the bottling job was the worst, and why?' gets a story. The mechanics of running such talks well sit in our piece on exit conversations that lead somewhere. The prompts below are tuned for controls, robotics and panel teams.
Nine prompts for a departing engineer or wireman
- 1
When did you start answering recruiters properly?
The date often lines up with one particular site posting or a broken promise.
- 2
Which line in the new letter tipped it?
Fixed pay, site allowance, city, title or the kind of project. Ask them to choose one.
- 3
How many nights in lodges did your last two jobs involve?
Check the answer against the travel register afterwards.
- 4
Who rang you after ten at night, and how often?
Shows whether service calls were shared or simply followed one name.
- 5
Which controller, robot or software did you want to master here?
A newer robot controller, safety relay design, a vision library or a SCADA historian.
- 6
Did the desk and site split match the interview?
The gap between promise and practice in project firms usually sits right here.
- 7
Did any plant treat you badly, and what did we do?
Silence from your own side wounds more than a customer's outburst.
- 8
What single change would have bought one more year?
Write the reply down verbatim.
- 9
What should your replacement be warned about?
Ends on something practical they can hand over.
Reading exits by desk, shop floor and site crew
Tag each leaver by team: design desk, panel shop, site crew or service desk. Add their platforms, their manager and the jobs of their final year. Keep their words separate from your interpretation. Then lay resignations against the FAT and SAT calendar. Do they bunch after site acceptance on large lines? After increment letters in April? After a new project head arrived? Three exits from the site crew and none from the desk point at travel and rotation, not at pay bands alone.
Put exit notes beside the travel register, the on-call log and the timesheets. A single company figure blurs every one of these signals, as our explainer on what a single attrition figure conceals sets out.
Giving each finding a named fixer
- Postings that stretch: the project head publishes a rotation plan and a rest rule after long stays.
- Breakdown calls on one name: the service manager runs a named rota and briefs a backup on each plant.
- Platform lock-in: the technical head decides who learns which controller family next, and by when.
- No visible ladder: owner and HR write the levels from trainee to site lead, with what each pays.
- Customer temper: the account manager raises it with the plant and logs what was said.
Every item needs an owner, a month and a review point. Tell the team which changes came from leavers, without names. GullyHR's retention planning for project teams begins from evidence of this kind. Our page on HR for industrial automation and robotics covers the other recurring patterns in this trade.
Hearing the story before the resignation mail
These prompts also work as stay conversations. Hold one when an engineer returns from a long posting, another after increment letters, and a third when a trainee first bills a customer. Our guide for shift-based plants suits factories that run rotas. In a project firm the natural moments are milestones instead: factory acceptance, site acceptance and the close of warranty.
