The First Solo Job Go/No-Go Checklist
Why this matters
Sending a new hire on their first unsupervised job is a real decision, not a scheduling formality, and too many shops make it by gut feel or by calendar: "they've been here five weeks, they must be ready." A new hire sent solo too early who fumbles in front of a customer damages trust that took weeks to build, in both the customer relationship and the new hire's own confidence. A new hire held back past genuine readiness gets bored, feels distrusted, and starts eyeing the door. This card gives you the actual criteria to check, so the call is a decision you can defend, not a guess.
The go/no-go table
Run down this table before the first unsupervised job. Every row should be a clear yes before you send them alone. A no on any single row is a no on the whole decision, not a "probably fine."
| Check | Go looks like | No-go looks like |
|---|---|---|
| Safety habits | Automatic, no reminders needed | Needs prompting, or has cut a corner even once |
| Job-type familiarity | Has run this exact job type multiple times with a senior tech present and not stepping in | Has only observed it, or has run it but the senior tech kept intervening |
| Documentation and systems | Logs time, materials, and notes correctly without help | Still needs help navigating the job system or forgets steps |
| Customer communication | Can explain findings and next steps clearly, handles basic questions | Freezes, defers everything, or gives answers that need correcting after the fact |
| Judgment on the unexpected | Says "I'd stop and call" when a reading or situation doesn't fit the pattern | Guesses, or pushes forward on something outside their experience |
| Backup availability | A specific, known person is reachable by phone for the job's duration | Nobody specific is lined up, or the plan is "call the office" with no named person |
Why "has run it multiple times unsupervised" is not on this list
Notice the job-type familiarity row does not require the new hire to have already worked unsupervised. That would be circular: you cannot require unsupervised experience as the bar for the first unsupervised job. What it requires instead is that a senior tech has watched them run this exact job type enough times, without needing to step in, that the pattern is proven under supervision. That is the real signal readiness testing is after.
The backup call matters more than it looks
The last row is the one shops skip most often, and it is not a formality. "Solo" should never mean "unreachable." Before the truck leaves, name one specific person who will answer the phone for the duration of that job, and make sure the new hire knows exactly who that is. "Call the office if you need anything" is not a plan; a specific name is. A new hire who calls their backup once during their first solo week is using the system correctly. Treat that call as a normal, expected event, not evidence the go decision was wrong.
What a clean go decision looks like
- Every row in the table is a genuine yes, not a hopeful yes.
- The new hire has been told explicitly: "I think you're ready, here's why, and here's who to call if anything's off."
- The specific job assigned for the first solo run is one they have handled well multiple times under supervision, not a harder variant "since they seem capable."
- Someone checks in partway through the day, even briefly, rather than treating "solo" as "out of sight."
What a clean no-go decision looks like
A no-go is not a failure, it is information, and it should be delivered that way. Tell the new hire specifically which row was the sticking point and what closing that gap looks like, with a rough sense of timeline. "You're not ready yet" with no specifics reads as a vague vote of no confidence. "You're strong on the mechanics, I want to see the customer conversation land smoothly a couple more times before you solo" is coaching, and most new hires respond well to a clear, specific bar rather than an open-ended delay.
If you're not sure, that's itself informative
If you genuinely cannot fill in the table with a confident yes or no on several rows, that usually means the new hire has not had enough supervised exposure yet to judge, not that they failed some invisible test. The fix is more supervised reps on the specific rows you cannot yet answer, not a rushed decision either direction. See related: New Hire Isn't Ready for Solo Jobs Yet: Decision Tree for the deeper diagnosis when a specific row is a clear no.
References
- Trade-standard practice for supervised-to-solo technician progression
- OSHA, on-the-job training and competency verification guidance
- See related: New Hire Isn't Ready for Solo Jobs Yet: Decision Tree, The Ride-Along Sequence That Actually Builds Competence