TCSI New Sub-Packets
Introduction
To support the Tertiary Collection of Student Information (TCSI) reporting requirements, four new sub-packets have been implemented within the system. These sub-packets provide enhanced support for recording and reporting student and course admission information where multiple records for these sub-packet data may exist for student or course admission packets.
TCSI sub-packets, also referred to as extensions, allow institutions to capture and report additional information that may change over time or occur multiple times within a student's lifecycle. The new functionality ensures compliance with TCSI reporting requirements while providing a more flexible approach to managing student and course admission data.
The following sub-packets have been implemented:
Student Packet Sub-Packets
Citizenship sub-packet — A new user interface will allow multiple citizenship records to be stored for a student. These citizenship records will be reported as part of the main Student Packet.
Disability sub-packet — The existing interface for recording student disability information will remain unchanged. A new sub-packet will be available on the TCSI reporting page so disability data can be reported separately and more clearly.
Course Admission Packet Sub-Packets
Basis for admission sub-packet — The existing course admission interface will be updated to allow up to two basis-for-admission records for a single course admission. This data will continue to be reported within the Course Admission Packet.
Course specialisation sub-packet — A new user interface will allow multiple course specialisations to be recorded for a course admission. A new sub-packet under course admission packet is added in the TCSI reporting grid to support efficient data reporting,
Disability Sub-Packet
Disability data for students can be added to the student profile or TCSI information pages. This information is reported under the student.
To do that:
Go to Student > Student Profile Summary
Click the TCSI icon > Student Information > Disability Information
Select Disability by ticking the checkbox and enter the Duration (from and to dates)
Click Update. The data reports successfully, and disability UIDs are received for the selected disabilities.
Student disabilities also appear in the Disability Sub-Packet.
Note: When adding another disability for the reported student, a trigger appears in the main student packet and a new sub-packet is created for the disability. The user can either report the information via the main student packet or switch to Disability packet and report the new information.
Reporting the disability from the disability grid generates a new UID and removes the trigger update in the main student packet:
If the user syncs the main student packet change, the disability data appears with the reported UID.
Updating the Reported Disability Data
To update disability data, go to Student > TCSI > Disability Information
If the effective from or to date of a reported student disability changes, the trigger update appears in the main student packet, and these changes must sync via the student packet.
The user can sync the student packet to send the new date update.
Deleting a Reported Disability for the Student
To delete a reported disability, the user can go to the disability sub-packet and click the delete icon to remove any reported disabilities for the student
Note: You cannot delete disability information from the Student TCSI section or the student profile after reporting. The system will display an error. The same validation applies when you try to delete the disability section on the student profile page
After deleting the disability from the reporting grid, you can delete the data.
Course Specialisation Sub Packet
You can now add multiple course specialisations to a student’s enrolment if more than one specialisation code applies. A new sub-tab, “Additional Course Specialisation,” appears under the Student Course Information section.
Note: The primary course specialisation code is added on the Student Course Information page. If additional course specialisation codes are required, they must be added in this section.
To add new course specialisation:
Go to Student > Student Profile Summary
Click the TCSI icon > Student Course Information > Additional Course Specialisation
Select values from the dropdowns and click Add. You can add up to three course specialisations.
Reporting Course Admission with Additional Specialisations for the first time
The main packet picks up the course specialisation from the main course admission page. Other specialisations appear as new records in the course specialisation sub-packet.
After reporting the data, UIDs are received for each record.
The main packet GET request displays the course specialisation UIDs.
The UIDs for each specialisation are stored in the TCSI course information grid
Note: If the user records and reports the same specialisation code twice, TCSI returns the same UID.
Delete a Reported Specialisation
You can delete any reported course specialisation from the student’s Additional Course Specialisation Page under TCSI course information section. If the records delete successfully, the system also removes the specialisations in TCSI via API.
If the user deletes the specialisation on the TCSI reporting page, the UID is removed from the course specialisation page.
If the student’s main course admission is deleted when multiple specialisations are reported, the system also deletes the reported specialisations data.
Basis For Admission Sub Packet
Users can now record up to two Basis for Admission codes per student course enrollment. The new dropdown, Additional Basis for Admission Code, is optional and only required if a course admission has more than one code.
To add new basis for admission:
Go to Student > Student Profile Summary
Click the TCSI icon > Student Course Information > Additional Basis for Admission Code
Select a value from the dropdown list
If the user adds duplicate basis for admission code values, an error message appears.
If the student has only one basis for admission code when reporting the course admission for the first time, record it in the Basis for Admission Code dropdown. Leave the Additional Basis for Admission Code blank.
If you add Additional Basis for Admission, a trigger in the course admission packet syncs changes and updates the packet
A new UID was received for the Basis for Admission, resulting in two reported basis for the course enrollment
Reporting Course Admission with Additional Basis for Admission for the first time
The system records both bases sent for course enrollment and TCSI returns different basis for admission UIDs for the reported data.
If the user changes any of those values, the course admission packet receives an update trigger button.
The update is sent to TCSI, which returns the UIDs for the changed basis for admission codes.
Updating Basis for Admission Values after Two Basis are Reported
To update basis for admission data, go to Student > TCSI > Student Course Information > Additional Basis for Admission Code
After the update a trigger is received in the course admission packet and once it is synced, the update is completed.
Citizenship Sub-Packet
A new Citizenship Information section has been added to the TCSI Student Information page. This update applies only to the student stage. The offer stage remains unchanged.
To manage:
Go to Student > Student Profile Summary
Click the TCSI icon > Student Information > Citizen Information
The user must first record citizenship status and effective from date in the main Basic Information grid. This data will appear in the new Citizenship Information section. The citizenship effective from date is mandatory when updating a student’s citizenship code.
Note: The system automatically calculates the citizenship effective to date when a student has multiple citizenship records. The previous citizenship's effective to date is one day before the new citizenship's effective from date.
When this student packet is reported, it selects the correct student citizenship code and date.
The data was reported successfully, and the system received the Student UID and Citizenship UIDs. It now stores these UIDs in the citizenship grid on the student TCSI information page.
Changing the Citizenship Code for a Reported Student
When a reported student’s citizenship code is changed, the system creates a new record in the citizenship grid. The previous citizenship UID is retained for the earlier citizenship record, and the Student UID is carried over to the new citizenship record.The user must record a new effective date for the updated citizenship record.
The system automatically stores the previous citizenship record’s effective to date as one day before the new record’s effective from date.
After the citizenship record is changed, a trigger or sync icon appears in the reported student packet. The preview reflects the updated citizenship record and effective from date.
The update is processed successfully, and a new citizenship UID is received for the updated citizenship record.
The new citizenship code is stored in the grid with the respective UID.
Deleting the Reported Student Packet
Deleting the TCSI student packet from the TCSI grid also deletes all recorded citizenship information for that student. The system retains only the latest citizen code.
If the user adds or updates any data for the citizen code, the system treats it as a new record.
Change in Citizenship Effective From Date
If the user changes only the effective from date for any citizen code, the following cases can occur:
If the student packet itself is unreported, the date change should only update the effective from date in Meshed.
The student is not yet reported, and the initially recorded effective date differs from the updated effective date.
Code 3 effective date from is changed from 01/05/2026 to 31/05/2026
Effective date updated to 31/05/2026
If the effective from date changes for a reported citizenship code, the UID for the reported citizenship remains the same. The date change creates an update trigger in the student packet, and the date update is sent.
Reported the student with code 3 effective from 31/05/2026
Updated the effective from date to 05/06/2026 but the code remains the same.
The trigger is received in the student packet, but the citizenship UID for the reported data goes away from the grid:
The data is updated successfully
Once synced, the UID is restored.
If the citizenship code is unreported and the effective from date changes, the system should simply update the date on the Citizenship page under TCSI Information, as no trigger in the student packet is needed.
In this case, the student packet is reported for a certain citizen code and has a new code which is not reported yet. The change in effective from date is for the new code where the data is not reported yet. The expectation here is that the date change for the unreported code will be reported with new Citizen code POST.
In the example below, another citizen code was added as code 1 with an effective date of 06/06/2026
This creates a new record in the citizenship grid and triggers the student packet.
Need help?
Do you have questions or doubts about this topic?
Send an email to support@meshedgroup.com.au
Do you have any suggestions? Interested in additional modules? Connect with our Sales Team by clicking the link below.