Skip to content
RegulensR
Compliance operations

Why most organisations cannot produce a complete licence register

Your binding obligations are as much in your consent order and factory licence as in any statute. Most organisations cannot produce a complete list of the licences they hold, let alone the conditions inside them.

Kavita IyerDirector of Solution Architecture3 min read0 views

Here is an exercise that takes an afternoon and reliably produces an uncomfortable result.

Ask each of your sites for a list of every licence, consent, registration, authorisation and NOC it holds, with the issuing authority, the number, the validity period and the person named on it.

In our implementations, the first pass is never complete, and it almost always surfaces at least one licence that has expired.

Why the register does not exist

Licences are obtained at the point of setting something up. A project team commissions a plant, obtains the twenty-odd approvals required, hands over to operations and disperses. The licences go into a file.

Operations inherits a running plant and a folder. Nobody hands over a register, because nobody built one — the project team was tracking approvals as tasks to be completed, not as obligations to be maintained.

Then time passes. The project team has gone. The plant manager has changed twice. The person named as occupier has been promoted to a different site. And the licence renewal that requires an application ninety days before expiry sits in a folder nobody opens.

Conditions are the larger issue

The licence itself is only half of it.

A consent to operate from a State Pollution Control Board carries site-specific conditions — often twenty to sixty of them. Effluent parameters, monitoring frequency, record-keeping, reporting obligations, restrictions on operating hours, requirements to install specific equipment by specific dates.

Those conditions are legally binding obligations. They are specific to your site, they differ from the conditions at your other site making the identical product, and they typically exist only inside a scanned PDF.

Two plants running the same process under the same rules can hold consents with materially different conditions, because different officers issued them at different times. Anyone who assumes the conditions are standard has not read two of them side by side.

Renewal is not a date problem

The obvious control is a calendar of expiry dates. It is insufficient, for a reason that only becomes apparent when you miss one.

Several licences accept renewal applications only within a defined window before expiry — sixty or ninety days is common. The authority's own processing time frequently exceeds that window. Applying on the first permissible day can still leave you operating past expiry with a pending application.

Whether that is acceptable varies. Some authorities issue a continuation acknowledgement; some do not. Some inspectors accept a pending application; some issue a notice.

The control that works tracks two dates: the expiry, and the date by which the application must be submitted given observed processing time at that specific authority. The second date drives the alert, and it is often earlier than the window opens — meaning preparation must start before you are permitted to apply.

Building the register properly

Start with a physical audit, not a system query. Ask each site to photograph every licence displayed and every certificate in the file. You will get things the corporate list does not have.

Capture the named individual. Every licence naming a person is a personal liability attaching to that person. Where the named person has left, that is an urgent correction, not a housekeeping item.

Extract the conditions. This is the work. Each consent, clearance and licence read, its conditions listed, each condition made an obligation with an owner and an evidence expectation. For a site with twenty licences this is a few days of careful reading, and it is the single highest-value output of an EHS compliance programme.

Calibrate lead times per authority. Observed processing time, per authority, per licence type. It differs, and your own history is the best available data.

Make expiry visible where the work is. The site should see its own renewal position. Corporate should see every site's.

What it is worth

The organisations that do this find three things in the first pass, consistently: a licence that has expired, a licence naming someone who has left, and a set of conditions nobody had read since issue.

None of those are exotic failures. They are the ordinary consequence of treating licences as documents rather than as obligations, which is how almost everyone treats them until something goes wrong.

LicensingEHSOperating model

Written by Kavita Iyer, Director of Solution Architecture

Part of the team that builds and maintains the Regulens obligation library and platform. If you disagree with something here, we would genuinely like to hear it — get in touch.

Everything here is how the product actually works

If the methodology in these articles matches how you think the problem should be solved, a demonstration will be a short conversation.