Traffic violation enforcement is one of the many routine tasks performed by officers, but for violators it frequently is an emotionally traumatic experience. In many cases, this is the only contact that a person has with our department. Officers should be aware of these conditions and should strive to make each contact educational and to leave the violator with the impression that the officer has performed a necessary task in a professional manner.

Once the officer has stopped the violator and approached, the officer will:

  •  Be alert at all times for the unexpected, but not be obviously apprehensive.
  • Be absolutely certain that the observations of the traffic violation were accurate -- without reservation.
  • Be prepared for the contact by having the necessary equipment and forms, if they are to be used, immediately available.
  • Decide on appropriate enforcement action based upon the violator's driving behavior, not attitude. In most cases, it is advisable to have the form of enforcement action decided prior to the initial contact with the violator.
  • Present a professional image in language.
  • Inform the violator what traffic law s/he has violated and the intended enforcement action; the violator should not be kept in suspense.
  • Ask for the violator's driver license.
  • Obtain another document of identification if the driver has no driver's license.
  • Allow the driver to discuss the violation.
  • Complete the forms required for the enforcement action taken or exercise a verbal warning, if this is the decision.
  • If a citation is issued, direct her/his attention to the information and options on the reverse side of the citation. 
  • Be alert to any emotional stress exhibited by the driver. If stress is present, the instructions may have to be repeated or the violator may need to calm down before resuming driving.
  • Return the violators drivers license and a copy of the citation and business card.
  • Assist the violator in safely reentering the traffic flow.
  • Do not follow the violator.

Revised July 1, 2011

Last Edited: March 21, 2017