Class summaries
On this page you will find detailed instructions on what a class summary is, how to create one in the CMS and how to complete each field in the class summary template in CMS.
If in doubt about where to start, please email science.curriculum@anu.edu.au

Related policies and procedures

How to guides and supporting documents

Document nameContents
Detailed information on how to complete each section of the form, including formatting restrictions
Click through guide on how to create and progress class summaries in CMS
Protocols for when class summaries can be approved at the school or referred to the college
When a class summary is cloned from a previous year, some of the key policy default statements need to be reviewed to ensure out-dated does not carry across into the new class summary.
Can be used to fill sections as appropriate

General information

A class is every instance in which a course is delivered. It is the "child" of a "parent" object: the course. A class summary contains information that is relevant to the year-on-year delivery of the course and is more dynamic than the course content that is published in the course entry in P&C.

ANU policy and our external regulators require all courses to have a class summary approved by the relevant Delegated Authority and available to students in the Learning Management System no later than two weeks before the start of the relevant teaching period. Some courses have multiple classes associated with them (eg for different modes of delivery or variable unit values) and some courses may be co-taught at different career (UG/PG/HDR) levels. Each class has a unique identifier (class number). All classes must have their own class summary.

Class summary information is published on the Programs & Courses catalogue and includes, at minimum:

  • Course description (cloned from course overview)
  • Learning outcomes (cloned from course overview)
  • Assessment for the session of delivery, linked to the relevant learning outcomes
  • Assessment due dates and return dates
  • Assessment details
  • Advise on whether the use of Artificial Intelligence is allowable/not allowable for any given assessment task.
  • Late submission policy
  • Inherent requirements information, if appropriate
  • Approved hurdle requirements, if appropriate
  • Honours Pathway Option information (if applicable), including opt-in/opt-out mechanisms
  • Field activities information (if applicable), including additional costs
  • Feedback details

Published example

Workflow:

  1. Proposal initiated by course convener or school administrator (CMS state: Draft)
  2. Proposal finalised by course convener and progressed to school administrator for review (CMS state: Submitted for review)
  3. Proposal reviewed by school administrator and progressed to Associate Director (Education) for approval: CMS state: Delegate Approval pending)
  4. Proposal reviewed by Associate Director (Education) (CMS state: Approved or Pending Feedback Resolution
  5. Approved proposals are published by the school administrator
  6. Proposals that are Pending Feedback Resolution return to step 2 

Suggested timelines for submission through the CMS for review and approval

  • Summer: 3 weeks before course commencement
  • Semester 1: Second Friday in January
  • Autumn: 3 weeks before course commencement
  • Winter: 3 weeks before course commencement
  • Semester 2: Second Friday in May
  • Spring: 3 weeks before course commencement

Publication deadline

2 weeks prior to the start of the semester/course