Policy 3.13


Advisory Committees


Part 1. Policy Statement

Each major technical program of study is required by Minnesota State Colleges and Universities to have an advisory committee. Clusters of programs that are cored or otherwise related may choose to have joint advisory committees.

Program/cluster advisory committees MUST meet at least twice each year. The agenda is determined by program needs for discussion.

An advising committee is a group of community members (knowledgeable in the technical field and drawn from both small and large companies, management and labor, other educational institutions, both genders, and people of different ethnic backgrounds) who work collaboratively with technical program faculty to plan, evaluate, and improve the technical program.

Part 2. Purpose

The Advisory Committee provides ongoing evaluation, consultation, research, and recommendations on the technical program curriculum to keep it current with the knowledge, skills, attitudes and values collaboratively identified by representatives of education and the industry partnership. The Advisory Committee functions as a partner in the collegiate structure and process for planning and continuous improvement, and articulates short and long term goals and objectives for the program.

The Advisory Committee focuses on curriculum content and resources; teaching methodology and curriculum development remains with the college faculty. Members of the Advisory Committee provide history, vision, and an awareness of workplace current practice and future trends and prevailing social and economic issues.

Part 3. Responsibility

The Advisory Committee meets a minimum of twice each academic year with technical program faculty and other college members; members participate in the work of the committee according to established techniques for group problem solving, decision making, and short and long term planning.

The committee's work must align with the College's established mission, policies and procedures, and strategic plan.

Date of Adoption: 7/1/1999

Date of Implementation (if different from from adoption date):

Date of Last Review: 7/1/1999

Date and Subject of Revisions: