Meta description: Build an ISO 14001 compliance obligations register for India with legal sources, owners, evaluation dates, evidence fields and an audit-ready template.

One missing environmental obligation can become a penalty that grows every day. Under Section 15 of the Environment (Protection) Act, 1986, a contravention for which no separate penalty is provided can attract ₹10,000 to ₹15 lakh, plus ₹10,000 for every day it continues. An ISO 14001 compliance obligations register turns scattered laws, consent conditions and customer commitments into controlled actions before an auditor or regulator finds the gap.

This guide is for Indian manufacturers, EHS managers and SMEs implementing the current ISO 14001:2026 environmental management system standard. It explains what belongs in the register, gives a practical template, and shows how to connect every entry to an owner, evaluation and evidence.

What Is an ISO 14001 Compliance Obligations Register?

An ISO 14001 compliance obligations register is a controlled list of environmental requirements that an organisation must, or has chosen to, meet. It records the source, applicability, required action, owner, evaluation method, compliance status and proof for each obligation.

ISO 14001:2026 is the current edition, published in April 2026. ISO has withdrawn ISO 14001:2015 and says certified organisations should discuss transition arrangements with their certification body. The official ISO 14001:2026 page says the core structure and intent remain familiar while the new edition improves clarity and alignment with climate, biodiversity and resource-efficiency priorities.

Three parts of the standard matter directly:

The standard does not prescribe an Excel sheet called a “legal register.” A database, controlled spreadsheet or software system can work. The test is whether the organisation can demonstrate a complete, current and repeatable process.

A bare list of Acts will fail that test. “Water Act applicable” does not tell a plant manager what to do. A usable entry says which site needs consent, which conditions apply, who checks effluent results, when the consent expires and where the evidence sits.

Separate Obligations, Environmental Aspects and Controls

These records should connect, but they are not interchangeable.

Record | Question it answers | Example

Environmental aspect register | How can our activities interact with the environment? | Boiler stack emissions

Compliance obligations register | Which legal or chosen requirement applies? | Air consent condition limiting particulate emissions

Operational control | How will we meet the requirement? | Maintain the air-pollution-control device and test the stack

Compliance evaluation record | Did we meet it, and what proves that? | Laboratory report within the consent limit

One aspect can have several obligations. Hazardous-waste generation may connect to authorisation, storage, labelling, manifest, disposal and annual-return requirements. Give each duty a stable ID, then link it to aspects, controls, tasks and evidence.

Copy This ISO 14001 Compliance Obligations Register Template

Use one row for each duty, prohibition, permit condition or voluntary promise.

Field | What to record

Obligation ID | Permanent code, such as ENV-WATER-001

Legal entity and site | The company, factory, warehouse or project covered

Environmental aspect | Air, effluent, water use, waste, chemicals, noise, land or biodiversity

Jurisdiction | Central, state, local, permit-specific, contractual or voluntary

Regulator or interested party | SPCB/PCC, CPCB, MoEFCC, customer, lender or certification body

Source | Full Act, rule, section, notification, consent clause, contract term and official link

Applicability trigger | Activity, discharge, waste type, product, location, capacity or commitment

Plain-language obligation | The exact action, limit, prohibition or filing requirement

Frequency or deadline | Continuous, event-based, monthly, annual, renewal date or consent-specific

Owner and reviewer | Named responsible role and independent checker

Required evidence | Consent, return, manifest, report, invoice, log, photograph or acknowledgement

Evaluation method | Document review, inspection, sampling, interview or portal verification

Evaluation frequency | Monthly, quarterly, annual or risk-based interval

Status | Compliant, non-compliant, partially compliant, not due or under review

Corrective action | Action, owner, due date and closure evidence

Effective date and version | When the requirement began and which text was assessed

Change trigger | Process, capacity, site, law, permit, customer or standard change

Last verified | Date, reviewer and primary source checked

Avoid “as per applicable law” in the source field. Record the full title and exact provision. Assign an owner with authority, such as Plant EHS Head or Waste Coordinator.

For a reusable general structure beyond environmental management, see the compliance obligation register template for Indian businesses. Keep this ISO 14001 register limited to the environmental management system scope and its environmental aspects.

Which Indian Environmental Obligations Should You Map First?

There is no universal environmental checklist for every Indian business. Applicability changes by process, discharge, fuel, waste, location, production capacity, consent category and state. Start with the following source groups, then verify exemptions and state requirements for each site.

Consent under the Water Act

Section 25(1) of the Water (Prevention and Control of Pollution) Act, 1974 generally requires previous State Pollution Control Board consent before establishing an industry, operation, process, treatment system or extension likely to discharge sewage or trade effluent, or before bringing a new outlet or discharge into use. The current India Code text of Section 25 also allows centrally notified exemptions for categories of industrial plants.

Record separate entries for initial consent, renewal, measurable consent conditions, reporting and prior approval before a process, capacity, outlet or pollution-load change. Take validity and renewal procedure from the order and current rules.

Consent under the Air Act

Section 21(1) of the Air (Prevention and Control of Pollution) Act, 1981 requires previous State Board consent to establish or operate an industrial plant in an air-pollution-control area, subject to notified exemptions. The official Section 21 text makes the jurisdiction and exemption check essential.

Map each consent condition separately: approved fuel, stack parameters, control equipment, monitoring frequency, emission limit and reporting. A valid consent does not prove continuing compliance.

Annual environmental statement in Form V

Rule 14 of the Environment (Protection) Rules, 1986 requires a covered industry, operation or process to submit the environmental statement for the financial year ending 31 March in Form V to the concerned State Pollution Control Board by 30 September each year. Coverage is tied to consent under Section 25 of the Water Act, Section 21 of the Air Act, or the specified hazardous-waste authorisation basis.

Create calendar and evidence fields for data collection, review, submission and acknowledgement.

Hazardous-waste authorisation, records and return

If the site generates or handles waste covered by the Hazardous and Other Wastes (Management and Transboundary Movement) Rules, 2016, map authorisation, storage, packaging, labelling, manifest, transporter, disposal and recordkeeping separately. Rule 20 requires covered occupiers and facility operators to submit the annual return in Form 4 to the SPCB/PCC by 30 June for the preceding financial year. The Ministry’s published governance review confirms the Rule 20 reporting cycle.

Directions, clearances and voluntary commitments

Add site-specific environmental-clearance conditions, consent directions, groundwater NOCs, local permissions and National Green Tribunal or court orders that bind the operation. These are often more operationally specific than the parent Act.

Then add requirements the organisation chose or agreed to meet: customer codes, lender covenants, industry commitments, community agreements and environmental-policy promises. ISO 14001 treats such commitments as compliance obligations once they fall within its definition; label them “voluntary” or “contractual” so nobody mistakes them for legislation.

Build the Register in Seven Controlled Steps

1. Freeze the environmental management system scope

List the entities, sites, activities, products and services inside the EMS, including controlled contractor and outsourced activities. A register cannot be complete if the boundary is vague.

2. Create a site fact sheet

Capture process flow, capacity, fuels, water sources, discharge points, emissions, chemicals, waste, licences and customer commitments. Review it before any operational change.

3. Research from primary sources

Work from India Code, the Gazette, MoEFCC, CPCB, the relevant SPCB/PCC and the actual permit. Save the official link, effective date and version reviewed.

4. Translate each source into a testable duty

Write one action or prohibition per row. “Comply with hazardous-waste rules” is not testable. “File the Form 4 annual return with the SPCB by 30 June and retain the acknowledgement” is.

5. Confirm applicability with evidence

Record why the entry applies. If relying on an exemption, save the notification and supporting facts. “Not applicable” without reasoning is an audit invitation.

6. Assign control, owner and proof

Link each obligation to a control and named owner. Define proof before the due date; a checkbox saying “done” is not enough.

7. Approve and baseline the register

Have competent personnel review high-consequence entries. Mark uncertainty openly, set a resolution date and preserve the approved baseline.

How Do You Evaluate Compliance Under ISO 14001:2026?

A register identifies duties; evaluation determines whether you met them. Clause 9.1.2 does not impose one universal evaluation frequency. Set intervals based on consequence, change rate, past failures, regulator interest and control reliability, while ensuring the programme covers all obligations over a defined period.

Use a simple cycle:

  1. Select the obligations due for evaluation.
  2. Review the exact legal or chosen requirement and current version.
  3. Inspect records, operations, monitoring data and permit conditions.
  4. Record a clear status and the evidence examined.
  5. Open corrective action for any failure or uncertainty.
  6. Verify closure and update management on material exposure.

Do not treat an internal audit as the only compliance evaluation. An ISO audit tests the management system; compliance evaluation tests fulfilment of each obligation.

Evaluate continuous limits through monitoring and annual filings through the submitted form and acknowledgement. Document why each frequency is suitable.

Keep the Register Current When Laws or Operations Change

The register needs two change feeds. External changes include Acts, rules, notifications, regulator directions, consent changes, judgments and customer requirements. Internal triggers include a new fuel, chemical, waste stream, borewell, line, location, capacity or contractor. An operational change can make an old law newly applicable.

Use version control. Close the previous row with an end date, create the new version and update future tasks. Preserve prior evaluation evidence against the rule that applied at that time.

At management review, report at least:

Excel or Software: What Should an Indian SME Use?

A controlled spreadsheet can suit one stable site with a small register. Restrict editing, use permanent IDs and preserve version history.

Move to software when you operate across states or sites, depend on many regulators, have several owners, or cannot reliably connect legal changes to affected obligations. The buying test is not dashboard colour. Ask whether the system can show the official source, applicability reason, effective date, owner, evidence, change history and overdue evaluation for every row.

Compliance Radar helps Indian businesses describe their operations once, identify applicable requirements across jurisdictions, build a compliance timeline and receive regulatory-change alerts. It does not replace a certification body or site-specific professional judgment; it reduces the discovery and monitoring gaps that make registers stale.

Check your compliance posture free at complianceradar.in and use the results to validate the legal side of your ISO 14001 register.

Frequently Asked Questions

Is an ISO 14001 compliance obligations register mandatory?

ISO 14001:2026 requires documented information about compliance obligations and evidence of evaluation, but it does not prescribe a document with this exact name or format. A controlled register is the clearest practical method for most organisations.

Is ISO 14001 certification legally mandatory in India?

Generally, no. ISO 14001 is a voluntary management-system standard unless a contract, tender, permit condition or other binding commitment makes certification or conformance necessary. Environmental laws and permit conditions remain mandatory independently of ISO certification.

What changed from ISO 14001:2015 to ISO 14001:2026?

The 2026 edition replaced the withdrawn 2015 edition. ISO says the core structure and intent remain, with clearer guidance, harmonised terminology and stronger alignment with environmental priorities. Organisations holding 2015 certificates should obtain their transition timetable from their certification body.

How often should the register be reviewed?

Review it whenever a relevant law, permit, contract, process, site or environmental aspect changes. Also conduct a full-scope periodic review, normally at least annually, while checking high-risk and fast-changing obligations more frequently.

Can one register cover several factories?

Yes, if every entry identifies the applicable legal entity, site, jurisdiction and local permit condition. Do not assume a conclusion for one SPCB, consent order or process automatically applies to another location.

Who should own the compliance obligations register?

One EMS coordinator should control the structure and versions, while operational owners remain accountable for individual duties. High-consequence legal interpretations should be reviewed by competent environmental or legal professionals.

What evidence should be linked to an obligation?

Use evidence that proves the requirement was met: permit, portal acknowledgement, return, laboratory report, calibration record, manifest, authorised recycler certificate, inspection log or corrective-action closure. The evidence must identify the right site, period and obligation.

Turn the ISO 14001 Compliance Obligations Register Into Action

An ISO 14001 compliance obligations register is not a legal scrapbook. It is a working control that connects each current requirement to the site fact that triggers it, a named owner, an evaluation date and evidence.

Start with your EMS scope and site facts. Map primary legal sources and consent conditions. Separate obligations into testable rows, evaluate them on a justified schedule, and version every change. That is what makes the register useful between audits, when the real regulatory risk exists.

Check your compliance posture free at complianceradar.in. Describe your business once to see applicable compliances, timelines, government schemes and regulatory-change alerts, then use that intelligence to strengthen your ISO 14001 system.

This article provides general information, not legal or certification advice. Verify current laws, notifications, consent conditions and ISO 14001:2026 requirements for your organisation before acting.