From the bus barn this month, I will be touching on the importance of proper documentation with regard to the basic skills performance of the student bus operator on the training bus. Going hand in hand with a standardized curriculum should be a standardized way of documenting student performance. When putting pen to paper, be sure an instructor’s documentation can be clearly understood by others who may need to refer back to it at a future date. Proper documentation is critical in the case of a student operator who may attempt to dispute a dismissal and may want to protest and pursue some type of legal options to challenge an instructor’s final evaluation.
Let's take a look at the “7-10 day front loaded” skill development driving program, which in my opinion is the most effective, revealing, and best manner in which to train and produce world class operators. For the student, “Training Bus-Day One” should be a “Familiarization Day.” The student will be familiarized with specific tasks that should be introduced and demonstrated by the instructor. Because the student is simply being “Familiarized,” the overall evaluation options of “Satisfactory” or “Unsatisfactory” should not yet apply. A “Yes” box is sufficient. Simply put, your Day One documentation should reflect that “Yes,” the student was “Familiarized.” Early on, and after Day One, during the “initial instructional training” phase of training bus basic skill development, the “Satisfactory” or “Unsatisfactory” check-off options will become applicable to the student’s daily performance.
Every “Unsatisfactory” check-off should be accompanied with a brief statement as to what occurred behind the wheel that justified the “Unsatisfactory” result. As the training moves on to the “Show Me” phase of training, which should occur during the final days of training, again any “Unsatisfactory” check-off should be supported with documentation, utilizing the words “student failed to” properly execute the action that was required.
RELATED: "Operator training: Mastering right turns"
Example: Student “failed to” properly perform the interior and exterior pre-trip inspection. Another example, such as following too closely behind another vehicle, student ‘failed to’ provide sufficient following distance.
Refrain from “sugar coated” documentation, which is the case when using “would have, could have and should have” in situations when a specific maneuver or skill was not performed correctly.
Example: In the case of a student operator who is proceeding too closely alongside a parked vehicle, stating the student “could have” positioned the bus further away from parked vehicle is weak documentation.
Instead, use stronger, more direct documentation that would read: Student “failed to” provide sufficient clearance between bus and parked vehicle right of bus.
Words like “excessive,” “insufficient,” “improper” and “failed to” should be standard training bus vocabulary utilized by the instructional staff. Needless to say, if any of these words appear on the final day of training, the “Qualified” box should not contain a check mark. If it does, this creates a documented contradiction.
In the case of a student who has been rated an “unsatisfactory – not qualified”, the final day comment should read, “According to the Standards of the Training Department of this Agency, student is “not qualified and not recommended” to advance into Passenger Service.” At this point, with all available training days exhausted, resignation or termination become the only two options available for the student. Having a set of properly documented tasking sheets available on file will justify the dismissal or resignation and becomes the glue that keeps a dismissal intact.
In closing, I recommend that all daily tasking sheets — and not just the final day tasking sheet — be completed in triplicate and signed by both the instructor and student. The master copy will become part of the student folder, the second copy given to the student, and the final copy is retained by the instructor.
A brief ‘one-on-one” verbal summary with each student — at the end of each training day — allows the instructor to inform them which skills still require further improvement. This “wrap up” should become part of the daily routine.
Remember: Instructors need to point out any unsatisfactory action at the precise moment it occurs to minimize any surprise reaction that a student may demonstrate during the verbal summary and review of the day’s tasking sheet. Instructors should quickly document exactly what occurred whenever an unsatisfactory action is observed. This will allow the proper detail to be recorded while it's still fresh in their minds, such as what happened, where it happened and at what time of day. This will preserve a mental snapshot for the instructor should they need to re-read their statement at a later date, and also, ensure that daily evaluations are accurate and complete — containing all that occurred during “behind the wheel” training activities. No exceptions.
So...... when it comes to documentation, “If it ain't in writing, it ain't!”
What safety issues would you like Louie to discuss? Send suggestions to [email protected] and maybe he will take up the subject in a future Safety Corner.
In case you missed it...
Read our METRO blog, "Innovative transit agency helps clear the air in Dallas-Fort Worth."
The RMS occurred last month in Albany, N.Y. and it was a truly remarkable learning experience for those in attendance. The RMS serves as a one-of-a-kind event that brings together transit risk management professionals from all across the country to focus on key topics related to safety, risk management, planning and prevention.
I recently attended, and had the opportunity to be part of a panel of speakers, at the NYC MTA Bus Safety Symposium. A variety of topics were discussed regarding bus and pedestrian safety issues. What was obvious is we all have a common goal to provide the safest transit systems possible, in spite of the possibility of increasing bus/pedestrian and bus/cyclist collisions.
I have had it with the never-ending meeting of the minds on the predominant causes of left-turn bus-pedestrian collisions. This whole issue is getting obscured with presentations that slice and dice every possible cause of these incidents into a collection of symbols, numbers and formulas. Please stop.
Statistics show that for many people, sleep can be a matter of life or death. This may sound overly dramatic, but let’s consider that in 2005 the NHTSA conservatively estimated that drowsy driving was responsible for at least 100,000 automobile crashes, 71,000 injuries, and 1,550 fatalities annually.¹ More recently, the NHSTA estimated at least 846 people died in 2014 due to the effects of drowsy driving.
Nowadays, there’s an app for everything. Very few of those apps can turn an everyday transit rider into a hero who summons help for a person in distress. A routine ride on your transit system can be suddenly disrupted if you witness an assault, a crime in progress or a medical emergency. That is why apps designed for public safety must take all imaginable scenarios into consideration.