You spent weeks finding the right person. You checked their references, liked them in the interview, and made the offer. They signed. Then, six weeks later, they handed their notice in.
Not because the job was wrong for them. Because the experience made them question whether they belonged.
This happens more often than most field service business owners want to admit. Research from Enboarder found that 86% of new hires decide how long they'll stay within their first six months. And the top reasons people leave within the first 90 days aren't about pay or job fit. They're about three things: unclear expectations, lack of connection, and feeling unsupported.
Every one of those is an onboarding problem, not a hiring problem.
Table of Contents:
Most onboarding advice is written for office workers. They sit in the same building as their manager. They can ask someone where the printer is, overhear conversations about how things work, and gradually absorb the culture through proximity. A field engineer's first week looks nothing like that.
They might spend the majority of it driving solo to jobs they've never done before, at sites they don't know, using software they've been shown once. Their "office" is a van. Their colleagues are scattered across different sites. Their manager is back at base dealing with a full schedule.
The isolation is real, and most onboarding guides don't address it. A new engineer who spends their first week feeling lost and unsupported isn't going to ask for help. They're going to quietly start wondering whether they made the right call accepting the job.
Replacing an engineer who leaves in that first 90 days costs roughly 20% of their annual salary according to research from the Center for American Progress, and that's before accounting for the jobs that don't get done well while they were finding their feet. Getting onboarding right isn't a nice-to-have. It pays for itself quickly.
[xyz-ihs snippet="Download-Brochure"]
Every person who starts a new job is running a background process in their head. They might not articulate it, but they're asking three questions from day one:
If the answer to any of those is no, disengagement begins quietly. Not with a resignation letter, just a slow withdrawal of energy, initiative, and commitment. As one leadership coach put it: "If leadership disappears after orientation, don't be surprised when employees do too."
Good onboarding answers all three questions clearly and early.
The period between someone signing their contract and showing up on Monday morning is the most overlooked phase of onboarding. Most businesses treat it as dead time. The smart ones treat it as the first chapter.
A few things are worth doing before day one that take little time and pay back quickly:
Day one has one job: make the new engineer feel like they made the right decision.
That doesn't require anything elaborate. It requires intention.
Start with a proper welcome before anything else. Not paperwork, not a briefing on the van policy. Just a conversation. Show them round, introduce them to everyone they'll interact with by name and role, and tell them something genuine about why you're pleased they're there.
Go over what the next few weeks will look like. Give them the 30-day outline in writing: what they'll be learning, who they'll be working with, what they'll be doing independently by the end of it. People with a clear picture of what's ahead settle in faster than those left to figure it out as they go.
Cover the basics of how the business works. Not a presentation, just a conversation: what kinds of jobs you do, who your customers are, how jobs flow from booking to invoicing, where they fit into that. This matters more than most business owners realise. An engineer who understands how their work connects to the bigger picture is far more motivated than one who's just been handed a list of jobs.
Don't overload day one with information. Covering every policy, every tool, every process in the first eight hours doesn't prepare someone; it overwhelms them. The goal for day one is connection and context. Everything else can wait.
One thing worth saving for after the introductions: go out with them on the first job, or send them with your most dependable engineer. Not to supervise, but to show them how you work, how you talk to customers, what the standard looks like in practice. This is worth more than any amount of verbal briefing.
The single most common onboarding failure in small field service businesses is the sink or swim approach: hand the engineer a phone, give them their first jobs, and leave them to figure it out.
It gets mistaken for autonomy. What it actually communicates is neglect.
"What looks like a performance issue is almost always an onboarding issue in disguise," as one HR professional put it. An engineer who's struggling in week three usually isn't struggling because they're not capable. They're struggling because no one showed them clearly what the standard was, or because they didn't know who to ask when they were stuck.
The first four weeks should be deliberately structured without being suffocating. A few principles that work:
Structuring onboarding in three stages helps both the business and the new engineer. Here's a practical version adapted for field service businesses.
At each milestone, have a proper conversation rather than a brief. What's working? What needs more attention? What does success look like from here?
Getting a new engineer to actually embody your company's standards: the way you communicate with customers, the quality of work you expect, the way jobs are documented, is one of the hardest things to achieve through instruction alone.
People don't absorb standards by being told them. They absorb them by seeing them modelled, by understanding why they exist, and by being given feedback when they fall short.
A few things that work better than a policy briefing:
Retention is partly about process, but it's also about something more straightforward: whether someone actually likes coming to work.
The research is consistent here. The top reasons good engineers leave are not usually about pay. They're about feeling undervalued, having no clear path forward, being overworked without acknowledgement, and working for a manager who's unresponsive or difficult to read.
A few things that actually move the needle, particularly in the first few months:
One of the biggest practical challenges with onboarding field engineers is that so much of what they need to know lives in scattered places: job sheets in one folder, asset history in another system, customer notes in someone's head.
Fieldmotion brings that information together in one place that's accessible from the phone a new engineer is already carrying. Job details, site history, asset records, customer notes, compliance documents — all of it is visible before they arrive on site. That means less time spent asking what happened at this site last time, less risk of arriving at a job without the context that should have come with it, and a faster path to working confidently and independently.
When a new engineer completes a job in Fieldmotion, the data feeds into invoicing, job history, and reporting automatically. They can see their work moving through the system, which does more for buy-in than any amount of telling them it matters.
For businesses trying to onboard engineers into a consistent way of working, having the process built into the software makes it teachable. Rather than hoping a new engineer picks up habits from whoever they shadow, the platform guides the workflow from the moment a job is assigned to the moment it's complete.
If you're finding that new engineers take longer to reach full productivity than they should, or that your standards vary between engineers, the communication and consistency problems that sit behind that are often as much about process as they are about people.
[xyz-ihs snippet="Book-Demo"]
How long should onboarding last for a field service engineer?
At minimum, 90 days of structured support: deliberate check-ins, clear milestones, and an evolving level of independence, not just a one-week handover and a phone. Most businesses treat onboarding as a one-week event and then wonder why engineers take months to reach full productivity. Research consistently shows that new hire productivity in the first month sits around 25% of full capacity. Realistic expectations and sustained support through the first three months produce better engineers faster.
What's the biggest onboarding mistake field service businesses make?
The sink or swim approach: giving a new engineer their first jobs and expecting them to figure out the rest. This gets confused with trusting someone's competence, but what it actually communicates is that no one thought through their first few weeks. Engineers who feel dropped in without structure don't become more self-sufficient; they become more anxious, and more likely to leave. The fix is simple: a written plan for the first 30 days, a buddy to answer informal questions, and weekly check-ins that actually happen.
How do I make sure a new engineer picks up our company standards?
Standards are absorbed through demonstration, not instruction. Take new engineers on jobs with experienced colleagues, show them what good looks like in practice, and connect every standard to the reason it exists. An engineer who understands that a thorough job sheet protects both the business and the customer will fill it in properly. An engineer who was told to fill it in will fill it in when they remember to.
What should I cover in a 30-day review?
Keep it conversational rather than formal. Three questions work well: what's going well and feels comfortable? What's still unclear or harder than expected? What support do you need that you're not currently getting? The answers to that third question are your most useful data. They tell you exactly what to fix before problems become habits, and they signal to the engineer that their experience matters to you.