1. Assessment Liaisons Orientation Meeting October 8

2. Assessment Initiative Why? – Assessment leads to continuous improvement – Provides measure of accountability Why now? – SACS standards Partial compliance on a number of measures – BOG Academic Learning Compacts – New leadership – Growth and strategic planning

3. Purpose of the Assessment Initiative To integrate planning, budgeting, assessment, accountability – Resulting in continuous improvement To bring us into full compliance with SACS To ensure we comply with BOG mandates

4. Scope of the Assessment Initiative Involves all organizational units of the university represented in our organization chart Covers functions and services of each unit Covers each academic program – Includes development of ALC’s Includes general education (and QEP indirectly)

5. Role and Responsibilities LRPIEC – Executive body Develops strategic plan Makes recommendations to executive group on priorities Monitor progress –Oversee plan annual renewal –Approves assessment plans –Reviews annual reports – Co-chaired by Provost and VP for Admin Services – PIP and AA staff LRPIEC

6. Deans Council and Administrative Services Directors Review assessment plans Suggest modifications as necessary

7. Assessment Liaison Interface with LRPIEC, PIP, and as appropriate – With admin units – College College assessment committee(s) –COB curriculum teams –CAS, program leadership –CHP, A team –COE, dean’s leadership council –CPS, division reps

8. Assessment Liaison Duties Coordinate development of the assessment plan Communicate feedback on review of the assessment plan Identify who needs training/assistance re assessment Ensure assessment plan progress is included in annual reports

9. College Assessment Committees Review development of college assessment plan Coordinate its implementation Report on its progress

10. Timelines SACS action plans called for assessment plans by the end of November – Need to accomplish as much as possible Review of plans by deans council, admin servs dirs, PIP, LRPIEC – January-March 2005 Implementation after approval