• To discuss how the system currently works – with auto rejects, Stage 1 rejects checking and Stage 2 reject checking. 

• Should the ex c box/can it be automatically ticked? 

• Consistency of overwriting criteria 

• Useful instances where we need it –  as it informs us e.g. late diagnoses that give context for GCSEs 

• Is it possible to have the UCAS text accessible from SF 

• Is there a way to offer a box to tick for young carers 

• Issues with missing data 

• Issues with incorrect data 

• Issues with wiping of data / school info when its the same GCSE and A level school 

• Stage 1 reading approach /dependent on capacity to identify where the data is missing or mismatched or incorrect 

• Need to be able to instantly bring through data when school look up used 

• Could temp support be used to add in missing school data entry 

• Inviting other teams to help with data entry 

Need a policy? To address, especially post reject. Do we need a quick text/update additional info policy to include predicted grades?

Ability to mark up if someone has done an LSE/Sutton Trust WP course – takes up time for UGA manager/selector to request ticking 

• Protocol for Seniors, and Selectors, where minor changes can be made, further guidance or further understanding of how the process works.  

To consider the distribution of training responsibilities and to consider the effect of having a temporary member of staff on the same programme(s).

Is it possible for rejections to only be transmitted to UCAS in school hours? Desirable in terms of support available to what is widely recognised as an increasingly permanently connected group of young people and also in terms of the general recognition of declining levels of mental health for 16-25s overall (covering most of our applicants).