E10 - Line results: Student allocations

Modified on Fri, 24 Apr at 3:20 AM

TABLE OF CONTENTS

Preamble

Analysing the Line results includes reviewing individual student allocations, especially for those missing main preferences and with incomplete programs. The Student allocations screen can help explain why subjects weren't granted and allows manual changes if needed.


Student allocations

How to access

  • Navigate to Lines > Line results > Student allocations, select the student from the drop down at the top right; or
  • Navigate to Lines > Line results > Student results, double click on any student.

What you will see

  1. Student's preferences on the left, Main and Reserves separated by a thick line
  2. Line numbers across the top, including a column for any dropped classes
  3. Green = allocated classes
  4. Grey = missed preference/ not allocated 
  5. Peach = same as grey cells, except the course belongs to a different year level (multi year dataset only)
  6. Class sizes, an * indicates class is at capacity


NOTE
Any courses the student has not selected as preferences will not be displayed on this screen.


Interpreting Student Allocations

Example 1. The student was granted all main preferences: Pref1 on Line 3, Pref2 on Line 2, and Pref3 on Line 1. Pref4 to Pref 6 are reserve preferences.

Example 2. The student was granted Pref1 and Pref3, but missed on Pref2 as 8PER did not run. Also missed Pref 4 (8OES) on Line 2,  due to a clash with a higher preference 8FOO. The student has been placed in 8INF on Line 1, so has a full program and requires no further counselling.



Example 3. The student needs six classes for a full program but none of their preferences fall on Line 4, creating a gap. They must be counselled to pick an alternate course in Line 4.
Note the following:
  • Three 10CHE classes run, one each in Lines 1, 2 and 3. This student has been placed into Line 1.
  • Line 2 10CHE class is at capacity, indicated by an asterisk.
  • Line 3 10CHE class is over capacity, indicated by the red highlight.

ALERT 
Over capacity can only occur when the user manually allocate students into the class after the lines were generated. See the Manual Changes section below.


Manual Changes

Although the system generates the best overall outcome for students, users may sometimes need to make manual student allocation changes. For example:
  • Student wants to be placed into a class that was originally at a lower preference.
  • A new student has been added after line generation and must be manually placed to avoid disrupting existing student allocations.


TIP
Manual changes can also be used to test alternative outcomes for certain students while iterating through the line generation process.


IMPORTANT 
Manual changes should only occur after forms are closed, after lines are generated and before classes are created.
Manual changes after class creation will not be translated across to classes unless Create classes is rerun.
Once classes are created, changes must be done via standard classlist management screens (Students > My Classes or Class List Manager).


How to make manual changes

  1. In Student allocations screen, find the class on the appropriate line.
  2. Double click on the preferred grey class. A warning will appear in the first instance of any session.
  3. Click "Allow changes to DRAFT class lists".


Example

The student was granted Pref5 (10MUS) in Line 5 but must be moved to Pref 7 (10DRA). As classes are not yet created, this change can be done in Student allocations screen by double clicking 10DRA and selecting 'Allow changes to DRAFT class lists'. 


The student is now allocated to 10DRA (green) increasing the class size to 11; 10MUS is now grey and class size reduced to 7.
WARNING 
All manual changes will be lost if you run Generate lines, Optimise or Populate classes again.



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article