Be careful when updating your repair procedures. What often happens over time is a given procedure gets so bloated it becomes useless in the field.
Suppose there was a problem during a repair. So the procedure gets a note added to it. The next time, it’s a different problem so another new note gets added. And so on, until the procedure seems to collapse under its own weight.
Distinguish between training deficiencies and procedural deficiencies. Make up for training deficiencies with better training, not longer procedures. Use the procedure to delineate the major steps, not to explain how to do them.
But what about situations where the repair is complex and involves specific steps that must be done in an exact sequence? Create an appendix for the procedure, and provide those steps in a simple checklist.
If the procedure is loaded with detail telling techs what they already know, they’ll skip through it and miss the important information that justified writing the procedure in the first place.
