13.10.2013 Views

Faculty Contract - Ferris State University

Faculty Contract - Ferris State University

Faculty Contract - Ferris State University

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

1<br />

2<br />

3<br />

4<br />

5<br />

6<br />

7<br />

8<br />

9<br />

10<br />

11<br />

12<br />

13<br />

14<br />

15<br />

16<br />

17<br />

18<br />

19<br />

20<br />

21<br />

22<br />

23<br />

24<br />

25<br />

26<br />

27<br />

28<br />

29<br />

30<br />

31<br />

32<br />

33<br />

34<br />

35<br />

36<br />

37<br />

38<br />

39<br />

B. Step 2 - Written Level<br />

1. In the event the grievance is not resolved in step 1, the grievance shall<br />

be written and signed by the grievant( s) and by the FF A on a standard Employer/FF A<br />

grievance form and presented to the administrator in step 1 within ten (l 0) working days<br />

of the discussion at step I, and shall set forth the specific acts that constitute the basis for<br />

the grievance and identify the specific language of the contract that is claimed to have been<br />

violated by those specific acts.<br />

2. The administrator shall communicate a decision in writing to the<br />

grievant(s) as promptly as possible, but no later than fifteen (15) working days after the<br />

grievance has been received.<br />

3. Any settlement, withdrawal, or other disposition of a grievance at this<br />

step is not a binding precedent in the disposition of similar grievances.<br />

c. Step 3<br />

In the event the grievance is not resolved at step 2, the FFA and grievant(s) shall<br />

present it to the administrator to whom the administrator in step 2 reports within ten (1 0)<br />

working days after the step 2 decision. The written grievance must be signed by the<br />

aggrieved member and the FF A and, in addition to the required information outlined in step<br />

2 above, shall include the reasons the proposed resolution of the grievance at step 2 is not<br />

satisfactory. The administrator shall, within ten (10) working days, meet with the grievant(s)<br />

and, if the grievant(s) wish (cs), with a representative of the FFA. The decision at this step<br />

shall be written and communicated to all persons concerned as promptly as possible, but not<br />

later than ten (1 0) working days after the meeting. If the grievance is initiated at step 3, the<br />

grievance shall be presented to the administrator to whom the administrator in step 2 reports<br />

within twenty (20) working days of when the grievance might reasonably be known to exist.<br />

D. Step 4 - provost/vice president for Academic Affairs Level<br />

1. In the event the grievance is not resolved at step 3, the FFA and<br />

grievant(s) may advance the grievance to the provost/vice president for Academic Affairs<br />

within ten (10) working days after the decision in step 3. This written submission must be<br />

signed by the grievant( s) and the FF A and shall include, in addition to the initial grievance,<br />

any amendments or appendices thereto, as required by steps 2 and 3 and the reason( s) the<br />

FFA and grievant(s) eonsider the disposition at step 3 to be unsatisfactory. If the grievance<br />

is initiated at step 4, the grievance shall be presented to the provost/vice president for<br />

Academic Affairs within twenty (20) working days of when the grievance might reasonably<br />

be known to exist.<br />

2. Following this submission, no more than ten (I 0) working days shall<br />

elapse before a meeting is held between a representative of the FF A and the provost/vice<br />

president for Academic Affairs or designee. The provost/vice president for Academic<br />

Affairs or designee shall answer the grievance, in writing, within ten (1 0) working days<br />

from the date of the meeting at which the grievance was discussed.<br />

39

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

Saved successfully!

Ooh no, something went wrong!