No Fresh DPI Required: If the Project DPI has already been submitted under Section 4, no fresh DPI shall be required for any subsequent application under Section 6 or Section 7(3), including applications relating to RC supersession, RC amendment, or similar cases. Likewise, where the DPI has been submitted under Section 6, no fresh DPI shall be required for any subsequent application under Section 7(3) or for further extensions, as applicable.

Use of Existing Login Credentials: The promoter shall use the same login credentials through which the original Project DPI was submitted. No new user credentials shall be created where an existing DPI is available.

Generate DPI for Subsequent Applications: The promoter shall select the "DPI Request for Extension" option on the dashboard to use the previously submitted Project DPI for the subsequent application.

Review and Update: After generation, the promoter may review, update, amend, or supplement the DPI and supporting documents, wherever required, while the original DPI shall remain preserved.

Avoid Duplicate Submission: Promoters shall not submit a fresh DPI or create new user credentials where a previously submitted DPI is available, ensuring continuity, consistency, and avoidance of duplicate data entry.

Track Application Status: The promoter may monitor the request status through the dashboard at each stage, including Request Submitted, Under Examination, DPI Generated, Available for Editing, and Final Disposal, as applicable.

General Principle: The DPI submitted at an earlier stage shall serve as the base DPI for subsequent applications, thereby eliminating repetitive submission of the same project information.