• Criteria
  • Excluded from the process
  • Changes that can be done administratively
• How to request a project
  • Conditions/Agreement
• Implementation

Criteria

A project is when a course change or changes creates downstream impacts to a significant number of other catalog requisites. Each project must be approved by Data, Academic Planning & Institutional Research (DAPIR) and the Office of the Registrar (RO). Even if the following criteria are met, a project may not be approved. If not approved, the subject owner must submit course proposals to be in alignment with the original course change proposal. If you're unsure if the changes meet this criteria or have further questions, please reach out to us.

• Where the impact is greater than ~>15 courses from the original change proposal
• Where there may be ~>5 courses revised that impact ~>15 courses
• Implementation of governance requested revisions which brings courses into alignment with best practices (DAPIR/RO requested changes)

Excluded from the process

• If removing a course from the requisite means the requisite would no longer have a course enforcing academic preparation.
• If a course is in the final stages of governance review and/or may meet the established deadlines in time to coincide with the instigator proposal.
• If the revisions on the original course change proposal are significant changes and need subject matter expert review/action (the course is not fundamentally the same).

Changes that can be done administratively

Deactivated (discontinued) courses

Catalog number/subject changes

Back-End requisites

Programs

How to request a project

1. A school/college academic planner must email DAPIR/RO (Melissa Schultz and Jess Richards) with a request/notification regarding a course change that has downstream impacts.
2. The RO runs a query to identify the location of the impacted course in requisites. DAPIR runs a query to identify any additional courses that may have proposed changes not yet implemented. The RO adds the list to the Course Project Google Drive (limited access).
3. DAPIR/RO determine whether the request meets the definition of a project and identifies a timeline by when the changes may take effect.
   1. Any course can be removed from the impact list if the administrative update would make significant changes to the meaning of the requisite.
   2. In-progress courses must have a determination made on whether they will be administratively updated or if they need to be shredded to update the requisite. This is subjective and will use a similar logic for when courses are shredded per policy.
4. DAPIR will send a list to schools/colleges that have impacted courses with a note that we will make these changes for which term, and if the subjects want to make additional changes to the requisite that they must submit a separate course proposal. That course proposal may take effect the same term as the administrative proposal.
5. DAPIR communicates back to the original school/college the effective date contingent by receiving the proposal by a certain date determined by the amount of administrative work required. If the proposals do not reach the University Curriculum Committee (UCC) step of workflow, the proposals may be deferred to the next effective date/term.
6. Once the UCC approves the initator course, DAPIR emails the affected schools/colleges after the UCC meeting to notify them the changes have happened and the impacted courses that will have administrative changes based on their current state (at rest or edited).

Conditions/Agreement

• Changes are implemented for a fall term.
• Changes do not require subject matter expert review (ie: removing a discontinued course or a subject change).
• Changes do not alter the meaning/intent of the requisite.
• This is a service that DAPIR/RO provides, and can be discontinued at any time.

Implementation