What the conditions actually are
An EC letter carries two kinds of condition. The specific conditions are written for that project: the treatment capacity to be installed, the green belt to be developed, the monitoring to be carried out, the commitments made during appraisal and at the public hearing where one was held. The general conditions are the standing requirements the Ministry or the State authority attaches to clearances of that class.
Both are enforceable. The distinction that matters operationally is that the specific conditions are the ones nobody else can tell you — they encode what your project said about itself during appraisal, and they are frequently the conditions a new project manager, arriving two years later, has never read.
The first task in any post-clearance engagement is therefore clerical and unglamorous: extract every condition from the letter into a register, with an owner and an evidence requirement against each. A condition without an owner is a condition nobody is generating evidence for.
Specific conditions
Written for this project, out of this appraisal. Capacities, green belt, monitoring, and the commitments given during appraisal and at the public hearing. Nobody outside the file knows them.
General conditions
The standing requirements attached to clearances of this class — reporting, display, compliance with other applicable law. Common across projects, and still enforceable against yours.
Both are enforceable. Only one of them is specific to what your project promised.
The reporting cycle is fixed, and it is the record
Compliance with EC conditions is reported half-yearly, and the cycle is a calendar obligation rather than a response to a request. The report states, condition by condition, what has been done, with the evidence that supports it.
Two failure modes recur. The first is the report that paraphrases the condition back as a status — "green belt: in progress" — which tells the regulator nothing and builds no record. The second is the report that is accurate but undocumented, where the monitoring was done and the data exists somewhere in an operations folder that nobody has connected to the condition it answers.
The half-yearly reports accumulate into the project's compliance history, and that history is what is read when the clearance is later amended, extended or transferred, and when the site is inspected. A thin history is not a neutral absence. It is the record.
The rule
Report against the condition, with the evidence, condition by condition.
A status line is not compliance reporting. The question the regulator is answering from your report is whether the promise made at appraisal has been kept, and that question needs the evidence attached to the promise.
- The condition is metState what was done and cite the evidence — the monitoring record, the completion certificate, the photograph with its date.
- The condition is not yet metSay so, with the reason and the date by which it will be. A disclosed slippage is a manageable finding; an undisclosed one is a credibility problem.
- The condition has become inapplicableExplain why, and seek amendment if the change is material rather than describing it only in the report.
Where the history is read back
Post-clearance compliance feels abstract until the project needs something. Three moments bring the file back out.
An amendment, when the project changes — capacity, layout, product mix, or the configuration on which the clearance rested. A validity extension, when the project has not been commissioned within the period the clearance runs for. And a transfer, when the project changes hands, where the transferee inherits the conditions along with the clearance and is entitled to know, in diligence, what state they are in.
In each case the authority is looking at the same thing: whether this project has kept its promises so far. That is also exactly what a lender's environmental and social due diligence looks at, which is why compliance history has a commercial value that is invisible until the week it is asked for.
Half-yearly
Compliance report against every condition, with evidence
Project proponent
On inspection
The site is examined against the conditions and the reported position
Regulator / monitoring authority
On amendment
The change is assessed against the clearance the project already holds
Appraisal committee
On extension
Validity is considered against progress and compliance to date
Regulatory authority
On transfer or financing
Conditions and their compliance status pass to the transferee, and are tested in diligence
Transferee / lender
The compliance record is written continuously and read at intervals. These are the intervals.
What good looks like
A project with its post-clearance obligations under control has four things. A condition register derived from the letter itself, not from memory. A named owner for each condition. Evidence generated on the cycle the condition implies rather than on the cycle the report demands. And a calendar that includes the reporting dates alongside the consent renewals, the NOC renewals and the statutory returns, because in practice these obligations share a team and compete for the same fortnight.
None of that is sophisticated. It is the difference between a compliance position that can be demonstrated on the day it is questioned and one that has to be reconstructed — and reconstruction, in our experience, is where the cost sits.
What to do with this
- 01Extract every condition from the EC letter into a register with an owner and an evidence requirement.
- 02Report half-yearly, condition by condition, with evidence — not status lines.
- 03Disclose slippage with a date. An undisclosed gap becomes a credibility finding.
- 04Treat material project changes as amendments, not as explanations in the next report.
- 05Keep EC reporting dates on the same calendar as consent and NOC renewals — one team carries all of them.
- 06Expect the compliance history to be read at amendment, extension, transfer and financing.