An engineer boards a Sunday night sleeper to a customer's plant. The visit is planned for nine days. He must set the frame on anchor bolts, grout and level it, and check earthing and phase rotation. Then come dry cycles, a trial on the customer's pouches, operator training and a signed acceptance protocol. It takes twenty-three. The compressed air line is late, a feeder jams on the customer's film, and the plant head keeps adding small requests. He rings the office twice. Both times he is told to stay until it is signed. Two months later he resigns.
The machine builders' hub page counts this among the commonest reasons good engineers quit. Field work is hard by nature. What tips it into unbearable is usually how the employer runs it.
How the strain builds on the road
- Trips stretch with no agreed end, because site readiness belongs to the customer.
- Lodging swings between a decent hotel and a dormitory above the customer's canteen, decided case by case, so colleagues sharing a site get unlike treatment.
- Claims stapled with bus tickets and lodge receipts wait weeks for approval, and the engineer funds the trip from his own salary meanwhile.
- Days spent on trains and buses count as neither work nor rest.
- Nobody at base owns the engineer's month, so the best fault-finder gets every urgent call.
- Customers ask for extra work on site, and the engineer has no authority to refuse or to escalate.
- Back at base, he lands straight on a shop build or is sent out again within days.
What the builder loses
Service and commissioning engineers carry the customer relationship. When one resigns, the builder loses fault-finding skill and every plant contact he had built. Rivals know this and approach him first. A new hire needs months on your models before he can be sent alone. Meanwhile the remaining engineers take more trips, and the cycle tightens.
A quieter cost follows. A tired engineer far from support cuts corners. He skips the session for the customer's operators, or leaves without a proper service report. Faults that should have been closed on site return as complaints to the owner.
Why it is handled so loosely
- The rules date from when the firm had one engineer. Practice grew trip by trip and was never written.
- Accounts and service see different things. Accounts sees cost per trip. Service sees a machine that must run. Nobody sees the engineer's month.
- Site time leaves no trace. Hours inside a customer's plant are not recorded the way shop hours are.
- Allowances become a bargaining chip. A generous rate for one engineer turns into a quiet raise the others hear about.
- No career exists beyond the road. Engineers watch seniors still travelling in their fifties and decide to leave before that.
Figures to pull first
- Last quarter's trips per engineer: days away, nights away and days at base between trips.
- The current lodging and allowance rules, if written, and how often exceptions were made.
- How long claims take from submission to settlement.
- Which engineers took the hardest sites, and who chose them.
- Exit notes from field staff who left in the past two years.
A fix in seven parts
- 1
Write one travel and site policy
Cover lodging standard, daily allowance, travel class (sleeper berth, air-conditioned coach or flight), advances and what counts as a working day. Apply it to every engineer and publish it.
- 2
Settle claims inside a fixed window
Agree the window with accounts and track it monthly. Pay an advance before long trips, so nobody bankrolls the company from his salary.
- 3
Record travel and site days properly
Log days away, travel days and weekend work. Agree how travel days and weekend site work are compensated, such as a day off at base.
- 4
Rotate the hard sites
Keep a trip roster per engineer. Spread difficult commissioning across the team, and send a junior alongside the senior on some of them.
- 5
Give every trip a base contact
One person at the office owns each site visit. The engineer calls daily, and that person handles the customer's delays and extra requests.
- 6
Set a return-to-base rule
After a long trip comes rest and a spell at base before the next one. Use base weeks for build work, training and reports.
- 7
Show a path off the road
Define routes to lead commissioning engineer, service manager, application or design roles, with the skills each one needs.
Lodging standard, and who books it.
Daily allowance, and what it covers.
Travel class by distance and time of travel.
Advance paid before trips longer than an agreed length.
Claim deadline for the engineer, and settlement deadline for accounts.
How travel days, Sundays and holidays on site are recorded and compensated.
Longest trip allowed before the base contact must review it.
Rest and base time after a long trip.
Kit carried: multimeter, insulation tester, laptop with programming cable and a spares box.
Who at base handles customer requests outside the agreed scope.
Site safety: induction, permits and the authority to halt unsafe work.Keeping it working
Review the trip roster monthly, beside claim settlement times. If one engineer's nights away keep climbing, step in before he does. Pay and allowance design can price site allowances so they stay fair across the team.
Packaging machine makers face the most short-notice calls; see their tracking of field days and leave. Compressor makers send technicians to furious customers, and their coaching for tense customer calls shows how to prepare them. For the hiring side, read why commissioning engineers are so hard to find.
