EC Compliance Scrutiny: Common Deficiencies That Get Reports Returned for Rectification or Gets Issued Deficiency Letters

Introduction

Every six months, project proponents across India file post-environmental clearance (EC) compliance reports with the authority that granted their clearance — the MoEF&CC, a State Environment Impact Assessment Authority (SEIAA), or the relevant State Pollution Control Board. Most proponents treat the half-yearly report as a formality. The reviewing officer does not.

A report that reads as a confident summary of progress to the person who wrote it often reads, to a senior reviewing officer, as a catalogue of evasions, contradictions, and quiet deferrals. When that happens, the report comes back — returned for rectification, accompanied by a direction to resubmit, and sometimes a show-cause notice. The project loses months, and the proponent loses credibility with the authority that will assess every future submission.

This article walks through the deficiencies that most reliably get EC compliance reports returned, written from the perspective of the officer doing the scrutiny rather than the consultant preparing the file. If you understand what the reviewer is trained to look for, you can find these problems yourself before they cost you a cycle.

How a reviewing officer actually reads a compliance report

A reviewer does not read the report front to back as a narrative. They read it as a cross-examination. Each EC condition is a question already on the record, and the compliance report is the proponent's answer under scrutiny. The officer's job is to test whether the answer is responsive, truthful, evidenced, and complete.

That framing matters because it explains why polished, well-formatted reports still get returned. Presentation is not the test. The test is whether each condition has been met, whether the evidence supports the claim, and whether anything has been left out, glossed over, or pushed to a later date without acknowledgement. A report can be immaculately typeset and still fail every one of those tests.

The deficiencies below are the ones that surface most often when a report is read this way.

1. Condition-by-condition mismatch

The single most common structural failure is a report that does not map cleanly onto the EC conditions it is meant to address. The clearance letter lists specific conditions — often numbered, sometimes split into general and specific schedules. The compliance report should answer each one, in order, with the condition reproduced and the compliance status stated directly beneath it.

What reviewers frequently receive instead is a thematic narrative that discusses the project's environmental performance in general terms without tying statements back to numbered conditions. When a reviewer cannot find the answer to Condition 7(iii) without hunting through three pages of prose, the report is already in trouble. The safest structure reproduces each condition verbatim and answers it immediately, leaving no condition unaddressed and no answer floating free of its question.

2. Vague compliance language that evades the actual obligation

Reviewers are alert to language that signals compliance without demonstrating it. Phrases such as "being complied with," "will be ensured," "necessary steps have been taken," and "the same is under process" are evasion markers. They describe intention or effort, not the achieved state the condition requires.

A condition that requires a sewage treatment plant to be operational is not satisfied by a statement that the STP is "being made operational." Either it is running, with monitoring data to prove it, or it is not — and if it is not, the report needs to say so plainly and explain the timeline for rectification. Soft language invites the reviewer to assume the obligation has not been met, because a proponent who had met it would simply say so and attach the proof.

3. Deferred obligations presented as ongoing compliance

Closely related is the obligation that has quietly been pushed into the future while being reported as if it were already in hand. Conditions tied to a project phase — for example, a commitment to install a particular system before occupancy, or to complete plantation within a defined period — are sometimes reported every cycle as "in progress" with no movement between reports.

A reviewer who compares the current report against earlier submissions will notice that the same obligation has been "in progress" for three consecutive cycles. That pattern converts a single soft answer into evidence of sustained non-compliance, and it is one of the fastest routes to a show-cause direction. Reviewers do compare cycles; the assumption that each report is read in isolation is wrong and dangerous.

4. Contradictions within the same report

Long compliance reports assembled from multiple inputs frequently contradict themselves. The water-management section reports one figure for fresh water drawn; the annexed monitoring data reports another. The narrative claims a green belt has been developed over a stated area; the photographs and the layout plan show otherwise. The report states zero-discharge status while also describing discharge to a drain.

Internal contradiction is corrosive because it does more than fail one condition — it undermines the reliability of the entire document. Once a reviewer catches one figure that does not reconcile, they read everything else more skeptically and look harder for the next inconsistency. A pre-submission reconciliation, checking that every number and claim agrees with every annexure, prevents this category entirely.

5. Evidentiary gaps and unsupported assertions

A compliance claim without evidence is, to a reviewer, an unproven assertion. Conditions that require monitoring, measurement, or third-party validation must be backed by the corresponding records: ambient air and water monitoring reports from a recognised laboratory, consent-to-operate documents, waste authorisation, plantation records, and dated photographs where relevant.

The common failures are an assertion with no annexure, an annexure that is out of date, monitoring data from a lab that is not appropriately accredited, or data that does not actually cover the reporting period claimed. A reviewer who finds monitoring data from the previous year stapled to a current report treats the underlying claim as unsubstantiated. Evidence must be current, relevant, properly sourced, and clearly cross-referenced to the condition it supports.

6. Stale statutory citations

Environmental regulation in India moves quickly. Rules are amended, thresholds revised, and standards superseded. A compliance report that cites a superseded version of a rule, an outdated standard, or a notification that has since been replaced signals to the reviewer that the proponent is operating from an old template and may not be aware of current obligations at all.

This is more than a cosmetic error. If the report demonstrates compliance against a standard that no longer applies, the proponent has effectively shown compliance with the wrong target. Keeping statutory references current — and confirming the applicable version before each submission — is a basic but frequently neglected discipline.

7. Selective reporting and conspicuous silence

Reviewers notice what is missing as much as what is present. A report that addresses every favourable condition in detail while passing over a difficult one in a single line, or omitting it entirely, draws attention precisely because of the imbalance. Silence on a known issue — a pending consent, an unresolved complaint, a monitoring exceedance — reads as concealment rather than oversight.

The counterintuitive truth is that disclosing a shortfall openly, with a credible rectification plan and timeline, is far more defensible than burying it. Reviewers respond better to candour backed by a corrective plan than to a clean-looking report that they suspect is hiding something. An omission discovered by the reviewer is an enforcement trigger; a shortfall disclosed by the proponent is a managed risk.

A pre-submission checklist

Before any half-yearly EC compliance report leaves your desk, test it against the questions a reviewer will ask:

• Does every numbered EC condition have a direct, clearly labelled answer?
• Is each compliance claim stated as an achieved state rather than an intention?
• Has any obligation been "in progress" across multiple cycles without movement?
• Do all figures and claims reconcile across the narrative and every annexure?
• Is every claim that requires evidence supported by current, relevant, properly sourced records?
• Are all statutory references the versions currently in force?
• Has every difficult or unfavourable condition been addressed openly, with a rectification plan where needed?

A report that survives those seven questions is one a reviewing officer will find hard to return.

The value of an adversarial review before you file

The most useful thing a proponent can do is have the report read, before submission, by someone whose explicit brief is to find its weaknesses — to read it the way a Joint Director or Member Secretary would, looking for evasions and gaps rather than confirming that the work was done. That adversarial scrutiny is uncomfortable by design, and it is exactly what spares a project the far more costly version that arrives from the regulator months later.

At Testa & Tegmen, EC compliance scrutiny is built around precisely this perspective. We review half-yearly and post-EC compliance reports against the granted conditions the way a senior reviewing officer would, surfacing the contradictions, deferred obligations, stale citations, and evidentiary gaps before the report reaches the authority — so that what you file is defensible the first time.