HSPCB vs DPCC Compliance: What Changes When Your Site Crosses the Delhi–Haryana Border

Builders working across the National Capital Region often assume that dust-control compliance is one single rulebook. On the ground it is not. A plot in Dwarka answers to the Delhi Pollution Control Committee, and a plot twelve kilometres away on Dwarka Expressway answers to the Haryana State Pollution Control Board. The equipment on the boundary looks identical, the officers ask similar questions, but the portals, the paperwork and the review rhythm are different enough that a file prepared for one regulator will stall with the other.

One CAQM framework, two enforcing boards

Both regulators enforce the Commission for Air Quality Management's directions for the NCR, including the requirement for continuous ambient monitoring at construction and demolition sites above 500 sqm and the CAQM direction of 11.06.2021 that underpins Haryana's dust-portal enforcement. That shared origin is why the physical checklist barely changes: anti-smog gun sized to plot area, CPCB-listed PM2.5 and PM10 sensor, PTZ cameras with a working live feed, green-net barricading, wheel-wash arrangements and covered material storage.

What changes is the administrative layer. DPCC site registration runs through Delhi's own Dust Portal 2.0 with GIS mapping and AI-assisted review of camera feeds. HSPCB registration for Gurugram, Faridabad, Sonipat, Panipat, Karnal and Rohtak sites runs on the Haryana dust portal, where the emphasis falls on the self-assessment format and the frequency with which you refresh photographic evidence.

Where the two diverge in practice

• Portal and login: separate accounts, separate document formats, no transfer of history between boards.
• Registration inputs: Delhi files lean heavily on the sanctioned plan and dust-mitigation plan; Haryana files put more weight on the self-assessment declaration and site photographs.
• Audit reporting: monthly dust-control audit reports for DPCC, versus periodic self-assessment updates plus inspection-triggered submissions for HSPCB.
• Camera expectations: DPCC PTZ camera integration is validated by a live preview test with the zonal officer; HSPCB reviewers usually want a working RTSP link plus DVR/NVR backup available on site.
• Industrial overlay: Haryana Red-category units are routinely asked about CSIR-NPL certified OCEMS as a Consent to Operate condition, which pulls stack emission monitoring into the same conversation as dust control.

Practical advice if you build in both states

Keep two evidence folders from day one rather than trying to reformat one for the other board later. Photograph the same equipment for both, but caption and date it in the format each portal accepts. Where a group has sites on both sides of the border, standardise the hardware — the same sensor model and the same camera series — so that a spare part or a firmware fix travels between sites without a fresh approval conversation.

If a notice arrives, respond in the language of the issuing board. A DPCC show cause notice reply is expected to address the specific clause cited with geotagged photographic evidence; an HSPCB closure or show-cause notice reply generally expects the self-assessment record, camera feed availability and monitoring logs attached alongside.