Instructions for Curricular Changes

  • Submitters design the curricular changes they intend. The academic unit initiating change(s) in its own course(s), major(s)/minor(s), or other academic program(s), normally bears responsibility for leading the process and overseeing the application-package.
  • Submitters consult with all parties potentially interested in their curricular changes: they inform, they collaborate, and they secure consent in principle.
  • Submitters download application-forms their designs need from the CAS-AC website; they prepare all forms and supplementary documents the application-package will require.
  • Submitters consolidate their proposed changes onto a set of before-and-after grids, one for each major and one for each minor that will be affected by changes proposed within the application-package. They consult their own academic unit's records, the Academic Requirement Outlines posted in LOCUS, colleagues in their collaborating stakeholder-units, and the current academic year's records in the CAS-AC DocFinity Platform for any changes recently approved but not yet coded or effective in LOCUS, so as to ensure that the information they provide in the "Current Major/Minor" column is the most recent approved for the major or minor in question. The "Proposed Changes" they outline should take off from the most recently approved form of the major or minor, as their point of departure.
  • Submitters proofread, double-check all information, resolve all inconsistencies between documents, and correct all errors.
  • The designated official Submitter logs in to the CAS-AC DocFinity Platform, double-clicks on "CAS_AC_SummaryMemo" in the Forms panel, and fills out a Summary Memo for the application-package.
    • The Unique ID generated by the Summary Memo will hold the application-package together in DocFinity, so that pertinent documents can be located and consulted.
    • The Table of Contents for the application-package that the submitter provides will enable stakeholders and reviewers to identify specific documents needing their attention, and to navigate the application-package efficiently.
    • The information the submitter provides about stakeholder-units and the type(s) of application contained within the package will enable DocFinity to route the application-package to the appropriate co-signatories: their approval is needed before the application-package can be reviewed.
  • When the submitter, having completed the Summary Memo, clicks the "submit" button, DocFinity will send the submitter an automated e-mail message confirming the Unique ID for the application-package.
  • The submitter now uploads into DocFinity all component application-documents, supplementary documents for each application, and before-and-after grids showing the full set of consequences intended for each major and for each minor that will be affected, and indexes every uploaded document with the Unique ID for the application-package and all other pertinent metadata.
  • After the Summary Memo is completed and all other documents in the application-package have been uploaded and indexed, the submitter goes to the Jobs Queue in the DocFinity Platform, checks the tasks in the task-menu, then checks the box "is the Submission Complete?", selects "Submission Complete," and signs off with the "Complete Job" icon in the toolbar. DocFinity will then send the application-package to the departmental chairperson or interdisciplinary program-director and to the co-signatory(ies, if any) identified in the Summary Memo's routing-information.
  • The departmental chairperson or interdisciplinary program-director and the co-signatory(ies) also use the Jobs Queue, Submission Complete, and Complete Job icon to sign off their consent to the application-package insofar as it concerns their academic units. Their approval will be recorded in the Diary of the Summary Memo. Approval of all parties is required before the Academic Council proceeds with its review.
  • Members of the College's Academic Council can find the application-package in their Jobs Queues after all the parties to the application-packge have recorded their approval. Ordinarily the most systematic review will be carried out first by at least one member of the Curriculum Committee, but depending on the nature of the application-package and its needs the Associate Dean for Academic Affairs, other members of the Council, the College's Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant may also check in.
    • All members of the Academic Council should familiarize themselves with all application-packages slated for the Council's review that month, in preparation for the monthly meeting of the Council. The Council's schedule is posted at the CAS-AC website.
    • Ideally, all questions about an application-package or any of its elements can be raised in advance of the monthly meeting, and any problems resolved. Reviewers should record their queries or corrections in the Diary of the document concerned, and follow up by e-mailing the submitter. The submitter can deliver explanations, discuss points of contention, or make changes, as appropriate (edit the Summary Memo eForm in DocFinity, or revise other documents outside DocFinity and upload using the Replace icon; in either case, also please also add a note to the Diary of the document in question confirming that the reviewer's concern has been addressed).
  • At the monthly meeting the Curriculum Committee makes its recommendations concerning the application-package. Submitters should always consider themselves invited to the meeting so that they can address questions and recommendations the Curriculum Committee or any other members raise in discussion. Unless the submitters withdraw applications, normally the Council votes on all proposals submitted for the month. The Council may, or may not, with the submitters' consent choose to make its approval conditional on specified amendments.
  • Following the monthly meeting, submitters have a brief period to complete any changes in the application-package requested by the Council conditioning its approval, or any other cleanup.
  • After the cleanup period, the Chairperson of the Council records the Council's approval in DocFinity.
  • After the Council's approval is recorded, the Dean's approval is recorded and approved changes are sent forward to the next reviewing body indicated in the Provost's Office's Chart of Approvals: changes involving major(s)/minor(s) go to the Board of Undergraduate Studies first if they involve more than one School within Loyola, or they go straight to the Provost's Office if the College alone is concerned; changes involving course-programming are sent to Registration & Records for processing by the effective date.
  • The Provost's Office sends submitters notification when the Provost has approved changes involving major(s)/minor(s) and other academic programs. Once this approval has been announced, program-changes too are sent to Registration & Records for processing by the effective date.
  • For permanent changes in coding of courses or programs, the academic unit (department or interdisciplinary program) initiating a change bears the responsibility to initiate the paperwork so as to effect that change.
    • It is helpful if the person who fills out and submits the Summary Memo can readily address any questions about the changes proposed, since the submitter’s name will be associated with the application-package and that person’s UVID will be built into the application-package’s automatically-generated Unique ID.
    • If the submitter is not the Chairperson or Program Director of the proposal's home-unit, the Chairperson/Program Director should be named as "Proposer (if other)" because that person gives authority for the academic unit submitting the application.
  • The submitter should identify all parties concerned in the changes proposed (e.g., cross-listing departments and tagging interdisciplinary programs in a course, or participating units in a cross-disciplinary major or minor), so that DocFinity may collect their approvals. Stakeholders’ approval will be recorded in the Diary Entries of the Summary Memo. The approvals verify the parties understand and consent to the changes proposed. A complete set of approvals must be received before the application can be considered by the Academic Council.
  • If the proposing unit’s changes provoke additional changes in a second academic unit’s programs, the second unit should submit the needed additional applications, under its own authority but together with the proposing unit’s package (for example, if the fictional Department of Forestry re-designs TREE 355, Environmental Justice, in such a way that the Department of Social Theory determines it would be suitable as an option in the Discrimination & Remedies requirement of the SOTH-BA, the Department of Social Theory should sign onto the Department of Forestry’s change and submit its own Change of Major application; using the same Unique ID as the Department of Forestry's application-package will hold the whole package together).
  • Application-packages must be submitted and approved in the CAS-AC DocFinity Platform with sufficient lead-time before the monthly meeting to allow
    • the Curriculum Committee to vet the application-packages thoroughly, so as to formulate the Committee's recommendations;
    • all members of the Academic Council to familiarize themselves with the application-packages sufficiently to consult with the bodies they represent and prepare to discuss and vote on the proposals at the monthly meeting;
    • submitters to address any questions or concerns raised by reviewers and to correct all documents in their application-packages, so that the Council's discussion and vote relate to finished products, and minimal cleanup will be required before approved applications can be moved forward for processing or further approval.
  • No application-package shall be vetted by the Curriculum Committee or reviewed or voted on by the Academic Council as a whole, unless the Chairperson/Program Director of the academic home-unit submitting the application(s) in question, shall have recorded approval of the submission in the CAS-AC DocFinity Platform no later than the submission-deadline for the month. Successfully-recorded approval shall appear, time-stamped, in the Diary of the Summary Memo for the application-package. In order to record approval, the Chairperson/Program Director
    • logs in to the CAS-AC DocFinity Platform;
    • either searches for the application-package by Unique ID using the Search panel or double-clicks on the appropriate queue in the Job Views panel and then "checks out" the appropriate Job;
    • reviews individual documents by clicking each document's check-box in the Search Results panel and then "views" from the toolbar;
    • personally reviews all documents in the package that pertain to the academic home-unit;
    • ensures that any potential questions, concerns, or problems in the application-package are resolved and all relevant documents corrected before the application-package proceeds any farther:
      • edits the Summary Memo eForm directly in DocFinity: clicks "edit" in the toolbar when the Summary Memo is open, "save" to save changes, and "close" to exit the edited eForm;
      • edits other documents outside DocFinity: downloads individual documents from DocFinity by the "download" icon in the Search panel's toolbar, or works from up-to-date file copies; in either case, re-uploads the edited documents using the Replace icon;
      • ensures that changes are carried through all pertinent documents so that the application-package remains consistent (for example, any changes made in a course-application must also be reflected in the course's Course Inventory Form and in all other documents where the course is referred to);
    • on completing review and determining the academic home-unit's mission will be advanced by the package's being approved,
      • exits and closes up any individual documents that are open;
      • if not already in the Jobs panels, goes to the Jobs panels and "checks out" the Job under consideration;
      • in the Tasks panel, checks the box "Is the Submission Complete?" and replies by selecting "Submission Complete," then checks the box for approval and replies by selecting "approved";
      • signs out of the Tasks panel by clicking the "Complete Job" icon in the toolbar: this step is vital for advancing the application-package.
    • Application-packages approved by the submitting home-unit's Chairperson/Program Director later than one month's aubmission-deadline may be reviewed in the following month.
    • If late recording of the submitting home-unit's approval causes the application-package to miss processing deadlines, it is the submitters' responsibility.
    • Because errors, inconsistencies, and unclarities need correction but correction takes time, submitters are advised
      • to design the curricular changes they intend carefully, with due attention to immediate and remote consequences;
      • to consult with all parties potentially interested in the proposed changes or affected by them, to address their concerns, and to secure their approval in principle in advance of submitting;
      • to proofread all documents rigorously.
    • It is preferable for submitters to submit application-packages, and for the submitters' Chairperson/Program Director to record approval on behalf of the academic home-unit, in advance of the submission-deadline.
  • No applications within an application-package shall be voted on by the Academic Council as a whole or shall receive the Council's approval if voted on by mistake, unless all co-signatory stakeholders partnering in the application shall have recorded approval of the application in the CAS-AC DocFinity Platform no later than the day of the monthly meeting. Successfully-recorded approval shall appear, time-stamped, in the Diary of the Summary Memo for the application-package. In order to record approval, the Chairperson/Program Director of each second unit partnering in the application
    • logs in to the CAS-AC DocFinity Platform;
    • either searches for the application-package by Unique ID using the Search panel or double-clicks on the appropriate queue in the Job Views panel and then "checks out" the appropriate Job;
    • reviews individual documents by clicking each document's check-box in the Search Results panel and then "views" from the toolbar;
    • personally reviews all documents in the package that pertain to the partnering second-unit;
    • ensures that any potential questions, concerns, or problems in the application-package are resolved and all relevant documents corrected before the application-package proceeds any farther:
      • makes a note of each question or concern in the Diary of the document(s) in question (opening the Diary by clicking the "view diary" icon in the toolbar of the Search Results panel where the individual document is selected, clicking the "add" icon in the toolbar of the opened Diary, writing the note in the blank text-box that opens, and clicking "save" in the toolbar);
      • e-mails the Submitter or other person connected with the application-package who would be able to address the concern, outlining it and identifying the document(s) to which that person should return so as to address it;
      • asks to be notified when the concern is addressed and the document(s) are updated;
      • when the document(s) are updated, completes the review;
    • on completing review and determining the partnering second-unit's mission will be advanced by the package's being approved,
      • exits and closes up any individual documents that are open;
      • if not already in the Jobs panels, goes to the Jobs panels and "checks out" the Job under consideration;
      • in the Tasks panel, checks the box "Is the Submission Complete?" and replies by selecting "Submission Complete," then checks the box for approval and replies by selecting "approved";
      • signs out of the Tasks panel by clicking the "Complete Job" icon in the toolbar: this step is vital for advancing the application-package.
    • The interval between the application's submission and the monthly meeting, as a cutoff for co-signatory approvals, allows for inclusion of appropriate stakeholders by recommendation of the Curriculum Committee or other reviewers during the Academic Council's review-process; but no application can go forward if it has not received approval by all its stakeholders.
    • It shall be the responsibility of the Curriculum Committee, as its Chairperson shall delegate, to double-check the application-package for outstanding approvals on the day of the monthly meeting, and to withhold the Committee's recommendation to approve from any applications still lacking their full sets of approvals.
    • The Council may determine that applications lacking approval of certain co-signatories can be voted on with the deletion of the non-approved partnership if it is secondary rather than integral to the application (e.g., a New Course proposed for cross-listing may go forward without an unapproved cross-listing, but a New interdisciplinary Major/Minor may not go forward without the approval of all its participating academic units). If such a determination is made, the submitters may accept such a deletion as a friendly amendment and, if the Council votes to approve the amended application, the submitters must undertake to amend all pertinent documents during the cleanup period.
    • It is preferable for submitters to submit application-packages only after securing approval in principle from all partnering stakeholders in advance, and for the stakeholders' Chairpersons/Program Directors to record approval on behalf of the academic second-units, in advance of the monthly meeting.
  • Curricular changes that will necessitate new or changed programming in a major/minor must be approved by the Academic Council no later than the December meeting of one academic year, in order to be on-track for effectiveness the following Fall term. Please recognize that this timetable limits the "effective date" that can be requested for any proposed curricular change.
  • New or changed course programming must be approved by the Academic Council no later than the February meeting of one academic year, in order to be on-track for effectiveness the following Fall term, or no later than the March meeting of one academic year, in order to be on-track for effectiveness in the Spring term of the following academic year. Please recognize that this timetable limits the "effective date" that can be requested for any proposed curricular change.

Either cross-listing or tagging may arise when a course serves a major or a minor outside its home unit.

  • “Tagging” means the name of the Interdisciplinary Program in question appears in LOCUS’s display of Course Attributes for a course belonging to a different home unit.
  • The tag permits students to search in the Class Schedule for classes that may serve a given interdisciplinary program’s major or minor, regardless of the classes’ Subject Area Codes and home units.
  • Although the tag should not appear on courses not included in the major or minor, applying the tag and including the course are two separate operations by R&R. The tag is part of course-coding in the Course Catalog; inclusion of a course in a major or minor is a function of the Academic Requirements Report.
  • “Cross-listing” means the same course, in terms of its defining content and objectives, is designated in LOCUS by course numbers in more than one Subject Area Code belonging to separate academic units.
  • Courses are cross-listed most often when they might be taught by members of faculty holding appointments to different academic units (for example, our fictional course Peaches is cross-listed as both TREE 134 in the Department of Forestry and FZZZ 134 in the Department of Things with Fuzz): a particular instructor’s home unit schedules the class under its own Subject Area Code. Academic Requirements Reports for both units’ major(s) and minor(s) must be set up so as to ensure that either course-number will be read as cross-crediting and serving students in both programs.
  • Courses required by a major or minor of an interdisciplinary program may need to be cross-listed with departmental courses, but usually tagging suffices.
  • Whereas a permanent tag always appears on a course, cross-listed courses appear together in LOCUS only if they are scheduled together as Combined Sections.
  • It is advantageous to cross-list courses in departmental Subject Area Codes when members of the faculty of either department can be expected to teach substantially the same class to students pursuing major(s) or minor(s) in either academic field (thus for example, our fictional Department of Forestry cross-lists TREE 134, Peaches, with FZZZ 134, Peaches, in the Department of Things with Fuzz). Typically the section of the course in the Subject Area of the home-department of the faculty member teaching the course is used as the enrollment section. Provided the equivalency of the cross-listed courses is correctly cross-credited in the applicable major(s)/minor(s), all students will receive the appropriate credit, whether or not the other cross-listed/equivalent course also appears in the Class Schedule in a Combined Section.
  • If there is no expectation members of both departments will teach the course, a second unit may include non-departmental courses in its own departmental majors and minors without cross-listing: the Department of Forestry requires its majors to take FZZZ 201, Bees, from the Department of Things with Fuzz, but never teaches an equivalent course.
  • Do recall for purposes of visibility, cross-listed courses appear together in LOCUS only if they are scheduled together as Combined Sections, regardless of whether or not they are also cross-credited.
  • Preliminary steps:
    • Design the curricular changes intended. Consult all parties potentially interested. Collaborate.
    • Download from the CAS-AC website blanks of all application-forms needed. Fill them out, following Instructions for Curricular Changes (this page).
    • Prepare all supplementary documents each application will require.
    • Consolidate the proposed changes onto a set of before-and-after grids, one for each major and one for each minor that will be affected by changes proposed within the application-package. Ensure all information in the "current major/minor" column accurately represents the most recently approved form of the major/minor, and that the information in the "proposed changes" column accurately describes all consequences for that major/minor, in terms of LOCUS's programming for Academic Requirements Reports.
  • After the elements of the application-package have thus been prepared and drafted, draft the Summary Memo:
    • Log in to the CAS-AC DocFinity Platform.
    • In the Forms panel, double-click on "CAS_AC_SummaryMemo": this action will open up a new Summary Memo autopopulated with the submitter's UVID, the date the Summary Memo is opened, and a Unique ID in the form UVIDmmddyyyy (e.g., mlettie05162017; in the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1).
    • The header-information of the Summary Memo completes identification of the submitting unit. If the Submitter is not the Chairperson/Program Director of the academic unit making the application, please name the Chairperson/Program Director as the "Proposer (if other)" in addition to the Submitter: the Chairperson/Program Director's authority for the submitting unit will be required to advance the application-package to DocFinity's distribution-queues and Academic Council's consideration.
    • The Unique ID generated by the Summary Memo will hold the application-package together in DocFinity, so that pertinent documents can be located and consulted.
    • The Table of Contents for the application-package that the submitter provides will enable stakeholders and reviewers to identify specific documents needing their attention, and to navigate the application-package efficiently. (See item on this page for a fictional example of the format.)
    • The information the submitter provides about stakeholder-units and the type(s) of application contained within the package will enable DocFinity to route the application-package to the appropriate co-signatories: their approval is needed before the application-package can be reviewed.
    • Proofread all elements of the Summary Memo to make sure they are correct, so that no errors enter the system and achieve any potential of confusing others.
  • Submitting the Summary Memo, completing the application-package, and advancing the application-package for needed approvals:
    • After completing and proofreading the Summary Memo, scroll down and click the "Submit" button. DocFinity will send the submitter an automated e-mail message confirming the Unique ID for the application-package.
    • Upload into DocFinity all the application-documents encompassed in the application-package, all the supplementary documents for each application, and the set of before-and-after grids, one for each major and one for each minor that will be affected by changes proposed within the application-package, showing how all changes in the application-package pertaining to that major/minor will fit in to existing or requested new programming.
    • Index all applications, supplementary documents, and grids with the Unique ID of the application-package, and with the additional metadata appropriate to each item.
    • Check out the application-package from the Job Queue. In the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete." Sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar. This step makes the application-package accessible to other viewers.
    • As DocFinity routes the application-package to the Chairperson/Program Director and any co-signatories whose authority the component application(s) severally need(s), they too should log in to DocFinity, open the Job Queue, and check out the application-package. They will be able to view individual documents from the Search panel. The Table of Contents in the Summary Memo whill show which documents require their attention. When they have reviewed pertinent documents, and worked with the submitting unit so as to address any concerns, they too use the Tasks panel and "Submission Complete" to indicate their approval. Signing out of the Tasks panel by clicking on the "Complete Job" icon will record their approval in the Diary of the Summary Memo. (If this step is omitted, the package will not advance.)
  • Once all approvals have been secured and recorded in the Diary of the Summary Memo, DocFinity will advance the application to job-queues of members of the College's Academic Council, and the Council's review can commence.

  

This sample Table of Contents imagines the fictional Department of Forestry is proposing a package of curicular changes relating to its major in Forestry, FRST-BS, and to a handful of courses, some of which are shared variously with the equally fictional Department of Social Theory, Interdisciplinary Program in Gender Studies, and School of Public Policy. The Summary Memo's Table of Contents provides a brief outline of the applications contained in the package, the stakeholders who share an interest in each application, and the supplementary documents supporting each application, application by application: stakeholders and reviewers will thereby be enabled to navigate the package efficiently. The sample Table of Contents follows:

  • Change in Major, FRST-BS
    • Parties Concerned: this application incorporates in the Forestry major the new courses proposed in this package: TREE 337 and TREE 367 (see below) will be electives [i.e., picked up by existing wild-card programming] in FRST-BS as all four courses will be in FRST-MINR, but GSP 359, Ecofeminism (cross-listed with TREE 358 and SOTH 359: see below) should be added to the options for the Ethics requirement of FRST-BS, and the cross-listed TREE 372, Urban Constituencies and City Government (PPOL 260) will serve as an alternative to TREE 371, National Park System, among the options for the Management requirement of FRST-BS.
    • Change in Major Form for FRST-BS; for related course-documents and before-and-after grid, see below
  • Change in Major, GSP-BA
    • Parties Concerned: this application incorporates in the Gender Studies major the new course in Ecofeminism, GSP 359, team-taught by members of the Department of Forestry and of the Department of Social Theory and cross-listed in both departments (TREE 358, SOTH 359: see below). This course should be added to the options for the Theory requirement of GSP-BA. It will be an elective in GSP-MINR as also in SOTH-BA and SOTH-MINR
    • Change in Major Form for GSP-BA; for related course-documents and before-and-after grid, see below
  • New Course, TREE 337, Parks and Urban Forestry
    • Parties Concerned: the course will be offered by the Department of Forestry as an elective [i.e., picked up by existing wild-card programming] in FRST-BS and FRST-MINR; we expect it will be of interest to the School of Public Policy when they complete design of the new major and BA-to-MPP programs in Urban Policy and Management, presently under discussion.
    • New Course Form for the proposed TREE 337
    • Sample Syllabus for the proposed TREE 337
    • Course Inventory Form for the proposed TREE 337
  • New Course, TREE 367, Applied Landscape Architecture
    • Parties Concerned: the course will be offered by the Department of Forestry as an elective in FRST-BS and FRST-MINR
    • New Course Form for the proposed TREE 367
    • Sample Syllabus for the proposed TREE 367
    • Course Inventory Form for the proposed TREE 367
  • New Course, GSP 359, Ecofeminism
    • Parties Concerned: the course will be team-taught by members of the Department of Forestry and of the Department of Social Theory, for the Interdisciplinary Program in Gender Studies; it will be cross-listed in both departments (TREE 358, SOTH 359) but the Gender Studies course is the “parent” course. The new course will be added to the options for the Theory requirement of the GSP-BA and the Ethics requirement of the FRST-BS (see Change in Major applications above); it will be an elective in GSP-MINR, FRST-MINR, SOTH-BA, and SOTH-MINR.
    • New Course Form for the proposed GSP 359 with cross-listed TREE 358, SOTH 359
    • Sample Syllabus for the proposed GSP 359/TREE 358/SOTH 359
    • Course Inventory Forms for each of GSP 359, TREE 358, SOTH 359
  • New Course Number for Cross-listing Existing Course: TREE 372, Urban Constituencies and City Government (PPOL 260, School of Public Policy)
    • Parties Concerned: the Department of Forestry seeks to create TREE 372 so as to cross-list the School of Public Policy’s course PPOL 260, Urban Constituencies and City Government. The course will serve as an alternative to TREE 371, National Park System, among the options for the Management requirement of FRST-BS (see Change in Major application above); it will be an elective in FRST-MINR
    • PermCross Form for the proposed TREE 372
    • Sample Syllabus for PPOL 260, proposed for cross-listing as TREE 372
    • Course Inventory Form for the proposed TREE 372
  • Major/Minor Grids: FRST-BS, FRST-MINR, GSP-BA, GSP-MINR, SOTH-BA, SOTH-MINR
  • Preliminary steps:
  • The new major(s)/minor(s) itself(themselves) must receive approval in its(their) own School in order to advance through the stages of academic approval (see Chart of Approvals). In the College of Arts and Sciences, the Academic Council brings to bear the insight of faculty across the College and representatives from the Undergraduate Student Government (see Charter).
  • We recommend that in preparing an application-package for the Council's review you draft first all the application-forms the package will encompass and the supplementary documents required to support them. Omit the Unique ID in this initial drafting phase; add it from the Summary Memo before uploading the whole package.
    • Download a blank New Major/Minor application-form from the CAS-AC website. The application form regularizes organization of information standard in the Council's review of curricular applications across the College, and needed for accurate processing of the new major/minor once it is approved. Together with the Academic Affairs/Innovation Proposal and a grid outlining the structures in which the new major/minor is to be programmed, the application form gives members of the Council a concrete understanding of the new curricular design.
    • The heading information of the New Major/Minor form corresponds to the heading information of the Summary Memo eForm.
    • Item 1 clarifies the specific request. If you are applying to create more than one new major or minor, even in the same field, nonetheless please use a separate New Major/Minor application form for each individual major or minor, and outline every major and every minor on its own grid.
    • The Plan Code of the new major or minor (item 2) will be a shorthand for it in LOCUS’s coding: typically plan-codes abbreviate the major/minor title in four characters, plus -BA/-BS/-MINR as applicable. Registration & Records will determine the Plan Code actually adopted. Propose here a code that makes sense to the submitting unit.
    • The list of stakeholders in addition to the Department or Interdisciplinary Program submitting the application (item 2.b) should correspond to this specific New Major/Minor’s part of the Table of Contents in the Summary Memo, and confirm it. This information is re-stated in the application form because not all applications in the package necessarily concern the same additional stakeholders. The line of the form may be copied and pasted in order to list multiple partners.
    • The statement of rationale for the major/minor in item 3 of the application-form should be as full as needed to make clear your plans for the proposed major/minor and demonstrate its merits. The Summary Memo’s brief statement of changes in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package. Fuller reference to the Proposal (see item 8) is implicit, but do not frustrate and confuse reviewers by merely referring them to the Proposal. The application form should contain a concise statement explaining the new major/minor, its structures, and why it would be beneficial to institute.
    • Item 4 details the association of any New Course applications with the present application or planned for the future.
    • Item 5 details the association of any Course Change applications, including any discontinuations, with the present application or planned for the future.
    • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 6) flags these considerations for other reviewers. In particular, if the proposal will require any changes in library-resources, please ensure the appropriate librarian is identified and included in item 5 of the Summary Memo.
    • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, Registration & Records undertakes to make new major/minor programming approved by AC no later than December of one academic year, effective as early as the Fall semester of the following academic year (item 7).
    • Supplementary documents entailed by your New Major/Minor application (item 8) are the Academic Affairs Proposal / Innovation Proposal and Major/Minor Grid (outline the new major/minor in the Proposed column).
  • Proofread everything. Correct all errors.
  • After all the application-forms and supplementary documents that will be involved in the application-package have been drafted and proofread, draft and submit the Summary Memo, following Instructions for Curricular Changes (this page). DocFinity will send the submitter an automated e-mail message confirming the Unique ID for the application-package.
    • Add the confirmed Unique ID to all application-forms and supplementary documents, including any New Major/Minor forms. In the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1.
    • Upload into DocFinity all the application-package's application-forms, all the supplementary documents for each application, and the set of before-and-after grids.
    • Index all applications, supplementary documents, and grids with the Unique ID of the application-package, and with the additional metadata appropriate to each item.
  • Check out the application-package from the Job Queue. In the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete." Sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar. This step makes the application-package accessible to other viewers and begins its routing to the Chairperson/Program Director and co-signatories for the approvals needed before the Council's review.
  • Members of the College's Academic Council can find the application-package in their Job Queues after all the parties to the application-packge have recorded their approval. Ordinarily the most systematic review will be carried out first by at least one member of the Curriculum Committee, but depending on the nature of the application-package and its needs the Associate Dean for Academic Affairs, other members of the Council, the College's Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant may also check in.
    • All members of the Academic Council should familiarize themselves with all application-packages slated for the Council's review that month, in preparation for the monthly meeting of the Council. The Council's schedule is posted at the CAS-AC website.
    • Ideally, all questions about an application-package or any of its elements can be raised in advance of the monthly meeting, and any problems resolved. Reviewers should record their queries or corrections in the Diary of the document concerned, and follow up by e-mailing the submitter. The submitter can deliver explanations, discuss points of contention, or make changes, as appropriate (edit the Summary Memo eForm in DocFinity, or revise other documents outside DocFinity and upload using the Replace icon; in either case, also please also add a note to the Diary of the document in question confirming that the reviewer's concern has been addressed).
  • At the monthly meeting the Curriculum Committee makes its recommendations concerning the application-package. Submitters should always consider themselves invited to the meeting so that they can address questions and recommendations the Curriculum Committee or any other members raise in discussion. Unless the submitters withdraw applications, normally the Council votes on all proposals submitted for the month. The Council may, or may not, with the submitters' consent choose to make its approval conditional on specified amendments.
  • Following the monthly meeting, submitters have a brief period to complete any changes in the application-package requested by the Council conditioning its approval, or any other cleanup.
  • After the cleanup period, the Chairperson of the Council records the Council's approval in DocFinity.
  • After the Council's approval is recorded, the Dean's approval is recorded and approved changes are sent forward to the next reviewing body indicated in the Provost's Office's Chart of Approvals: changes involving major(s)/minor(s) go to the Board of Undergraduate Studies first if they involve more than one School within Loyola, or they go straight to the Provost's Office if the College alone is concerned; changes involving course-programming are sent to Registration & Records for processing by the effective date.
  • The Provost's Office sends submitters notification when the Provost has approved changes involving major(s)/minor(s) and other academic programs. Once this approval has been announced, program-changes too are sent to Registration & Records for processing by the effective date.
  • Preliminary steps:
    • Design the curricular changes intended. Consult all parties potentially interested. Collaborate.
    • Your application-package (under one Unique Number) will require one Change in Major/Minor application form for each major, and one for each minor, that will require re-programming of its Academic Requirements Report in order to realize the curricular changes the application contemplates.
    • Note that New Courses (for example) will not necessitate a Change in Major/Minor application if they will all be picked up as desired in the major/minor by an existing elective-rule, e.g., TREE 3##, any 300-level course of the (fictional) Department of Forestry.
    • Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes, whether or not Change in Major/Minor applications are required.
  • We recommend that you draft in advance all the application-forms that will be part of your application-package, and the supplementary documents required to support them. Omit the Unique ID in this initial drafting phase; add it from the Summary Memo before uploading the whole package.
    • Download a blank Change in Major/Minor application-form from the CAS-AC website. The application form regularizes organization of information standard in the Council's review of curricular applications across the College, and needed for accurate processing of changes in the major/minor once they are approved. Together with a grid outlining the structures in which the changed major/minor is to be programmed, the application form gives members of the Council a concrete understanding of the changed curricular design.
    • The heading information of the Change in Major/Minor form corresponds to the heading information of the Summary Memo eForm.
    • Item 1 clarifies the specific request. If you are applying to change more than one major or minor, even if the same change is to be made in several different major(s)/minor(s), nonetheless use a separate Change in Major/Minor application form for each individual major or minor, and outline every major and every minor on its own grid.
    • The Plan Code of the major or minor concerned in the application-document (item 2) is used in LOCUS for coding purposes (e.g., DANC-BA for the major in Dance). Convenient places to look so as to confirm your Plan Code include the index-list of the Academic Requirements Outlines and the outlines themselves: you can navigate to the Academic Requirements Outlines from the portal-page that displays when you’ve logged in to LOCUS.
    • The list of stakeholders in addition to the Department or Interdisciplinary Program submitting the application (item 2.b) should correspond to this specific Change in Major/Minor’s part of the Table of Contents in the Summary Memo, and confirm it. It is re-stated in the application form because not all applications in the package necessarily concern the same additional stakeholders. The line of the form may be copied and pasted in order to list multiple partners.
    • The statement of changes in the major/minor, and their rationale, in item 3 of the application-form should be as full as needed to make clear your plans for the major/minor and demonstrate the merits of the changes. The Summary Memo’s brief statement of changes in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.
    • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 4) flags these considerations for other reviewers. In particular, if the proposal will require any changes in library-resources, please ensure the appropriate librarian is identified and included in item 5 of the Summary Memo.
    • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, Registration & Records undertakes to make changes in major/minor programming approved by AC no later than December of one academic year, effective as early as the Fall semester of the following academic year (item 5).
    • A Before-and-After Grid for the major/minor in question will certainly be entailed by your Change in Major/Minor application; please also prepare any associated course-applications (instructions, this page) and their supplementary documents.
  • Proofread everything. Correct all errors.
  • After all the application-forms and supplementary documents that will be involved in the application-package have been drafted and proofread, draft and submit the Summary Memo, following Instructions for Curricular Changes (this page). DocFinity will send the submitter an automated e-mail message confirming the Unique ID for the application-package.
    • Add the confirmed Unique ID to all application-forms and supplementary documents, including any Change in Major/Minor forms. In the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1.
    • Upload into DocFinity all the application-package's application-forms, all the supplementary documents for each application, and the package's set of before-and-after grids.
    • Index all applications, supplementary documents, and grids with the Unique ID of the application-package, and with the additional metadata appropriate to each item.
  • Check out the application-package from the Job Queue. In the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete." Sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar. This step makes the application-package accessible to other viewers and begins its routing to the Chairperson/Program Director and co-signatories for the approvals needed before the Council's review.
  • Members of the College's Academic Council can find the application-package in their Job Queues after all the parties to the application-packge have recorded their approval. Ordinarily the most systematic review will be carried out first by at least one member of the Curriculum Committee, but depending on the nature of the application-package and its needs the Associate Dean for Academic Affairs, other members of the Council, the College's Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant may also check in.
    • All members of the Academic Council should familiarize themselves with all application-packages slated for the Council's review that month, in preparation for the monthly meeting of the Council. The Council's schedule is posted at the CAS-AC website.
    • Ideally, all questions about an application-package or any of its elements can be raised in advance of the monthly meeting, and any problems resolved. Reviewers should record their queries or corrections in the Diary of the document concerned, and follow up by e-mailing the submitter. The submitter can deliver explanations, discuss points of contention, or make changes, as appropriate (edit the Summary Memo eForm in DocFinity, or revise other documents outside DocFinity and upload using the Replace icon; in either case, also please also add a note to the Diary of the document in question confirming that the reviewer's concern has been addressed).
  • At the monthly meeting the Curriculum Committee makes its recommendations concerning the application-package. Submitters should always consider themselves invited to the meeting so that they can address questions and recommendations the Curriculum Committee or any other members raise in discussion. Unless the submitters withdraw applications, normally the Council votes on all proposals submitted for the month. The Council may, or may not, with the submitters' consent choose to make its approval conditional on specified amendments.
  • Following the monthly meeting, submitters have a brief period to complete any changes in the application-package requested by the Council conditioning its approval, or any other cleanup.
  • After the cleanup period, the Chairperson of the Council records the Council's approval in DocFinity.
  • After the Council's approval is recorded, the Dean's approval is recorded and approved changes are sent forward to the next reviewing body indicated in the Provost's Office's Chart of Approvals: changes involving major(s)/minor(s) go to the Board of Undergraduate Studies first if they involve more than one School within Loyola, or they go straight to the Provost's Office if the College alone is concerned; changes involving course-programming are sent to Registration & Records for processing by the effective date.
  • The Provost's Office sends submitters notification when the Provost has approved changes involving major(s)/minor(s) and other academic programs. Once this approval has been announced, program-changes too are sent to Registration & Records for processing by the effective date.
  • Preliminary steps:
    • Design the curricular changes intended. Consult all parties potentially interested. Collaborate.
    • Consider what major(s)/minor(s) the proposed New Course may serve, both in the proposing academic unit and in second unit(s). If the new course will be specifically required by any major/minor (i.e., all students pursuing that major/minor must take this course), or if it will be a requirement-option choice (i.e., it will figure in a list of specified courses from which students choose a certain number), a Change in Major/Minor application will be required for each major and for each minor involved. On the other hand, the new course will not necessitate a Change in Major/Minor application if it will be picked up as desired in the major/minor by an existing elective-rule, e.g., TREE 3##, any 300-level course of the (fictional) Department of Forestry.
    • Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes, whether or not Change in Major/Minor applications are required.
  • We recommend that you draft in advance all the application-forms that will be part of your application-package and the supplementary documents required to support them. Omit the Unique ID in this initial drafting phase; add it from the Summary Memo before uploading the whole package.
    • Download a blank New Course application-form from the CAS-AC website. The application form regularizes organization of information standard in the Council's review of curricular applications across the College, and needed for accurate processing of the new course once it is approved. Together with a sample syllabus and a Course Inventory Form for the proposed course, and one major/minor grid for each major or minor which will be affected, the application form gives members of the Council a concrete understanding of the new curricular design.
    • The heading information of the New Course form corresponds to the heading information of the Summary Memo eForm.
    • The "proposed course information" in item1 will be basic to the course's coding in LOCUS. It must match the corresponding items of the Course Inventory Form. Double-check to be sure the subject-area code is correct and that the course-number you propose is not already in use, or that you address its disposition in associated documents of the application-package. The longer Course Title will appear in the Browse Catalog display. If it conforms to the character-limit of the shorter Course Abbreviation, you can use the same title for the abbreviation also; but if you need the additional characters for a full statement of the title, a slightly shorter version of the course-title will fit in more abbreviated displays.
    • The rationale in item 2 of the application-form should be as full as needed to make clear your plans for the course and demonstrate its merits. The Summary Memo’s brief statement in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.
    • Item 3 accounts for the history of the course. It is not required to pilot a new course under a Special Topics number, but if a related course has been offered before the new course is applied for, previous experience helps explain and justify the new course. Registration & Records recommends that no course be offered more than three times as a special-topics course before a permanent free-standing course-number should be sought for it.
    • The statements of the new course's focus and outcomes (items 4.a and 4.b) will display as the course's description in LOCUS. They must match the corresponding items of the Course Inventory Form.
    • Item 5.a accounts for any conditions or protocols that will regulate enrollment in the new course; corresponding items of the Course Inventory Form must match.
    • If the new course will be a pre-requisite or co-requisite for other course(s: item 5.b), please also submit as a part of this application-package their New Course and/or Course Change request(s), so that all new or changed programming can be made concurrently.
    • Item 6 outlines the use of writing as a modality of the new course.
    • Item 7 indicates the extent to which the new course is designed to rely on on-line instruction.
    • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying faculty, library, equipment, and other resources the proposed new course will require so as to be realized successfully flags these considerations for other reviewers (items 8.a and 8.b).
    • If a second (or more) Course Number is desired for the new course, in a Subject Area Code belonging to a different academic unit, the cross-listed course(s) may be created by this application (item 9.a): such cross-listing most often is desired when the same course in its substance might be taught by members of faculty holding appointments to different academic units.
      • From this course-creation forward to the end of time, the home unit and the second unit(s) will share responsibility to ensure that the “child” course(s) match(es) the attributes of the “parent” course as either is updated.
      • Please ensure that all partners in the course are identified in the Summary Memo (Table of Contents and routing information) so that all relationships are understood and all proper authority respected.
      • Please ensure that a separate Course Inventory Form for each “child” course, matching the attributes of the “parent” course but headed according to its own “home” academic unit, is submitted and indexed together with the Course Inventory Form for the new “parent” course.
      • Specify the cross-listed courses’ role in all majors and minors in which they will function, including the cross-listing department’s, in item 11.
      • Include the new courses in before-and-after grids for each affected major and minor. File those grids as supplementary documents to this application-package and index with its Unique ID.
      • These lines in the application-form may be copied and pasted so as to accommodate more than one cross-listing.
    • If any Interdisciplinary Program(s) wish(es) to include the new course in its/their major(s)/minor(s), the appropriate tag(s) may be included as Course Attribute(s) of the new course through this application (item 9.b).
      • Please ensure that all partners in the course are identified in the Summary Memo (Table of Contents and routing information) so that all relationships are understood and all proper authority respected.
      • Specify the new course’s role in all majors and minors in which it will function, including the tagging IDPs’, in item 11.
      • Include the new course in before-and-after grids for each affected major and minor. File those grids as supplementary documents to this application-package and index with its Unique ID.
      • These lines in the application-form may be copied and pasted so as to accommodate more than one tagging.
    • Item 10 accounts for any course-discontinuations that may be associated with the creation of the new course.
    • Item 11 registers not only all major(s)/minor(s) in which the new course will figure, but also whether it will be (i) specifically required in any major/minor, so that all students pursuing the major/minor must complete it successfully, (ii) included in a list of specified courses from which students pursuing the major/minor must successfully complete a certain, smaller number of courses and, if the major/minor includes more than one such list, in which list(s) the course is to figure, or (iii) covered by a wildcard-rule such as “students take three TREE 3xx electives.”
      • New Courses will necessitate Change in Major/Minor applications if they will satisfy a specific requirement or requirement-option choice, so that existing programming of the ARR(s) must be changed.
      • New Courses will not necessitate Change in Major/Minor applications if they will all be picked up as desired in the major/minor by an existing elective wildcard-rule.
      • Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be touched by the proposed changes, even if Change in Major/Minor applications are not required.
    • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, Registration & Records undertakes to make new courses approved by AC no later than February of one academic year, effective as early as the Fall semester of the following academic year, and new courses approved by AC no later than March of one academic year, effective as early as the Spring semester of the following academic year (item 12; once it is effective the new course will be picked up by existing Elective rules in all applicable major(s)/minor(s), but any changes in major/minor programming - i.e., if the new course will be specifically required or will figure in any requirement-option lists - must be approved no later than December of one academic year in order to become effective as early as the Fall of the following academic year).
    • A syllabus and a Course Inventory Form for the proposed new course will be entailed as supplementary documents to this New Course application. Please also incorporate this new course in Before-and-After Grids for every major and for every minor that will be affected by it.
  • Proofread everything. Correct all errors.
  • After all the application-forms and supplementary documents that will be involved in the application-package have been drafted and proofread, draft and submit the Summary Memo, following Instructions for Curricular Changes (this page). DocFinity will send the submitter an automated e-mail message confirming the Unique ID for the application-package.
    • Add the confirmed Unique ID to all application-forms and supplementary documents, including any New Course forms. In the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1.
    • Upload into DocFinity all the application-package's application-forms, all the supplementary documents for each application, and the package's set of before-and-after grids.
    • Index all applications, supplementary documents, and grids with the Unique ID of the application-package, and with the additional metadata appropriate to each item.
  • Check out the application-package from the Job Queue. In the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete." Sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar. This step makes the application-package accessible to other viewers and begins its routing to the Chairperson/Program Director and co-signatories for the approvals needed before the Council's review.
  • Members of the College's Academic Council can find the application-package in their Job Queues after all the parties to the application-packge have recorded their approval. Ordinarily the most systematic review will be carried out first by at least one member of the Curriculum Committee, but depending on the nature of the application-package and its needs the Associate Dean for Academic Affairs, other members of the Council, the College's Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant may also check in.
    • All members of the Academic Council should familiarize themselves with all application-packages slated for the Council's review that month, in preparation for the monthly meeting of the Council. The Council's schedule is posted at the CAS-AC website.
    • Ideally, all questions about an application-package or any of its elements can be raised in advance of the monthly meeting, and any problems resolved. Reviewers should record their queries or corrections in the Diary of the document concerned, and follow up by e-mailing the submitter. The submitter can deliver explanations, discuss points of contention, or make changes, as appropriate (edit the Summary Memo eForm in DocFinity, or revise other documents outside DocFinity and upload using the Replace icon; in either case, also please also add a note to the Diary of the document in question confirming that the reviewer's concern has been addressed).
  • At the monthly meeting the Curriculum Committee makes its recommendations concerning the application-package. Submitters should always consider themselves invited to the meeting so that they can address questions and recommendations the Curriculum Committee or any other members raise in discussion. Unless the submitters withdraw applications, normally the Council votes on all proposals submitted for the month. The Council may, or may not, with the submitters' consent choose to make its approval conditional on specified amendments.
  • Following the monthly meeting, submitters have a brief period to complete any changes in the application-package requested by the Council conditioning its approval, or any other cleanup.
  • After the cleanup period, the Chairperson of the Council records the Council's approval in DocFinity.
  • After the Council's approval is recorded, the Dean's approval is recorded and approved changes involving course-programming are sent to Registration & Records for processing by the effective date.
  • As indicated in the Provost's Office's Chart of Approvals, changes involving major(s)/minor(s) go to the Board of Undergraduate Studies first if they involve more than one School within Loyola, or they go straight to the Provost's Office if the College alone is concerned. The Provost's Office sends submitters notification when the Provost has approved changes involving major(s)/minor(s) and other academic programs. Once this approval has been announced, program-changes too are sent to Registration & Records for processing by the effective date.
  • Preliminary steps:
    • Design the curricular changes intended. Consult all parties potentially interested. Collaborate.
    • The Course Change application is used when a course’s “home” department seeks to change its programming in the Course Catalog. It now excludes requests by “second” academic units to create new courses for the purpose of cross-listing the existing course or to tag the existing course for the purpose of including it in an interdisciplinary major/minor: those changes may be sought concurrently with Course Changes by the home department but by means of separate applications initiated by the “second” academic units (PermCross and PermTag applications, respectively).
    • Consider whether the changed course will also change its role in any major(s) or minor(s), of the proposing academic unit and of any second unit(s). If it will, a Change in Major/Minor application will be required for each major and for each minor involved.
    • Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be touched by the proposed changes, whether or not Change in Major/Minor applications are required.
  • We recommend that you draft in advance all the application-forms that will be part of your application-package and the supplementary documents required to support them. Omit the Unique ID in this initial drafting phase; add it from the Summary Memo before uploading the whole package.
    • Download a blank Course Change application-form from the CAS-AC website. The application form regularizes organization of information standard in the Council's review of curricular applications across the College, and needed for accurate processing of the course-change(s) following approval. Together with a sample syllabus and a Course Inventory Form for the proposed course, and one major/minor grid for each major or minor which will be affected, the application form gives members of the Council a concrete understanding of the changed curricular design.
    • The heading information of the Course Change form corresponds to the heading information of the Summary Memo eForm.
    • Please double-check and ensure you supply correctly all information about the current coding of the course and its role in any major(s)/minor(s) it serves (item 1). Current coding information for the existing course may be consulted in the Course Catalog in LOCUS.
    • Please double-check and ensure you supply correctly all information about the current role(s) the course serves in any major(s)/minor(s), as well as its own coding (item 1). Information about courses’ current roles in majors and minors may be consulted in the Academic Requirements Outlines: you can navigate to the AROs from the portal-page that displays when you’ve logged in to LOCUS.
    • If the course is to be discontinued (“yes” to item 2), the reason why remains good to know (item 3), and Registration & Records will want a Course Inventory Form (item 7) filled out for discontinuation of the course (items 2.1, 2.2, 2.3, 2.4, and 2.6 or 2.7 of the Course Inventory Form), but other items of the application-form can be skipped and other supplementary documents omitted.
    • The rationale in item 3 of the application-form should be as full as needed to make clear your plans for the course and demonstrate the merits of the changes. The Summary Memo’s brief statement in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.
    • Item 4 indicates what element(s) of the existing course is/are changing, and specifies the change(s). The corresponding elements of the Course Inventory Form must match.
      • The longer Course Title (item 4.a) will appear in the Browse Catalog display. If it conforms to the character-limit of the shorter Course Abbreviation, you can use the same title for the abbreviation also; but if you need the additional characters for a full statement of the title, a slightly shorter version of the course-title will fit in more abbreviated displays.
      • Changed statements of the course's focus and outcomes (item 4.c) will display as the course's description in LOCUS.
      • Item 4.f is a catch-all for changes not accounted for by the other items. It also encompasses changes in library, equipment, and other resources the proposed course-change(s) will require so as to be realized successfully: although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, this item flags these considerations for other reviewers.
    • Item 5 registers, and should highlight, all changes in major/minor programming associated with the course-change, but also 5.b registers the specifics of the broader question in item 1: is the course (i) specifically required in any major/minor, so that all students pursuing the major/minor must complete it successfully, (ii) included in a list of specified courses from which students pursuing the major/minor must successfully complete a certain, smaller number of courses and, if the major/minor includes more than one such list, in which list(s) the course figures, or (iii) covered by a wildcard-rule such as “students take three TREE 3xx electives”?
      • Course Changes will necessitate Change in Major/Minor applications if they will need to change existing programming of the ARR(s) in order to satisfy a specific requirement or requirement-option choice.
      • Course Changes will not necessitate Change in Major/Minor applications if they will all be picked up as desired in the major/minor by an existing elective-rule, or if existing programming of the ARR(s) will not need to be altered in light of the Course Changes.
      • Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes, even if Change in Major/Minor applications are not required.
    • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, Registration & Records undertakes to make course-changes approved by AC no later than February of one academic year, effective as early as the Fall semester of the following academic year, and course-changes approved by AC no later than March of one academic year, effective as early as the Spring semester of the following academic year (item 6); but changes in major/minor programming must be approved no later than December of one academic year in order to become effective as early as the Fall of the following academic year.
    • A syllabus and a Course Inventory Form for the changed course will be entailed as supplementary documents to this Course Change application. Please also incorporate this changed course in Before-and-After Grids for every major and for every minor in which it figures.
  • Proofread everything. Correct all errors.
  • After all the application-forms and supplementary documents that will be involved in the application-package have been drafted and proofread, draft and submit the Summary Memo, following Instructions for Curricular Changes (this page). DocFinity will send the submitter an automated e-mail message confirming the Unique ID for the application-package.
    • Add the confirmed Unique ID to all application-forms and supplementary documents, including any Course Change forms. In the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1.
    • Upload into DocFinity all the application-package's application-forms, all the supplementary documents for each application, and the package's set of before-and-after grids.
    • Index all applications, supplementary documents, and grids with the Unique ID of the application-package, and with the additional metadata appropriate to each item.
  • Check out the application-package from the Job Queue. In the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete." Sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar. This step makes the application-package accessible to other viewers and begins its routing to the Chairperson/Program Director and co-signatories for the approvals needed before the Council's review.
  • Members of the College's Academic Council can find the application-package in their Job Queues after all the parties to the application-packge have recorded their approval. Ordinarily the most systematic review will be carried out first by at least one member of the Curriculum Committee, but depending on the nature of the application-package and its needs the Associate Dean for Academic Affairs, other members of the Council, the College's Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant may also check in.
    • All members of the Academic Council should familiarize themselves with all application-packages slated for the Council's review that month, in preparation for the monthly meeting of the Council. The Council's schedule is posted at the CAS-AC website.
    • Ideally, all questions about an application-package or any of its elements can be raised in advance of the monthly meeting, and any problems resolved. Reviewers should record their queries or corrections in the Diary of the document concerned, and follow up by e-mailing the submitter. The submitter can deliver explanations, discuss points of contention, or make changes, as appropriate (edit the Summary Memo eForm in DocFinity, or revise other documents outside DocFinity and upload using the Replace icon; in either case, also please also add a note to the Diary of the document in question confirming that the reviewer's concern has been addressed).
  • At the monthly meeting the Curriculum Committee makes its recommendations concerning the application-package. Submitters should always consider themselves invited to the meeting so that they can address questions and recommendations the Curriculum Committee or any other members raise in discussion. Unless the submitters withdraw applications, normally the Council votes on all proposals submitted for the month. The Council may, or may not, with the submitters' consent choose to make its approval conditional on specified amendments.
  • Following the monthly meeting, submitters have a brief period to complete any changes in the application-package requested by the Council conditioning its approval, or any other cleanup.
  • After the cleanup period, the Chairperson of the Council records the Council's approval in DocFinity.
  • After the Council's approval is recorded, the Dean's approval is recorded and approved changes involving course-programming are sent to Registration & Records for processing by the effective date.
  • As indicated in the Provost's Office's Chart of Approvals, changes involving major(s)/minor(s) go to the Board of Undergraduate Studies first if they involve more than one School within Loyola, or they go straight to the Provost's Office if the College alone is concerned. The Provost's Office sends submitters notification when the Provost has approved changes involving major(s)/minor(s) and other academic programs. Once this approval has been announced, program-changes too are sent to Registration & Records for processing by the effective date.
  • Preliminary steps:
    • Design the curricular changes intended. Consult all parties potentially interested. Collaborate.
    • The Permtag application is used by an Interdisciplinary Program seeking to add a “tag” to the Course Attributes of an existing course and to include the course in major(s)/minor(s) of the IDP. The tag enables students majoring or minoring with the IDP to search in the Class Schedule in LOCUS for classes listed under other academic units’ Subject Area Codes. (Tags should not appear on courses not included in the IDP major/minor in question, but the tag as a Course Attribute is separate in LOCUS’s programming from the Academic Requirements Reports of majors and minors.)
    • Typically IDPs use Permtag applications when they initiate requests to tag and include a small number of existing courses in their major(s)/minor(s), in an independent application-package. Each Permtag application form makes its request for a single course; it can now add the newly tagged course as specifically required, a requirement-option, or an elective in the interdisciplinary major/minor. Larger sets of requests, however, especially if they involve changes to existing structures of the interdisciplinary major/minor, may be explained and processed more readily with Change in Major/Minor applications. Permtag or Change in Major/Minor applications motivated by departmental course-requests may be prepared by the IDP and either submitted by the departmental submitters as part of their application-package or submitted concurrently by the IDP in a separate application-package that cross-refers to the departmental submission.
    • Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes, whether or not Change in Major/Minor applications are required.
  • We recommend that you draft in advance all the application-forms that will be part of your application-package and the supplementary documents required to support them. Omit the Unique ID in this initial drafting phase; add it from the Summary Memo before uploading the whole package.
    • Download a blank Permtag application-form from the CAS-AC website. The application form regularizes organization of information standard in the Council's review of curricular applications across the College, and needed for accurate processing of the new course once it is approved. Together with a sample syllabus and a Course Inventory Form for the course, and one major/minor grid for each major or minor which will be affected, the application form gives members of the Council a concrete understanding of the new curricular design.
    • The heading information of the Permtag form corresponds to the heading information of the Summary Memo eForm.
    • Please double-check and ensure you supply correctly all information about the current coding of the course and its role in any major(s)/minor(s) it serves (item 1). Current coding information for the existing course may be consulted in the Course Catalog in LOCUS.
    • Please double-check and ensure you supply correctly all information about the current role(s) the course serves in any major(s)/minor(s), as well as its own coding (item 1). Information about courses’ current roles in majors and minors may be consulted in the Academic Requirements Outlines: you can navigate to the AROs from the portal-page that displays when you’ve logged in to LOCUS.
    • Please ensure that the “home” department of the “parent” course is identified in the Table of Contents and in item 3 or 4, as appropriate, of the Summary Memo: its signatory must be included in the routing of the submission-package.
    • Item 2 clarifies the specific request. Convenient places to look so as to confirm your Plan Code include the index-list of the Academic Requirements Outlines and the outlines themselves: you can navigate to the Academic Requirements Outlines from the portal-page that displays when you’ve logged in to LOCUS.
    • The rationale in item 3 of the application-form should be as full as needed to make clear your plans for the course and its role(s) in the major(s)/minor(s), and to demonstrate the merits of the changes. The Summary Memo’s brief statement in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.
      • Please recall that since students’ Academic Requirements Reports function by Subject Area Codes, not the interdisciplinary tags, interdisciplinary majors and minors normally are programmed in terms of individually required courses and requirement-option lists, not the wildcard-programmed choices in a single Subject Area that constitute “electives” in LOCUS’s sense.
    • Item 4 registers, and should highlight, the role(s) the tagged course will have in the IDP’s major(s)/minor(s), but also the specifics of the broader question in item 1 (including any departmental major(s)/minor(s) in which it may serve as an elective, in LOCUS’s sense, by wildcard programming, in contrast to the IDP major(s)/minor(s): see note above). Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes.
    • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 5) flags these considerations for other reviewers.
    • Item 6: presuming that approvals subsequent to Academic Council’s are gathered on-pace, since programming of IDP major(s)/minor(s) is necessarily at stake in a Permtag application (see above), Registration & Records undertakes to make Permtag applications approved by AC no later than December of one academic year, effective as early as the Fall semester of the following academic year.
    • A syllabus and a Course Inventory Form for the course and Before-and-After Grids for each major and for each minor encompassed by this Permtag application will be required as supplementary documents.
  • Proofread everything. Correct all errors.
  • After all the application-forms and supplementary documents that will be involved in the application-package have been drafted and proofread, draft and submit the Summary Memo, following Instructions for Curricular Changes (this page). DocFinity will send the submitter an automated e-mail message confirming the Unique ID for the application-package.
    • Add the confirmed Unique ID to all application-forms and supplementary documents, including any Permtag forms. In the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1.
    • Upload into DocFinity all the application-package's application-forms, all the supplementary documents for each application, and the package's set of before-and-after grids.
    • Index all applications, supplementary documents, and grids with the Unique ID of the application-package, and with the additional metadata appropriate to each item.
  • Check out the application-package from the Job Queue. In the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete." Sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar. This step makes the application-package accessible to other viewers and begins its routing to the Chairperson/Program Director and co-signatories for the approvals needed before the Council's review.
  • Members of the College's Academic Council can find the application-package in their Job Queues after all the parties to the application-packge have recorded their approval. Ordinarily the most systematic review will be carried out first by at least one member of the Curriculum Committee, but depending on the nature of the application-package and its needs the Associate Dean for Academic Affairs, other members of the Council, the College's Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant may also check in.
    • All members of the Academic Council should familiarize themselves with all application-packages slated for the Council's review that month, in preparation for the monthly meeting of the Council. The Council's schedule is posted at the CAS-AC website.
    • Ideally, all questions about an application-package or any of its elements can be raised in advance of the monthly meeting, and any problems resolved. Reviewers should record their queries or corrections in the Diary of the document concerned, and follow up by e-mailing the submitter. The submitter can deliver explanations, discuss points of contention, or make changes, as appropriate (edit the Summary Memo eForm in DocFinity, or revise other documents outside DocFinity and upload using the Replace icon; in either case, also please also add a note to the Diary of the document in question confirming that the reviewer's concern has been addressed).
  • At the monthly meeting the Curriculum Committee makes its recommendations concerning the application-package. Submitters should always consider themselves invited to the meeting so that they can address questions and recommendations the Curriculum Committee or any other members raise in discussion. Unless the submitters withdraw applications, normally the Council votes on all proposals submitted for the month. The Council may, or may not, with the submitters' consent choose to make its approval conditional on specified amendments.
  • Following the monthly meeting, submitters have a brief period to complete any changes in the application-package requested by the Council conditioning its approval, or any other cleanup.
  • After the cleanup period, the Chairperson of the Council records the Council's approval in DocFinity.
  • After the Council's approval is recorded, the Dean's approval is recorded and approved changes involving course-programming are sent to Registration & Records for processing by the effective date.
  • As indicated in the Provost's Office's Chart of Approvals, changes involving major(s)/minor(s) go to the Board of Undergraduate Studies first if they involve more than one School within Loyola, or they go straight to the Provost's Office if the College alone is concerned. The Provost's Office sends submitters notification when the Provost has approved changes involving major(s)/minor(s) and other academic programs. Once this approval has been announced, program-changes too are sent to Registration & Records for processing by the effective date.
  • Preliminary steps:
    • Design the curricular changes intended. Consult all parties potentially interested. Collaborate.
    • The Permcross application is used by a Department or Interdisciplinary Program seeking to create a new course number in a Subject Area Code of its own, for purposes of cross-listing an existing course. Typically cross-listing is desired when members of different departments or programs will be called on to teach, in substance, the same course; courses required for Interdisciplinary Programs’ majors or minors may need to be cross-listed with departmental courses, but usually tagging suffices instead (for tagging, use the Permtag form).
    • Consider whether the new course created by the Permcross application will be picked up by any major(s)/minor(s) in addition to the one(s) principally intended, for example by wildcard elective-programming in the subject-area code (e.g., TREE 3##): before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be touched by the proposed changes.
  • We recommend that you draft in advance all the application-forms that will be part of your application-package and the supplementary documents required to support them. Omit the Unique ID in this initial drafting phase; add it from the Summary Memo before uploading the whole package.
    • Download a blank Permcross application-form from the CAS-AC website. The application form regularizes organization of information standard in the Council's review of curricular applications across the College, and needed for accurate processing of the new course once it is approved. Together with a sample syllabus and a Course Inventory Form for the proposed course, and one major/minor grid for each major or minor which will be affected, the application form gives members of the Council a concrete understanding of the new curricular design.
    • The heading information of the Permcross form corresponds to the heading information of the Summary Memo eForm. We recommend that you draft in advance all the application-forms that will be part of your application-package, including any Permcross forms needed, omitting only temporarily the Unique Number.
    • Please double-check and ensure you supply correctly all information about the current coding of the existing course and its role in any major(s)/minor(s) it serves (item 1). Current coding information for the existing course may be consulted in the Course Catalog in LOCUS. ("Advisory" pre-requisites appear in the course-description; "enforced" pre-requisites also appear in the Enrollment Requirement Group.) We need to be fussy about all the elements of the existing course, because the new, cross-listed course will need to match it in all respects and be coded as an alternative for any Electives the “parent” course satisfies.
    • Please double-check and ensure you supply correctly all information about the current role(s) the existing course serves in any major(s)/minor(s), as well as its own coding (item 1). Information about courses’ current roles in majors and minors may be consulted in the Academic Requirements Outlines: you can navigate to the AROs from the portal-page that displays when you’ve logged in to LOCUS. We need to be fussy about all the elements of the existing course, because the new, cross-listed course will need to match it in all respects and be coded as an alternative for any Electives the “parent” course satisfies.
    • Please ensure that the “home” department of the “parent” course is identified in the Table of Contents and in item 3 or 4, as appropriate, of the Summary Memo: its signatory must be included in the routing of the submission-package.
    • The rationale in item 2 of the application-form should be as full as needed to make clear your plans for the cross-listed course and demonstrate the merits of the new cross-listing. The Summary Memo’s brief statement in the Table of Contents, by contrast, introduces the application-package overall and assists approvers and reviewers in navigating the package.
    • Item 3 states for the new course in the submitter’s Subject Area Code the basic identifying information that will have to be created in LOCUS. The Subject Area Code, obviously, will be different from that of the pre-existing course; the Course Number in the submitter’s Subject Area Code may or may not be the same as the number of the pre-existing course. All other parameters of the new course, however (including course-title, description, and enrollment-restrictions: items 3, 4, and 5), should match those of the pre-existing course.
    • Item 6 provides the space to distinguish whether the existing course is specifically required, a requirement-option, or an elective in its current major/minor inclusions, as well as to add the new cross-listed course and its status in any additional majors/minors it will implicate. All the majors/minors will need re-programming so as to include interchangeably both the pre-existing course and the new cross-listed course. Note that before-and-after grids are required as supplementary documents in the application-package for every major and for every minor that will be affected by the proposed changes.
    • Item 7 accounts for any course-discontinuations that may be associated with the creation of the new cross-listed course.
    • Although the College’s Academic Council bases its recommendations on the academic merits of the proposal, not the proposal’s resource-needs, identifying library, equipment, and other resources the proposed changes will require so as to be realized successfully (item 8) flags these considerations for other reviewers.
    • Presuming that approvals subsequent to Academic Council’s are gathered on-pace, since cross-crediting the now cross-listed courses will necessitate re-programming of major(s)/minor(s) (see note above), Registration & Records undertakes to make Permcross applications approved by AC no later than December of one academic year, effective as early as the Fall semester of the following academic year.
    • A syllabus and a Course Inventory Form for the course and Before-and-After Grids for each major and for each minor encompassed by this Permcross application will be required as supplementary documents.
  • Proofread everything. Correct all errors.
  • After all the application-forms and supplementary documents that will be involved in the application-package have been drafted and proofread, draft and submit the Summary Memo, following Instructions for Curricular Changes (this page). DocFinity will send the submitter an automated e-mail message confirming the Unique ID for the application-package.
    • Add the confirmed Unique ID to all application-forms and supplementary documents, including any Permcross forms. In the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1.
    • Upload into DocFinity all the application-package's application-forms, all the supplementary documents for each application, and the package's set of before-and-after grids.
    • Index all applications, supplementary documents, and grids with the Unique ID of the application-package, and with the additional metadata appropriate to each item.
  • Check out the application-package from the Job Queue. In the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete." Sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar. This step makes the application-package accessible to other viewers and begins its routing to the Chairperson/Program Director and co-signatories for the approvals needed before the Council's review.
  • Members of the College's Academic Council can find the application-package in their Job Queues after all the parties to the application-packge have recorded their approval. Ordinarily the most systematic review will be carried out first by at least one member of the Curriculum Committee, but depending on the nature of the application-package and its needs the Associate Dean for Academic Affairs, other members of the Council, the College's Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant may also check in.
    • All members of the Academic Council should familiarize themselves with all application-packages slated for the Council's review that month, in preparation for the monthly meeting of the Council. The Council's schedule is posted at the CAS-AC website.
    • Ideally, all questions about an application-package or any of its elements can be raised in advance of the monthly meeting, and any problems resolved. Reviewers should record their queries or corrections in the Diary of the document concerned, and follow up by e-mailing the submitter. The submitter can deliver explanations, discuss points of contention, or make changes, as appropriate (edit the Summary Memo eForm in DocFinity, or revise other documents outside DocFinity and upload using the Replace icon; in either case, also please also add a note to the Diary of the document in question confirming that the reviewer's concern has been addressed).
  • At the monthly meeting the Curriculum Committee makes its recommendations concerning the application-package. Submitters should always consider themselves invited to the meeting so that they can address questions and recommendations the Curriculum Committee or any other members raise in discussion. Unless the submitters withdraw applications, normally the Council votes on all proposals submitted for the month. The Council may, or may not, with the submitters' consent choose to make its approval conditional on specified amendments.
  • Following the monthly meeting, submitters have a brief period to complete any changes in the application-package requested by the Council conditioning its approval, or any other cleanup.
  • After the cleanup period, the Chairperson of the Council records the Council's approval in DocFinity.
  • After the Council's approval is recorded, the Dean's approval is recorded and approved changes involving course-programming are sent to Registration & Records for processing by the effective date.
  • As indicated in the Provost's Office's Chart of Approvals, changes involving major(s)/minor(s) go to the Board of Undergraduate Studies first if they involve more than one School within Loyola, or they go straight to the Provost's Office if the College alone is concerned. The Provost's Office sends submitters notification when the Provost has approved changes involving major(s)/minor(s) and other academic programs. Once this approval has been announced, program-changes too are sent to Registration & Records for processing by the effective date.
  • Your application package is required to include one before-and-after grid for every major and one for every minor that will be affected by the curricular changes being considered.
    • The structurally complete, clear graphic presentation by the grids concisely shows reviewers the academic context of your proposed curricular changes, complementing your verbal statement why the changes are desirable.
    • If any new programming of your major(s)/minor(s) will be involved, the grids will also facilitate it and ensure the revised structure of the major or minor will be understood in the same terms by all.
    • The section-specific Temporary Tag/Cross-list requests also need the same information so as to ensure students receive program-credit correctly.
  • Please note that a single course may figure in more than one major or minor: one grid will be required for each major and for each minor concerned in the application-package. On the other hand, separate course-applications within the package may be concerned in the same set of major(s) and minor(s): only one grid per major or per minor should be submitted with the application-package, each accounting for the full set of courses involved.
  • The grid is organized according to the operations by which students’ Academic Requirements Reports are programmed in LOCUS.
    • “Individually required courses” are the ones that normally every student must complete successfully in order to earn the major or minor. Conceptual groups of individually required courses may be described by lists within the category (see sample grid for DANC-BA, below).
    • “Requirements with options” permit students choices within sets of individually specified courses. A single major/minor may include more than one different requirement-option choice, according to its conceptual structure. Requirements for choices may be structured in terms of the course or of the credit-hour. (See sample grid for DANC-BA, below.)
    • “Electives” are courses students may use to complete the course- or hours- requirements of the major or minor, when their choice is constrained not by a list of specified courses but by a Subject Area Code or level of courses within the Subject Area Code (e.g., 4 credit-hours DANC 2## or DANC 3##: see sample grid for DANC-BA, below).
  • Note for Interdisciplinary Programs: since students’ Academic Requirements Reports function by Subject Area Codes, not the interdisciplinary tags (tags function only within LOCUS’s Class-Search operations in the Class Schedule), interdisciplinary majors and minors normally are programmed in terms of individually required courses and requirement-option lists.
  • The current programming in LOCUS of your major(s)/minor(s)’ Academic Requirements is reflected by the Academic Requirements Outlines (follow links from the portal-page after you log in to LOCUS). We recommend that all departments and interdisciplinary programs prepare charts for each of the majors and minors you oversee, reflecting current coding, and store them for ready reference in a drive shared by your fellow faculty-members. When you begin to prepare any curricular-change application, compare your reference-charts and those of any other parties concerned against the AROs for the current catalogue, resolve any discrepancies in consultation with the Associate Dean for Academic Affairs, and use the corrected information in the “Current major/minor” column.
  • Depending on the complexity of the curricular changes you are proposing, the “Proposed changes” column may identify proposed changes briefly (e.g., “add new course SUBJ xxx to Requirement-Option Choice 2”) or re-draw the category with a new list. Please state “no change” when the category should not change.
  • Proofread everything. Correct all errors.
  • A sample grid for the 2017-18 form of the B.A. in Dance is posted by way of illustration:

 

Item

Current Major/Minor

Proposed Change(s)*

Major/Minor title

Dance (DANC-BA) [2017-18 programming as example]

 

Individually required courses (i.e., all students must take each course)

Foundational Courses:
DANC 250: Dance History
DANC 270: Dance Kinesiology
THTR 321C: Costuming Practicum
THTR 321E: Electrics Practicum

Synthesis:
2 credit-hrs DANC 323: Rehearsal and Performance
DANC 360: Dance Pedagogy
DANC 370: Composition: Dance
DANC 380: Senior Showcase Capstone
DANC 394: Internship in Dance

 

Requirements with options (e.g., students must take 2 of 5 listed courses)

Applied Courses, Ballet: total 8 credit-hours
DANC 341: Intermediate Majors Ballet
DANC 343: Advanced Majors Ballet

Applied Courses, Pointe: total 4 credit-hours
DANC 312: Pointe I
DANC 314: Pointe II

Applied Courses, Modern Dance: total 4 credit-hours (2 hrs at each level)
DANC 224: Majors Modern II
DANC 324: Majors Modern III

 

Elective courses (i.e., programmable by wild-card rules, rather than by identifying specific courses required or for students to choose among)

4 credit-hours DANC 2## or higher-level (DANC 3##)

 

Credit Hours

40

 

Other changes

   

Proposed effective date

n/a

Fall, __________

  • The Academic Council has deputed some curricular changes to the Associate Dean for administrative action:
    • discontinuing an inactive major;
    • discontinuing an inactive minor;
    • discontinuing an inactive course;
    • discontinuing an inactive course from an active major or minor;
    • re-numbering a course;
    • approving specific sections of courses in specific semesters for a temporary tag or cross-listing (see instructions);
    • implicitly, the Associate Dean's concern with maintaining the integrity of the Academic Council's approvals in curricular matters means that the Associate Dean will work to correct or clarify apparent errors in the programming or displays of LOCUS.
  • Discontinuations and re-numberings may be initiated by an e-mail message to the Associate Dean for Academic Affairs, outlining the specific change(s) sought and why.
    • The Associate Dean will investigate the history and ramifications of the change(s) desired, so as to determine how they may be effected without complications: the Associate Dean will advise the inquirer about the results of these investigations.
    • As the Chart of Academic Approvals shows, major/minor and course discontinuations are to be approved at the College level by the Dean, by the Board of Undergraduate Studies if more than one School is concerned, and at the University level by the Provost: the Associate Dean will advance recommendations from Chairperson(s)/Program Director(s) to the Dean, for further forwarding and recommending.
    • Usually, one or more Course Inventory Forms will be required to effect discontinuations or re-numbering of courses. As the Course Inventory Form requires, the Chairperson or Program Director of the academic home-unit of the courses must authorize the changes. Course Inventory Forms should be processed through the Dean's Office, which will forward them to Registration and Records for action.
  • Temporary tags and temporary cross-listing of courses are initiated by the stakeholding academic units by application through the CAS-AS DocFinity Platform: see instructions for Temporary Tags and Cross-listings.
  • Please direct inquiries about apparent programming-errors in LOCUS to the Associate Dean.
  • Submitters design the curricular changes they intend.
  • Submitters consult with all parties potentially interested in their curricular changes: they inform, they collaborate, and they secure consent in principle.
  • Individual submitters follow applicable policies of the department, interdisciplinary program, or other academic unit that is to be the corporate submitter and, ultimately, supervising unit of the curricular design being proposed, so that
    • their colleagues shall understand the proposal;
    • the academic unit's consent to the proposal shall have been secured;
    • the Chairperson/Program Director shall be able to sign off on the application-package within the application-process, with the academic unit's voice.
  • Submitters familiarize themselves with the processes and forms that will be involved in the Academic Council's review of their proposed curricular changes: they study the instructions set forth in this website, they consult colleagues, and they follow the guidance of the Associate Dean.
  • Submitters proofread fanatically.
  • One individual submitter fully knowledgeable about the curricular change(s) to be proposed serves as Submitter in the College's curricular-review process through Academic Council and the CAS-AC DocFinity platform. That person
    • works with colleagues in the proposing academic unit and other partners in the proposal, as applicable - in all matters connected with the application, but in particular (at this point) to ensure that all application-forms and supplementary documents are completed correctly (download application-forms from the CAS-AC website and follow instructions on this page);
    • assembles the application-forms and supplementary documents and, based on them, completes and submits the Summary Memo (instructions, this page);
    • adds the Unique ID from the Summary Memo to each application-form and supplementary document (in the rare event that you submit multiple packages of curricular-change applications on the same date, please add to the automatically generated Unique ID a number after the date so as to differentiate separate submissions, e.g., mlettie05162017-1);
    • uploads into the CAS-AC DocFinity platform all application-documents comprised by the application-package, all supplementary documents for each application, and before-and-after grids showing the full set of consequences intended for each major and for each minor that will be affected;
    • indexes the full set of uploaded documents with the application-package's Unique ID and other metadata applicable to each item;
    • reviews the application-package and, in the Job Queue, checks Submission Complete and signs out with the Complete Job icon so that DocFinity can advance the package to the Chairperson/Program Director and co-signatories, if any, for approval needed before Academic Council can review the application(s).
  • The Chairperson/Program Director of the submitting academic home-unit is responsible for recording approval of the application-package, on the home-unit's behalf, in the Tasks panel of the Jobs workspace in DocFinity no later than the submission-deadline for the month (after ensuring that all documents of the application-package present the application in its full detail accurately and consistently), in order for the application-package to be reviewed that month.
  • While the application-package is under review, the DocFinity Submitter, the Chairperson/Program Director, and other members of the submitting academic unit and partners in the application-package may receive queries about the application-package from members of the Curriculum Committee, other members of the Academic Council, the Associate Dean for Academic Affairs, other members of the Dean's Office, or other persons concerned in the proposed changes. Submitters receiving such queries bear the responsibility to respond to them appropriately: depending on the nature of the query, correcting errors, explaining, consulting, resolving differences, making amendments, etc., all with the knowledge and consent of the Chairperson/Program Director, other members of the submitting academic unit, and partners in the change(s) proposed.
    • Reviewers should record their queries or corrections in the Diary of the document concerned, and follow up by e-mailing the Submitter.
    • The Submitter should ensure queries find the appropriate response expeditiously.
    • The Summary Memo eForm can be edited directly in DocFinity: click "edit" in the toolbar when the Summary Memo is open, "save" to save changes, and "close" to exit the edited eForm. The Submitter should also, please, add a note to the Diary of the Summary Memo confirming that the reviewer's concern has been addressed.
    • Other documents should be edited outside DocFinity (download the document from DocFinity by the icon in the Search panel's toolbar, or work from an up-to-date file copy) and re-uploaded using the Replace icon. The Submitter should also, please, add a note to the Diary of the document in question confirming that the reviewer's concern has been addressed.
    • Submitters who make changes in an application-package should ensure that changes are carried through all pertinent documents so that the application-package remains consistent: for example, any changes made in a course-application must also be reflected in the course's Course Inventory Form and in all other documents where the course is referred to.
  • Submitters should always consider themselves invited to the Academic Council's monthly meeting where the application-package is to be discussed, so that they can address questions and recommendations the Curriculum Committee or any other Council members raise in discussion. The Council's schedule is posted at the CAS-AC website.
  • At any point while the application-package is under review, down to discussion in the Academic Council's monthly meeting, submitters may determine the application-package should be withdrawn, for further consultation and modification or entirely. They should notify, at a minimum: the current head of the Curriculum Committee, the current Chair of the Council, their academic unit's/s' current Representative(s) on the Council, the Associate Dean for Academic Affairs, the Assistant Director for Communications and Academic Affairs, and any partners in the proposal.
  • If the Council votes to oppose a curricular change, the submitters and their partners may not proceed as if the change had been approved, but may revise the proposal and make a new application at a future time.
  • If the Council votes to table a curricular change, the submitters and their partners may not proceed as if the change had been approved, but should revise the proposal in ways that address the Council's concerns, for reconsideration at a later meeting.
  • If the Council votes to makes its approval conditional on specified amendments, the submitters and their partners should
    • ensure that their colleagues in their academic home-units understand and approve of the amendments;
    • during the cleanup period following the Council's meeting, make all changes required in the application-package so as to reflect the amendments consistently across the package (please make confirmatory notes in the Diary of each document altered);
    • consult with the Chair of the Council, the meeting-month's head of the Curriculum Committee, and any other members of the Council particularly concerned in the amendments so as to ensure that all appropriate changes have been made correctly and the amendments are reflected consistently across the application-package;
    • notify the Chair of the Council, the Associate Dean for Academic Affairs, the Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant that the amendments and their documentation have been completed.
  • If the Council votes to approve a curricular change, the Submitter should use the cleanup period following the Council's meeting to double-check that all documents in the application-package are complete and correct and reflect the changes approved consistently across the package (please make notes in the Diary of each document altered, and please notify the Associate Dean for Academic Affairs, the Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant that all cleanup has been completed).
  • If the changes approved involve courses, they normally appear in LOCUS during the preceding summer if they have been approved for effectiveness in a given Fall term, or during the preceding fall if they have been approved for effectiveness in a given Spring term: in the latter part of that preceding season, submitters should double-check the Course Catalog to ensure that all updates have been made as approved.
  • If the changes approved involve changes in the programming of major(s), minor(s), or other academic program(s), the Provost's Office sends submitters notification when the Provost has approved them. Once this approval has been announced, submitters may begin to promulgate information about the changes and their effective date and to take other measures appropriate to the changes' taking effect.

The Chairperson/Program Director of the academic unit submitting curricular-change application(s) may, or may not, serve as the Submitter of application-documents in the CAS-AC DocFinity Platform. For fuller explanation of the DocFinity Submitter's role, please see the question, What responsibilities do Submitters bear?, this page. This account describes responsibilities peculiar to the Chairperson or Program Director.

  • The Chairperson/Program Director oversees curricular-design processes of the academic unit, so that
    • curricular changes proposed in the College are well grounded on current and forward-looking expertise in content and in pedagogy;
    • the faculty concerned with the curricular changes proposed understands them and consents to them - thereby the Chairperson/Program Director will be able to sign off on the application-package with the academic unit's voice;
    • curricular changes proposed conform with the academic unit's, College's, and University's practices or, if they will call for other changes or additional resources, those needs can be identified and considered appropriately in the curricular-approval process;
    • any partnerships in the curricular changes proposed, as appropriate, support the collegiality of the College and the strengths of the academic units concerned and of their academic programs.
  • After the DocFinity Submitter has completed the Summary Memo, uploaded and indexed all other documents in the application-package, and certified "Complete Job," the Chairperson/Program director will receive an automated e-mail message identifying the application-package and requesting review and approval. The Chairperson/Program Director should then
    • log in to the CAS-AC DocFinity Platform;
    • either search for the application-package by Unique ID using the Search panel or double-click on the appropriate queue in the Job Views panel and then "check out" the appropriate Job;
    • review individual documents by clicking the document's check-box in the Search Results panel and then "view" from the toolbar: whether you are the Chairperson/Program Director of the academic unit submitting the application-package, or the Chairperson/Program Director of a second unit partnering with the submitters in the application, review all documents in the package that pertain to your academic unit;
    • if you identify any problems with the documents as submitted or other questions or concerns about the proposal, please
      • make a note of your question or concern in the Diary of the document(s) in question (open the Diary by clicking the View Diary icon in the toolbar of the Search Results panel where the individual document is selected, click the Add icon in the toolbar of the opened Diary, write the note in the blank text-box that opens, and click Save in the toolbar) - this note both helps to direct the submitters' attention and lets other reviewers know the question has already been raised;
      • e-mail the Submitter or other person connected with the application-package who would be able to address your concern, outlining it and identifying the document(s) to which that person should return so as to address it;
      • ask the person to whom you write to let you know when the concern is addressed and the document(s) are updated;
      • when the document(s) are updated, complete your review;
    • when you have completed your review of documents in the application-package that pertain to the academic unit for which you hold responsibility and when you judge the academic unit's mission will be advanced by the package's being approved,
      • exit and close up any individual documents that are open;
      • if you are not already in the Jobs panels, go there and "check out" the Job under consideration;
      • in the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete," then check the box for approval and reply by selecting "approved";
      • sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar: this step is vital for advancing the application-package.
    • Approval of the application-package, on behalf of the academic home-unit submitting it, must be recorded in the Tasks panel of the Jobs workspace in DocFinity by the Chairperson/Program Director no later than the submission-deadline for the month in order for the application-package to be reviewed that month.
  • While the application-package is being reviewed by Chairperson(s)/Program Director(s) of any second units in the curricular request, the Curriculum Committee, other members of the Academic Council, or members of the Dean's Office, the Chairperson/Program Director may be addressed by reviewers with questions or concerns about the application. If so, please
    • ensure the query(ies) find the appropriate response(s) expeditiously, consulting colleagues in the application-package as appropriate;
    • if resolution of the query(ies) requires updating of any document(s) in the application-package, update it(them) or direct the Submitter to do so - in either case
      • care should be taken that changes are carried through all pertinent documents so that the application-package remains consistent;
      • a note should be added to the Diary of each document updated confirming that the reviewer's concern has been addressed;
      • a reply should be made to the person who raised the concern, inviting that person to resume review of the application-package.
  • Submitters, including the Chairperson/Program Director as appropriate, should always consider themselves invited to the Academic Council's monthly meeting where the application-package is to be discussed, so that they can address questions and recommendations the Curriculum Committee or any other Council members raise in discussion.
  • At any point while the application-package is under review, down to discussion in the Academic Council's monthly meeting, the Chairperson/Program Director or other submitters may determine the application-package should be withdrawn, for further consultation and modification or entirely. They should notify, at a minimum: the current head of the Curriculum Committee, the current Chair of the Council, their academic unit's/s' current Representative(s) on the Council, the Associate Dean for Academic Affairs, the Assistant Director for Communications and Academic Affairs, and any partners in the proposal.
  • If the Council votes to oppose a curricular change, the Chairperson/Program Director may not proceed as if the change had been approved, but may work with submitters and any partners to revise the proposal and make a new application at a future time.
  • If the Council votes to table a curricular change, the Chairperson/Program Director may not proceed as if the change had been approved, but should work with submitters and any partners to revise the proposal in ways that address the Council's concerns, for reconsideration at a later meeting.
  • If the Council votes to makes its approval conditional on specified amendments, the Chairperson/Program Director should
    • ensure that submitters and their colleagues in their academic home-units understand and approve of the amendments;
    • during the cleanup period following the Council's meeting, make or direct the Submitter to make all changes required in the application-package so as to reflect the amendments consistently across the package (please make confirmatory notes in the Diary of each document altered);
    • consult with the Chair of the Council, the meeting-month's head of the Curriculum Committee, and any other members of the Council particularly concerned in the amendments so as to ensure that all appropriate changes have been made correctly and the amendments are reflected consistently across the application-package;
    • notify the Chair of the Council, the Associate Dean for Academic Affairs, the Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant that the amendments and their documentation have been completed.
  • If the Council votes to approve a curricular change, the Chairperson/Program Director or the Submitter should use the cleanup period following the Council's meeting to double-check that all documents in the application-package are complete and correct and reflect the changes approved consistently across the package (please make notes in the Diary of each document altered, and please notify the Associate Dean for Academic Affairs, the Assistant Director for Communications and Academic Affairs, and the Dean's Executive Assistant that all cleanup has been completed).
  • If the changes approved involve courses, they normally appear in LOCUS during the preceding summer if they have been approved for effectiveness in a given Fall term, or during the preceding fall if they have been approved for effectiveness in a given Spring term: in the latter part of that preceding season, the Chairperson/Program Director should double-check the Course Catalog to ensure that all updates have been made as approved.
  • If the changes approved involve changes in the programming of major(s), minor(s), or other academic program(s), the Provost's Office sends submitters notification when the Provost has approved them. Once this approval has been announced, the Chairperson/Program Director and submitters may begin to promulgate information about the changes and their effective date and to take other measures appropriate to the changes' taking effect.

Formally, the Academic Council's process for review of curricular-change applications presupposes that the academic unit - department or interdisciplinary program - initiating a permanent change bears the responsibility to initiate the paperwork so as to effect that change. Nonetheless, some changes necessarily involve extensive collaboration by second unit(s) partnering in the curricular design proposed. Individual members of a second unit's faculty and its Chairperson/Program Director should work with the submitters, the Council, the Dean's Office, and other parties to the process so as to strengthen the proposal, the academic units concerned and their academic programs, and the collegiality of the College.

  • In curricular design, assist submitters
    • to appreciate the value their proposal brings to students in the context of both units' programs;
    • to incorporate beneficial material and pedagogy;
    • to identify resource-needs.
  • As the submitters prepare application-materials,
    • prepare supplementary documents for your academic unit that are needed to support submitters' applications, such as Course Inventory Forms for cross-listed "child" courses in the second unit's Subject Area Code;
    • prepare any allied applications to be submitted as part of the submitters' application-package or concurrently by the second unit, such as a Change in Minor application incorporating a new course of the submitters in a requirement-option list (file jointly or separately but concurrently as it better serves the clarity of the proposals concerned);
    • if it makes best sense for the second unit to submit a concurrent curricular-change application-package, prepare and submit it (instructions, this page);
    • assist preparing before-and-after grid(s) for the submitters' application-package, showing how their proposal will be reflected in your major(s)/minor(s).
  • When the application-package has been submitted by its DocFinity Submitter and approved by the home unit's Chairperson/Program Director, the Chairperson/Program Director of the second unit will receive an automated e-mail message identifying the application-package and requesting review and approval. The Chairperson/Program Director of the second unit should then
    • log in to the CAS-AC DocFinity Platform;
    • either search for the application-package by Unique ID using the Search panel or double-click on the appropriate queue in the Job Views panel and then "check out" the appropriate Job;
    • review individual documents by clicking the document's check-box in the Search Results panel and then "view" from the toolbar: please review all documents in the package that pertain to your academic unit;
    • if you identify any problems with the documents as submitted or other questions or concerns about the proposal, please
      • make a note of your question or concern in the Diary of the document(s) in question (open the Diary by clicking the View Diary icon in the toolbar of the Search Results panel where the individual document is selected, click the Add icon in the toolbar of the opened Diary, write the note in the blank text-box that opens, and click Save in the toolbar) - this note both helps to direct the submitters' attention and lets other reviewers know the question has already been raised;
      • e-mail the Submitter or other person connected with the application-package who would be able to address your concern, outlining it and identifying the document(s) to which that person should return so as to address it;
      • ask the person to whom you write to let you know when the concern is addressed and the document(s) are updated;
      • when the document(s) are updated, complete your review;
    • when you have completed your review of documents in the application-package that pertain to the academic unit for which you hold responsibility and when you judge the academic unit's mission will be advanced by the package's being approved,
      • exit and close up any individual documents that are open;
      • if you are not already in the Jobs panels, go there and "check out" the Job under consideration;
      • in the Tasks panel, check the box "Is the Submission Complete?" and reply by selecting "Submission Complete," then check the box for approval and reply by selecting "approved";
      • sign out of the Tasks panel by clicking the "Complete Job" icon in the toolbar: this step is vital for advancing the application-package.
    • Approval of applications involving partnering second-units, on behalf of those academic units, must be recorded in the Tasks panel of the Jobs workspace in DocFinity by the second unit's Chairperson/Program Director no later than the day of the meeting at which the application-package is to be discussed and voted on by the Academic Council, in order for the stakeholder's partnership to receive its approval. It is preferable for submitters to submit application-packages only after securing approval in principle from all partnering stakeholders in advance, and for the stakeholders' Chairpersons/Program Directors to record approval on behalf of the academic second-units, in advance of the monthly meeting.
  • While the application-package is being reviewed by any other second units in the curricular request, the Curriculum Committee, other members of the Academic Council, or members of the Dean's Office, the Chairperson/Program Director of a second unit partnering in the application-package may be addressed by reviewers with questions or concerns about the application. If so, please
    • ensure the query(ies) find the appropriate response(s) expeditiously, consulting colleagues in the application-package as appropriate;
    • if resolution of the query(ies) requires updating of any document(s) in the application-package, update it(them) or direct the Submitter to do so - in either case
      • care should be taken that changes are carried through all pertinent documents so that the application-package remains consistent;
      • a note should be added to the Diary of each document updated confirming that the reviewer's concern has been addressed;
      • a reply should be made to the person who raised the concern, inviting that person to resume review of the application-package.
  • When members of a second unit are substantially involved in the proposal, they as well as members of the proposing academic unit may consider themselves invited to the Academic Council's monthly meeting where the application-package is to be discussed, so that they can address questions and recommendations the Curriculum Committee or any other Council members raise in discussion.
  • At any point while the application-package is under review, down to discussion in the Academic Council's monthly meeting, submitters (possibly in consultation with partnering second units) may determine the application-package should be withdrawn, for further consultation and modification or entirely. If partner-units in the application did not participate in such a decision, they should be notified of it as soon as practicable: they may work with submitters to revise the proposal and make a new application at a future time.
  • If the Council votes to oppose a curricular change, neither the submitters nor their partnering second units may proceed as if the change had been approved, but they may work together to revise the proposal and make a new application at a future time.
  • If the Council votes to table a curricular change, neither the submitters nor their partnering second units may proceed as if the change had been approved, but they should work together to revise the proposal in ways that address the Council's concerns, for reconsideration at a later meeting.
  • If the Council votes to makes its approval conditional on specified amendments, partnering second units should
    • ensure they understand and, to the extent they are involved, approve of the amendments;
    • during the cleanup period following the Council's meeting, double-check those parts of the application-package in which they are concerned and confirm they have been updated so as to reflect the amendments correctly and consistently - work with the submitters as necessary to this result.
  • If the Council votes to approve a curricular change, partnering second units should use the cleanup period following the Council's meeting to double-check that those parts of the application-package in which they are concerned are complete and correct - work with the submitters as necessary to this result.
  • If the changes approved involve courses, they normally appear in LOCUS during the preceding summer if they have been approved for effectiveness in a given Fall term, or during the preceding fall if they have been approved for effectiveness in a given Spring term: in the latter part of that preceding season, partnering second units should double-check the Course Catalog to ensure that all updates in which they are concerned have been made as approved, and work with the submitters if further catching-up is needed.
  • If the changes approved involve changes in the programming of major(s), minor(s), or other academic program(s), the Provost's Office sends submitters notification when the Provost has approved them. Once this approval has been announced, submitters and partnering second units may begin to promulgate information about the changes and their effective date and to take other measures appropriate to the changes' taking effect.
  • As provided for in the By-Laws, members of the College's Academic Council (variously Departmental, Interdisciplinary Program, At-Large, or Student Government Representatives) are appointed to the standing committees including the Curriculum Committee by the Council Chairperson with the approval of the Council. A preliminary Curriculum Committee is formed at the April meeting concluding one academic year so that its members may convene in late August and review proposals for the September meeting beginning the new academic year. The membership of the Curriculum Committee may be updated at the September meeting or later in the academic year, and new members join the Committee's work.
  • Members of the Curriculum Committee work together with exemplary collegiality. The internal workings of the Curriculum Committee are the Curriculum Committee's own to perfect; this account describes the Curriculum Committee's responsibilities to the Council and the College's curricular-review process.
  • Members of the Curriculum Committee review current curricular applications to the Council in advance of the monthly meeting. A preliminary Curriculum Committee is formed at the April meeting concluding one academic year so that its members may convene in late August and review proposals for the September meeting beginning the new academic year. The membership of the Curriculum Committee may be updated at the September meeting or later in the academic year, and new members join the Committee's work.
  • After an application-package has received the approval of the submitting chairperson/program director and any cosignatory chairperson(s)/program director(s) of second unit(s) partnering in the package's application(s), DocFinity moves it for review to the Common Queue for CAS - Academic Council Members BPM:
    • Curriculum Committee members may either search for the application-package by Unique ID using the Search panel or double-click on the appropriate queue in the Job Views panel and then "Check Out" the appropriate Job;
    • Curriculum Committee members review individual documents by clicking the document's check-box in the Search Results panel and then "view" from the toolbar: they review all documents in the package, so as to understand the whole proposal clearly in detail:
      • the Summary Memo identifies the individual Submitter for the application-package, the package's home department or interdisciplinary program, any additional academic unit(s) partnering in the curricular request(s), and the types of request in the package; its Table of Contents outlines component requests, partner(s) in them if any, their intentions briefly, and supplementary documents relating to them: it enables members of the Curriculum Committee, like other reviewers, to understand the application-package as a whole and to navigate its elements efficiently;
      • the individual applications detail component requests and their rationales more fully: they normally are at the principal focus of the Curriculum Committee's attention;
      • supplementary documents severally support the applications: it is helpful for Curriculum Committee members to double-check their details;
    • at the end of any viewing of application-documents, Curriculum Committee members exit and close up any individual documents that are open, and if they used the Job Queue to review the package, they "Return Job" so that DocFinity will let the next user view it readily.
    • The Curriculum Committee has no duty to review any application-package unless the Chairperson/Program Director of the academic home-unit submitting the application(s) shall have recorded approval of the submission in the CAS-AC DocFinity Platform no later than the submission-deadline for the month. Successfully-recorded approval shall appear, time-stamped, in the Diary of the Summary Memo for the application-package.
  • If a member of the Curriculum Committee identifies any inconsistencies among the documents as submitted or other unclarities about the proposal, please
    • make a note of the question in the Diary of the document(s) where it is relevant (open the Diary by clicking the View Diary icon in the toolbar of the Search Results panel where the individual document is selected, click the Add icon in the toolbar of the opened Diary, write the note in the blank text-box that opens, and click Save in the toolbar) - this note both helps to direct the submitters' attention and lets other reviewers know the question has been raised;
    • e-mail the Submitter or other person connected with the application-package who would be able to address the question, outlining it and identifying the document(s) to which that person should return so as to address it;
    • ask the person to whom you write to let you know when the question is addressed and the document(s) are updated;
    • when the document(s) are updated, complete your review;
    • on completing review of the application-package, exit and close up any individual documents that are open, "Return[ing] Job" if in the Job Queue;
    • note your questions and their resolution when the Curriculum Committee discusses the application-package, so that all members of the Committee understand the package in its most-finalized form to date.
  • Members of the Curriculum Committee discuss together all application-packages submitted for the current month's review and action by the Academic Council as a whole:
    • they register any corrections made in the package during the review, so that all members of the Committee understand the package in its most-finalized form to date (it is normally not necessary to report corrections further, but the Council needs the Committee to consider all matters that may have a bearing on the applications' substance);
    • they assess the academic merits of the curricular change(s) proposed;
    • they consider whether, and how best, the proposal(s) could be clarified or strengthened so as to serve students, participating academic units, the College, and the University better academically;
    • they formulate the Committee's recommendations for the Academic Council.
  • To the extent it is practicable, it is helpful for a designated member of the Curriculum Committee to communicate the Committee's thoughts to each group of submitters ahead of the Academic Council meeting at which their application-package is to be discussed, outlining any concerns the Committee feels or anticipates the Council may feel and working with the submitters so as to address them appropriately. If any changes are made in the application-documents at this stage it is important that the Committee Chairperson be kept apprised of them.
  • The Curriculum Committee's Chairperson for the month, or another member designated by the Committee, prepares the Committee's report for the Academic Council.
  • The Curriculum Committee, as its Chairperson shall delegate, on the day of the monthly meeting at which an application-package is to be discussed by the Council, shall double-check the application-package for outstanding approvals. At the meeting the Committee shall withhold its recommendation to approve any applications still lacking their full sets of approvals on that day. Successfully-recorded approval shall appear, time-stamped, in the Diary of the Summary Memo for the application-package. (If the Council determines a missing co-signatory approval is secondary, not integral, to the application [e.g., an unapproved cross-listing may be dropped and a proposed New Course still go forward if it is otherwise fully approved, but a New interdisciplinary Major/Minor may not go forward without the approval of all its participating academic units], the Council may vote on the application with the unapproved element stripped out, as a friendly amendment in light of which the submitters must undertake to amend all pertinent documents during the cleanup period. It is preferable for submitters to submit application-packages only after securing approval in principle from all partnering stakeholders in advance, and for the stakeholders' Chairpersons/Program Directors to record approval on behalf of the academic second-units, in advance of the monthly meeting.)
  • At the Academic Council's monthly meeting,
    • the Curriculum Committee's Chairperson for the month, or another member designated by the Committee, presents the Committee's recommendations to the Council;
    • as needed so that all Council members may understand clearly, the Curriculum Committee's Chairperson for the month or other members of the Committee explain any qualifications in the Committee's report or divisions among Committee members; they make every effort to present the Submitters' position clearly or they defer to Submitters present to speak for their proposal directly;
    • members of the Curriculum Committee including the Chairperson for the month vote together with the other voting members of the Academic Council, in the best interests of the College's academic mission and in light of the Council's discussion.
  • Following the Academic Council's monthly meeting, the Curriculum Committee's Chairperson for the month or other members of the Committee as appropriate remain available to help submitters address the Committee's and Council's concerns in any revisions and later re-submission of applications (if the Council votes to oppose or to table an application) or to incorporate amendments conditioning the Council's approval or other cleanup (if the Council votes to approve an application conditionally or simply).
  • As established by the Charter of the Academic Council of the College of Arts and Sciences, a representative of each of the departments or other academic units of the College of Arts and Sciences, at-large representatives of the faculty of the College, and representatives of Student Government of Loyola Chicago shall be included as voting members of the Council. This account describes particularly the representatives' responsibilities to the Council in the College's curricular-review process, but more generally representatives are expected:
    • to be familiar with the Charter and By-Laws of the Academic Council, and by upholding their terms to preserve the collegiality and good functioning of the College, in curricular and other matters.
    • to attend all meetings of the Council or, if they will be unable to attend a particular meeting, with the approval of the entity they represent to send a knowledgeable substitute (please tell the Chairperson of the Council, the Associate Dean for Academic Affairs, and the Assistant Director for Communications when a representative will be absent and a substitute will be attending, and who);
    • to be attentive to the interests of the entity they represent in the Council's deliberations, and to bring that entity's perspective to the Council;
    • to consider, to deliberate, and to vote in Council in the best interests of the entity they represent and of the College and the University as wholes, particularly their academic mission;
    • to communicate the Council's decisions in curricular matters and deliberations in all matters to the entity they represent, each month.
  • All members of the Academic Council review current curricular applications to the Council in advance of the monthly meeting, so that they may confer with colleagues in the entity they represent about concerns relating to it and offer submitters and the Council the best advice they can concerning all proposals:
    • Council members may either search for individual application-packages by Unique ID using the Search panel or double-click on the Common Queue for CAS - Academic Council Members BPM in the Job Views panel and then "Check Out" each Job individually;
    • Council members review individual documents by clicking the document's check-box in the Search Results panel and then "view" from the toolbar: they should review at least the Summary Memo and the individual applications of each application-package, so as to understand the whole proposal, and supplementary documents as needed to clarify and confirm detail;
    • on completing review of the application-package, Council members exit and close up any individual documents that are open, and if they used the Job Queue to review the package, they "Return Job" so that DocFinity will let the next user view it readily.
  • If a Council member identifies any inconsistencies among the documents as submitted or other unclarities about the proposal, please
    • make a note of the question in the Diary of the document(s) where it is relevant (open the Diary by clicking the View Diary icon in the toolbar of the Search Results panel where the individual document is selected, click the Add icon in the toolbar of the opened Diary, write the note in the blank text-box that opens, and click Save in the toolbar) - this note both helps to direct the submitters' attention and lets other reviewers know the question has been raised;
    • e-mail the Submitter or other person connected with the application-package who would be able to address the question, outlining it and identifying the document(s) to which that person should return so as to address it;
    • ask the person to whom you write to let you know when the question is addressed and the document(s) are updated;
    • when the document(s) are updated, complete your review;
    • at the end of any viewing of application-documents, exit and close up any individual documents that are open, "Return[ing] Job" if in the Job Queue.
  • At the Academic Council's monthly meeting, Council members:
    • attend to the Curriculum Committee's recommendations;
    • raise any concerns of the entity they represent regarding any curricular proposal, or make any other suggestions they judge will help improve the proposal;
    • deliberate constructively, with constant regard to students' benefit, the academic units' and College's mission, and necessary constraints such as the University's administrative structures and timetables;
    • vote on proposals in the best interests of the College's academic mission and in light of the Council's discussion.
  • Following the Academic Council's monthly meeting, Council members whose remarks have figured significantly in the Council's discussion, especially regarding any modifications of proposals (whether adopted by friendly amendment or to be incorporated in a revised proposal later), would benefit their colleagues by remaining available to submitters as they address concerns with their application-packages.
  •  As provided for in the By-Laws, the Council members elect the Chairperson of the Academic Council of the College of Arts and Sciences as the last item of new business at the April meeting concluding one academic year, so that the Chairperson will be in place for the whole of the following academic year. The Chairperson's responsibilities are implied by the By-Laws. Generally, the Chairperson like all members of the Council should be familiar with the Charter and By-Laws of the Academic Council, and by upholding their terms should help preserve the collegiality and good functioning of the College, in curricular and other matters. This account describes particularly the Chairperson's responsibilities in the Council's review of proposed curricular changes.
  • The Chairperson, like all members of the Academic Council, reviews current curricular applications to the Council in advance of the monthly meeting:
    • the Chairperson may either search for individual application-packages by Unique ID using the Search panel or double-click on the Common Queue for CAS - Academic Council Members BPM in the Job Views panel and then "Check Out" each Job individually;
    • the Chairperson reviews individual documents by clicking the document's check-box in the Search Results panel and then "view" from the toolbar: the Chairperson should review at least the Summary Memo and the individual applications of each application-package, so as to understand the whole proposal, and supplementary documents as needed to clarify and confirm detail;
    • on completing review of the application-package, the Chairperson exits and closes up any individual documents that are open, "Return[ing] Job" if in the Job Queue so that DocFinity will let the next user view it readily.
  • If the Chairperson identifies any inconsistencies among the documents as submitted or other unclarities about the proposal, please
    • make a note of the question in the Diary of the document(s) where it is relevant (open the Diary by clicking the View Diary icon in the toolbar of the Search Results panel where the individual document is selected, click the Add icon in the toolbar of the opened Diary, write the note in the blank text-box that opens, and click Save in the toolbar) - this note both helps to direct the submitters' attention and lets other reviewers know the question has been raised;
    • e-mail the Submitter or other person connected with the application-package who would be able to address the question, outlining it and identifying the document(s) to which that person should return so as to address it;
    • ask the person to whom you write to let you know when the question is addressed and the document(s) are updated;
    • when the document(s) are updated, complete your review;
    • at the end of any viewing of application-documents, exit and close up any individual documents that are open, "Return[ing] Job" if in the Job Queue.
  • In preparation for the Academic Council's monthly meeting, the Chairperson:
    • is in communication with the monthly Chairperson of the Curriculum Committee, the Associate Dean for Academic Affairs, the Assistant Director for Communicaion and Academic Affairs, and, as necessary, submitters and partners in proposals and/or Council representatives whose home units have concerns about any application packages, so as to be aware of likely topics for the Council's deliberations;
    • prepares an agenda for the meeting;
    • prepares to conduct the Council's deliberations concerning proposed curricular changes and other matters before the Council.
  • At the Academic Council's monthly meeting, the Chairperson:
    • conducts the meeting, pursuant to the By-Laws;
    • attends to the Curriculum Committee's recommendations;
    • to the extent practicable, ensures that concerns brought to the Council regarding any proposal or suggestions for proposals' improvement are aired fully and fairly and receive due discussion;
    • fosters the Council's constructive collaboration within the context of academic units' and the College's mission and administrative structures;
    • officiates over Council members' voting and votes as a member of the Council.
  • Following the Academic Council's monthly meeting, the Chairperson:
    • remains available to submitters as they address concerns with their application-packages;
    • receives notification from submitters when any amendments conditioning the Council's approval of a proposal have been incorporated and any other cleanup completed;
    • signs off in DocFinity the Council's approval of all approved and cleaned-up application-packages for the month:
      • in DocFinity, in the Jobs panel, "Check[s] Out" the approved and cleaned-up Job;
      • in the Tasks panel, checks the box "Is the Submission Complete?" and replies by selecting "Submission Complete," then checks the box for approval and replies by selecting "approved";
      • signs out of the Tasks panel by clicking the "Complete Job" icon in the toolbar;
      • advises the Dean's Executive Assistant the Council's approval has been recorded.
  • The Associate Dean for Academic Affairs of the College of Arts and Sciences works with the Academic Council so as to facilitate the College's collaboration in academic and curricular matters: this account describes those endeavors.
  • The Associate Dean seeks to know University policies that affect academic and curricular concerns of the College, and to transmit pertinent information to parties involved.
  • The Associate Dean is familiar with the Charter and By-Laws of the Academic Council, and aims by upholding their terms to preserve the collegiality and good functioning of the College, in curricular and other matters.
  • The Associate Dean strives to understand how University systems supporting academic operations work, and to recommend measures that will effect academic units' curricular designs soundly.
    • The Associate Dean's expertise in forms designed for use in Council processes and for interfacing with other University entities arises from this activity.
    • Because forms transmit operational information to entities with different functions, expertise, and perspective across the University, the Associate Dean is obliged to insist on accuracy and consistency across documents, even when the information may seem redundant.
  • The Associate Dean researches academic and curricular history of the College, its academic units, and their course-catalogue, and works to preserve the effectiveness of the College's curricular designs as approved in valid process.
    • The Associate Dean's concern for record-keeping arises from this activity.
    • Please direct inquiries about apparent programming-errors in LOCUS to the Associate Dean.
  • The Associate Dean advises submitters as they design curricular changes and as they prepare paperwork for the Council's review, at the submitters' request and as far as, amid the Associate Dean's, submitters', and Council members' other duties, the constraints of the Council's reviewing-schedule allow for constructive intervention.
  • The Associate Dean backs up the Assistant Director for Communications and Academic Affairs in trouble-shooting submitters', chairpersons'/program directors', and Council members' use of the CAS-AC DocFinity platform.
  • The Associate Dean serves as a consultant for the Curriculum Committee, at Committee members' request.
  • The Associate Dean is available to Council members, at their request, for inquiries regarding curricular questions.
  • The Associate Dean consults with the Chairperson of the Academic Council, the Chairperson of the Curriculum Committee each month, and the Assistant Director for Communications and Academic Affairs concerning the agenda for the monthly meeting.
  • The Associate Dean attends the meetings of the Academic Council and undertakes to support their good order and functioning.
    • The Associate Dean may provide information to Council discussions about University and College policies and practices, and about curricular requests under review, as requested or as the information pertains to the discussion and is not otherwise supplied.
    • The Associate Dean assists with record-keeping of Council meetings, including preparation and amendment of the Minutes.
    • The Associate Dean is not a voting member of the Council.
  • The Academic Council has deputed some curricular changes to the Associate Dean for administrative action:
    • discontinuing an inactive major;
    • discontinuing an inactive minor;
    • discontinuing an inactive course;
    • discontinuing an inactive course from an active major or minor;
    • re-numbering a course;
    • approving specific sections of courses in specific semesters for a temporary tag or cross-listing (see instructions).