Short answer: engineers will leave, but one departure need not strand a customer. Make handover a standard stage, with structured notes, archived code, a second engineer in reviews and a walkthrough before closure, and tie part of closure to it. What follows shows how an owner puts that into practice, then tackles the follow-up worries owners voice most.
First, measure the exposure
Most owners sense the risk without knowing its size. An exposure map fixes that in a day. List every installed system still under warranty or an annual maintenance contract, plus every platform the firm supports. Beside each, write who could take a breakdown call alone. A row with one name is exposed. An exposed row on an anchor account, or on a contract due for renewal, is urgent.
Customer, plant and line.
System: palletising cell, cartoner controls, inspection stations, pumping-network SCADA.
Controller, robot or software versions running on site.
Engineers able to support it unaided.
Engineers able to support it with help.
Contract: warranty until when, maintenance contract renewal date, or none.
Exposure: single name, two names, wider team.The map rarely lies, but a few everyday signs confirm what it shows. Look for these before trusting any row marked two names.
- The plant's maintenance foreman phones one engineer's mobile directly, bypassing the service desk.
- Only one person has ever logged in remotely to that site's controller or SCADA server.
- Teach points, recipes or reject thresholds were last changed by the same engineer every time.
- Warranty visits to that account always carry the same name on the travel register.
- Nobody else can say which software version is actually running on site today.
Second, seat a second chair on every live system
For each exposed row, choose a second engineer. They join the next service visit, sit through a program review with the author, and answer a share of warranty calls while the author stays reachable. Introduce them to the customer's maintenance head in person, so the plant knows a second number exists. On new orders, the second chair is fixed at kickoff and attends design review and factory acceptance.
Third, price handover into the job
Handover collapses when it is unpaid effort squeezed in after commissioning. Put hours for it in every estimate, as a line the customer never sees cut. Spell out what it covers. Commented logic sits in the server archive. Drive and robot backups sit beside it. Network addresses and passwords go into the firm's credential vault. A one-page note lists quirks and open punch points. Before the job closes, the second chair rebuilds the system from the archive onto spare hardware. Release part of any project bonus only when that rebuild works.
Fourth, keep tools and access in the firm's name
Programming laptops, software licences, dongles, remote-access credentials and customer passwords belong to the company, never to individuals. Keep a device and access register showing who holds what. When someone resigns, the register shows exactly what to collect and which customer passwords to rotate on their last day.
Fifth, plan the notice period account by account
When a key engineer resigns, open the exposure map that afternoon. For every account where they are the single name, book joint visits, a rebuild check and a handover note well before the final fortnight. The offboarding process sets the sequence. The bench-level detail of master copies and site edits sits in our pattern guide on single-engineer projects.
What if the engineer resists sharing?
Reluctance usually springs from two sources: no time, or fear of becoming dispensable. Hours in the estimate cure the first. Speak to the second directly. Having trained a successor is grounds for promotion on a specialist ladder, not a step toward redundancy, and the ladder should say so in writing. If reluctance persists after both, handle it through the normal performance route.
Won't a second chair price us out of tenders?
It does not double the labour. The second chair needs perhaps a few days on a typical job: design review, factory acceptance, one site visit and some calls. Set that beside a stranded customer, a botched callback or a lost maintenance renewal and it looks cheap. Plenty of buyers like hearing that two engineers know their line.
What do we tell the customer?
Present it early and as a strength: their system now has two named engineers. If one leaves, tell the plant before the engineer does, name the successor and offer a joint visit. Customers accept departures. What they resent is discovering one by accident when a breakdown call goes unanswered.
How quickly does the exposure fall?
The map takes a day. Second chairs on the riskiest accounts can be seated inside a quarter. Pricing handover into estimates changes habits within a few projects. GullyHR's documentation process design builds the records that hold this together. The vision firms' documentation guidance shows one business type's version. Further people risks that recur among integrators are listed on our robotics and controls hub.
