What this is
What is a permit condition compliance log?
What is a permit condition compliance log?
A record that tracks compliance against each individual numbered condition of an environmental permit, rather than the permit as a single pass or fail. Each condition carries its own type, frequency, evidence requirement and status, so the log shows which obligations are met and which are not.
How is this different from the permit register?
The permit register lists which permits, licences and consents are held, their conditions and expiry dates. This log is the ongoing evidence trail against one permit's conditions as they come due; the register changes rarely, the log constantly.
What counts as evidence of compliance with a condition?
Whatever the condition requires: a monitoring result, certificate, calculation, supplier declaration, or third-party verification. A status of compliant with no evidence recorded is not distinguishable, on inspection, from a status that was never true.
Scope
When is a permit condition compliance log required?
This log is the ongoing evidence trail for one permit already on the register, not where the permit itself is recorded, and not a general legal compliance sweep across every obligation the site holds.
Use this template when
- A permit has been issued or varied and its conditions need to be tracked from that point on
- A condition's own frequency has come due, continuous, daily, weekly, monthly, quarterly or annually
- A permit renewal or regulator audit is approaching and the condition-by-condition position needs to be current
- A monitoring result, inspection or incident suggests a condition may not be met
- The linked permit register needs this log to make the permit's compliance position visible, not just its existence
Do not use it for
- Environmental Permit Register, which lists every permit, licence and consent held, with conditions and expiry dates, not ongoing compliance
- Compliance Evaluation Record, which evaluates compliance across all legal and other requirements generally, not one permit's numbered conditions
- Emissions Permit Compliance Review, a periodic review focused on emissions permits rather than a continuous condition-by-condition log
- Legal and Other Requirements Register, the broader register of applicable law the organisation holds itself to
- Environmental Performance Report, which aggregates performance indicators for reporting rather than tracking individual conditions
Compliance mapping
Which ISO 14001 cl.9.1.2 requirements does this satisfy?
ISO 14001 clause 9.1.2 requires compliance obligations to be evaluated at a determined frequency with results kept as documented information. A permit's numbered conditions are the sharpest form that takes, each one specific and individually enforceable rather than a general duty.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 14001 cl.9.1.2 | Evaluate compliance with compliance obligations and know the status | Conditions |
| ISO 14001 cl.9.1.2 | Determine the frequency at which compliance is evaluated | Conditions |
| ISO 14001 cl.9.1.2 | Retain documented information as evidence of the evaluation results | Conditions |
| ISO 14001 cl.6.1.3 | Determine and have access to the compliance obligations that apply | Header |
| ISO 14001 cl.10.2 | React to nonconformity and take action to control and correct it | Conditions |
| ISO 14001 cl.9.1.1 | Monitor and evaluate performance against time-bound obligations | Improvement conditions |
| ISO 14001 cl.9.3 | Compliance status is input to management review | Summary |
What it does not cover
- Environmental Permit Register, the record of which permits are held and their conditions and expiry, not ongoing compliance against them.
- Compliance Evaluation Record, which evaluates the full set of legal and other requirements, not one permit's conditions.
- Emissions Permit Compliance Review, a periodic emissions-focused review rather than a continuous per-condition log.
- Legal and Other Requirements Register, the organisation's broader list of applicable legal requirements.
- Environmental Performance Report, which reports aggregate performance indicators rather than individual condition status.
Global
Permit Condition Compliance Log requirements by country
The duty to comply with a permit's conditions is set by the permit itself, so the log's legal weight comes from whatever instrument granted the permit, not from ISO 14001, which governs how the evaluation is managed.
Clean Air Act Title V permits; Clean Water Act NPDES permits
Both attach numbered conditions, monitoring and reporting duties directly to the permit, with self-monitoring reports on a fixed schedule.
A missed Title V or NPDES condition is typically found through the facility's own required reporting before an inspector arrives, making frequency tracking a direct control.
Environmental Permitting (England and Wales) Regulations 2016 and equivalents
Permits carry numbered conditions covering emission limits, monitoring, record keeping and improvement programmes, each enforceable on its own.
Compliance assessment is explicitly condition-based, so a log organised any other way does not answer the question actually asked.
ISO 14001:2015 cl.9.1.2
Requirement to evaluate compliance obligations at a set frequency and retain the evidence.
Certification audits check whether the frequency was set per obligation and followed, not whether one annual sweep touched everything.
How to complete it
How to complete a permit condition compliance log, step by step
The log will accept a single quarterly pass through every condition and look complete. What decides whether it holds up is whether each condition was checked on its own terms and any miss surfaced rather than absorbed into a percentage.
A continuous emissions limit and an annual report sit in the same permit, but checking them on one schedule over-checks one and under-checks the other. Set the frequency from the condition itself.
A compliant status with Evidence Available marked partly or no is a claim the log cannot back up. The evidence type should match what the condition demands, and the record should not close until it exists.
Most regulators treat a self-reported non-compliance more favourably than one discovered on inspection, and the log is where that choice gets made or missed by default.
An improvement condition with a stated date is either met by that date or overdue; there is no partial credit. Overdue improvement conditions need the same visibility as a non-compliant steady-state one, because a permit can fail on either.
What auditors find
Most common permit condition compliance log findings
The log usually exists and is updated. The findings concern whether the update matched each condition's own demands, and whether a gap was surfaced or quietly absorbed.
| Finding | Clause | What fixes it |
|---|---|---|
| Condition marked compliant with Evidence Available recorded as partly or no. | ISO 14001 cl.9.1.2 | Do not close a condition as compliant until the evidence it requires is actually held and referenced. |
| Continuous or daily conditions reviewed on the same schedule as monthly or annual ones. | ISO 14001 cl.9.1.2 | Set the review frequency from the condition itself and log each against its own cadence. |
| Non-compliance identified but not self-reported to the regulator. | ISO 14001 cl.10.2 | Make the self-reporting decision explicit for every non-compliant entry, with a reason where not reported. |
| Improvement condition past its deadline with no corrective action record raised. | ISO 14001 cl.9.1.1 | Raise a CAPA the moment an improvement condition becomes overdue, not at the next summary review. |
| Log entries not linked back to the permit reference on the permit register. | ISO 14001 cl.6.1.3 | Populate the permit reference on every entry so register and log stay reconcilable. |
| Compliance percentage trending down over successive periods with Action Required left at no. | ISO 14001 cl.10.2 | Treat a worsening trend as its own trigger for action, independent of any single condition. |
Case in point
Case in point: the compliant permit with one condition nobody had actually checked
A processing site held a permit with an annual reporting condition and a continuous stack emissions limit. The log was updated every quarter and the whole permit marked compliant each time, with the annual report as the only evidence attached, because it was the only document anyone had recently produced. The continuous limit had no monitoring evidence for over a year, not because it was breached, but because nobody had asked at the frequency the condition required.
A routine inspection requested the continuous monitoring records specifically and found six weeks with no data, due to an uncalibrated analyser never flagged because nothing in the log's rhythm would have caught it. The permit had been broadly compliant throughout, but the site could not show it, and an unevidenced condition is treated the same as a failed one. The fix was giving the continuous condition its own line and frequency, so a data gap would surface before an inspector had to ask.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- ENV-040
- Archetype
- Log
- Record ID
- PCC2-2026-000
- Scoring
- Compliance percent
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 14001 cl.9.1.2
- Links
- Links Permit Register
- Tags
- Environment, Compliance
- Sections
- 4
- Fields
- 43
- Follow up fields
- 5
- Repeating sections
- 1
- Links out
- 3
Header
10 fieldsLog ID*
Auto sequence. Format PCL-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Permit Reference*
Links to ENV-039 Reference Number
Period Covered*
Compiled By*
Condition By Condition
Regulators do not ask whether you feel compliant. They pick a condition and ask for the evidence. This log is where that evidence lives.
Conditions
Repeats12 fieldsCondition Number*
Condition Summary*
Condition Type*
Emission limit, monitoring, reporting, operational, improvement or record keeping.
Owner*
Frequency
Evidence Type*
Evidence Location
Evidence Available*
- Yes3 pts
- Partly1 pt
- No0 pts
Compliance Status*
- Compliant3 pts
- Partially compliant1 pt
- Non compliant0 pts
Non Compliance Detail
Self Reported To Regulator
Self reporting is almost always treated more favourably than discovery by inspection.
- Yes3 pts
- No0 pts
CAPA ID
Links to FDN-014 CAPA ID
Improvement conditions
3 fieldsImprovement Conditions Set
Completed By Deadline*
Overdue*
Summary
18 fieldsConditions Assessed*
Fully Compliant*
Compliance Percent*
Non Compliances*
Self Reported*
Found By Regulator*
Evidence Gaps Found*
Being compliant with no evidence is indistinguishable from being non compliant.
Trend Versus Last Period*
- Improving3 pts
- Stable2 pts
- Worsening0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Reported To Management Review*
Next Review Due*
Environmental Lead*
Signature*
Site Manager*
Second Signature*
ENV-040 · record IDs look like PCC2-2026-000 · Links Permit Register
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The log is a checklist against a document. What fails is the surrounding rhythm: a continuous condition checked at the wrong frequency, an improvement condition running past its date, a self-reporting decision never made.
Holds each permit's conditions against their own stated frequency and flags any evaluation overdue against that frequency, not a shared schedule.
Watches monitoring results, inspection findings and improvement deadlines for anything that should change a compliance status, and holds the write for approval.
Reconciles this log against the permit register and the legal requirements register so a permit reference stays traceable both ways.
Feeds overdue improvement conditions and open corrective actions into the operational schedule that closes them.
This template lives in KnowEnviro — environment and energy. Aspects, permits, waste, emissions, spills and sustainability reporting.
Meet KnowEnviro→Glossary
Permit Condition Compliance Log definitions and key terms
- Permit condition
- An individually numbered, individually enforceable requirement attached to a permit, distinct from the permit's existence or expiry date.
- Emission limit
- A condition setting a maximum quantity or concentration of a substance that may be released, monitored continuously or at a stated interval.
- Self-reporting
- Voluntarily notifying the regulator of a non-compliance before it is otherwise discovered, generally treated more favourably than detection by inspection.
- Improvement condition
- A permit condition requiring a specific action be completed by a stated date, tracked to that deadline rather than a recurring frequency.
- Compliance obligation
- A legal requirement an organisation must comply with, of which a permit condition is one specific, externally issued instance.
FAQ
Frequently asked questions about permit condition compliance log
Should every condition be reviewed on the same schedule?+
No. Each condition carries its own frequency, continuous, daily, weekly, monthly, quarterly or annually, and the log should reflect that rather than one shared interval. A shared interval guarantees some conditions are checked too rarely to catch a gap before it matters.
Is a compliant status enough without evidence attached?+
No. A compliant status with no evidence, or evidence only partly available, cannot be demonstrated on inspection and is treated the same as an actual non-compliance. The evidence type should match what the condition requires before the status is recorded as compliant.
Should a missed condition be reported to the regulator?+
In most regimes, self-reporting a non-compliance is treated more favourably than the regulator finding it independently. The log should record that decision explicitly for every non-compliant entry rather than defaulting to silence.
How are improvement conditions different from the rest?+
They are tied to a deadline, not a recurring frequency, with no partial credit against that deadline. An improvement condition should be tracked to its own overdue status, separate from the steady-state conditions the permit also carries.
What does the compliance percentage actually tell you?+
It is a rollup, not a substitute for reading the conditions individually. A high percentage next to one unresolved, high-consequence condition is not a genuinely clean permit.
How does this log relate to the permit register?+
The permit register records which permits exist, their conditions and expiry; this log is the ongoing evidence trail against those conditions as they come due. The two stay linked by the permit reference so both can be read together.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Environmental Management
Legal and Other Requirements Register
Lists every law, regulation, permit and commitment that applies to your operation
Compliance Evaluation Record
Records the periodic evaluation of whether you actually comply with each obligation
Waste Stream Register
Lists every waste stream produced on site, with its classification, container and disposal route
Waste Transfer Record
Records waste leaving site, including type, quantity, carrier and destination
Hazardous Waste Record
Records generation, storage and disposal of hazardous waste
Waste Area Inspection
Checks waste storage areas for correct segregation, labelling, containment and housekeeping
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 14001:2015 clauses 9.1.2, 6.1.3 and 10.2
- Environmental Permitting (England and Wales) Regulations 2016
- Clean Air Act Title V and Clean Water Act NPDES permit programmes (US)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.