Resources / Shop SOPs
Shop SOPs for fleet maintenance
A shop SOP is a short written procedure for a job your fleet shop does the same way every time, including the places where your way differs from the manufacturer's book and why. This page lists which SOPs a fleet shop needs, how to write one from a veteran technician's head in an afternoon, and how to keep them current.
What an SOP is in a fleet shop, and what it is not
The manufacturer's service manual tells you how to do a job on that engine. An SOP tells you how this shop does that job on these units. Most of the two overlap. The SOP is worth writing for the part that does not: the step you add, the step you skip, the torque figure you use instead, and the reason.
That makes an SOP the written form of the shop's tribal knowledge, one job at a time. The tribal knowledge in fleet maintenance page covers where that knowledge hides. SOPs are where the procedural part of it goes once it is found.
NASA's 2021 review of its own knowledge continuity practice put job documentation, meaning "responsibilities, roles, policies, procedures, contacts, milestones," on its list of practices to standardize, and its first recommendation was to "standardize processes, templates, and guidance to support knowledge capture" (NASA, Ensuring Knowledge Continuity during Employee Transitions, 2021). Procedures are on the list. So is a template, which is why there is one below.
Keep each SOP to one page. A procedure a technician will not read in the bay is a procedure that exists only for the audit.
Which SOPs a fleet maintenance shop needs
Two kinds. The first kind has a rule behind it, and the SOP exists so the shop meets the rule the same way on every unit. The second kind has no rule, just a job that goes wrong when it is done from memory. Here is a working list for a fleet under federal motor carrier rules. School bus and transit fleets sit under state programs and FTA guidance, so swap the rule column for yours.
| SOP | Why it needs one | Rule behind it |
|---|---|---|
| Driver vehicle inspection report handling | Who reads the report, what gets fixed before release, what the certification says | 49 CFR 396.11 and 396.13 |
| Preventive maintenance, per unit class | The interval this shop runs and the local additions to the OEM checklist | 49 CFR 396.3, "systematically inspect, repair, and maintain" |
| Periodic inspection | Who is qualified, what is checked, where the proof goes on the vehicle | 49 CFR 396.17 |
| Brake inspection and repair | Only a qualified person, with evidence of qualification on file | 49 CFR 396.25 |
| Maintenance records | What goes in the file, in what words, and how long it is kept | 49 CFR 396.3(b) |
| Fault intake and diagnosis | What is checked first on each engine family before a part is ordered | None. Shop practice |
| Unit specific overrides | The zip tie, the relocated sensor, the connector that fails before the sensor does | None. Shop practice |
| Parts ordering | Cross references that fit, suppliers by part type, the do not buy list | None. Shop practice |
| Road call | What goes on the truck, who is called, what is tried before a tow | None. Shop practice |
| Bulletin and recall handling | Who receives it, where it is filed, how the affected units are flagged | None. Shop practice |
Your safety program will add its own, lockout and tagout among them. Those follow your program's rules and are not covered here. The retention periods for the records SOP are on the federal fleet inspection rules page, with section numbers.
Write the second kind first. The rule backed SOPs are usually half written already, because the rule gives you the steps. The shop practice SOPs exist nowhere but in someone's head, and that someone has a retirement date.
How to write an SOP from a veteran's head in an afternoon
Do not hand the veteran a blank template. He will write three lines and go back to work. Do this instead, in the bay, with a phone.
- Pick one job, on one unit class.
Not "brakes". The brake inspection on the refuse units. Narrow enough to finish today.
- Record him doing it, narrating.
Every step out loud, including the ones he thinks are obvious. Especially those. When he does something the manual does not say, ask why, and record the answer. NASA's supervisors' guide notes that clips of three to five minutes "can pass information without overwhelming viewers" (NASA, Knowledge Continuity: A Guide for Supervisors, undated). A whole job may take several clips. That is fine.
- Transcribe and strip to steps.
Someone other than the veteran does this. Number the steps. Cut the story. Keep the numbers, the sequence, and every "because".
- Mark each departure from the book.
Where the SOP differs from the OEM manual, say so in the step, cite the manual page it replaces, and give the reason in one sentence. This is the whole value of the document. Everything else is in the manual already.
- Read it back to him.
Ten minutes. He will correct two steps and add one you missed. Then he initials it. His name stays on the SOP, so the next person knows whose practice it is.
- Supervisor approves, new hire tests.
The foreman signs it. Then the newest technician does the job from the sheet alone. Where he stalls, the SOP is missing a step. Fix it before it is filed.
Six steps, one afternoon, one SOP. Ten afternoons covers the shop practice list above. The interview side of this, questions that get answers, is on how to run knowledge capture interviews with fleet veterans.
The one page SOP skeleton
Copy this. Every field earns its place, and the two at the bottom are the ones that keep it alive.
How to keep shop SOPs current after the unit or the rule changes
An SOP goes stale the day something under it moves. The unit is replaced with a newer model year and the override no longer applies. A bulletin changes the procedure. A rule is amended. If nobody is watching for those events, the SOP quietly becomes wrong, and a wrong SOP with a veteran's name on it is worse than none, because it is trusted.
Tie each SOP to triggers rather than a calendar. The calendar review, once a year, catches what the triggers missed. The triggers catch what matters.
| Trigger | Who acts | What happens to the SOP |
|---|---|---|
| A unit is added or replaced | Foreman | Every SOP listing that unit class is reopened. Overrides re checked on the new unit. |
| A bulletin or recall lands | Whoever receives it, per the bulletin SOP | Affected SOPs get the bulletin cited and the step changed, same week. |
| A rule changes | Fleet manager | Rule backed SOPs re read against the new text. |
| A tech finds the SOP wrong in the bay | That tech, by voice | Flagged the same day. Owner corrects or explains. Version number moves. |
| The source veteran gives notice | Foreman | Every SOP with his name is read back to him before he leaves. Missing ones are written. |
| Annual | SOP owner | Read through. Retire any SOP for a unit class the fleet no longer runs. |
The fourth row is the one that makes the system self correcting. A technician who can flag an SOP in ten seconds, from the bay, will. One who has to find the foreman and fill in a form will just do the job his own way and the SOP ossifies. The knowledge continuity plan is where the review cadence and the SOP owners get written down together.
SOPs a technician can ask for out loud
YardWise holds SOPs as one of four levels of knowledge, the fleet's standing practice, alongside the manufacturer's manuals, what individual technicians know with their name attached, and knowledge tied to a specific unit. A technician asks by push to talk voice and gets a cited answer in under five seconds: the manual page, and the shop's departure from it with the veteran's name and the reason. The SOP and the book it sits on top of come back together.
The write up process above maps onto it directly. The narrated clips go in by voice. The supervisor approval step is built in, so nothing is served as shop practice until the foreman signs it. And the flag from the bay is a voice note, which is what makes the fourth trigger row work. Manuals and bulletins go in as PDFs, scans, or a photo of the page. The how it works page shows the path from clip to answer.
YardWise does not write the SOP or decide what the shop's practice should be. That is the veteran and the foreman. It does not keep the 396.3 records, which stay in the maintenance system. It makes the procedure findable by the person doing the job, which is the only place an SOP was ever going to be useful.
Shop SOP questions, answered short
What is a shop SOP in fleet maintenance?
A short written procedure for a job the shop does the same way every time, including where the shop's way differs from the manufacturer's manual and why. The manual covers the engine. The SOP covers this shop, on these units.
Which SOPs does a fleet shop need?
Rule backed ones for driver inspection report handling, preventive maintenance per unit class, the periodic inspection, brake work, and maintenance records, under 49 CFR Part 396 for motor carriers. Shop practice ones for fault intake, unit specific overrides, parts ordering, road calls, and bulletin handling. Write the shop practice ones first, because they exist nowhere else.
How do you write an SOP from a veteran technician?
Record him doing the job while narrating, in clips of a few minutes. Have someone else transcribe and strip it to numbered steps. Mark every departure from the manual with the page it replaces and the reason. Read it back to him, get the foreman's approval, then have the newest technician do the job from the sheet alone.
How long should an SOP be?
One page. A procedure a technician will not read in the bay only exists for the audit. Put the manual reference on the sheet rather than copying the manual into it.
How often should shop SOPs be reviewed?
On triggers, not just on a calendar. A unit replaced, a bulletin received, a rule changed, a technician flagging it wrong from the bay, or the source veteran giving notice each reopen the SOP. An annual read through catches what the triggers missed.
Where should SOPs live so technicians use them?
Where the technician is standing when he needs one, searchable, with the manual page and the veteran's name attached. A binder in the office is a walk and a search, and most techs will do the job from memory instead.
See an SOP answer a technician by voice, with the veteran's name on it
Bring one procedure your shop does differently from the book. We will show you what it looks like written down, cited, and findable in the bay.
Book a demo