REF1 Researcher form
Released : 5.18
Updated : 5.19, 5.20
REF1 Researcher form
REF1 Researchers are accessed via the Manage REF1 Researchers screen. Each researcher has a single REF1 form.
The REF1 form enables you to capture REF-specific metadata for each researcher, as per the submission requirements. This includes:
Staff Category
Identifying info such as HESA ID, ORCID ID, and date of birth
Contract information
REF2 affiliations and attributions
Field descriptions and logic
Overview banner
The REF1 form includes an overview banner, displaying:
Researcher name
Proprietary ID
Primary group
REF1 inclusion status
REF1 confirmation workflow state
Unit of Assessment
Inclusion in submission
This section enables you to capture whether an individual is to be included in the REF2021 submission, and any inclusion notes (which are for internal use only and are not returned in the submission XML).
REF1 field | Description | Further notes |
Include in submission | Flag an individual as included / not in the submission. | By default, all users are selected as Included in submission |
Submission inclusion notes (for internal use only) | Capture notes relating to the submission inclusion decision | Is for internal use only and will not be included in the submission XML |
Staff category
REF1 field | Description | Further notes |
Staff category | Choose between Category A (current staff on the census date) and Category B (former staff on the census date) | By default, all users are assigned Category A. |
Identifying information
REF1 field | Description | Further notes |
HESA ID | HESA staff identifier. | Captured in this section for Cat A only. HESA IDs for Cat Bs are captured in individual contract details (see below). |
Date of birth | ||
ORCID | You can select from Connected or Claimed ORCIDs in Elements, or manually enter another ORCID. |
Early career researcher
REF1 field | Description | Further notes |
Is Early Career Researcher | Category A only. | Will only be returned in the submission XML if no HESA ID is provided |
Research group
For Category A staff, if Research groups are enabled for the Unit (see the Managing Units of Assessment support article), the Research group section is visible in the main REF1 form. For Category B staff, Research groups are captured per contract returned (see below).
If Unit configuration allows REF1 Researchers to be assigned to more than one Research group | If Unit configuration does not allow REF1 Researchers to be assigned to more than one Research group |
|
|
Contract information
Due to the differing data requirements for Category A and Category B staff, the Contract Information section differs, depending on the selected Staff category.
Category A
Cat A REF1 field | Description | Further notes |
Contract FTE | Contracted FTE on the census date. | Minimum 0.2, maximum 1.0. Two decimal places maximum. |
FTE notes (internal use only) | Capture notes relating to the contract FTE returned | Is for internal use only and will not be included in the submission XML |
Research connection | Is required if Contract FTE is between 0.2 and 0.29 inclusive (field will appear if Contract FTE input is between 0.2 and 0.29 (inclusive)) | |
Reason for no Research connection statement | Is required if no Research connection statement is provided and FTE is 0.2-0.29 (field will disappear if Research connection field is populated) | |
Fixed-term contract | If the individual is on a fixed term contract, provide the start and end dates | |
Secondment | If the individual is on secondment, provide the start and end dates | |
Unpaid leave | If the individual is on unpaid leave, provide the start and end dates |
Category B
For each eligible employment period where an output is being claimed, it is possible to capture the required contract details.
Cat B REF1 field | Description | Further notes |
HESA ID | HESA staff identifier. | |
Research group | If Research groups are enabled for the Unit (see Managing Units of Assessment support article), they can be selected here | |
Start date | Start date of the eligible employment period where an output is being claimed. Is mandatory. | |
End date | End date of the eligible employment period where an output is being claimed. Is mandatory.c | |
Contract FTE | FTE of REF-eligible contract | Minimum 0.2, maximum 1.0. Two decimal places maximum. |
FTE notes (internal use only) | Capture notes relating to the contract FTE returned | Is for internal use only and will not be included in the submission XML |
Research connection | Is required if Contract FTE is between 0.2 and 0.29 inclusive (field will disappear if Contract FTE input is 0.3 or above) | |
Reason for no Research connection statement | Is required if no Research connection statement is provided and FTE is 0.2-0.29 (field will disappear if Research connection field is populated) | |
Secondment | If the individual was on secondment, provide the start and end dates | |
Unpaid leave | If the individual was on unpaid leave, provide the start and end dates |
REF2 Research outputs
REF1 field | Description | Further notes |
REF6a individual circumstances (minimum of one output waived) | Capture whether the individual's minimum requirement of one attributed output has been waived due to REF6a individual circumstances | Completing this field enables accurate calculations as to each individual's minimum and maximum attributions, and the Unit's attributions as a whole |
Zero output attributions expected | In order to accurately calculate the number of attributed REF2s required for the unit (which includes reducing the overall number required by one for each Cat A submitted with zero attributions and no REF6a waiver), indicate here whether it is expected that the individual will have zero attributions and no REF6a waiver | Completing this field enables accurate calculations as to the required number of REF2s for the Unit |
Number of O-Confidential reports or S-Research data sets and databases being input directly into the REF submission system | Where you wish to input REF2 outputs directly in the REF submission system (e.g. O-Confidential reports not held in Elements), input the number of outputs attributed to this individual. | This field is for internal use only and enables accurate calculations as to each individual's minimum and maximum attributions. |
Title(s) of O-Confidential reports or S-Research data sets and databases being input directly into the REF submission system | Title(s) of any REF2 outputs being input directly into the REF submission system | This field is for internal use only and enables you to keep track of which outputs are being referenced in the field above |
Calculated number of REF2 attributions | Calculation of the number of REF2 outputs attributed to the individual | This calculation is performed as per the logic described in the Counting REF2 Research outputs support article. |
Output affiliation list | Lists all outputs affiliated with the individual and the submission status of each |
REF1 Data confirmation workflow
The REF1 form includes a Data confirmation workflow, helping to support you in managing the compilation and checking of all required REF1 data. The values available are:
Entry in progress (default value)
Checking underway
Confirmed
