Athena SWAN and CoreHR

Athena SWAN specific data coding are then applied including:

  • academic and research groupings
  • professional and support groupings
  • TUPE mappings
  • organisation structure changes
  • joint application groupings


Where staff do not appear in the expected category or are missing from the Athena SWAN dataset it is likely to be because of the way their appointment is recorded in Core, for example:

  • a researcher coded to the staff classification of AS ‘Research Support’ instead of AP ‘Research Staff’ will not appear in the Athena SWAN dataset grouping 'Academic and Research' but in the 'Professional and Support' group

  • a staff member with a professorial title conferred through the Recognition of Distinction will only appear with the correct title for Athena if the title is correctly recorded in Core

Data quality in Core

Data in Core are generally reliable. Where incorrect data are found it is important to make corrections at source in Core. 

This ensures the data are correct when subsequent extracts are run and will also assist departments in meeting obligations to hold accurate data under the General Data Protection Regulation (2018).


Between 1 - 31 July each year we release a Core report to allow users to view their potential Athena SWAN dataset, check and resolve any issues:

  • HRINFO02_AthenaSWAN Potential Staff Data

In addition two data quality validation reports are always available:

HINT: It will be beneficial to run and clear all anomalies from your HRINFO01_Data Quality Validation report before reviewing the HRINFO02_AthenaSWAN Potential Staff Data report.