Go to top of page

PIR Half Year Load Estimates (PLE) file scope

Version Details

Version: 1.0
First Year: 2015
Last Year: -


Providers approved under the Opens in a new window: Tertiary Education Quality and Standards Agency Act 2011 (TEQSA Act) must report preliminary EFTSL data. The data reported should include students enrolled between 1 January and 30 June of the reporting year.

The data reported in the Half Year Load Estimates submission is reported EFTSL at an aggregated level.

Return to top


Update 2021: The Timing details below were as at TEQSA's official request from 2017. In 2021 the Provider Information Request is due to be reported and verified by 30 June. Any advice referencing 31 August has been superseded but is retained for historical purposes.

The Half Year Load Estimates submission is due by 31 August. Data can be submitted from 1 July – 31 August.

The submission date in the reporting schedule is the final deadline when data should be received by the department. Data can be submitted prior to the due date and early submission is encouraged.

Return to top

Submission method

Submissions are made using the Higher Education Provider Client Assistance Tool (HEPCAT). More information about this process is in the HEPCAT user guide Part 2.

Return to top


Information about the structure and elements in the Half Year Load Estimates submission is in the structure guidelines for the relevant reporting year.

Each record in the Half Year Load Estimates submission must have a unique combination of values for:

These elements are the key identifiers for a record.

Return to top


Generally revisions to course of study data must be coordinated through the department.

A revision can only be made to course information where a particular code has been reported incorrectly through a genuine administrative error. For example, if an incorrect value was reported for any of the key elements they can be revised to reflect the correct information.

Return to top

More information

For more information about terms used in these guidelines see the glossary.

Return to top