This page contains Frequently Asked Questions (FAQs) about Data and Reporting related to the National Higher Education Code to Prevent and Respond to Gender-based Violence (National Code). These FAQs are based on queries raised following the release of the Guidance on Collecting Annual Reporting Data and in a subsequent webinar on data and reporting.
On this page:
The National Higher Education Code to Prevent and Respond to Gender-based Violence and the Guidance on Collecting Annual Reporting Data should be primary sources for clarity on Annual Reporting requirements.
This is a living resource and will be updated over time as new questions arise. If you are a provider and have questions regarding your legislated reporting requirements, you can contact the GBV Regulator via GBVRegulator@education.gov.au
The Guidance on Collecting Annual Reporting Data should be the key source for anyone seeking guidance on Annual Data Reporting to the GBV Regulator.
Use and publication of data reporting
How the GBV Regulator will use annual reporting data?
The GBV Regulator is an outcomes-based regulator, focused on whether providers’ systems and approaches are effectively preventing and responding to gender-based violence, rather than on technical compliance with individual data points in isolation.
We will use reported data to understand risk, trends and maturity over time, and to guide proportionate, supportive regulatory engagement rather than taking punitive action based on single indicators.
There are two key ways we will use annual reporting data:
To monitor provider compliance with the National Code:
- We will use certain elements in annual data reporting data, alongside other sources of information, to assess provider compliance with the National Code and inform its compliance monitoring priorities.
- This does not mean a concerning data point will automatically or immediately result in deeming a provider non-compliant. Given the quantitative nature of the data requested it is most likely to be used to flag areas where we may want to request further information to undertake further regulatory action, including requesting additional information from a provider.
- For example, if data indicates that a provider is consistently not meeting the 45-day timeframe for resolving formal reports of gender-based violence, we may seek more information to determine whether there may be underlying issues with that provider’s systems and processes. This could identify that there are valid reasons for the length of time taken to complete these processes and therefore no further compliance action is required.
To support identification of sector wide risks, trends, and systemic issues:
- Data plays a critical role in understanding the nature and prevalence of gender-based violence, identifying the needs of diverse groups, measuring progress and informing policy and program design for continuous improvement.
- Reported data will help us as a regulator to analyse patterns in gender-based violence incidents across the sector- this is why the data is being requested at the ‘incident’ level rather than in an aggregated form.
- This analysis of sector wide risks, trends, and systemic issues will inform guidance, capacity building, and continuous improvement across the sector.
Will the regulator require individual university data be published?
The National Code and the GBV Regulator does not expect providers to publish individual data.
The GBV Regulator will consider what sector-wide information may be appropriate to share publicly and will consult with providers before publishing any data.
Should bystander reporting be actively promoted at the university?
Bystander reporting can play an important role in identifying risks and enabling timely, effective responses.
In line with the intent of the National Code, providers can promote bystander reporting so that individual members of their community are aware of behaviours that may constitute gender based violence and can take appropriate action and report it if they witness it. This will support providers having a fuller picture of the gender-based violence that is occurring in their community.
Bystanders should also be encouraged to seek support from their provider where needed, consistent with trauma informed and person centred approaches to preventing and responding to gender based violence.
Annual data reporting scope and definitions
How does the GBV Regulator use the term ‘incident’ with regards to annual data reporting?
The GBV Regulator acknowledges that gender-based violence is rarely a single, isolated event and we were aware the term ‘incident’ may cause some confusion.
We use the term ‘incident’ to refer to occurrences of gender-based violence, in alignment with the wording of the National Code, however we recognise that this terminology can unintentionally reinforce individualised responses and obscure the systemic and structural nature of gender-based violence.
What is an in-scope incident?
An in-scope incident is any incident which:
- relates to an allegation of gender-based violence perpetrated by or against a student or staff member of the higher education provider
- is disclosed or reported to the higher education provider, or a relevant student accommodation provider (as per Standard 7).
Will data be required on the discloser, reporter and respondent?
Yes, although the primary focus is on collecting data about the discloser and respondent.
The Data Elements table in Appendix A of the Guidance on Collecting Annual Reporting Data includes all data elements providers will be required to collect. These are broken into four categories:
- Elements relating to the disclosure/formal report and incident details, including who made the disclosure or formal report? (Page 19, Data element No. 4)
- Elements relating to the Discloser
- Elements relating to the Respondent
- Elements relating to the provider/student accommodation provider’s response.
Is a third party or bystander the ‘discloser’ if they are not the person who experienced the behaviour but they reported it? Or is the ‘discloser’ always the person who experienced the behaviour?
The terms Discloser and Disclosure are used throughout the National Code and Guidance on Collecting Annual Reporting Data.
It is important to acknowledge these are distinct terms with distinct meanings under the National Code:
- Discloser means a person who has shared their experience of Gender-based Violence. In practical terms, this will often be a victim-survivor. It is possible that the Discloser may not be the person reporting the incident.
- Disclosure means the provision of information about a person's experience of Gender-based Violence to a Provider by the Discloser or another person. It is possible that the Disclosure may be made by a person other than the Discloser.
Will we only have to report on incidents and disclosures, or also on prevention and training initiatives?
The Guidance on Collecting Annual Reporting Data only relates to annual data reporting requirements under Standards 6.12-6.14 of the National Code. This is a prescribed reporting requirement that providers must comply with on an annual basis.
Standard 6 of the National Code also sets out a range of other data that the Regulator may request from a provider. Specific examples of the types of data that may be requested are outlined at Standards 6.8 – 6.11 and includes things like process data on implementation of policies, procedures, plans and related activities, like prevention and training initiatives.
Providers must ensure they have familiarised themselves with these requirements to ensure compliance with any future requests for data. Requests for this kind of data will likely be made on an ad hoc basis or through other mechanisms, such as progress reporting.
Providers should also be tracking data on broader initiatives and actions to prevent and respond to gender-based violence to support progress reporting against their whole of organisation plan which is due 6 monthly to the governing body and each 2 years to us as the Regulator.
Will Child Safe Organisation Act requirements be included so that reporting of incidents involving children (under 18) can be done at the same time?
Compliance with state or territory legislation, such as the Queensland Government’s Child Safe Organisation Act, is the responsibility of individual providers.
The scope of the annual data reporting requirements is limited to gender‑based violence data as outlined in the National Code. For annual data reporting, the GBV Regulator will not require inclusion of any data beyond what is noted as required under Standards 6.12 – 6.14 of the National Code.
This does not preclude providers from streamlining their own processes and collecting broader data in their own systems, such as obligations under state/territory or other Commonwealth legislation.
Annual Data Collection
When are providers required to begin collecting data on incidences of gender-based violence?
Under the National Code, providers are required to begin collecting data on the incidences of gender-based violence:
- From 1 January 2026 for Table A and B providers
- From 1 January 2027 for all other providers registered under the Tertiary Education Quality and Standards Agency Act 2011
Data must be collected each calendar year and reported to the GBV Regulator by 30 June of the following year.
How should providers manage discrepancies in data collected before and after guidance was issued by the Regulator?
The GBV Regulator acknowledges that Table A and B providers were required to commence data collection from 1 January 2026, and that the Guidance on Collecting Annual Reporting Data was not published until March 2026.
The data elements outlined in the Guidance on Collecting Annual Reporting Data will be those required for reporting to the GBV Regulator. Where providers were unable to collect data in line with the Guidance, relevant data fields can be marked as ‘unknown or N/A’.
Providers should clearly note any such gaps or discrepancies when submitting their annual reporting data.
Do we need to report on all 78 data elements for every incident?
The GBV Regulator acknowledges the National Code introduces significant requirements for the collection of data related to instances of gender-based violence, and it may take time to implement mature data collection processes and systems which align with these requirements.
As the National Code establishes legal requirements, all data reporting obligations are required by law. However, we are adopting a phased approach to data collection.
In recognition of this, the data elements table outlined at Appendix A of the Guidance on Collecting Annual Reporting Data indicates whether a data element is:
- Required from year one – these data elements must be included in all reporting from the commencement of the National Code. These elements relate to basic information about incidents, disclosers and respondents, as well as the provider’s response to the incident and it is expected providers will already be collecting this information.
- Required once mature – these data elements may be listed as ‘unknown’ or ‘N/A’ in the first 1-2 years of reporting to the GBV Regulator, recognising that these elements may not have previously been collected by the provider and will require time to collect safely and effectively. These elements relate to more detailed information about incidents, disclosers and respondents.
Some data elements are “mandatory” from the get-go and others are not. Does this mean that we shouldn’t worry about the non-mandatory for now?
The GBV Regulator understands providers are at different stages of readiness in their data collection systems, and some elements may require time to build capacity and implement safely. This is why there is distinction between data elements required from year one and data elements that may take longer to collect safely.
Over time providers will be expected to show active progress toward collecting all required data - for example updating systems and processes to enable full collection.
It is important to consider this longer-term view when making any systems or process upgrades or investments.
Will we be able to leave blank data fields if we do not have that particular data?
For each reported incident, all data element fields must contain a value (as per the accepted values column in Appendix A of the Guidance on Collecting Annual Reporting Data.
This means that where a field is not applicable, or the provider does not have the data, it must be marked ‘N/A’ rather than being left blank. This ensures that data integrity and quality is maintained when the data is uploaded into the GBV Regulator’s system.
Why doesn’t violence type include family/domestic violence or intimate partner violence?
The data elements table at Appendix A of the Guidance on Collecting Annual Reporting Data includes a list of accepted values for types of gender-based violence, consistent with the definition in the National Code.
The types of violence include, for example, sexual harassment, systems abuse, physical and non-physical violence. These can all be features of what may happen across different contexts of violence, for example, within a family or domestic relationship, a dating or intimate partner relationship or in the workplace. For consistency, the list of types is limited to the nature of the act or acts of violence.
Other data elements are deliberately included to cover the context for acts of violence - those being:
- discloser relationship to respondent
- number of Respondents involved
- additional persons or accomplices involved; and
- location.
Cross referencing data elements will allow both providers and the Regulator to identify forms of violence we know to be common including family and domestic violence, intimate partner dating violence and workplace sexual harassment.
The GBV Regulator acknowledges that the types of gender-based violence may not exactly correlate with provider’s existing systems, however there is a need to collect data consistently across the sector which will enable effective analysis.
Providers can still choose to collect additional information about the types of gender-based violence being reported, provided they can meet the specific reporting requirements of the GBV Regulator.
How do providers report on historic or ongoing incidents?
All incidents of gender-based violence disclosed or reported to the provider within a reporting period must be included in annual data reporting, regardless of when the incident occurred, and including where the matter is still ongoing (for example, where investigations or appeals are still underway).
For example, if someone discloses or formally reports an incident that occurred prior to the reporting period, this should still be included in annual data reporting for that period. In reporting the incident, you will need to include the date of the incident, which will demonstrate if, for example, it is a historical or recent incident.
If an incident is ongoing at the end of the reporting period, it must still be included in the data reporting for that period. The provider will be able to report the incident as ‘ongoing’ as per Appendix A of the Guidance on Collecting Annual Reporting Data.
The GBV Regulator may separately follow-up with providers to seek information regarding the outcomes of incidents which were reported as ongoing to ensure compliance with the National Code, as appropriate.
Will additional sub-categories be created to support data collection?
No, there is no plan to add any additional sub-categories to the data elements outlined in Appendix A of the Guidance on Collecting Annual Reporting Data.
The GBV Regulator recognises the need to provide certainty regarding data collection and reporting requirements to enable providers to adapt or develop their IT systems.
Will there be an option in future to identify if a student was domestic or from overseas?
Where a discloser or respondent is a student, the current data elements capture whether the student is a domestic or overseas student, where the student was born, and their primary spoken language.
All of these are detailed in the accepted values column on pages 22 to 32 of the Guidance on Collecting Annual Reporting Data and are intended to support consistent and comparable reporting across the sector.
Do we need to collect and report data on incidents that do not relate to a student or staff member?
The National Code sets out requirements regarding students and staff of higher education providers. If an incident only involves third parties (for example, between members of the public who are accessing the university’s campus), it falls outside the scope of the National Code and should not be reported through the annual data reporting process.
If an incident occurs on provider property, providers may still have a duty of care to support an appropriate response or consider risks that the incident highlighted and take action to mitigate these to ensure student and staff safety.
Providers are being required to record sensitive information, for example, sexuality, religious affiliation or sex assigned at birth. Does this conflict with a person‑centred and trauma‑informed approach and can you clarify how this should be managed?
In line with the National Code, all data collection processes must be trauma‑informed and person‑centred, and providers need to prioritise safety, privacy and security when engaging with students and staff.
We recognise that some providers may not yet have the systems or processes in place to capture sensitive information safely and effectively, and this is why these elements are currently identified as ‘required when mature’ (see Pages 14-15 of the Guidance on Collecting Annual Reporting Data).
Providers are not required to collect data elements if doing so would compromise a trauma‑informed approach. Providers should use their judgement in how and when sensitive questions are asked to ensure individuals feel safe and supported.
Where it is possible to collect data in a safe and trauma informed way, all data fields should be completed but where this is not possible, providers can mark these elements as unknown.
Sometimes a provider may be aware that a student is Indigenous, but not know if they are Aboriginal, Torres Strait Islander, or both. How should this be managed?
Providers must make efforts to collect the data as required in Appendix A of the Guidance on Collecting Annual Reporting Data). where it is possible to collect that data in a safe and trauma-informed way.
Where a provider is not able to collect a specific data element safely, the data element should be marked as ‘unknown’ as per the accepted values column. This ensures that data integrity and quality is maintained when the data is reported to the GBV Regulator.
For example, in a scenario in which a provider does not know the indigenous status of a student or staff member, and they cannot safely collect this information, this data element should be marked ‘unknown’.
Are Providers required to report pre-existing complaints (i.e. lodged prior to 1 January 2026) that remain ongoing or were finalised after 1 Jan 2026?
No. Where an incident was reported to the provider prior to 1 January 2026 it must not be included in the annual reporting for 2026. The same approach will apply for non-university higher education providers in 2027.
Providers should still seek to align their approach to managing any outstanding disclosures in line with the Standards of the National Code to ensure an effective and safe response for disclosers and respondents.
One of the data elements asks, ‘when was the victim/survivor first enrolled in their current course’, how is this relevant and are you looking for the first date they interacted with this university/course or the most recent course?
The date/data that the GBV Regulator is seeking here is when was the student first enrolled in their current course of study.
Appendix A of the Guidance on Collecting Annual Reporting Data requires providers to record the month and year that a student commenced their current course of study, where they are a Discloser or Respondent.
Collecting and reporting on this data supports identification of any trends or patterns to inform whether there are particular times in a student’s study journey where they are at a higher risk.
The GBV Regulator recognises that study journeys are not linear and interruptions to study might be long or short depending on people’s circumstances and needs. Having the date of when the student first enrolled in current course is useful as gives an indication of timing; it tells us at what stage of the study journey an incident happened.
Can you tell us whether and how the location of incidents will be reported? And how third-party organisations (not only student accommodation providers) may be listed?
Appendix A of the Guidance on Collecting Annual Reporting Data outlines required data elements and accepted values for each element.
Data element 15 specifically requires a provider to report the location/s that the incident/s took place, and provides a list of locations as accepted values.
Accepted values include multiple off-campus settings, as well as other which should allow for reporting the location of an incident at a third-party organisation’s property.
Data duplication and incident counting and recording
What happens if the same incident is reported to the provider and to the student accommodation provider? How should this be reported to avoid duplication?
To avoid compromising the integrity of data, Higher Education providers must ensure they have arrangements in place with student accommodation providers to avoid duplication of data wherever possible. For example, where an incident may have been reported to both the student accommodation provider and the higher education provider, this should only be recorded as a single incident.
Providers must consider privacy and security implications and determine appropriate arrangements for data sharing between student accommodation providers and the provider.
If there are multiple disclosures of the same incident (e.g. a victim-survivor disclosure followed by reports from bystanders), should these be recorded and reported as: a single incident with multiple reporters, or multiple disclosure records?
Where multiple disclosures are made about what the provider believes or knows to be the same underlying incident, each disclosure must still be reported separately.
This means that every disclosure received within the reporting period, regardless of whether it relates to the same incident, should be recorded and reported as its own entry in annual reporting to the GBV Regulator.
Where the same respondent is identified across multiple disclosures or incidents over time, should these be treated as separate incidents, linked as related records or aggregated as a pattern of behaviour?
Each disclosure made to the provider within the reporting period should be reported separately, even where the same respondent is involved across multiple disclosures or incidents over time.
The GBV Regulator does not expect providers to aggregate disclosures into a single record or formally identify patterns of behaviour when reporting to us.
Under Standard 4.4 providers are required to undertake a risk assessment in response to all disclosures and formal reports of gender based violence, and to manage and monitor any identified risks on an ongoing basis. This may mean analysing records and identifying trends in order to minimise risks and improve prevention and response efforts.
If an incident involves multiple respondents, should reporting reflect a single incident with multiple respondents or multiple respondent-linked records?
For a single disclosure or formal report of an incident involving multiple respondents, data reporting should reflect a single incident. Data element no. 10 (How many Respondents were identified?) and No. 11 (Were any additional persons involved?) allow for the provider to record that multiple respondents or additional people were involved.
Providers are required to report separate counts for the total number of disclosures and formal reports. If a disclosure progresses to a formal report, should it be counted in one or both categories?
The data elements table provided at Appendix A of the Guidance on Collecting Annual Reporting Data requires a provider to record how an incident was initially reported (data element 13), and where it was initially reported as a disclosure, if it progressed to a formal report (data element 14).
This enables the GBV Regulator to capture the individual number of disclosures and formal reports as per Standard 6.13.
Annual Data Reporting and templates
When and how must a provider submit annual reporting data under Standards 6.13 and 6.14?
To comply with the National Higher Education Code to Prevent and Respond to Gender based Violence, providers are required to begin collecting data on the incidence of gender-based violence:
- From 1 January 2026 for Table A and B providers
- From 1 January 2027 for other providers registered under the Tertiary Education Quality and Standards Agency Act 2011
This data is required to be collected under Standards 6.13 and 6.14 for each calendar year, and then reported to the GBV Regulator by 30 June the following year.
Data reporting will be uploaded using a mandatory Microsoft Excel template via the National Code Web Portal – this is an online facility which will enable providers to securely provide data, reporting and other information as required to the GBV Regulator.
The web portal will verify uploaded data to ensure it complies with all formatting requirements and, where errors are identified, providers will be required to re-submit.
Further information regarding the web portal, including detailed user guides will be provided in due course.
Will you be providing a data reporting template and, if so, why has it not been provided yet?
Yes, the GBV Regulator will be providing a Microsoft Excel template for reporting, and it is mandatory that providers use it to report data to the us.
We are currently undertaking significant work to develop an IT solution to facilitate providers securely reporting data to the GBV Regulator. Part of this process is developing a template that interacts with that IT solution to facilitate effective uploading and verification of the data.
As sharing the reporting template with providers is dependent on these capabilities being finalised, we are unable to provide it until this work has been completed. The template will be made available later this year.
Will the template be optional? What if we have an existing system that produces a report in a different format?
Providers will be required to use the Microsoft Excel Reporting Template that we issue, noting it will include important validations required for uploading to our system. No other submission format will be accepted.
This is to ensure consistent collection of information for analysis purposes and to ensure high quality data.
Providers must adhere to the accepted values required in the template – these values will match those outlined in Section 3.2 of the Guidance on Collecting Annual Reporting Data – data elements.
The GBV Regulator is aware that many providers have existing data collection systems and have commenced data collection. The data elements outlined in the Guidance on Collecting Annual Reporting Data will be those required by the template.
Providers will need to ensure they can extract data to facilitate reporting by the required due date in the mandated template. There may be a need to manually export data in the first reporting year.
Will a template also be provided to record process data on implementation of policies, procedures, plans and related activities?
The annual reporting template will only relate to Annual Reporting Data, as required under Standards 6.12-6.14.
We are not planning at this time to create a template for collecting process data as related to Standards 6.8 – 6., noting this data is likely to be requested on an adhoc basis, without the need for standardisation across the sector.
See related question: Will we only have to report on incidents and disclosures, or also on prevention and training initiatives?
How does the level of detail required for annual reporting interact with providers internal reporting processes? Should providers be aiming to provide the same level of detail they have internally if this is more?
We recognise that different providers will have different internal reporting systems and processes. The National Code does not prescribe a single model for how internal data should be collected or managed internally.
For annual reporting to the GBV Regulator, providers must be able to supply the level of detail set out in the Guidance on Collecting Annual Reporting Data and required under the National Code. This means that, regardless of how a provider’s internal systems operate, they will need to ensure they can extract and report all data elements specified in the Guidance on Collecting Annual Reporting Data.
The data reporting template will not allow any additional fields of data to be added. For National Code compliance, the key requirement is that all ‘Required for Year One’ elements, and, over time, all ‘Required at maturity’ elements, can be accurately reported to the GBV Regulator.
Providers may choose to collect additional information internally if it supports their broader prevention and response work. Providers should ensure privacy and security is considered as part of any internal reporting.
Privacy and data security
How will sensitive and personal information provided to the GBV Regulator be protected?
The Universities Accord (National Higher Education Code to Prevent and Respond to Gender-based Violence) Act 2025 includes several information gathering provisions that are necessary for the performance of the GBV Regulator’s functions and exercise of its powers under the National Code.
In line with Standard 6.3(c) of the National Code, all data must be de-identified before it is provided to the GBV Regulator. The mandatory annual data reporting template will be designed to specifically prevent accidental uploading of identifiable information such as names, addresses, or student/staff ID numbers.
Once received by the GBV Regulator, data will be stored and handled securely in line with the Department of Education’s Complete Privacy Policy.
What do we do if capturing and submitting certain data poses the risk of an individual being identified? Will there be any guidance or support around concerns on maintaining anonymity and de-identification, particularly in small cohorts?
All providers will need to balance capturing data with privacy and consistently sensitive and trauma informed practice. Student and staff safety must always be the priority, and collecting data should never supersede safety.
In line with Standard 6.3(c) of the National Code, all data must be de-identified before it is provided to the GBV Regulator. The mandatory reporting template will be designed to specifically prevent accidental uploading of identifiable information such as names, addresses, or student/staff ID numbers; however, providers should also consider whether reportable characteristics may result in a student or staff member being identifiable.
Particular consideration should be given to the sample population size, or any identifiable characteristics which could result in a discloser or respondent being identified and having their privacy compromised.
Where there is a risk of a person being reasonable identifiable, the provider must take steps to de-identify data, including marking relevant data elements as ‘N/A’. More information to support providers in managing personal information is available at Privacy guidance for organisations and government agencies | OAIC.
Providers can contact the GBV Regulator for support with this, however, must not provide identifiable information about relevant parties when discussing matters with us.