APT 2.0 Operational Guide for Processing Migrated GDS Compassionate Engagement Applications
APT 2.0 Operational Guide Released for Processing Migrated GDS Compassionate Engagement Applications
The Department of Posts has issued an Operational Guide for Processing Migrated Applications in the GDS Compassionate Engagement Module of Advanced Postal Technology (APT) 2.0. The guide, Version 1.0 dated 06.08.2026, provides operational instructions for handling applications migrated from the Legacy GDS Compassionate Module to APT 2.0.
Download GDS Compassionate Engagement Applications in PDF
Migration of Pending Applications
As per the approved Migration Plan and Directorate Letter No. 17-33/2025-GDS dated 21.07.2026, migration of data from the Legacy GDS Compassionate Module to the GDS Compassionate Engagement Module in APT 2.0 was completed between 27.07.2026 and 05.08.2026.
Only applications that had not been pushed to CCE in the Legacy Module were migrated to APT 2.0. Such cases are available at the same processing stage at which they were pending. Applications already pushed to CCE have not been migrated and will continue to be processed through the Legacy Module up to DPS Approval. The Legacy Portal is now intended only for CCE/DPS processing, with no provision for reversal or pushing new cases to CCE.
The migration is a one-time activity, and no further migration of pending cases will be undertaken.
Handling of Missing or Incomplete Data
Certain mandatory fields that were unavailable in the Legacy Module have been populated with suitable default values such as “NA” during migration. These include Employee Reservation Category, Case Mark Number, Last Office of Working, Family Address, Applicant Disability Percentage, Applicant PwBD Category, Father's/Guardian's Name, Mother's Name, FIR Number and Dependent Mobile Number.
Where such information is required during processing, the application may be reverted to the Applicant, Sub-Division or Division, as applicable, for updating. Any partially completed application submission or verification in the Legacy Module has been reset and must be completed afresh in APT 2.0.
Discrepancy Cases
Applications containing critical missing information or discrepancies have been placed under the “List of Cases with Discrepancies.” Examples include missing Parent Office details, Sub-Division/Division/Region/Circle details, Verification Sub-Division details and invalid system-generated 8-digit Employee IDs.
Such applications will not be available in the regular workflow until the concerned Division updates the required information through the dedicated provision in APT 2.0. Once the discrepancy is rectified, the application will automatically become available at its corresponding pending stage.
In cases involving an invalid Employee ID, the Division is required to create a valid Employee ID in the PIS Module and update it so that the case is removed from the Discrepancies dashboard.
Viewing Migrated Cases
Migrated cases can be viewed by Divisions through the “List of Cases Registered” report. The field “Migrated from Legacy to APT” is marked as “Yes”, enabling users to identify migrated applications and check their current status.
Applications that were at different processing stages in the Legacy Portal will be available at the same stage in APT 2.0. For example, a case that was pending for verification at SDH will be available in the SDH Login under the “Sub Division Verification” card.
The guide also states that credentials and instructions regarding closure of the old applicant portal and access to the new portal will be communicated to applicants through their registered email and mobile number.
Process for Updating Discrepancies
The guide provides a dedicated process for updating discrepancies in APT 2.0. The Division user has to log in to the GDS – Compassionate Engagement (CCE) application and select “List of Cases with Discrepancies” from the menu.
The dashboard displays migrated employee cases for which discrepancies were identified. By clicking the Employee ID hyperlink, the user can access a screen showing only the fields flagged with discrepancies. Correctly migrated fields are not displayed, making the correction process focused on the affected information.
The user must enter the correct values for the discrepant fields and click Submit. Once the update is successfully completed, the case is removed from the discrepancy dashboard and reflected at the concerned processing stage. This enables the case to resume processing from the same stage at which it was left in the Legacy Module, without loss of progress.
Conclusion
The Operational Guide provides a structured mechanism for managing migrated GDS Compassionate Engagement applications in APT 2.0, while ensuring that cases retain their respective processing stages. The dedicated discrepancy dashboard and field-level correction facility are intended to help Divisions identify and rectify migration-related issues efficiently and continue processing cases without loss of progress.
The Department has also clarified that the Operational Guide is only an illustration for effective use of the APT software solution. In case of any doubt regarding Departmental rules, orders or guidelines, users must refer to the relevant Directorate instructions and rulings, as the APT Operational Guide itself should not be cited as a ruling.