The option to copy an employee who has moved to another property within the Trust. I understand old records need to remain for Workforce census, but moving them or copying them would be helpful.
Lucy Brighton
Feb 11, 2026
Improving this process would be very helpful. Users have reported the transfer of employee data between sites as a time consuming process to re-add the data again on the new site and is open to data entry issues.
Please consider whether export and import into fields is a development option to save user time or a copy function
I agree that this would be really useful if this could be added.
As HR within a MAT we often need to see all roles an employee holds across different properties without having to remember or locate where they previously sat. If these could be linked automatically under the employee’s main record (rather than split by property), it would save a significant amount of time and reduce errors.
This would also be beneficial for School Business Managers, who need appropriate access to view staff linked to their school. If records were stored under a single employee profile with properties/roles attached, rather than held separately at a property level, it would simplify access controls and reduce the need to manually adjust visibility each time an employee moves.
I absolutely appreciate the need to retain records for SWC purposes. However, rather than restricting movement, could there be a way to simply indicate which property a role should be reported against for Census, and use that indicator to manage:
Which role is used for SWC, and
Who should have access permissions to view that role,
while still keeping everything connected under one consolidated employee record?
This approach would maintain compliance, improve usability, and better reflect the reality that we operate as one employer.
Improving this process would be very helpful. Users have reported the transfer of employee data between sites as a time consuming process to re-add the data again on the new site and is open to data entry issues.
Please consider whether export and import into fields is a development option to save user time or a copy function
I agree that this would be really useful if this could be added.
As HR within a MAT we often need to see all roles an employee holds across different properties without having to remember or locate where they previously sat. If these could be linked automatically under the employee’s main record (rather than split by property), it would save a significant amount of time and reduce errors.
This would also be beneficial for School Business Managers, who need appropriate access to view staff linked to their school. If records were stored under a single employee profile with properties/roles attached, rather than held separately at a property level, it would simplify access controls and reduce the need to manually adjust visibility each time an employee moves.
I absolutely appreciate the need to retain records for SWC purposes. However, rather than restricting movement, could there be a way to simply indicate which property a role should be reported against for Census, and use that indicator to manage:
Which role is used for SWC, and
Who should have access permissions to view that role,
while still keeping everything connected under one consolidated employee record?
This approach would maintain compliance, improve usability, and better reflect the reality that we operate as one employer.