607078

Confirmation decision applicant experience enhancement

Updated terminology at the confirmation stage on the applicant portal to clearly communicate that accepting any offer confirms the applicant’s place at the university.

577027

Send a bespoke email to multiple applicants

Admissions officers now send bespoke emails to multiple applicants. The Create new email option is available in the Communicate to applicants bulk action in Application queries. Admissions officers can then enter a free text message to the selected applicants, for up to 100 applicants at a time, which will send the email to their preferred email address.

Admissions officers require the permission Communication - Send and Application - Edit permission for the selected applicants to send bespoke emails to multiple applicants.

610349

Creation of an interview record

Admissions officers can now create interview records on the new Interview tab on the applicant overview. Admissions officers:

• Define the date and time of the interview.

• Choose whether the interview will be remote or in-person.

  • For remote interviews, define the meeting URL such as the URL for a Microsoft Teams meeting.

  • For in-person interviews, define the location of the interview by selecting values from the new reference data.

• Add applicant instructions and notes for the panellists.

The data setup for interviews adds the following:

New permissions

Permissions in the Admissions area Applications:

• Interview – Edit

• Interview – View

New communication template

• Application interview email and subject

New reference data

New editable reference data for Applications to define the location of interviews:

• Site: Site such as The Wolds Centre.

• Building: Building such as West Building.

• Room: Room used for interviews, such as Room 101.

620777

Interviews: Applicant portal

Applicants can view tasks that contain details relating to their interviews. This includes both remote and in-person interviews, instructions, and interview panellists.

569719

Referee portal

Overview

The referee portal helps admissions teams collect references more efficiently. Referees can submit references online, upload documents, and track their submissions. Document intelligence, which requires a level 3 licence, can extract references from uploaded documents automatically. Applicants and admissions officers get better visibility and control throughout the process.

Key functionality includes:

End-to-end process

Applicants can now add referees, who receive invitations to register and submit references or documents. Admissions officers review and approve submissions, triggering automatic status updates.

Referee portal

Referees with multiple references now land on a summary dashboard showing reference status and outstanding counts. Each entry includes applicant details, institution, course, and actionable buttons. Referees can view all submitted content, including cancelled or declined items. If a virus is detected in an upload, the referee is notified via a banner and an email, with a prompt to resubmit via the dashboard.

Admission officer tools

Admissions officers gain new tools to manage referee accounts, update their emails, resend or cancel invitations, and reset cancelled ones. Status controls allow reversing decisions, cancelling references tied to closed or withdrawn applications, and viewing lifecycle logs for key events. Improvements to the user interface include new status chips indicating reference progress and entry system, such as UCAS and Direct.

Applicant portal

Applicants and agents with access to the applicant portal can now add, edit, or replace referees, resend invitations (limited to once every 24 hours), and view reference status via intuitive banners. Expired invitations (after 7 days) trigger actionable tasks. Uploaded references are securely attached to applications but remain hidden from applicants and agents. Improvements to the user interface include clear banners guiding applicants through next steps.

Data setup

The data setup required for the functionality described above is done automatically. For example, the new reference data for clearance checks has been added automatically so any additional setup of reference data is not needed.

The following have been added automatically:

New clearance checks

• Clearance check type CCRFR01 - Reference from referee 1 and corresponding clearance check task template TKRFR01: Provide referee details 1

• Clearance check type CCRFR02 Reference from referee 2 and corresponding clearance check task template TKRFR02 - Provide referee details 2

• Clearance check type CCRFR03 Reference from referee 3 and corresponding clearance check task template TKRFR03 - Provide referee details 3

New communication templates

• Referee portal registration email and subject

• Referee portal expired invitation email and subject

• Referee portal acknowledgement email and subject

• Referee portal reference status updated email and subject

• Referee portal document virus found email and subject

New permissions

Admissions area Referee portal: Referee portal - view

Admissions area Applicant portal and Agent portal:

• Application - Edit referee

• Application - Submit referee details

People area Actions:

• Referee portal - Cancel invite

• Referee portal - Resend invite

573758

API version rollover and new API versioning strategy

The following API versions have changed:

• API version 2023-02-01 has moved from Stable to Deprecated. Please migrate your integrations from this version within the next 9 months.

• API version 2023-11-15 has moved from Preview to Stable.

A new API versioning strategy has also been introduced:

• New Preview API versions will be introduced as changes are made.

• Each API catalogue tile, such as Application and Curriculum, will receive its own API version.

This makes it easier to maintain integrations, while also allowing Tribal to reduce the time taken to stabilise new integration endpoints. In turn, this will allow faster adoption of new features.

Note that:

• APIs will only be versioned when it is necessary for adoption of a new feature. Meaning that you will not need to update your integration APIs for any tiles that do not change.

• Every API version will be in a supported state (Stable or Deprecated) for a minimum of 18 months from the time it becomes Stable.

• Versions for APIs that do not need to change will remain supported for a lot longer than this, because no new Preview versions will be introduced.

• Every API version will be in the Deprecated state for a minimum of 9 months to allow migration to a newer API version.