Law Updates

Subject

Summary: The Punjab Pollution Control Board ( PPCB ) has issued an Office Order dated 09 June 2026 to settle confusion around Environmental Clearance for construction, township and area development projects. The order tells PPCB officers exactly how to handle consent applications for projects that fall under Item 8(a) and Item 8(b) of the EIA Notification, 2006. It covers buildings, townships, area development schemes and plotted development. At the heart of the confusion was one simple question: when does a project need prior Environmental Clearance (EC), and when does it only need PPCB Consent to Establish (CTE)? This order gives PPCB officers a common answer, so that similar projects are treated the same way across the state. Background of the EIA Notification, 2006 and Item 8(a) & 8(b) What Is the EIA Notification, 2006? The EIA Notification, 2006 is a rule made by the Ministry of Environment, Forest and Climate Change (MoEF&CC). It lists certain types of projects that cannot start construction without first getting Environmental Clearance. Environmental Clearance is basically a green signal from the government. It confirms that a project has been checked for its likely impact on the environment before construction begins. Building and construction projects, along with townships and area development projects, are two categories listed in this notification. That is where Item 8(a) and Item 8(b) come in. What Are Building and Construction Projects Under Item 8(a)? Item 8(a) covers plain building and construction projects. A project falls under this category when its built-up area is: 20,000 sq. m. or more, but less than 1,50,000 sq. m. Built-up area means the total covered floor area of a building, every floor added together. For open-to-sky facilities, PPCB treats the activity area as the built-up area instead. What Are Township and Area Development Projects Under Item 8(b)? Item 8(b) covers a different type of project, townships, area development schemes, and plotted developments. These projects are checked against two thresholds: •    Total project area of 50 hectares or more, and/or •    Total built-up area of 1,50,000 sq. m. or more EIA Item 8(a) vs 8(b) at a Glance EIA Category Project Type Key Threshold Environmental Clearance Item 8(a) Building & Construction ≥20,000 sq. m. and <1,50,000 sq. m. built-up area Required Item 8(b) Township / Area Development / Plotted Development ≥50 hectares and/or ≥1,50,000 sq. m. built-up area Required Why Did PPCB Issue This Clarification? The trouble started because different PPCB offices were reading the rules differently. Some offices treated certain projects as needing EC. Others did not. This inconsistency made it hard for developers to know what to expect. PPCB has also requested a proper answer regarding this matter from MoEF&CC through letters dated 09 May 2023 and 27 May 2025. Before this, the new process ensures that all officers will receive the same treatment for similar projects. So, PPCB decided to set out one procedure that every officer and office of the Board must follow until the Ministry sends its own clarification or PPCB issues further orders. What Has Changed Under the New PPCB Clarification? This section is crucial as it guides officers on how to accurately classify projects, ensuring they feel empowered and responsible for consistent decision-making regarding prior EC requirements. Building and Construction Projects Under Item 8(a) If a project's built-up area is 20,000 sq. m. or more but less than 1,50,000 sq. m., PPCB will treat it as an Item 8(a) project. Prior Environmental Clearance is required before construction begins. Township, Area Development and Plotted Development Under Item 8(b) For townships, area development, and plotted development projects, prior EC is required when: Total project area is 50 hectares or more, and/or Total built-up area is 1,50,000 sq. m. or more PPCB has clarified that built-up area here can be worked out either on an actual basis or on an FAR (Floor Area Ratio) basis, whichever applies to the project. Projects Below 50 Hectares Here is where the clarification gets genuinely useful. Suppose a project sits below the 50-hectare mark, but its total built-up area still crosses 20,000 sq. m. (though it stays under 1,50,000 sq. m.). What happens then? PPCB says: if no single building or plot within that project reaches 20,000 sq. m. built-up area on its own, the project does not need prior Environmental Clearance under this clarification. It still needs PPCB Consent to Establish, though, that requirement does not go away. When an Individual Building or Plot Crosses 20,000 Sq. Metres Now take the same situation, project area below 50 hectares, total built-up area between 20,000 sq. m. and 1,50,000 sq. m., but this time, one particular building or plot inside the project has a built-up area of 20,000 sq. m. or more on its own. In that case, PPCB says that specific building or plot cannot be built until it separately obtains prior Environmental Clearance under the applicable Item 8(a) provisions. The rest of the project may not need EC, but that one building or plot does. PPCB Applicability Decision Project Situation EC Requirement PPCB Consent Requirement Building & Construction project: built-up area ≥20,000 sq. m. and <1,50,000 sq. m. Prior EC required (Item 8(a)) Applicable PPCB consent Township/Area/Plotted Development project: total area ≥50 hectares Prior EC required (Item 8(b)) Applicable PPCB consent Any project with total built-up area ≥1,50,000 sq. m. Prior EC required (Item 8(b)) Applicable PPCB consent Project area <50 ha; total built-up area >20,000 and <1,50,000 sq. m.; no individual building/plot ≥20,000 sq. m. No prior EC required under this clarification Consent to Establish (CTE) required Same project as above, but one individual building/plot ≥20,000 sq. m. Prior EC required under Item 8(a), only for that individual building/plot Applicable PPCB consent How Will Environmental Clearance Applicability Be Determined? Officers are expected to work through the project in a set order. 1. Check the Type of Project First, identify what kind of project it is, plain building and construction, or a township, area development, or plotted development scheme. This decides whether Item 8(a) or Item 8(b) applies. 2. Check the Total Project Area Next, check whether the total land area of the project is 50 hectares or more. This threshold applies specifically to Item 8(b) projects. 3. Check the Total Built-Up Area Then check the total built-up area against the 20,000 sq. m. and 1,50,000 sq. m. marks. This is central to both Item 8(a) and Item 8(b). 4. Check Individual Building or Plot Area This step matters a lot under the new clarification. Even if the whole project stays under the main thresholds, one large building or plot inside it can still trigger EC on its own. 5. Check Actual and FAR-Based Built-Up Area FAR, or Floor Area Ratio, is a planning term. It tells you how much construction is allowed on a plot compared to the plot's size. PPCB has said that built-up area can be calculated either by actual measurement or by using the FAR-based figure, depending on which applies to the project. Understanding the Difference Between Item 8(a) and Item 8(b) Building and Construction Projects Under Item 8(a) Item 8(a) is about buildings, putting up structures on land. Think offices, apartment blocks, or standalone commercial buildings. Township and Area Development Projects Under Item 8(b) Item 8(b) is broader. It covers development of an entire area, roads, drainage, sewage lines, electricity networks, and other civic infrastructure, alongside the buildings themselves. Why the Nature of the Project Matters The PPCB order refers to observations made by the Supreme Court of India on this exact question. The Court had noted that Item 8(a) and Item 8(b) are listed separately in the EIA Notification for a reason, they are not meant to be treated as the same thing. A building and construction project is simply the addition of structures on land. A township project is the creation of an entirely new area for residential, commercial, or industrial use, and is different in scale and character from a single building project. In simple words: Item 8(a) mainly looks at building and construction. Item 8(b) deals with wider township and area development. Environmental Clearance vs Consent to Establish: What Is Required? When Is Prior Environmental Clearance Required? Prior EC is required wherever a project meets the Item 8(a) or Item 8(b) thresholds explained above, including the individual building/plot situation. When Is PPCB Consent to Establish Required? Even projects that do not need prior EC under this specific clarification still need PPCB Consent to Establish before they can start. CTE is a separate requirement under the Water Act and Air Act. Why EC and CTE Are Not the Same Approval? These two approvals do different jobs, and one does not replace the other. Environmental Clearance = approval under the EIA framework, required for specified categories of projects like those under Item 8(a) and 8(b). Consent to Establish = pollution control consent granted by PPCB before a project or activity is set up, under the Water Act and Air Act. A project that avoids the EC requirement under this clarification still has to go through CTE. The clarification does not remove PPCB's consent process, it only decides when EC is additionally needed. Implementation Timeline and Effective Date The EIA Notification came into force on 14 September 2006. PPCB wrote to MoEF&CC seeking clarity on 09 May 2023, and again on 27 May 2025. PPCB's own Office Order carrying this clarification is dated 09 June 2026. The order takes effect immediately and applies until MoEF&CC sends its clarification or further orders are issued. It supersedes all earlier communications on the same subject. Important Dates Date Event 14 September 2006 EIA Notification, 2006 came into force 09 May 2023 PPCB wrote to MoEF&CC seeking clarification 27 May 2025 PPCB wrote to MoEF&CC again, seeking clarification 09 June 2026 PPCB issued the present Office Order Awaited Final clarification/further orders from MoEF&CC What Is the Impact of the PPCB Clarification on Businesses? 1. Residential Projects Developers building large residential blocks need to check the total built-up area carefully, including whether any single tower or block crosses 20,000 sq. m. on its own. 2. Commercial Projects Office parks and commercial complexes fall squarely under Item 8(a) once the built-up area crosses 20,000 sq. m. 3. Township Projects Large townships need to track both total land area and total built-up area, since either can trigger the Item 8(b) threshold. 4. Area Development Projects Projects that develop land, roads, drainage, utilities, without necessarily building large structures, still fall under Item 8(b) scrutiny based on area. 5. Plotted Development Projects Plotted developments need close attention to individual plot sizes, since one oversized plot can require separate EC even if the overall project stays under the main thresholds. 6. Projects Applying for PPCB Consent Every project, whether or not it needs EC, should expect to go through the Consent to Establish process with PPCB. Developers should check project classification, area, and built-up area carefully before construction begins, rather than assuming their project is automatically exempt. How Can Businesses Achieve Compliance Under the New Rules? Identify the project type, building/construction, township, area development, or plotted development. Calculate the total project area. Calculate the total built-up area. Check both actual and FAR-based built-up area, where relevant. Check the built-up area of every individual building or plot separately. Determine whether Item 8(a) or Item 8(b) applies. Confirm whether prior EC is required for the project, or for any individual building/plot. Apply for PPCB Consent to Establish wherever required. Keep project plans and area calculations ready and documented. Track future updates from PPCB and MoEF&CC. What Are the Benefits of the PPCB Clarification for Businesses? More uniform processing of applications across PPCB offices. A clear, threshold-based way to check EC applicability. Better project planning, since developers know what to expect earlier. Less confusion between Item 8(a) and Item 8(b) categories. Better preparation before applying for PPCB consent. This order does not remove any compliance requirement on its own, it only makes the existing requirements easier to apply consistently. Is the PPCB Clarification a Regulatory Relief or an Additional Compliance Burden? Aspect Regulatory Relief Additional Compliance Burden Uniformity across PPCB offices Yes, one procedure now applies to all offices and officers None; this is a pure benefit Projects below 50 ha, built-up area under 1,50,000 sq. m., no oversized building/plot Relief, no prior EC needed, only CTE Developer must still prove, with documentation, that no building/plot crosses 20,000 sq. m. Individual building/plot ≥20,000 sq. m. inside an otherwise exempt project No relief here New burden, that specific building/plot needs separate prior EC, which was easy to miss before this clarification FAR-based built-up area calculation Gives developers a recognized method (actual or FAR) to calculate area Burden, developers need accurate FAR workings, not just physical measurements, to avoid wrong classification Predictability for project planning Relief, developers can plan financing and construction schedules with more certainty. Burden, any change in design (e.g., enlarging one block) can shift the project into the EC-required category mid-planning Risk if MoEF&CC later disagrees None directly from this order Significant burden, project proponent remains responsible for obtaining EC if a contrary clarification comes later, even after starting work under CTE. Consent to Establish requirement Not removed by this order Burden, CTE is still mandatory even for projects that skip prior EC Existing EC holders Not affected, no new burden Must continue following original EC conditions in full It minimizes the uncertainty in the processing of the application by PPCB, but it doesn't minimize the compliance work itself. In fact, it adds a new requirement for developers: checking of the individual building/plot becomes a new item for careful analysis, because failure in this step would mean constructing the building without EC. What Happens If MoEF&CC Issues a Different Clarification? This part of the order deserves close attention. PPCB's current procedure is not final, it is a working arrangement until the Ministry responds. If MoEF&CC later issues a clarification that goes against PPCB's current approach, the project proponent will have to obtain Environmental Clearance in line with that new clarification. Responsibility for compliance stays with the project proponent, not PPCB. PPCB has also stated that it will not be liable for any construction activity carried out, or money spent, by a project proponent based on a Consent to Establish or Consent to Operate issued before such a contrary clarification arrives. In practice, PPCB may add this as a condition directly inside the CTE/CTO itself. This is worth planning for, not fearing. Developers who keep good documentation and stay updated on regulatory changes will be in the best position if the position changes later. What Happens to Projects That Already Have Environmental Clearance? Projects that have already obtained Environmental Clearance under the EIA Notification, 2006 must continue to comply with all conditions attached to that clearance. This new PPCB order does not cancel, replace, or loosen those existing EC conditions in any way. What Business Opportunities Are Created by the PPCB Clarification? The clarification creates room for focused compliance support work, including: Environmental Clearance applicability assessment Item 8(a)/8(b) project classification support Built-up area and FAR-based area assessment PPCB Consent to Establish assistance Environmental compliance documentation Ongoing regulatory monitoring for real estate and development projects What Should Businesses Do Before Starting Construction? Check the project category, building/construction, township, area development, or plotted development. Check the total project area against the 50-hectare threshold. Check the total built-up area against the 20,000 sq. m. and 1,50,000 sq. m. thresholds. Check the built-up area of every individual building or plot. Check FAR-based area where it applies. Confirm whether prior EC is required for the project or for any individual building/plot. Obtain PPCB Consent to Establish wherever applicable. Keep all supporting documents and area calculations on file. Track future updates from PPCB and MoEF&CC. How Can Corpseed Help With Environmental Clearance and PPCB Compliance? Working through these thresholds correctly, especially the individual building/plot check, is easy to get wrong without experience. Corpseed can support businesses through each step of this process. 1. Environmental Clearance Applicability Assessment Reviewing project details to determine whether prior EC is required under the current PPCB position. 2. Item 8(a) and 8(b) Project Classification Helping developers correctly classify their project as building & construction, or as township/area development/plotted development. 3. Project Area and Built-Up Area Assessment Working out total project area and total built-up area, on both actual and FAR basis. 4. PPCB Consent to Establish Assistance Supporting the CTE application process under the Water Act and Air Act. 5. Environmental Compliance Documentation Helping put together the documentation needed to support area calculations and classification decisions. 6. Ongoing Regulatory Monitoring Tracking future updates from PPCB and MoEF&CC so businesses are not caught off guard by a later change in position. If you are planning a construction, township, or area development project in Punjab, it is worth getting your project's EC applicability checked before construction begins, rather than after. PPCB's clarification gives officers one consistent way to handle Item 8(a) and Item 8(b) applications, replacing the inconsistent approach that different offices had been following. For developers, the message is simple: project type, total area, total built-up area, and the size of each building or plot all decide whether prior Environmental Clearance is needed. Consent to Establish remains a separate, ongoing requirement, regardless of whether EC applies. Businesses should treat this as PPCB's current working position, not a permanent rule, since MoEF&CC's own clarification is still pending. Careful area calculations, done early, remain the best way to avoid compliance problems later.

Subject

Summary: EPFO issued a circular on 23 July 2026 about a new way to report technical problems. The circular introduces the EPFO Samadhan Setu Portal, a web application built for EPFO field offices. This portal replaces the older Issue Tracker Portal, which has now been discontinued. The Samadhan Setu Web Application is meant for reporting technical issues linked to applications and utilities managed by EPFO's IS Division. It is not a portal for the general public or for individual PF members. It is an internal tool used by EPFO offices. The circular also lays down clear rules. These rules cover how to raise an issue, what details to add, how to avoid duplicate issues, and when an issue can be closed. This article explains the circular in plain language. It covers what Samadhan Setu is, how the process works, what officials need to do, and what this change means for EPFO field offices. Background of the EPFO Issue Reporting Framework 1. What Is the EPFO Technical Issue Reporting System? A technical issue reporting system is a tool for notifying the IT team about a problem. For EPFO, this means reporting problems in the software, applications, or online utilities that field offices use every day. These are not policy questions. They are technical glitches, such as an application not working properly or a utility displaying incorrect data. 2. How Were Technical Issues Reported Earlier? Before this change, EPFO field offices used the Issue Tracker Portal to report such problems. This portal served as the main channel for logging technical complaints related to EPFO's IT systems. The circular does not describe the internal workings of the earlier portal in detail. It simply states that this portal is now discontinued and replaced by Samadhan Setu. 3. Why Does EPFO Need a Dedicated Issue Reporting System? EPFO field offices depend on many digital applications for daily work. When something goes wrong in these systems, offices need a fast and clear way to inform the IT Division. A dedicated system helps keep every issue recorded in one place. It also helps the right team see the right problem without confusion. 4. Who Is Covered Under the New Issue Reporting Process? The circular is addressed to all Regional Provident Fund Commissioners (In-Charge) of Regional Offices. This means the process applies to EPFO field offices and their officials. This is not a portal for employers or employees to log in and use directly the circular concerns EPFO's internal technical issue reporting process, not a public-facing service. What Has Changed with the Launch of Samadhan Setu? 1. What Is the Samadhan Setu Web Application? The Samadhan Setu Portal is a web application deployed over the MPLS network. MPLS is a private network used inside EPFO for secure communication between offices. The portal is meant for EPFO field offices to report technical issues connected to applications and utilities managed by the IS Division. Officials use it after getting approval from the APFC or RPFC-II of their office. 2. Why Is the Issue Tracker Portal Being Discontinued? The circular states plainly that the existing Issue Tracker Portal will be discontinued once Samadhan Setu is deployed. In the future, all technical issue reporting for field offices moves to the new application. 3. Samadhan Setu vs Issue Tracker Portal Particular Earlier System New System Issue reporting platform Issue Tracker Portal Samadhan Setu Users EPFO field offices EPFO field offices Issue assignment Earlier process Automatic assignment based on category Supporting information As applicable Relevant supporting files/records Duplicate issue handling Earlier process Existing issue must be checked first 4. What Are the Key Changes in the Issue Reporting Process? A new portal, Samadhan Setu, replaces the Issue Tracker Portal. Issues are raised after approval from the APFC or RPFC-II. The application automatically assigns the concerned team based on category. Relevant supporting files must be attached where applicable. Offices must check for existing similar issues before raising a new one. The name and mobile number of the concerned official must be given. How Does the Samadhan Setu Portal Work? Step 1: Access the Samadhan Setu Portal The circular states that the portal is accessible over the MPLS network. This keeps the system limited to EPFO's internal, secure network rather than the open internet. Step 2: Log in Through the Field Office Login Each field office logs in using its own login ID. Every regional office would follow a similar login format for its own location. Step 3: Select "Report Issue" Once logged in, the user clicks the "Report Issue" tab, found on the left sidebar or top bar of the portal. This is where a new technical issue is raised. Step 4: Select the Relevant Category The user picks a category that matches the type of issue. Choosing the correct category is important because the system uses this category to decide which team receives the issue. Step 5: Enter the Issue Summary and Description Two fields need to be filled: Summary- a short line explaining the problem. Description- full details of what went wrong, filled in as relevant to the issue. Step 6: Upload Relevant Supporting Files The portal has an upload file box. Officials should attach supporting material where it helps explain the issue. Not every issue needs the same type of attachment; files should be added as relevant. Step 7: Automatic Assignment to the Concerned Team This step marks a real change from the earlier process. The circular says the user shall not assign any team on their own for a fresh filing. The application automatically assigns the concerned team based on the category selected. Step 8: Existence of the Same/Similar Issue Before reporting any issue, it should be checked whether the issue already exists and is either pending or resolved. If the issue already exists, it is advisable to add remarks to the existing issue rather than report a new one. Step 9: The Name and Mobile Number of the Concerned Official This is another important field where the name and mobile number of the official reporting the issue should be provided. Implementation Timeline and Operational Norms 1. When Was Samadhan Setu Deployed? The circular is dated 23 July 2026. It confirms that the Samadhan Setu Web Application has been deployed over the MPLS network for use by EPFO field offices. 2. When Is the Issue Tracker Portal Being Discontinued? The circular states that the existing Issue Tracker Portal is discontinued with the deployment of Samadhan Setu. No separate transition date is mentioned in the circular. 3. Who Needs to Follow the New Process? All Regional Provident Fund Commissioners (In-Charge) of Regional Offices and the officials working under them need to follow this new process for reporting technical issues. 4. What Are the Key Operational Requirements? Check for existing or similar issues first. Select the correct issue category. Provide a clear summary and description. Attach relevant supporting records. Give the name and mobile number of the concerned official. Avoid duplicate or irrelevant issue reporting. Why Has EPFO Implemented Samadhan Setu? To Create a Structured Technical Issue Reporting Process The new portal gives a fixed structure for reporting problems, using set fields like category, summary, description, and attachments. To Route Issues to the Correct Team By automatically assigning the relevant team based on category, the process removes the need for the field office to guess which team should handle a problem. To Reduce Duplicate Issues Requiring a check for existing issues before raising a new one helps avoid the same problem being logged multiple times. To Improve Communication Recording the name and mobile number of the concerned official means the resolution team has a direct point of contact for follow-up. To Support Better Issue Resolution A clear summary, detailed description, and relevant supporting documents give the concerned team more context to examine and resolve the problem. To Create a Standardised Internal Process Overall, the circular sets a common format that every field office is expected to follow. This does not guarantee any fixed resolution time, but it does bring more consistency to how issues are logged. What Information Must Be Provided While Raising an Issue? 1. Issue Category The category tells the system what type of problem is being reported. It automatically assigns the issue to the correct team. 2. Issue Summary A short line that gives a quick idea of the problem at a glance. 3. Detailed Issue Description A fuller explanation of what is going wrong, filled in as relevant to the specific issue. 4. Supporting Files and Documents Files that help explain the problem, uploaded through the file box on the portal, where applicable. 5. Name and Mobile Number of the Concerned Official Contact details of the official raising the issue, so the resolution team can reach out if needed. 6. Other Relevant Records Such as UAN, Challan/TRRN Numbers and Screenshots Where relevant, offices should attach records like Member IDs (MIDs), UAN, challan or TRRN numbers, and screenshots, along with any other necessary records connected to the issue. Information Why It Matters Category Helps route the issue Summary Gives a quick view of the problem Description Explains the issue in detail Supporting records Helps the concerned team examine the issue Official's contact details Supports communication What Are the Guidelines for Raising and Closing Issues on Samadhan Setu? 1. How Should CPGRAMS-Related Cases Be Reported? CPGRAMS is the Centralised Public Grievance Redress and Monitoring System used across government departments. If an issue is based on a pending CPGRAMS grievance, the office must clearly mark it as a "CPGRAM case" while raising it on Samadhan Setu. Before raising such a case, the office must confirm that the matter is genuinely technical in nature. A policy issue is not to be raised here; the concerned business division at Head Office should instead resolve it. 2. When Can an Issue Be Marked as Closed? The circular gives specific situations where an issue becomes infructuous and can be marked as Closed: Settlement or rejection of the related claim. Resolution through the Special VDR/App functionalities. Resolution through other existing mechanisms. Issuance of speaking orders. Clarifications issued through Head Office circulars. Introduction of new functionality in the application software. This is not an automatic closure rule for every issue. It applies only where one of these specific situations makes the original issue no longer relevant. 3. What Supporting Documents Should Be Attached? While raising an issue, offices should attach all relevant supporting documents connected to that specific problem, such as: Clear scanned copies PDFs Text files MIDs (Member IDs) UAN Challan/TRRN numbers Screenshots Any other necessary records These documents should be attached to facilitate faster and clearer resolution, based on what is relevant to the issue at hand. 4. Which Process or Operational Queries Should Not Be Raised? Field offices are asked not to raise issues that are actually questions about process flow or the operational procedure of an application. Such questions should instead be checked against: Relevant user manuals Standard Operating Procedures (SOPs) Instructions or circulars issued by Head Office 5. Why Should Redundant or Repetitive Issues Be Avoided? The circular clearly states that redundant, repetitive, or irrelevant queries should not be raised on Samadhan Setu. Doing so adds unnecessary volume to the system and can make it harder for teams to focus on genuine technical problems. What Is the Impact of Samadhan Setu on EPFO Field Offices? Impact on Regional and Field Offices Field offices now use a single, structured portal for all technical issue reporting instead of the earlier Issue Tracker Portal. Impact on Officials Raising Technical Issues Officials need to learn the new login process, select the right category, write clear summaries and descriptions, attach relevant documents, and provide contact details for every issue raised. Impact on IT and Concerned Resolution Teams Because issues are automatically assigned by category, the concerned resolution teams should receive issues that are already sorted by subject area, without manual routing. Impact on Technical Issue Resolution Clearer descriptions and relevant supporting records give resolution teams more useful information to work with when examining a reported problem. Impact on Internal Digital Operations The change reflects a broader move within EPFO toward a more organised, digital way of managing internal technical support requests across field offices. How Can EPFO Offices Follow the New Samadhan Setu Process? 1. Check Whether the Issue Falls Under the Portal Confirm that the problem is a genuine technical issue linked to an EPFO application or utility, not a policy or process question. 2. Check for an Existing Similar Issue Search the portal to see if the same or a similar issue has already been raised or resolved. 3. Select the Correct Issue Category Pick the category that matches the problem, since this decides which team receives the issue. 4. Provide Complete and Accurate Details Fill in a clear summary and a full description of the issue. 5. Attach Relevant Supporting Evidence Add scanned copies, PDFs, screenshots, UAN, challan/TRRN numbers, or other records connected to the issue. 6. Provide Correct Contact Details Add the name and mobile number of the concerned official raising the issue. 7. Clearly Identify CPGRAMS-Linked Cases Mark the issue as a "CPGRAM case" where it is based on a pending CPGRAMS grievance and is genuinely technical. 8. Avoid Policy and Process Clarification Queries Refer such questions to user manuals, SOPs, or Head Office instructions instead of raising them on the portal. 9. Avoid Duplicate, Repetitive and Irrelevant Issues Do not raise the same concern more than once, and skip queries that are not relevant to a genuine technical problem. 10. Follow Relevant Manuals, SOPs and Head Office Instructions Use these existing resources for process-related doubts rather than the issue reporting portal. Samadhan Setu Checklist Correct category selected Existing issue checked Issue summary added Detailed description added Relevant documents attached Official's name provided Mobile number provided CPGRAMS case identified, where applicable What Are the Benefits of the Samadhan Setu Portal? More Structured Technical Issue Reporting Every issue follows the same format, with category, summary, description, and attachments. Automatic Assignment to the Concerned Team Offices no longer need to decide which team should handle an issue; the system does this based on category. Better Issue Documentation Supporting files and clear descriptions mean each issue carries more useful context from the start. Reduced Duplicate Reporting Checking for existing issues before raising a new one can cut down repeated tickets for the same problem. Better Communication with Concerned Officials Recording contact details allows resolution teams to reach the right person directly. Improved Internal Issue Management A single portal, in place of two overlapping systems, keeps issue tracking centralised for field offices. More Standardised Technical Issue Handling The rules for CPGRAMS cases, closure conditions, and process-related queries bring more consistency to how field offices report and manage technical issues. Is Samadhan Setu a Better Decision or an Additional Operational Burden? 1. Why the New System Can Improve Issue Management? Automatic team assignment, a duplicate-check requirement, and clear documentation fields can make technical issue handling more organised for EPFO field offices. 2. What Additional Work Will EPFO Offices Need to Do? Learn the new portal and login process. Check old or existing issues before raising a new one. Enter complete summary and description details. Attach relevant supporting records. Choose the correct category every time. Avoid raising irrelevant or repetitive tickets. 3. Does the New Process Create Operational Challenges? Some adjustment period is likely, since officials need to get used to a new portal and a more detailed reporting format. The circular does not suggest this adjustment will be difficult, but a short learning curve is a normal part of any system change. 4. Short-Term Process Changes vs Long-Term Benefits Short-Term Change Potential Long-Term Benefit Learning the new portal More standardised reporting More complete issue details Better issue understanding Checking existing issues Fewer duplicate tickets Correct category selection Better issue routing 5. Overall Assessment Samadhan Setu asks field offices to follow a more detailed process than before. In exchange, it offers a more organised way to report and track technical issues, with automatic team routing and clearer documentation. What Opportunities Can the New Digital Issue Reporting System Create? Better Digital Governance A single structured portal supports more organised internal governance of technical issue handling at EPFO. Improved Internal Issue Tracking Centralising all issues on one platform makes it easier to keep a record of what has been reported and resolved. Better Identification of Recurring Technical Problems Category-based logging can help EPFO notice patterns in the type of technical issues that come up often. More Standardised Application Support A common format for reporting issues across all field offices supports more consistent application support overall. Better Data for Technical Issue Management Structured fields like category, summary, and description create more usable data for reviewing and managing technical issues over time. What Should EPFO Field Offices Do After the Launch of Samadhan Setu? Move away from the discontinued Issue Tracker Portal. Use Samadhan Setu for applicable technical issues. Ensure concerned officials understand the new process. Check whether a similar issue already exists. Select the correct issue category. Provide complete details in the summary and description. Attach relevant supporting documents. Provide official contact details. Follow manuals, SOPs, and Head Office instructions for process queries. Avoid repetitive and irrelevant issues. How Can Corpseed Help Businesses With EPFO and Compliance Requirements? While Samadhan Setu is an internal EPFO tool for field offices, many organisations still need help understanding how EPFO processes work and staying compliant with PF rules. EPFO and PF Compliance Guidance:  Support in understanding EPFO registration, contribution, and filing requirements for organisations. Support in Understanding EPFO Processes:  Help in reading and interpreting EPFO circulars, forms, and procedures in simple terms. Documentation and Compliance Assistance:  Assistance with preparing and organising documents needed for EPFO-related filings. Support for EPFO-Related Compliance Requirements:  Guidance on meeting ongoing EPFO compliance obligations connected to payroll and labour law. End-to-End Regulatory Compliance Assistance:  Broader support across EPF Compliance, Payroll Compliance, and Labour Law Compliance for organisations that want a clearer view of their obligations. Organisations that need help understanding EPFO Registration, PF Registration, or related compliance requirements can reach out to Corpseed for guidance.

Subject

Summary: On 25 July 2026, the Bureau of Indian Standards (BIS), under the Department of Consumer Affairs, published a fresh Gazette notification announcing the BIS standards amendment 2026. This notification, issued on 21 July 2026 under Sub-rule (1) of Rule 15 of the Bureau of Indian Standards Rules, 2018, amends eight Indian Standards across a wide range of product categories from bicycles and LPG cylinders to aluminium cans, snowboard equipment, automotive RFID systems, fluid power O-rings, food-grade metal cans, and stainless-steel infant feeding bottles. If your company is involved in producing, importing, or selling any of these products in India, then this notification has a direct bearing on your BIS Licence, your Product Test Procedures, and your Certificate Renewal Process. If manufacturers neglect the new amendment numbers, they may fail BIS surveillance audits and the ISI mark renewal process . This guide breaks down every amendment in simple language, explains exactly who is affected, and lays out a practical roadmap for compliance. Hence, you know what to do before the transition window closes on 19 January 2027. Key Highlights of the Notification Issued by the Bureau of Indian Standards (BIS), Department of Consumer Affairs, Government of India. Notification dated 21 July 2026 published in the Gazette of India (Extraordinary, Part III Section 4) on 25 July 2026. Issued under Rule 15(1) of the BIS Rules, 2018. Amends 8 Indian Standards spanning consumer goods, industrial components, and food-contact packaging. All eight amendments take effect from 20 July 2026. Manufacturers get a transition window the pre-amendment version of each standard remains valid only until 19 January 2027. After 19 January 2027, products must conform to the amended standard to retain BIS certification/ISI marking. The amended standards include: bicycle cranks and chain wheels, LPG welded steel cylinders, aluminium beverage cans, snowboard-boot ski-binding interfaces, automotive RFID systems, fluid power O-rings, three-piece metal food/beverage cans, and stainless-steel infant feeding bottles. Products affected span consumer durables, packaging, automotive components, and food-contact articles, several of which fall under mandatory BIS certification (Compulsory Registration Scheme or ISI mark). Manufacturers holding an existing BIS licence for any of these 8 standards must update their Quality Assurance Plan (QAP) to reflect the amendment number. Non-compliance after the transition date can result in rejection during BIS surveillance inspection, licence non-renewal, or market withdrawal of non-conforming stock. Exporters relying on IS/ISO dual-numbering standards (like the O-ring and snowboard-boot standards) should also check equivalence with the referenced ISO standard. The Regulatory Framework 1. Bureau of Indian Standards Rules, 2018 The BIS Rules, 2018 govern how BIS formulates, amends, and notifies Indian Standards. Rule 15(1) specifically empowers BIS to notify amendments to already established standards through the Official Gazette, which is the legal basis for this July 2026 notification. 2. Role of the Bureau of Indian Standards BIS is India's national standards body. It sets product specifications (Indian Standards, or "IS" numbers), operates the ISI mark scheme, and enforces the Compulsory Registration Scheme (CRS) for select product categories. Many of the products covered in this notification aluminium cans, metal food cans, LPG cylinders, and infant feeding bottles fall under mandatory or safety-critical certification regimes. 3. Objective of the Amendment Instead of introducing completely new standards, BIS has chosen to revise the existing, recognized Indian Standards to align with current testing standards or limits. This is an essential part of India’s quality infrastructure and is a mandatory process for every license holder of the concerned standard. 4. Industries Covered The amendment touches multiple industries simultaneously: Bicycle and cycle component manufacturing LPG cylinder and industrial gas equipment manufacturing Beverage packaging (aluminium and metal cans) Winter sports equipment (snowboard boots) Automotive electronics (RFID systems) Fluid power / hydraulic-pneumatic component manufacturing (O-rings) Food and beverage metal packaging Infant care products (stainless steel feeding bottles) What Has Changed: Standard-by-Standard Breakdown S. No. Indian Standard Product Amendment Effective From Old Standard Valid Until 1 IS 1281:2025 (4th Revision) Bicycles Cranks and Chain Wheels Amendment No. 1, July 2026 20 July 2026 19 January 2027 2 IS 3196 (Part 1):2013 (6th Revision) Welded Low Carbon Steel Cylinders (LPG, >5 litres) Amendment No. 5, July 2026 20 July 2026 19 January 2027 3 IS 14407:2023 (1st Revision) Aluminium Cans for Beverages Amendment No. 1, July 2026 20 July 2026 19 January 2027 4 IS 15841:2009 / ISO 11634:1996 Snowboard-Boots Interface with Ski-Binding Amendment No. 1, July 2026 20 July 2026 19 January 2027 5 IS 16722:2018 RFID System for Automotive Applications Amendment No. 2, July 2026 20 July 2026 19 January 2027 6 IS 17891 (Part 3):2023 / ISO 3601-3:2005 Fluid Power Systems O-rings (Quality Acceptance Criteria) Amendment No. 1, July 2026 20 July 2026 19 January 2027 7 IS 18427:2024 Three-Piece Round Open-Top Metal Cans for Food & Beverages Amendment No. 1, July 2026 20 July 2026 19 January 2027 8 IS 18800:2023 Stainless Steel Feeding Bottle for Infants Amendment No. 1, July 2026 20 July 2026 19 January 2027 Note: The Gazette notification lists the amendment number, month/year of issue, date of establishment, and the sunset date for the pre-amendment standard for each of the 8 standards above. It does not specify the detailed technical content of each amendment (i.e., exactly which clauses, test methods, or parameters were changed within each standard). Manufacturers should procure the full amendment document/errata for their specific standard from BIS to identify the precise technical modifications applicable to their product. Old Standard vs New Standard: What It Means for You Every standard listed above has a 6-month transition window (20 July 2026 to 19 January 2027) during which manufacturers may continue operating under the pre-amendment version. From 20 January 2027 onward, only the amended version of the standard will be recognised for BIS certification, testing, and surveillance purposes. Implementation Timeline / Compliance Deadlines Milestone Date Notification signed 21 July 2026 Notification published in Gazette of India 25 July 2026 Amendments take effect 20 July 2026 Transition period for existing licence holders 20 July 2026 – 19 January 2027 Deadline to align with amended standards 19 January 2027 Amended standard becomes sole applicable version From 20 January 2027 This is not a distant deadline the roughly 6-month transition window is tight for manufacturers who need to update product design, testing documentation, or Quality Assurance Plans (QAP) filed with BIS. Why the Government Introduced These Changes While the notification itself is procedural (it simply announces that amendments "have been established"), BIS routinely amends standards to: Improve quality control by tightening test methods or acceptance criteria. Enhance consumer and product safety, particularly relevant for LPG cylinders and infant feeding bottles. Maintain alignment with international ISO standards visible here in the dual IS/ISO numbering for the snowboard-boot and O-ring standards. Support export competitiveness by keeping Indian Standards technically current with global benchmarks. Strengthen traceability and consistency across licensed manufacturers using the same base standard. Impact on Businesses 1. Bicycle & Cycle Components Manufacturers (IS 1281) Manufacturers of crank and chain wheels having a BIS license under IS 1281:2025 should refer to Amendment No. 1 and update testing and QAP documentation before the deadline for transition. 2. LPG Cylinder Manufacturers (IS 3196 Part 1) This is a critical safety category product. Amendment No. 5 to IS 3196 (Part 1):2013 is the fifth amendment cycle of this standard, showing continuous improvement in safety measures. Manufacturers of cylinders can anticipate an inspection of this amendment from BIS. 3. Aluminium & Metal Can Manufacturers (IS 14407, IS 18427) Two separate standards in this notification affect beverage and food packaging aluminium cans (IS 14407) and three-piece metal cans (IS 18427). Packaging manufacturers supplying FMCG and beverage brands should coordinate compliance across both standards if they manufacture multiple can formats. 4. Snowboard/Winter Sports Equipment Importers (IS 15841) As this standard is linked to ISO 11634:1996, importers and distributors of snowboard boots should verify whether their supplier's ISO compliance documentation also satisfies the amended Indian Standard. 5. Automotive Component & RFID System Manufacturers (IS 16722) This is the second amendment to IS 16722:2018, suggesting an evolving standard. Automotive RFID system suppliers, especially those supplying OEMs, should treat this as a priority compliance item given the fast pace of change in this standard. 6. Fluid Power / Hydraulic Component Manufacturers (IS 17891 Part 3) O-ring manufacturers supplying fluid power systems need to review the amended quality acceptance criteria under Part 3 of IS 17891, referenced against ISO 3601-3:2005. 7. Infant Feeding Bottle Manufacturers (IS 18800) Given the sensitive end-use (infant care), manufacturers of stainless-steel feeding bottles should treat compliance with Amendment No. 1 as an urgent, non-negotiable priority both for regulatory and brand-trust reasons. 8. MSMEs vs Large Manufacturers Large manufacturers who have their own regulatory experts will be able to incorporate such changes within the framework of existing quality assurance programs quite easily. MSMEs, on the other hand, will lack in-house expertise in this respect and will need help to comprehend amendment documents and update QAPs. How Businesses Can Achieve Compliance Identify applicability- Confirm which of the 8 amended standards apply to your product portfolio. Procure the official amendment document- Obtain the specific amendment text/errata from BIS for each applicable standard. Conduct an internal compliance audit- Compare your current product specification and test reports against the amended standard. Review your BIS licence and QAP- Your existing Quality Assurance Plan filed with BIS may need to be updated to reference the new amendment number. Coordinate with your testing laboratory- Ensure your in-house or NABL-accredited external lab has updated test protocols matching the amendment. Update technical documentation- Revise product specification sheets, test certificates, and manufacturing records. Plan for surveillance/renewal inspections- BIS surveillance officers will check for the amended standard once the transition period lapses. Train quality control and production staff on any parameter changes introduced by the amendment. Build in a buffer before 19 January 2027- Don't wait until the deadline month to start the compliance process. Benefits for Businesses Avoid penalties and licence suspension by staying ahead of the compliance deadline Uninterrupted use of the ISI mark, protecting market access and retailer trust Smoother BIS surveillance audits with updated, amendment-aligned documentation Stronger export credibility, especially for standards cross-referenced with ISO Reduced risk of product recall or stock rejection due to non-conforming specifications Competitive advantage over slower-moving competitors who delay compliance Right Decision or Additional Burden? For manufacturers with well-established quality systems in place, these modifications pose no challenge but are merely part of the standard updating process. Most modifications usually represent fine-tuning of the current rules and do not require the introduction of completely new procedures for compliance. A 6-month period is quite adequate for major manufacturers with internal regulatory expertise. However, for MSMEs and small producers, who lack such expertise, even routine modification may be a challenge, as it takes time to understand the amendment documents, collaborate with testing facilities, and make changes to the filing with BIS. The notice alone provides no easier way to deal with smaller manufacturers. Business Opportunities Created This amendment cycle also opens opportunities for: BIS compliance and regulatory consultants helping manufacturers interpret and implement changes NABL-accredited testing laboratories conducting amendment-specific product testing Packaging and can manufacturers who can offer amendment-compliant products to FMCG brands ahead of competitors Quality system and documentation support providers assisting MSMEs with QAP updates What Manufacturers Often Get Wrong A pattern that regulatory consultants see repeatedly with standard amendments like this one is treating them as a "paperwork-only" update. In reality, amendments to established standards can touch multiple layers of a manufacturer's operations simultaneously: Design and specification:  if the amendment tightens a dimensional tolerance, material grade, or performance threshold, the product itself may need re-evaluation, not just the paperwork describing it. In-house testing infrastructure:  if a new test method or acceptance criterion is introduced, existing lab equipment or test protocols may not be sufficient, requiring either equipment upgrades or outsourcing to an accredited external lab. Supplier and raw material chain:  for packaging-related standards like aluminium cans or metal food cans, a change in the base standard can cascade down to raw material or component suppliers, who also need to confirm their inputs meet the revised specification. Batch and inventory management: manufacturers with existing inventory produced under the old standard need a clear plan for how that stock is treated once the transition window closes on 19 January 2027. Because the amendment numbers vary by standard Amendment No. 1 for some, Amendment No. 2 for IS 16722, and Amendment No. 5 for IS 3196 (Part 1) the maturity and complexity of each change is also likely to differ. A fifth amendment cycle, as seen with the LPG cylinder standard, often reflects a standard that has been under continuous refinement, which can mean more substantial changes than a first-time amendment. A Closer Look at the Compliance Risk For manufacturers holding a live BIS licence under any of these 8 standards, the practical risk is not abstract it plays out in three specific scenarios: Surveillance audit after the transition date. BIS conducts periodic surveillance visits to licensed manufacturing units. If a surveillance officer visits after 19 January 2027 and finds the QAP, test records, or product specification still referencing the pre-amendment standard, this is flagged as a non-conformance, which can trigger corrective action requirements or, in more serious cases, licence suspension. Licence renewal. BIS licences are typically renewed periodically. A renewal application submitted after the transition deadline, but still referencing the old standard, is likely to face queries or rejection until updated documentation is submitted. Market and retailer confidence. For consumer-facing products like beverage cans, infant feeding bottles, and bicycle components, large retailers and brand owners increasingly conduct their own vendor compliance checks. A supplier still operating under a superseded standard can lose shelf space or contracts to a competitor who is already compliant, independent of what BIS itself does. Understanding which of these three risk categories applies most directly to your business is a useful starting point for prioritising your compliance timeline. Sector-by-Sector Compliance Checklist To make this notification actionable rather than just informational, here is a starting checklist tailored to each affected category: Manufacturers of bicycles and bicycle components (IS 1281): Pull Amendment No. 1, cross-check the specifications for cranks and chain wheel dimensions and materials, revise your QAP, and check with your test laboratory on whether the existing test jigs are still valid. LPG cylinder manufacturers (IS 3196 Part 1): In view of this being the fifth amendment cycle, please make this a priority safety assessment exercise. Cross-check the welding, wall thickness, and pressure test parameters as per Amendment No. 5, and ensure that your test laboratory is calibrated and up to date. Manufacturers of aluminium and metal cans (IS 14407, IS 18427): In case you are manufacturing both aluminium and metal three-piece cans, comply with both standards simultaneously to prevent duplication of effort. Check with your raw material suppliers (coils/sheets) on any flow-down of specifications. Suppliers of snowboard boots and winter sports equipment (IS 15841): Please confirm with your overseas supplier on whether their certification under ISO 11634:1996 qualifies them to be compliant with Amendment No. 1 as well. Automotive RFID system manufacturers (IS 16722): As the second amendment to this standard, review what changed compared to Amendment No. 1, and assess whether it affects hardware design, frequency parameters, or only test/documentation requirements. Manufacturers of fluid power and O-rings (IS 17891 Part 3): Cross-check the revised quality acceptance criteria with the present batch testing process and revise the inspection records accordingly. Infant feeding bottles (IS 18800): Considering that infant safety is of critical importance in its end-use application, you should give priority to this category in case you are manufacturing any other products from the above-listed categories. Why Choose Corpseed? Navigating a multi-standard BIS amendment notification, especially one that spans consumer goods, packaging, automotive components, and infant-care products requires more than just reading the Gazette. Corpseed supports manufacturers through: Interpreting the exact scope and applicability of each BIS amendment to your specific product Conducting a compliance gap analysis between your current specification and the amended standard Assisting with BIS licence review, QAP updates, and documentation realignment Coordinating with testing laboratories for amendment-specific product testing Preparing your facility and paperwork for BIS surveillance inspections Providing end-to-end regulatory advisory so you don't have to track Gazette notifications on your own Corpseed's Core Message Regulatory deadlines don't wait, and BIS surveillance audits don't offer much leniency for outdated documentation. If your business manufactures bicycles, LPG cylinders, aluminium or metal cans, snowboard equipment, automotive RFID systems, O-rings, or infant feeding bottles, the time to review your BIS licence against this July 2026 amendment is now, not in December 2026. Talk to Corpseed's regulatory compliance team today to get a clear compliance roadmap before the 19 January 2027 deadline. Conclusion The 2026 amendment to BIS standards encompasses an astonishing number of industries, including bicycles, LPG cylinders, beverage cans, winter sports equipment, automobile electronic devices, fluid power elements, food packing, and infant care products. Though the notice issued regarding the same is just another regulatory update under Rule 15(1) of the BIS Rules 2018, the deadline is real, as manufacturers will only have until 19 January 2027 to meet the requirements of the amendments, after which the old versions will become obsolete. This can be easily managed by manufacturers who have their own in-house regulatory team. But for MSMEs and other small manufacturers, it might become a documentation and testing burden if delayed too much. Better be safe than sorry; review your relevant standard now.

Subject

Summary: The Ministry of AYUSH notified the Drugs (Eleventh Amendment) Rules, 2026 in the Gazette notification on 24 July 2026. The amendment makes changes to the Drugs Rules, 1945 pursuant to the power conferred under Section 33N of the Drugs and Cosmetics Act, 1940. The amendment is based on the draft notification which was initially published for comments in February 2025, dated 14 February 2025). The amendment applies specifically to manufacturers operating under the Ayurvedic, Siddha, Unani, Sowa-Rigpa, and Homoeopathy systems of medicine. It touches licensing, product coding, labelling, inspection procedures, stability studies, inspector qualifications, and the Good Manufacturing Practice (GMP) schedules that govern factory premises and quality systems for these manufacturers (Schedule M-I for Homoeopathy, and Schedule T for Ayurveda, Siddha, Sowa-Rigpa, and Unani). This guide summarises the changes rule by rule, sets out the compliance timelines specified in the notification, and offers a practical checklist for manufacturers assessing what needs to change in their operations. All statements below are based directly on the text of the notification where a point is not explicitly addressed in the gazette, that is noted rather than assumed. Regulatory Background The parent law that governs drug manufacturing, selling, and distribution in India is the Drugs and Cosmetics Act of 1940, which covers AYUSH (Ayurveda, Yoga and Naturopathy, Unani, Siddha, and Homeopathy) drugs. The Drugs Rules of 1945, which are formulated under the aforementioned Act, provide all technical details. The Ministry of AYUSH periodically amends these rules to reflect changes in manufacturing practice, quality expectations, and administrative processes. The Eleventh Amendment was made after consultation with the Ayurvedic, Siddha and Unani Drugs Technical Advisory Board, as required under the Act. It amends several individual rules (154 through 169) as well as two full GMP schedules: Schedule M-I (Homoeopathy) and Schedule T (Ayurveda, Siddha, Sowa-Rigpa, and Unani). Key Changes at a Glance Manufacturing licences issued under Rules 154 and 154A will remain perpetually valid the periodic renewal requirement is removed. Rules 156 and 156A, which dealt with licence renewal procedures, are omitted from the Drugs Rules, 1945. A one-year exemption window is introduced for single-plant-ingredient, extract-based patent or proprietary formulations under Rule 157, along with a new naming requirement. A uniform, standardised specific product code format is introduced under Rule 158B, replacing the earlier system existing codes must be reissued in the new format within two years. Qualification criteria for technical experts under Rule 160B are revised, and a microbiologist qualification route is added. Labelling requirements under Rule 161 are relaxed to allow display of full ingredient lists and other label information via QR code, GTIN, or barcode where space is limited. New provisions under Rule 161B govern shelf-life determination based on accelerated versus real-time stability studies. Inspections under Rule 162 move to a risk-based approach rather than a blanket inspection model. Central Drugs Laboratory testing provisions (Rules 163BB and 163C) are updated to include AYUSH Ministry-approved autonomous testing laboratories. Inspector qualification requirements under Rule 167 are revised. A new labelling disclosure requirement for cosmetic categories (Husn-e-Afza/Azhagh-sadhan) is added under Rule 169, with compliance required by 31 July 2028. Schedule M-I (Homoeopathy GMP) and Schedule T (Ayurveda, Siddha, Sowa-Rigpa, Unani GMP) are substantially rewritten, covering premises, personnel, equipment, quality control, raw materials, and records, with compliance required by 31 July 2029. A new supplementary GMP guideline (Schedule T, Paragraph D) is added specifically for Rasaushadhi, Rasamarunthukal, and Kushtajat herbo-mineral-metallic formulations addressing handling of mercury, lead, and arsenic. Rule-by-Rule Changes 1. Licensing: Rules 154, 154A, 156, 156A Under the amendment, any manufacturing licence issued under Rule 154(1) or Rule 154A (1) "shall remain valid perpetually." This removes the need for periodic renewal of these licences. Correspondingly, Rules 156 and 156A, which set out renewal-related provisions, are omitted from the Drugs Rules, 1945 altogether. The notification does not specify transitional treatment for licences that were already up for renewal at the time of commencement manufacturers with licences nearing their previous renewal date should confirm treatment with their state licensing authority. 2. Rule 157: Patent and Proprietary Medicines Rule 157(1C) is amended with a new proviso. Extract-based, single-plant-ingredient Ayurvedic, Siddha, Sowa-Rigpa, or Unani formulations that are licensed, or are to be licensed, as patent or proprietary medicines (as defined under Section 3(h)(i) of the Act) are exempted from the relevant sub-rule for one year from the commencement of the Eleventh Amendment Rules. A further proviso requires that such single-ingredient extract-based formulations be named with a prefix or suffix specific to the licensee intended to distinguish licensee-specific branding from generic ingredient names. 3. Rule 158B: Uniform Product Coding A new sub-rule (VII) sets out a standard pattern for the "specific product code" assigned to AYUSH drugs. The pattern combines: The State or Union Territory code, a designation of licence type (D or E, denoting licence or loan licence), the serial number of the licence, the system of medicine (classical or patent/proprietary referred to as "PP"), the product's serial number and the year of product approval. The Central Government will specify the details of the State/UT code component separately. Existing product codes must be reissued in this new pattern within two years of the amendment's commencement. Notably, the rule also states that the State/UT code, licence-type designator, and licence serial number embedded within the product code will itself be treated as the manufacturing licence number. 4. Rule 160B: Technical Personnel Qualifications The qualification criteria for experts under Rule 160B(2)(ii)(b) are revised. The updated item (i) recognises a degree qualification under Schedule II of the Indian Medicine Central Council Act, 1970, or a qualification recognised under Section 35 of the National Commission for Indian System of Medicine Act, 2020, or a graduate degree in pharmacy (in Ayurveda, Siddha, Sowa-Rigpa, or Unani) from a recognised university. A new item (iv) is inserted, recognising a microbiologist holding a bachelor's degree in microbiology with six months' experience in quality control, or a postgraduate degree in microbiology from a recognised university. 5. Rule 161: Labelling The second proviso to Rule 161(1) is substituted. Where the list of ingredients in a medicine is too long to fit on the label, the list may now be printed separately and enclosed with the packaging, with a reference to this on the label or displayed through a QR code, Global Trade Item Number (GTIN), or barcode. Rule 161(3)(iv) is also substituted to require that the specific product code, preceded by the words "specific product code" or "S.P.C.", be printed or written on the label within two years of the amendment's commencement. A new sub-rule 161(3A) permits all label information to additionally be displayed through QR code, GTIN, or barcode. 6. Rule 161B: Stability Studies and Shelf Life A new sub-rule (2A) sets out how shelf life is to be determined when a drug's approval was based on accelerated stability studies rather than real-time studies. Depending on whether the accelerated study covered three or six months, the licensee sets a shelf life of one or two years, respectively, and submits the accelerated study report to the licensing authority referred to in Rule 151. The licensee must then submit a real-time stability study report within one year of the expiry of the shelf life that was granted based on the accelerated data. An explanation clarifies that any shelf life determination beyond two years must be based on real-time stability study data, not accelerated data alone. A further new sub-rule (9) states that where the dosage form of an Ayurvedic, Siddha, or Unani drug (as defined under Section 3(a) of the Act) is changed, the expiry date for that drug category must be supported by accelerated or real-time stability study data, as applicable. 7. Rule 162: Risk-Based Inspection Clause (i) of Rule 162 is substituted to require inspectors to inspect all premises licensed for manufacture of Ayurveda, Siddha, Sowa-Rigpa, or Unani drugs within their allotted area "as needed as per risk-based approach," rather than on a fixed periodic basis, to verify compliance with licence conditions and the Act and Rules. 8. Rules 163BB and 163C: Testing Laboratories Rule 163BB (1) removes a cross-reference to Section 11(2) of the Act. A new sub-rule (4) designates the authorised drugs testing laboratory of an autonomous organisation of the Ministry of AYUSH, where approved under Part XVIA, to act as the Central Drugs Laboratory for testing suspected Ayurveda, Siddha, Unani, Sowa-Rigpa, or Homoeopathy drug samples referred to under Section 11(2) of the Act. Rule 163C is amended in two places to add a reference to "Central Drugs Laboratory, as the case may be" alongside the existing reference to the Ghaziabad (Uttar Pradesh) facility. 9. Rule 167: Inspector Qualifications Rule 167 is substituted in full. A person appointed as an Inspector under Section 33G of the Act must hold a degree in Ayurveda, Siddha, Sowa-Rigpa, or Unani systems of medicine, or a degree in pharmacy of these systems, conferred by a university recognised for this purpose by the Central Government or a State Government. 10. Rule 169: Cosmetic Labelling A new clause (3A) requires that, for the category of Saundarya Prasadak (Husn-e-Afza) / Azhagh-sadhan (cosmetic preparations), the quantity of base material be printed or written on the label in addition to the information already required under clause 3. This requirement must be complied with by 31 July 2028. Compliance Timeline The notification specifies several distinct deadlines, tied to the commencement date of the Eleventh Amendment Rules (24 July 2026, the date of publication) or to fixed calendar dates: Requirement Timeline Applicable Rule Reissue of existing product codes in the new uniform format Within 2 years of commencement Rule 158B(VII)(c) Printing of specific product code (S.P.C.) on labels Within 2 years of commencement Rule 161(3)(iv) Exemption window for single-ingredient extract-based patent/proprietary formulations 1 year from commencement Rule 157(1C) Real-time stability study report following accelerated-data shelf life Within 1 year of expiry of granted shelf life Rule 161B(2A)(b) Base material quantity disclosure for cosmetic categories (Husn-e-Afza/Azhagh-sadhan) By 31 July 2028 Rule 169(3A) Compliance with amended Schedule M-I (Homoeopathy GMP) By 31 July 2029 Schedule M-I, Para 12 Compliance with amended Schedule T (Ayurveda/Siddha/Sowa-Rigpa/Unani GMP) By 31 July 2029 Schedule T, Para 9 Timelines above are as stated in the notification. Where a provision does not specify a deadline (for example, risk-based inspection or revised inspector/technical staff qualifications), it is understood to apply from the date of commencement 24 July 2026 unless a licensing or state authority issues separate transitional guidance. Old Rule vs New Rule: Selected Comparisons Licence Validity Aspect Position Before Amendment Position After Amendment Licence validity Subject to periodic renewal under Rules 156/156A Perpetually valid once issued (Rules 154(4), 154A(5)) Renewal rules Rules 156 and 156A in force Rules 156 and 156A omitted Product Coding Aspect Position Before Amendment Position After Amendment Product code format No single uniform national pattern specified in this rule Standard pattern: State/UT code + licence type + licence serial + system of medicine + product serial + approval year Transition N/A Existing codes to be reissued in new format within 2 years Ingredient and Label Information Display Aspect Position Before Amendment Position After Amendment Long ingredient lists Printed on label or separately enclosed, referenced on label May additionally be displayed via QR code, GTIN, or barcode General label information Physical label only May also be displayed via QR code, GTIN, or barcode (Rule 161(3A)) Shelf-Life Determination Aspect Position Before Amendment Position After Amendment Basis for shelf life beyond 2 years Not specifically addressed in this manner Must be based on real-time stability study data Accelerated-study-based approval No defined follow-up mechanism in this rule Real-time study report due within 1 year of expiry of the granted shelf life Inspections Aspect Position Before Amendment Position After Amendment Inspection approach Inspector to inspect all licensed premises in allotted area Inspection frequency/scope guided by risk-based approach Changes to the GMP Schedules Both GMP schedules governing factory premises and quality systems are substantially revised. These changes are extensive, and manufacturers should review the full schedule text directly the summary below highlights the areas of change. Schedule M-I Homoeopathic Drugs Premises: Increased emphasis on cleaning and sanitization with additional requirements to avoid back siphonage or backflow in the drainage system. Building usage limits specified: premises shall not be put to any use other than the preparation of homoeopathic drugs, with specific requirements for separate storage and production premises if other premises are required within the same campus. Specific requirements for air filtering in production premises (at least five-micron filters), clearance of production lines between batches, and temperature-humidity requirements are detailed. Water treatment, waste disposal (bio-medical waste disposal under the Bio-Medical Waste (Management and Handling) Rules, 2016), medical check-up and fire safety requirements are detailed. Plant and equipment section revised, including minimum spacing between machinery, personal hygiene and clothing requirements for workers, and segregation of raw material storage by category. Potentisation section, container/closure section, trituration/tableting section, and ophthalmic preparation section specifications are substituted with more detailed facility and equipment requirements, including specific area minimums (for example, 20 square metres for potentisation and ophthalmic sections, 55 square metres for the trituration/tableting section). Quality Control Division requirements are fully substituted, specifying minimum personnel qualifications, equipment lists, and the division's functions regarding raw material and finished product testing, stability studies, and market complaint handling. Raw material handling, packaging materials, and finished goods store requirements are elaborated, along with standard operating procedures, records, and register requirements. Compliance with these Schedule M-I amendments is required by 31 July 2029. Schedule T Ayurveda, Siddha, Sowa-Rigpa, and Unani Drugs General requirements for location, surroundings, and building design are substituted, addressing contamination risk, pest control, drainage, and fire safety. Water supply, waste and effluent disposal, and container-cleaning provisions are elaborated, with specific attention to Schedule E1 ingredient disposal. Storage requirements (stores) are detailed for raw materials, packaging materials, and finished goods, including labelling, colour-coded status labels (yellow/green/red for under test/approved/rejected), and category-based segregation of raw materials (metallic/mineral origin, animal sources, fresh and dry herbs, excipients, volatile oils, plant concentrates, Schedule E1 ingredients, and inflammable substances). Working space, machinery and equipment, and Batch Manufacturing Record (BMR) requirements are substituted with more detailed documentation expectations. Worker health, clothing, sanitation, and medical examination requirements are elaborated. The requirement for the Quality Control Section is replaced with the minimum area (150 sq. ft.), personnel composition (one expert from the respective system of medicine, chemist, botanist/pharmacognosist, and microbiologist where applicable), and equipment list. Requirement for Training and Internal Audit (Self-Inspection) is included. A separate Supplementary Guidance (Paragraph D) is provided for preparation of Rasaushadhi, Rasamarunthukal and Kushtajat herbo-mineral-metallic preparations. This includes manufacture process areas (heating/Bhatti section, grinding/drying section, related stores), temperature monitoring during processes such as Bhasmikaran and Kupi-pakwa rasayana, handling of mercury, lead and arsenic, quality control of products (which includes classical parameters like Varitaratwa, Rekhapurnatwa and others), product recall procedure and personnel medical examination/ rotation for minimizing occupational exposure. Adherence to the above changes to Schedule T is mandatory by 31 July 2029. Why the Changes Were Introduced? While the notification itself does not include an explanatory statement of legislative intent beyond the standard preamble, the substance of the changes reflects several recognisable regulatory objectives: Reducing administrative burden on manufacturers by removing periodic licence renewal, replacing it with perpetual validity. Improving product traceability and standardisation through a uniform, nationally consistent product coding system. Enabling modern labelling technology (QR codes, GTIN, barcodes) to address space constraints on physical labels while preserving access to full ingredient and product information. Strengthening scientific rigour around shelf-life claims by distinguishing accelerated stability data from real-time data and requiring follow-up verification. Shifting inspection resources toward a risk-based model, which is consistent with broader regulatory trends toward proportionate oversight. Raising and clarifying technical personnel and inspector qualification standards, including recognition of microbiology expertise. Modernising and detailing GMP requirements for Homoeopathy and Ayurveda/Siddha/Sowa-Rigpa/Unani manufacturing, including specific, previously less-detailed provisions for herbo-mineral-metallic (Rasaushadhi) formulations given their handling of substances such as mercury, lead, and arsenic. Practical Compliance Checklist for Manufacturers The following checklist reflects the areas manufacturers are likely to need to review, based on the amendments described above. It is a general guide, not an exhaustive substitute for a formal compliance review. Confirm current manufacturing licence status and understand how perpetual validity interacts with any renewal that was pending at the time of commencement. Review existing product codes and prepare for reissuance in the new uniform format within the two-year window. Assess label design and printing processes to accommodate the specific product code requirement and, if desired, QR code/GTIN/barcode integration for ingredient and label information. Review stability study protocols to distinguish which products rely on accelerated versus real-time data, and build in the follow-up real-time study submission timeline. Compare the qualifications of technical staff and quality control staff members against the modified criteria provided under Rules 160B and GMP schedule. In respect of cosmetic products that fall in the Husn-e-Afza /Azhaaghsadhan category, plan to disclose the base material quantity on the label before the expiry of 31 July 2028. Assess the gaps at the facility level with reference to the modified criteria of Schedule M-I or Schedule T for premises layout, water purification, waste management, dedicated manufacturing area, list of equipment, and record-keeping system before 31 July 2029. In case of the manufacture of Rasaushadhi, Rasamarunthukal, and Kushtajat, check the supplementary GMP guidelines on dedicated manufacturing area and safe handling of mercury, lead and arsenic. Modify SOPs, Batch Manufacturing Record and internal audit schedule in accordance with the substituted GMP schedule requirements. Review the internal training program to ensure that staff are aware of the modified guidelines and respective timelines. Conclusion The Drugs (Eleventh Amendment) Rules, 2026, bring together several distinct types of change: administrative simplification (perpetual licence validity), a modernised approach to product identification and labelling (uniform coding, QR/GTIN/barcode display), tightened scientific standards for shelf-life claims, a shift toward risk-based inspection, updated qualification standards for technical and inspection personnel, and a substantial overhaul of the GMP schedules for Homoeopathy and for Ayurveda, Siddha, Sowa-Rigpa, and Unani manufacturing including new, more detailed guidance for herbo-mineral-metallic (Rasaushadhi) formulations. Manufacturers across these AYUSH systems have a phased set of deadlines to work against: one year, two years, and 31 July 2028 and 2029, respectively, for different provisions. Given the operational scope of the GMP schedule changes in particular, an early internal review against the specific rule and schedule text is likely to be more manageable than a compressed effort closer to the 2029 deadline. This summary is based on the text of the Gazette notification dated 24 July 2026, as published by the Ministry of AYUSH. Manufacturers should consult the full text of the notification and, where necessary, seek independent legal or regulatory advice specific to their products and operations.

Subject

Summary: The Ministry of Road Transport and Highways (MoRTH) has proposed changes to the Central Motor Vehicles Rules, 1989. These are the motor vehicle ownership transfer rules that decide how a vehicle moves from one owner to another. The draft notification was issued on 21 July 2026. The proposal touches many people. It affects vehicle owners, authorised dealers, and the way vehicles move between dealers before they reach a new buyer. Under the proposed changes, three forms get special attention: Form 29C, the new Form 29CA, and Form 30. The draft also proposes a limit on how many times a vehicle can move between authorised dealers, and a six-month limit on how long a dealer can hold a vehicle without transferring it. The VAHAN portal is expected to play a bigger role in the proposed digital process. This notification is still a draft. It is not a final rule yet. This article explains, in simple words, what MoRTH has proposed, what each form does, how the transfer process may work, and what vehicle owners and dealers should do while the proposal is still open for comments. Background of the Motor Vehicle Ownership Transfer Framework Existing Legal Framework for Vehicle Ownership Transfer The Motor Vehicles Act, 1988, governs vehicle ownership in India, and the Central Motor Vehicles Rules, 1989. These rules explain how a vehicle's ownership record is created, updated, and transferred. Every registered vehicle has an owner recorded with a registration authority. When a vehicle changes hands, this record must also change. This keeps a clear trail of who owns which vehicle at any given time. Role of Authorised Dealers and VAHAN An authorised dealer is a dealer who holds a valid authorisation certificate, given in Form 29B. Many people do not sell their old vehicle directly to a new buyer. Instead, they hand it over to a dealer, and the dealer finds a buyer. Because the vehicle can sit with a dealer, or move between dealers, before it reaches a final buyer, tracking who has the vehicle at each stage matters. This is where VAHAN comes in. VAHAN is the government's digital vehicle database. It stores registration details and, under the proposed rules, would play a bigger part in recording each step of a transfer. Role of Important Forms Vehicle transfer already uses a few standard forms. Here is what each one does. Form Simple Meaning Main Purpose Form 29 Notice of transfer Records transfer information Form 29B Dealer authorisation Shows dealer's authorisation Form 29C Owner-to-dealer delivery Records delivery to authorised dealer Form 29CA Dealer-to-dealer delivery Records movement between authorised dealers Form 30 Ownership transfer Records transfer to the new owner What has Changed Under the Proposed MoRTH Rules? Ownership Transfer Can Be Processed Through Any Registering Authority in the State Right now, transfer work is often tied to one specific registering authority. Under the proposed changes, an owner or dealer could go to any registering authority in the state where the vehicle is registered, instead of being limited to one office. Valid RC, Insurance and PUC Will Matter The draft rules propose that a vehicle's ownership cannot be transferred if its registration certificate (RC), insurance certificate, or Pollution Under Control (PUC) certificate is not valid. In simple words, the paperwork has to be in order before the transfer can go through. Pending Challans, Taxes and User Fees Can Block Transfer If there are any unpaid traffic challans, any tax demands, or unpaid user charges, then according to the suggested guidelines, the transfer shall not be allowed. This will compel the owner or dealer to pay all the due amounts before transferring a vehicle. New Form 29CA for Dealer-to-Dealer Transfers This is one of the biggest proposed changes. Right now, there is no separate form to record a vehicle moving from one authorised dealer to another. The draft rules propose Form 29CA for exactly this purpose. It would be filed electronically on the portal, and the portal would generate an acknowledgement number automatically once it is submitted. Under the proposal, this form must be filed every time the vehicle moves to a different dealer, or comes back to the original dealer. Limit on Two Transfers Between Authorised Dealers It is suggested that a vehicle cannot be continuously transferred between dealers indefinitely. The draft suggests that the maximum limit of transfers in possession could be two transfers between authorised dealers before the transfer of ownership takes place using Form 30. Six Months’ Limit for Vehicles in Possession of Dealers A time limit is also suggested. The vehicle should not remain in the possession of a dealer beyond six months after the date the owner files Form 29C without transferring ownership using Form 30. Six-Month Limit for Vehicles Held by Dealers The proposal also sets a time limit. A dealer should not hold a vehicle for more than six months from the date the owner filed Form 29C, without transferring ownership through Form 30. VAHAN Will Auto-Fetch Vehicle Details Under the proposed framework, once someone enters a vehicle's registration number on a form, details such as the owner's name and address, the vehicle's make, chassis number, and engine number would be automatically pulled from the VAHAN portal. This should reduce repeated manual entry. Proposed Change What It Means Form 29CA Tracks dealer-to-dealer movement Two-transfer limit Vehicle cannot keep moving between dealers without Form 30 Six-month limit Dealer cannot keep vehicle indefinitely Valid documents RC, insurance and PUC must be valid Pending dues Challans, taxes and user fees can stop transfer VAHAN integration Vehicle details can be auto-fetched What is Form 29CA and Why is it Important? What Is Form 29CA? Form 29CA is a new form proposed under the draft rules. It is meant to record the fact that one authorised dealer has handed over a vehicle to another authorised dealer. When Will Form 29CA Be Used? It would be used every time a vehicle moves from one authorised dealer to another, and also when the vehicle is sent back to the original dealer. Who Will File Form 29CA? The authorised dealer who currently holds the vehicle would file the form when handing it over to another authorised dealer. What Information Will It Record? Form 29CA is proposed to record: Vehicle registration number Dealer details Dealer authorisation details Delivery information Relevant vehicle documents Required declarations Once the form is submitted successfully, the portal is proposed to generate an acknowledgement automatically. Form Used For Form 29C Owner gives vehicle to dealer Form 29CA One authorised dealer gives vehicle to another Form 30 Ownership moves to buyer/new owner How Will the Proposed Vehicle Ownership Transfer Process Work? Step 1: Owner Gives Vehicle to an Authorised Dealer The process begins when the registered owner hands over the vehicle to an authorised dealer and files Form 29C. Step 2: Dealer Checks the Vehicle Before moving forward, the dealer is expected to check the vehicle's records, including its RC, insurance, PUC, pending challans, tax dues, user fees, any legal cases, and any finance, lease, or hypothecation status. Step 3: Vehicle May Move to Another Dealer If the vehicle moves to a second dealer, the current dealer would file Form 29CA to record this handover. Step 4: Dealer-to-Dealer Movement Is Limited The vehicle cannot keep bouncing between dealers forever. The draft proposes a limit of two dealer-to-dealer transfers before an owner change becomes necessary. Step 5: Ownership Transfer Through Form 30 Once a buyer is found, ownership is transferred to that buyer through Form 30. This is what finally changes the registered owner on record. Step 6: Six-Month Deadline If ownership is not transferred through Form 30 within six months of the original Form 29C filing, the proposal says ownership would automatically shift to the dealer who last held the vehicle. What Are the Key Conditions for Transferring a Vehicle to an Authorised Dealer? The draft rules propose that a vehicle cannot be transferred to, or between, authorised dealers if any of the following apply: Invalid registration certificate Invalid insurance Invalid PUC certificate Pending challans Pending tax demand Unpaid user fees An ongoing criminal case A case involving prohibited goods A pending accident case The vehicle is under superdari (police custody) The vehicle is under a hire-purchase, lease, or hypothecation agreement Issue Effect Invalid RC Transfer may be blocked Invalid Insurance Transfer may be blocked Invalid PUC Transfer may be blocked Pending challan Transfer may be blocked Pending tax/user fee Transfer may be blocked Legal/financial restriction Dealer transfer may be blocked What Is the Proposed Six-Month Rule for Authorised Dealers? When Does the Six-Month Period Start? The clock is proposed to start from the date the registered owner files Form 29C, handing the vehicle to the first authorised dealer. What Must Happen Within Six Months? Within this window, ownership should be transferred to a buyer through Form 30. What Happens If Six Months Are Crossed? If the six months pass without a Form 30 transfer, the draft rules propose that ownership would automatically move to the last authorised dealer who held the vehicle. This change would be reflected on the VAHAN portal. What If the Vehicle Has Moved Between Dealers? Here is a short example. Suppose the Owner hands the vehicle to Dealer X, who passes it to Dealer Y, who passes it to Dealer Z. If Form 30 is not completed within six months of the original Form 29C filing, the proposal says ownership would shift to Dealer Z, the last dealer holding the vehicle. Key Point: The six-month period could become an important deadline for authorised dealers and used vehicle businesses to track closely, since missing it changes who legally owns the vehicle. What is the Two-Transfer Limit Between Authorised Dealers? The draft proposes that possession can move between authorised dealers only twice, counting any transfer back to a previous dealer, before an ownership change through Form 30 becomes compulsory. What Role Will the VAHAN Portal Play Under the Proposed Framework? Under the proposed changes, VAHAN is expected to support more of the ownership transfer process digitally. Entering a registration number could auto-fetch details like the owner's name, address, chassis number, and engine number directly into the relevant form. Form 29CA's acknowledgement would be generated electronically. Ownership changes, including the automatic ones after the six-month deadline, are proposed to be reflected directly on the portal. Registered owners are also proposed to get an electronic intimation whenever their vehicle is delivered from one dealer to another. What is the Implementation Timeline and Regulatory Status? 1. Is This a Final Rule? No. This is a draft proposal, not a final rule. 2. What Is the Objection Period? The notification allows a 30-day window for objections and suggestions from the public. 3. When Will It Become Effective? If finalised, the rules would generally take effect after final publication in the Official Gazette. 4. What Should Businesses Do Now? Read the proposal carefully Review existing dealer processes Check vehicle records for pending dues or invalid documents Prepare for digital filing of Form 29CA Track further developments from MoRTH Wait for the final notification before treating the proposal as a binding requirement Why Has MoRTH Proposed These Changes? The proposed provisions appear aimed at better tracking of who physically holds a vehicle at any point, especially when it passes through more than one dealer. They also seem to focus on building clearer digital records through VAHAN, putting more checks on outstanding dues and document validity before a transfer, and limiting how long a vehicle can sit with dealers without a final ownership change. Overall, the draft rules seem to be pushing dealer-to-dealer vehicle movement toward the same kind of digital, traceable record that already exists for owner-to-buyer transfers. Who Will Be Affected and What Is the Impact on Businesses? Stakeholder Possible Impact Vehicle Owners More checks before transfer Authorised Dealers New Form 29CA and deadline tracking Used Vehicle Dealers More control over inventory movement Used Vehicle Buyers Better ownership trail Dealership Networks Need to track dealer-to-dealer movement Finance/Lease Cases Restrictions may affect transfers Impact on Used Vehicle Businesses Businesses that regularly move vehicles between dealer networks may need to plan inventory movement more carefully, since a vehicle cannot keep shifting between dealers without eventually completing an ownership transfer. Impact on Vehicle Owners Owners handing a vehicle to a dealer would want to make sure their documents and dues are clear beforehand, since these can block the process. Impact on Used Vehicle Buyers Buyers stand to benefit from a clearer ownership trail, since dealer-to-dealer movement would be recorded, not left informal. How Can Businesses Achieve Compliance Under the Proposed Rules? Before Taking a Vehicle Check the RC Check the insurance Check the PUC Check for pending challans Check for pending taxes Check for pending user fees Check for legal cases Check for finance, lease, or hypothecation status During Dealer-to-Dealer Movement File Form 29CA Keep the acknowledgement Record dealer details Track the number of transfers Keep vehicle documents updated Before Six Months End Identify the buyer Complete Form 30 Update ownership records Keep proof of transfer What Are the Benefits of the Proposed Framework? Better ownership transparency Better dealer accountability Stronger digital records Better vehicle tracking Clearer dealer-to-dealer movement Better document checks before transfer Better due diligence for used vehicle buyers Greater VAHAN integration Is This a Right Decision or an Additional Compliance Burden? Why It Could Help Benefit What It Means in Practice Better tracking of vehicle possession At every stage, the portal would show which dealer currently holds the vehicle, instead of this being informal knowledge. A clear ownership trail from owner to buyer Every handover, from the original owner through each dealer to the final buyer, would have a matching form and record. Stronger checks on documents before transfer RC, insurance, and PUC validity would be checked before a transfer goes through, reducing the chance of an invalid vehicle changing hands. More accountability for dealers Since Form 29CA names the dealer handing over the vehicle and the one receiving it, responsibility at each step becomes traceable. Fewer disputes over dues Pending challans, tax demands, and user fees would need to be cleared before transfer, reducing the chance of a buyer inheriting unresolved dues. Where It Could Add Work Compliance Task Why It Adds Work Filing Form 29CA for each dealer-to-dealer movement Every single handover between dealers, including a return to the original dealer, would need a separate filing. Keeping more detailed records Dealers would need to retain acknowledgements, dealer details, and declarations for each Form 29CA filed. Monitoring the six-month deadline Dealers would need a reliable way to track the six-month window from the original Form 29C date for every vehicle in their possession. Tracking the two-transfer limit Businesses handling multiple vehicles would need a system to count how many times each vehicle has moved between dealers. Extra document checks before every handover RC, insurance, PUC, challans, tax dues, and legal case status would need to be checked before each transfer, not just the first one. Greater dependence on the portal working smoothly Since acknowledgements, auto-fetched details, and ownership updates are proposed to run through VAHAN, any portal downtime could delay the process. Overall View The proposal may add more paperwork and process tracking for dealers in the short term. At the same time, it could make vehicle ownership records clearer and easier to track for everyone involved, from the original owner to the final buyer. What Business Opportunities Could These Changes Create? If finalised, the proposal could open up practical opportunities such as vehicle ownership transfer assistance, documentation support for dealers, dealer compliance support, regulatory advisory services, record management tools, compliance deadline tracking, used vehicle due diligence checks, and ongoing regulatory monitoring for businesses that deal in high transfer volumes. What Should Vehicle Owners and Authorised Dealers Do Now? For Vehicle Owners Keep RC, insurance, and PUC valid Clear pending dues before handing over a vehicle Keep Form 29C records safe Check the dealer's authorisation before handover Track the transfer status of the vehicle For Authorised Dealers Check Form 29B authorisation status Prepare for the proposed Form 29CA process Record every dealer-to-dealer transfer Track the two-transfer limit Track the six-month deadline Maintain vehicle documents properly These are preparation steps for a draft proposal. They are not instructions from a final law, since the rules have not yet been finalised. How Can Corpseed Help Businesses Navigate the Proposed Vehicle Compliance Framework? 1. Regulatory Compliance Advisory Explaining what the draft rules propose, in plain terms, for owners, dealers, and used vehicle businesses Flagging which parts of daily operations may need changes if the rules are finalised Advising on how to align internal processes with the proposed framework early 2. Documentation Assistance Helping check RC, insurance, and PUC validity before a vehicle changes hands Assisting with preparing and organising documents needed for Form 29C, Form 29CA, and Form 30 Supporting dealers in maintaining Form 29B authorisation records 3. Ownership Transfer Support Guiding owners and dealers through each step of the proposed transfer process Helping identify when Form 30 becomes necessary before the six-month deadline Assisting with resolving pending challans, tax dues, or user fees that could block a transfer 4. Dealer Compliance Support Helping dealers set up a process for filing Form 29CA at every dealer-to-dealer handover Assisting with tracking the two-transfer limit across multiple vehicles Supporting dealer networks in keeping consistent records across locations 5. Monitoring of Regulatory Updates Tracking the draft's progress through the 30-day objection period Alerting businesses to any changes between the draft and the final notification Keeping clients informed once the rules are officially published in the Gazette 6. Compliance Process Guidance Advising on record management systems for Form 29CA filings and acknowledgements Helping set up deadline tracking for the six-month rule Supporting internal checklists so document and dues checks happen before every handover Key Takeaways The proposal to change the motor vehicle ownership transfer rules is still a draft, not a final law. Form 29CA is proposed for recording dealer-to-dealer vehicle movement. Dealer-to-dealer transfers would be limited to two before an ownership change is required. Six months is proposed as the maximum period a dealer can hold a vehicle before ownership transfer. Valid vehicle documents and cleared dues would become important conditions for transfer. VAHAN would support more digital data handling, including auto-fetching vehicle details. Final requirements will depend on the notification that is ultimately published after the objection period ends.