Contingent workers

Although they are not employees, the designation in Oracle or Staff Infobase for them is Contingent Worker as they are expected to carry out paid work. This category covers agency workers (including Unitemps), external examiners, consultants and sole traders or self employed.

Please note:
For Unitemp positions, the Unitemps office will complete all requests for access to ensure the dates align with their contract dates and that no duplicate requests are processed.

There is an automated process to enable access via a Staff Infobase workflow similar to that of a PAF.

Please note:
All requests for contingent worker status require the Director of school/service approval and Business Manager approval within faculties. A contingent worker will not be able to access any systems or buildings until this approval is in place. This will ensure that Directors are aware of the presence of contingent workers in their areas and the reasons for this.
Apart from staff engaged via Unitemps, the nominating employee will complete the request form by directly inputting the contingent worker details into Staff Infobase, which on submission will automatically be routed to the relevant Director (and then Business Manager if a school or faculty request) for workflow approval. Once the request is approved it will forward to the HR Operations Team for them to activate the access. For temporary staff engaged via Unitemps, as budget approval has already been supplied at the time of the booking, the engaged Unitemp details will be entered onto Staff Infobase by the Unitemp booking staff member, rather than the LJMU hiring manager.

Faq Items

Categories this guidance covers

Categories this guidance does not cover

Submitting Contingent Worker Request

Timescales

Ending contingent worker access

Nominating employees' responsibilities and obligations

Expenses

Contact details