Getting Started with Your Program Review

August

1. Download the current version of the Program Review Template: Instructional or Non-Instructional.
2. Gather the data - Academic Programs
   • Faculty Chairs should request and obtain the ODS program review data set from the Office of Academic Affairs. Other relevant data sources include eLumen, Tableau, SLO and PLO assessment results, and analysis and Annual Unit Plans. CTE programs should also use Perkins/VTEA and Launchboard data.
3. Gather the data - Administrative Units
   • Authoring managers or directors should have all of their key performance indicators and administrative outcome results in hand, which should have been assessed the prior year.

September

1. Attend the Program Review Training in the Fall (you’ll receive an invitation).

September – December

1. The responsible party writes the Program Review document. The data is the foundation. Build the narrative around the story that the data tells.
2. The responsible party should consult with the overseeing administrator early in the process for input about the Program Review.
3. CTE Program Reviews should be presented to their advisory committee for feedback.
4. Input from any other important stakeholders, including department members, is recommended during this process.

Spring Semester

Program Reviews are evaluated and approved during the Spring term through the following process:

1. Submission. The Program Review is submitted to the Program Review Chair (Suzie Ama) at the beginning of Spring semester or at least 7 days prior to a scheduled meeting. (See the link to Meeting Dates on the committee page.) The Program Review Committee evaluates the completeness and appropriateness of the document, using a rubric that is provided to responsible parties during the September training.
2. First Program Review Committee Meeting. During the first review, the Program Review Committee meets with the responsible party to discuss its findings and make recommendations for improvement.
3. Revision. The responsible party makes recommended changes, working with Matt Mann if help is needed with formatting.
4. Resubmission. The responsible party submits revised Program Review to Suzie Ama at least 7 days prior to a scheduled meeting.
5. Second Program Review Committee Meeting. The Program Review Committee meets with the responsible party to verify that changes were made. If so, the Program Review is approved. If not, further recommendations are made, and Steps 4-6 are repeated. Occasionally, a Program Review will be ready for final approval at the first meeting, and Steps 4-6 are not necessary. Usually, 2 meetings are needed for a Program Review to be approved.
6. Academic Senate. If the Program Review pertains to an academic program, the responsible party submits the program review to the Academic Senate, and the proposer presents a summary of key findings to the Academic Senate, which votes to affirm. If the Program Review is not academic, skip this step.
7. College Council. The responsible party submits the Program Review to the college President or Academic Senate President for presentation at the following College Council meeting. College Council votes to approve or not approve.
8. Publishing. After approval from College Council, the responsible party submits the document to Matt Mann for publishing to the college web site.