08.04.2015 Views

standard operating procedure college station fire department

standard operating procedure college station fire department

standard operating procedure college station fire department

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SUBJECT: Disciplinary Procedures SOP: 200.2.10<br />

CATEGORY: Administrative Procedure PAGE: 2 of 5<br />

2. The Station Officer will complete the Record of Employee Performance Conference (oral and written<br />

warnings) form, counseling the employee concerning the problem or unacceptable behavior. The officer<br />

will give suggestions for improvement and explain the consequences of continued unacceptable behavior or<br />

job performance. This record shall be signed by both the employee and supervisor. Written warnings will<br />

become part of the employee’s permanent personnel file located in the Human Resource Department.<br />

3. The employee has the right to appeal the discipline. The employee has three working days to request a<br />

hearing. If a hearing request is made, the Battalion Chief will arrange the hearing date and time with the<br />

Assistant Fire Chief. The Assistant Fire Chief will review all pertinent information in the appeal and issue a<br />

decision. The employee may then request to appeal the decision to the Fire Chief using the guidelines that<br />

are found in the City Policy Manual.<br />

4. The decision of the Fire Chief shall be final.<br />

5. No appeal shall be permitted beyond the appeal to the Department Head for minor disciplinary action.<br />

6. The employee may place a letter of rebuttal in their file if they do not agree with the ruling of the Fire<br />

Chief.<br />

C. SUSPENSION WITHOUT PAY OR RECLASSIFICATION WITH REDUCTION OF PAY: Suspension<br />

without pay or reclassification with reduction of pay serves as a third step in the disciplinary process.<br />

(Intermediate action) This documentation will be written by the Station Officer and followed through by the<br />

Battalion Chief. The Battalion Chief will schedule a conference with the Assistant Fire Chief to review the<br />

disciplinary action before any final action is taken.<br />

1. The Station Officer will investigate the following; who was involved, witnesses involved, circumstances<br />

surrounding the incident, when it happened, and how the situation can be avoided in the future.<br />

2. The Station Officer will complete the Record of Employee Performance Conference (suspension or<br />

reclassification) form, counseling the employee concerning the problem or unacceptable behavior. The<br />

officer will give suggestions for improvement, explaining the actions that will be taken, future<br />

consequences, and the employee's right of appeal. This record shall be signed by both the employee and<br />

supervisor. This record will become part of the employee’s permanent personnel file located in the Human<br />

Resource Department.<br />

3. The employee may appeal the decision of the Fire Chief within five working days to the Review Board as<br />

outlined in the "The City of College Station Policy and Procedures Manual, Disciplinary and Termination<br />

Policy", approved by city council.<br />

For the purposes of clarification working days will be considered Monday through Friday.<br />

D. TEMPORARY SUSPENSION WITH PAY: An employee may be suspended with pay pending<br />

investigation of misconduct, as set forth in the formal <strong>procedure</strong>s for disciplinary hearings. Misconduct<br />

includes, but not limited too: Theft, Gross insubordination, Intoxication on duty, Failure to follow direct<br />

orders at the scene of an emergency, or Fighting in the workplace. The Battalion Chief can asses the<br />

suspension immediately, but must notify the Assistant Fire Chief immediately of any suspensions.<br />

rev:7/97;3/99;re#’d 11/02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!