Course preferences packet 2025
Version Details
- Version:
- 1.00
The course preferences packet is used to report all preferences listed on an application for current higher education undergraduate award courses submitted directly to a Table A or Table B provider. Each course preferences packet must be linked to an established course applications packet.
Scope
Table A and Table B providers that receive direct applications are required to report one or more course preferences packets for every preference listed in an application the provider has reported through a course application packet. That is, a course preferences packet must be reported for each valid application lodged by a domestic applicant where the application contains at least one preference for a Commonwealth supported place in a higher education undergraduate award course.
A course preferences packet must be reported for each preference listed by the applicant on a valid application. This includes current preferences for courses cancelled by providers and current preferences for courses for which the applicant is not eligible. The reported course preferences for an application may also include:
- bridging, enabling or non‑award courses
- postgraduate courses
- domestic fee‑paying undergraduate courses
- courses offered in the vocational, education and training sector.
Reporting deadlines
The reference date for the preliminary 2025 University Applications and Offers Collection is 29 Jan 2025. The preliminary 2025 University Applications and Offers Collection is due on 12 Feb 2025.
The reference date for the final 2025 University Applications and Offers Collection is 14 May 2025. The final 2025 University Applications and Offers Collection is due on 28 May 2025.
Initial reporting requirement
| Element | Required reporting |
|---|---|
| *UID23: Course applications resource key or E700 / E415: Unique application combination | Required for all in-scope course preferences |
Initial reporting requirement - Extension: course preferences
| Element | Required reporting |
|---|---|
| *E713: Preference ordinal position | Required for all in-scope course preferences |
| *E306: Provider code | Required for all in-scope course preferences |
| *E310: Course of study type | Required for all in-scope course preferences |
| *E724: Sector code | Required for all in-scope course preferences |
| *E709: Intake year | Required for all in-scope course preferences |
| E461: Field of education code | Required for all in-scope course preferences |
| E462: Field of education supplementary code | Required for all in-scope course preferences |
| E744: Intake month | Required for all in-scope course preferences |
| E559: Campus postcode | Required for all in-scope course preferences |
| E329: Mode of attendance code | Required for all in-scope course preferences |
*These elements must be reported together when a course preferences packet is created
Uniqueness
Each course preferences packet must have a unique combination of the values for:
- course application identifier (UID23 or combination of E700/E415)
- preference ordinal position (E713)*
*B2G API users may report multiple preference packets with preference ordinal position (E713) with the same allowable value of '00' or '99'
Revising and adding data
A provider can correct any data already in a course preferences packet, if required. A provider may create as many additional course preference packets as necessary to add course preferences to a course application.
TCSI Data Entry file upload
Templates for TCSI Data Entry are available on the Higher education file templates page.
