How to Turn a Ride-Along Into Actual Curriculum
Why this matters
Most ride-alongs are exposure, not training. The apprentice rides for six months, sees whatever the calendar happened to hand them, and comes out competent at the four things that came up twice and blank on everything else. Nobody planned it, so nobody can say what they can do. That is why a shop with a "training program" still cannot answer the only question that matters on a Tuesday morning: can this person run that call alone.
Curriculum is what closes that gap, and it is not a binder. It is a list of things the apprentice must be able to do, mapped to the job types that produce those situations, sequenced against the calls you actually sell. The work stays the same work. The planning costs a few hours once and about ten minutes a week after that.
Step 1: Derive the objective list from your own job mix
Pull the trailing 90 days of completed calls out of your job history and sort them by job type. You are not writing a trade-school syllabus. You are writing the curriculum for the work your shop actually sells, in the proportion it sells it.
Say the pull comes back looking like this (illustrative, but the shape is typical for a small residential shop):
| Job category | Share of completed calls |
|---|---|
| Service diagnostics | 44% |
| Planned maintenance | 27% |
| Repair and component replacement | 19% |
| Install or changeout | 6% |
| Callback and warranty return | 4% |
That table is your syllabus weighting before you write a single objective. Diagnostics is nearly half the board, so nearly half the curriculum belongs to diagnostics. Anything under roughly 5% of calls does not get its own objectives in the first pass. It is not that installs do not matter, it is that the calendar will not produce enough of them to teach against, and an objective you cannot practice is a line item that sits open forever and makes the whole sheet look dishonest.
The failure mode here is teaching what the senior tech enjoys teaching. Installs are satisfying to demonstrate, visible, and finite. Diagnostics is frustrating to teach and hard to narrate. So the apprentice comes out install-strong and diagnostically helpless, which is exactly backwards against a board that is 44% diagnostics.
Step 2: Write objectives as observable actions, not topics
A topic cannot be signed off. An action can. Every objective needs three parts:
- A verb someone can watch. Isolates, measures, states, sequences, verifies, documents.
- A condition. With what tools, on what equipment, under what supervision.
- A bar. What counts as done right, including the tolerance for being wrong.
"Understands the control circuit" is a topic. Here is the same thing as an objective: "Isolates a control-circuit fault to either a component or the wiring using a multimeter, states the expected reading out loud before probing, and explains what the reading ruled out. Bar: correct isolation on 3 consecutive calls without prompting."
The "states the expected reading before probing" clause is the load-bearing part and it is worth stealing for half your diagnostic objectives. A tech who measures first and interprets after can be pattern-matching. A tech who predicts first is reasoning, and you can hear whether the reasoning is sound even on the calls where the prediction is wrong.
Where an objective touches a real hazard, the safety action is inside the objective, not adjacent to it. "De-energizes and verifies dead with a known-good meter, proves the meter on a live source before and after, then measures" is one objective. Do not write the measurement objective and assume the lockout objective covers it, because the apprentice will do them in whatever order the day allows.
Step 3: Map each objective to the job types that produce it
This is the spine of the whole system. Without it you have a wish list; with it you have a schedule that dispatch can run.
| Objective (abbreviated) | Job types that produce it | How often that type runs | Touches to sign off |
|---|---|---|---|
| Verify dead before contact | Every repair, most diagnostics | Daily | 5 |
| Predict-then-measure on a control fault | Service diagnostics | Most days | 3 |
| Full maintenance sequence unaided | Planned maintenance | Weekly, seasonal peaks | 3 |
| Read the equipment history before touching it | All types | Daily | 3 |
| Document a no-fault-found honestly | Diagnostics, callbacks | Weekly | 2 |
| Isolate a supply problem from a load problem | Diagnostics, callbacks | Weekly | 3 |
Two things fall out of this table immediately. First, the objectives tied to daily job types will complete themselves if you simply pair correctly. Second, the objectives tied to a job type that runs weekly are the ones that will stall, and those are the ones that need a deliberate assignment rule rather than luck.
"Touches to sign off" is the count of separate calls where you expect to see the behavior before you believe it. Three is a sane default for a routine skill and it is not arbitrary: one is a demonstration, two is a repeat that may be memory, three across different equipment is the first honest evidence of transfer. Raise it to five for anything where the failure mode is injury rather than a callback.
Step 4: Sequence by what the calendar will hand you
Textbook order is prerequisite order. Field order is prerequisite order filtered by what actually shows up. Take the objectives, then sort them by two factors in this priority:
- Safety and access gates first. Anything the apprentice must be able to do before being allowed to touch the equipment at all. These are not negotiable and they are not weighted by frequency.
- Then frequency, highest first. Teaching a rare skill early means teaching it, waiting five weeks for the next instance, and re-teaching it. That is two teaching sessions to get one skill, and you paid for both.
Prerequisite depth is real but shallower than people assume. Most field skills have one or two genuine prerequisites, not a chain of six. If your sequence has a skill sitting behind four gates, check whether the gates are real or whether you are just reproducing the order you happened to learn it in.
Step 5: Give dispatch one rule it can actually follow
A curriculum that lives in a document and not in the board is decoration. The rule is one sentence: when a call matching an open objective lands and the assigned teacher is available, the apprentice rides it, unless the call is a true emergency or the customer has declined a second person on site.
Then set the pairing budget honestly. Teaching calls run longer. If a routine diagnostic call averages 1.5 hours solo and 2.2 hours when it is being taught, each teaching call costs about 0.7 hours of extra field time, roughly 47% longer than the solo version. A shop that can absorb 6 teaching calls a week is spending about 4.2 extra field hours a week on training. That is the real number to look at when someone says training is free.
Decide the budget before the busy week hits, because the busy week is when it silently drops to zero and never comes back. Six teaching calls a week that survive July beats twelve that evaporate in May.
Step 6: Track coverage on one page
One row per objective, three states: seen (watched it done and narrated), done with coaching (performed it with the teacher present and correcting), done unaided and signed (performed it correctly with the teacher observing silently, on the required number of touches).
Keep it on one page. A tracker that needs scrolling gets updated for two weeks and then abandoned. Update it in the debrief, not later from memory, because memory upgrades "seen" to "done" without asking permission.
A worked example: eight weeks against a 34-objective list
A four-tech shop takes on one apprentice. The objective list comes out at 34 items after the job-mix pass. The apprentice rides four days a week.
Here is the arithmetic that surprises every owner who does it for the first time. On a five-call day, you can teach at real depth on about two calls. The others are running late, the customer is talkative, the fix is trivial, or the tech is behind and takes over. Two teaching touches a day, four days a week, is 8 touches a week. Over 8 weeks that is 64 touches.
The 34 objectives at an average of 3 touches each need 102 touches to reach signed. You have 64. That is enough to fully sign off about 21 objectives (64 divided by 3 is 21.3), which leaves 13 of 34 untouched, about 38% of the list.
That is not a failure of the plan. It is the plan telling you the truth eight weeks early instead of eight months late. You now have exactly two levers: extend the timeline to about 13 weeks for full coverage at the same pace, or rank the 34 and accept that the bottom 13 wait for the next block. Ranking is almost always the right call, because the bottom 13 are usually the low-frequency objectives that the calendar was not going to produce anyway.
What you must not do is keep the 34-item list and the 8-week timeline and let both quietly slide. That produces the outcome everyone knows: at week 8 the apprentice has partial exposure to 30 objectives and full competence in none, which is worse than deep competence in 21, because partial competence is the state where a person is confident enough to proceed and not skilled enough to catch themselves.
What changes the answer
- Heavy seasonality. If 60% of your maintenance volume lands in two months, front-load every maintenance objective into that window and let diagnostics wait. Teach against the season you are in, not the one on the sheet.
- Commercial mix. Commercial calls run longer and have fewer of them, so touches accumulate slowly and each one is worth more. Raise the depth per call and lower the touch count expectation.
- An experienced hire rather than a green apprentice. Do not start at objective one. Run the whole list as an assessment over the first two weeks, mark what they already do unaided, and build the curriculum from the gaps. Making a 12-year tech demonstrate lockout on five calls to satisfy a tracker is how you lose them.
- Two apprentices at once. The teaching capacity, not the learner capacity, is the constraint. Two apprentices on one teacher does not double throughput, it roughly halves the depth per touch. Either add a second teacher or stagger the start dates.
How to verify you got this right
Three checks, all fast:
The dispatch test. Ask your dispatcher what the apprentice needs next. If they cannot answer in one sentence, the curriculum is not in the board and it will not run.
The pull-forward test. Pick an objective marked signed at random and ask the apprentice to walk through it cold, on a job they are not currently on. If the answer starts with "well, it depends on how Dave does it," you have signed off imitation, not competence.
The coverage-honesty test. Compare the tracker against the completed-call history. If the tracker says the maintenance sequence was signed off across three touches but the history shows the apprentice was on only two maintenance calls that month, someone is filling in the tracker from memory, and every number on it is now suspect.
References
- See related: The Ride-Along Sequence That Actually Builds Competence, The New Tech Ride-Along Checklist
- See related: The Competency Sign-Off SOP, The Ride-Along Debrief SOP
- OSHA general industry guidance on training employees before assigning hazardous tasks
- U.S. Department of Labor apprenticeship program standards, on-the-job learning structure