ELIGIBILITY: A faculty member is to be considered eligible by reason of service for a faculty development leave when he/she has served as a member of the faculty of the university for at least two consecutive years, although preference will be given to faculty with longer periods of service. This service may be as an instructor or as an assistant, associate, or full professor, or an equivalent rank, and must be full-time academic duty but need not include teaching.
PROCEDURAL MECHANISM: The faculty member should communicate his/her intent to submit an application for faculty development leave to the school development leave committee prior to submission of an application. The faculty member should first discuss the proposal with his/her department head. Items to be discussed should be: a) purpose of the proposal; b) benefits of the development leave to the individual, the department, the school, and/or the university; and, c) plans for replacing or covering the applicant's departmental responsibilities. The faculty member should then submit a copy of the proposal to the department chair to review. The faculty member will forward the leave proposal along with his/her department chair's written recommendation and rationale for the approval or disapproval of the proposal and recommendations, if any, to strengthen the proposal to the school committee established to review faculty development leave proposals. The school committee will assess the proposals based on criteria appropriate to their school's mission, consistent with the criteria established by the university.
School Faculty Development Leave Committee. The school committee's written recommendations and rationales for approvals or disapprovals, or other recommendations to strengthen the proposal, shall be forwarded along with the applicant's proposal and the department head's recommendations to the dean of the school for review. The dean shall review the proposal and recommendations, and, as deemed necessary, seek clarification of the proposal, make recommendations to improve the proposal, and/or otherwise consult with the applicant or department head. The dean shall then forward the proposals with his/her written rationales along with the school committee's rationales for recommending approval or disapproval of the proposals to the Executive Vice President for Academic Affairs ("EVPAA"). The EVPAA will forward all proposals and respective recommendations to the University Faculty Development Leave Committee. The Committee will review, evaluate and prioritize the proposals based on the established criteria. The Faculty Development Leave Committee shall then forward its priority scores, written evaluations and any additional recommendations to the EVPAA. A summary of the committee's evaluations and recommendations will be forwarded to the candidates at this time. The EVPAA shall review all relevant information on each proposal; seek clarification, if needed; and, in the exercise of his discretion, make recommendations to strengthen the proposals. The EVPAA shall then approve or disapprove the requests for development leave and inform the dean of the appropriate school.
CRITERIA: Faculty development leave is a privilege earned by the faculty member's record of positive contributions to the educational and research missions of the department, school and university. The following criteria will be used by the University Faculty Development Leave Committee in evaluating and prioritizing the proposals forwarded to the Committee:
FACTORS: Other factors to be considered are:
FORMAT OF THE APPLICATION: The applicant should provide a double-spaced narrative of approximately 1000 words, maximum of four pages, which describes: 1) the goals for the development leave; 2) the activity and time for which the leave is requested; 3) where the work will be done and written evidence of an outside institution's willingness to provide facilities for carrying out his/her proposal; 4) its relevance to the applicant's professional development and the institution; and 5) any proposed arrangements that the applicant has made for the coverage of his/her responsibilities while on leave. A two page biographical sketch in USPHS format should also be provided and applicants are discouraged from submitting reprints.
TIMETABLE: The faculty development leave proposal should be sent to the school's committee by April 1 or November 1 depending on the cycle chosen. (For a January start date, the cycle begins in April. For a proposed July 1 start date, the cycle begins in November.) The dean should receive the proposals May 1 or December 1. The dean will forward the proposals to the EVPAA by June 1 or January 1. The University Faculty Development Leave Committee will evaluate and prioritize the proposals and will then deliver the results to the EVPAA by July 1 or February 1. The applicants and other pertinent individuals will be notified by August 1 or March 1 whether or not the proposal is approved. (See Timetable.)
OTHER STIPULATIONS: If there is any change in an applicant's proposal after the proposal has been approved, the applicant must notify the EVPAA as to those changes. In the EVPAA's discretion, the change may be allowed or the proposal may require a resubmission through the application process.
The precise terms of the development leave should be in writing and should be given to the recipient prior to the commencement of the leave. Recipients assume an implied obligation to return for service of at least the same duration as their development leave.
Each recipient must, upon leave completion, file copies of a report of leave activities with the departmental chair (or equivalent), the dean, and the EVPAA.
Fall (for a July 1 start date) |
Spring (for a January 1 start date) |
|
School FDL Committee |
November 1 |
April 1 |
School Dean |
December 1 |
May 1 |
EVPAA and University FDL Committee |
January 1 |
June 1 |
University Faculty Development Leave Committee begins review |
February 1 |
July 1 |
EVPAA Notifies Dean/Applicant |
March 1 |
August 1 |
Updated 3/98; 08/07; 04/08
| HOOP Home Page | Appendix C Table of Contents | Policy 4.21