New Hire Isn't Ready for Solo Jobs Yet: Decision Tree
Why this matters
The schedule says this new hire should be running solo calls by now, and your gut says otherwise. Send them out anyway and a shaky new hire in front of a customer with nobody to catch a mistake turns into a callback, a safety incident, or a customer who never books again. Hold them back with no explanation and you demoralize someone who might just need one specific thing fixed, not more time in general. The fix is naming exactly what kind of "not ready" you're looking at, because the four common versions need four different responses, and confusing them wastes weeks.
Start here: is this a safety concern
If the readiness gap involves anything that could hurt the new hire, a customer, or property, that overrides every other consideration below. A new hire who is technically fast but cuts safety corners, freezes around live hazards, or has not internalized lockout and PPE habits does not go solo, full stop, no matter what the calendar says. Fix the safety gap first and completely before revisiting anything else on this list.
Step 1: Name which kind of "not ready" this actually is
Watch the new hire on their next few supervised jobs and sort what you see into one of four buckets. They look similar from the outside, "still needs help," but the fix is different for each.
| What you observe | Likely cause | Where the fix lives |
|---|---|---|
| Solid on the mechanics, but slow and hesitant | Skill or repetition gap | More reps on this specific job type |
| Confident and fast, but misses the same category of thing repeatedly | Blind spot in training | Targeted coaching on that one gap |
| Technically fine, but freezes or fumbles with the customer | Communication or confidence gap | Practice the conversation, not the task |
| Good on routine work, falls apart the moment something is unusual | Judgment gap, no pattern library yet | More exposure to variation before solo |
Step 2: If it's a skill or repetition gap, give them more reps, not more instruction
A new hire who understands the job but is still slow and hesitant on the actual mechanics does not need a new explanation of the task. They need to do it more times. Re-explaining a task the new hire already understands conceptually wastes time and can make them feel like they are failing at something they actually grasp.
- Keep them at the "leading with a senior tech present" stage on this specific job type for longer, rather than moving them to solo and hoping repetition happens on its own with nobody watching.
- Track the count. If you have run this job type with them five times and hesitation has not dropped, this may not be a pure repetition problem, recheck against the other buckets.
Step 3: If it's a recurring blind spot, coach the specific gap directly
Some new hires are fast and confident overall but consistently miss one category of thing: they never check a specific reading before proceeding, they consistently skip a documentation step, they miss the same type of cue every time. This is not a general "needs more time" problem, it is a specific, nameable gap.
- Name it explicitly to them. "You're strong on the diagnosis, but you're skipping the verification step every time. Let's fix that one thing." A vague "keep working on it" does not target a specific gap.
- Watch specifically for that one behavior on the next few jobs rather than re-evaluating everything. A targeted gap gets fixed fastest with targeted attention, not a full restart of training.
Step 4: If it's a customer-facing confidence gap, practice the conversation separately from the task
Some new hires can do the technical work well but visibly struggle the moment they have to explain something to a customer, present an option, or handle a question they were not expecting. Sending them solo before this is fixed does not just risk an awkward interaction, it risks a customer who reads hesitation as incompetence regardless of the actual work quality.
- Role-play the specific conversations they will need to have: explaining a diagnosis, presenting a recommendation, handling "how much is this going to cost." Practicing away from a live customer removes the stakes while the skill builds.
- Have them observe a few more customer interactions specifically, not because their technical skill needs more watching, but because their communication does. Frame it to them that way so it does not feel like a demotion.
Step 5: If it's a judgment gap on anything unusual, give them more exposure to variation before going solo
The trickiest bucket. A new hire can be genuinely excellent on the routine, high-frequency jobs and still not be ready for solo work, because solo work means they will eventually hit something outside the pattern with nobody there to catch it. This new hire looks ready on paper, their numbers on routine work are solid, but has not yet built the judgment to recognize when something does not fit the usual pattern.
- Deliberately expose them to more edge cases while still supervised, rather than assuming competence on the routine 80 percent of jobs means readiness for the other 20 percent.
- Ask them directly: "What would you do if this reading didn't match what we usually see?" Their answer tells you whether they have a judgment framework or just a memorized pattern. A new hire who says "I'd stop and call someone" has the judgment even without the specific experience yet; that answer is often enough to justify a supervised trial with a very reachable backup.
Step 6: If none of the above fits, or several buckets overlap, extend supervision and reassess on a set date
Sometimes a new hire genuinely spans more than one bucket, or you are not confident enough yet to say which one it is. That is a legitimate answer, but it needs a plan attached, not an open-ended "let's see how it goes."
- Name a specific date to reassess, not "when they seem ready." An undated extension quietly becomes indefinite and nobody notices until the new hire is frustrated at being held back with no explanation.
- Tell the new hire honestly what you are watching for and why. Being held back from solo work with no stated reason reads as a vote of no confidence; being told "here's specifically what I want to see before you solo" reads as coaching.
Quick recap
- Safety concerns override everything else, fix those completely first.
- Sort the gap: repetition, a specific blind spot, customer-facing confidence, or judgment on the unusual.
- Repetition gap: more reps on this job type, not more explanation.
- Blind spot: name it specifically and watch for that one thing.
- Confidence gap: practice the conversation, separate from the technical task.
- Judgment gap: more exposure to variation while still supervised.
- Unclear or overlapping: extend supervision with a specific reassessment date, and tell the new hire why.
References
- Trade-standard practice for supervised-to-solo technician progression
- OSHA, on-the-job training and competency verification guidance
- See related: The First Solo Job Go/No-Go Checklist, The Ride-Along Sequence That Actually Builds Competence