Loading...
compliance

Air Permit Deviation Report

An Air Permit Deviation Report template for documenting permit-limit deviations, excess emissions, probable cause, and corrective actions in one submission. Use it to capture the facts needed for Part 70 reporting and follow-up.

Fill it now — Free Get Started
Customize with AI →

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Manufacturing · Utilities · Chemical Processing · Oil And Gas · Waste Management

Overview

This Air Permit Deviation Report template is built to document a specific air permit deviation from first notice through corrective action. It collects the submission notice, facility and permit details, the deviation window, whether excess emissions occurred, what monitoring was impacted, the probable cause, and the follow-up owner. The structure is meant to support a clean internal record that can be reviewed, audited, and used for required reporting.

Use this template when a facility exceeds a permit limit, misses a permit condition, experiences a monitoring interruption tied to compliance, or needs to document a startup, shutdown, or malfunction event that may affect emissions reporting. It is especially useful when multiple people need to contribute facts but the final record must stay consistent and traceable.

Do not use it as a general incident log for unrelated safety events, maintenance notes, or routine equipment work. It is also not a substitute for legal review when a deviation may trigger state-specific or permit-specific reporting obligations. If the event is still under investigation, record what is known, mark conditional fields where needed, and update the report once the root cause and corrective actions are confirmed. The goal is to preserve the facts, keep the audit trail intact, and make follow-up easy to assign and close.

Standards & compliance context

  • This template supports documentation commonly used for air permit deviation reporting under 40 CFR Part 70, but site-specific permit language and state requirements still control the final filing obligation.
  • The form is designed around data minimization by collecting only the fields needed to document the deviation, emissions impact, cause, and corrective action.
  • If the report is shared outside the facility, review whether any names, emails, or other PII should be limited to authorized compliance personnel only.
  • Maintain an audit trail for edits, submissions, and follow-up changes so the record remains defensible during internal review or regulatory inspection.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Submission Notice

This section establishes who submitted the report and when, which is essential for an audit trail and deadline tracking.

  • Report Type (required)
  • Submission Date (required)
  • Reported By

    Optional. Enter only if needed for follow-up or audit trail.

  • Reporter Email

    Optional. Used only for follow-up questions.

Facility and Permit Details

This section ties the event to the correct facility, permit, and emission unit so the deviation is not misfiled.

  • Facility Name (required)
  • Facility ID or Site Code

    Optional if your organization uses a site identifier.

  • Title V Permit Number (required)
  • Affected Emission Unit(s) (required)

    List the unit, stack, process line, or control device involved.

  • Permit Condition or Limit Reference (required)

    Enter the specific permit condition, limit, or monitoring requirement involved.

Deviation and Emissions Details

This section records what happened, when it happened, and whether the event affected emissions or monitoring data.

  • Date Deviation Started (required)
  • Start Time (required)
  • Date Deviation Ended
  • End Time
  • Deviation Description (required)

    Describe the event, the permit limit or condition affected, and any visible or measured emissions impacts.

  • Did excess emissions occur? (required)
  • Was monitoring or CEMS/COMS data impacted? (required)

Conditional Event Details

This section appears when the event needs pollutant-level or emissions-estimate detail, keeping the form focused when it can be.

  • Event Category (required)
  • Affected Pollutants
  • Estimated Excess Emissions

    Enter the estimated quantity in the unit used by your permit or report (for example, tons).

  • Emissions Units

Probable Cause and Contributing Factors

This section captures why the deviation happened so reviewers can evaluate whether the issue was isolated or systemic.

  • Probable Cause (required)

    Summarize the most likely cause of the deviation or excess emissions.

  • Contributing Factors
  • Was a root cause analysis completed? (required)

Corrective Actions and Follow-Up

This section turns the report into an action plan by assigning ownership, deadlines, and any required follow-up.

  • Immediate Actions Taken (required)
  • Corrective Actions (required)

    Describe actions taken or planned to prevent recurrence.

  • Follow-Up Required

    Check if additional investigation, maintenance, or reporting is needed.

  • Follow-Up Owner

    Optional. Assign only if follow-up is needed.

  • Target Completion Date

How to use this template

  1. 1. Enter the submission notice first, including the report type, submission date, and the name and email of the person responsible for the initial filing.
  2. 2. Fill in the facility and permit details exactly as they appear on the permit so the deviation can be matched to the correct source unit and condition.
  3. 3. Record the deviation window, describe what happened in plain language, and indicate whether excess emissions occurred or monitoring was impacted.
  4. 4. Complete the conditional event fields with the event category, affected pollutants, estimated emissions, and units only when the event requires that level of detail.
  5. 5. Document the probable cause, contributing factors, and whether root cause analysis was completed so reviewers can see whether the investigation is finished or still open.
  6. 6. Assign immediate actions, corrective actions, and follow-up ownership, then set a target completion date and review the record for missing fields before submission.

Best practices

  • Use the exact permit condition reference from the permit file instead of a paraphrase so reviewers can trace the deviation quickly.
  • Record the deviation start and end times in a consistent time zone and format to avoid confusion during reporting and audit review.
  • State whether excess emissions occurred even when the event seems minor, because that distinction affects downstream reporting decisions.
  • Use progressive disclosure for estimated emissions and pollutant fields so reporters only see them when the event category requires them.
  • Describe the probable cause in operational terms, not just as a generic equipment failure, so the corrective action can address the real issue.
  • Assign a named follow-up owner and target completion date for every open action so the report becomes a tracked workflow, not a static record.
  • Keep the form focused on the minimum necessary information and avoid collecting unrelated PII that does not support the compliance record.

What this template typically catches

Issues teams running this template most often surface in practice:

The reporter leaves the permit condition reference blank, which makes it hard to verify the exact obligation that was missed.
The deviation window is incomplete because only the date is entered and the start or end time is missing.
Excess emissions are not clearly marked, leaving reviewers unsure whether the event needs additional reporting.
Estimated emissions are entered without units, which makes the number unusable for comparison or filing.
The probable cause is written as a vague label instead of a specific operational explanation.
Corrective actions are listed, but no follow-up owner or target completion date is assigned.
Monitoring impacts are omitted even though the event affected data quality or availability.

Common use cases

Power Plant Environmental Compliance Lead
A compliance lead documents a boiler emissions exceedance, ties it to the correct permit condition, and assigns follow-up to operations and maintenance. The report becomes the internal record used to decide whether additional external reporting is needed.
Chemical Facility EHS Manager
An EHS manager records a process upset that affected multiple pollutants and requires root cause analysis. The template helps separate the event narrative, estimated emissions, and corrective actions into a reviewable compliance file.
Waste-to-Energy Operations Supervisor
An operations supervisor logs a monitoring outage that interrupted compliance data collection during a scheduled run. The form captures the outage window, impacted monitoring, and the immediate steps taken to restore control.
Oil and Gas Environmental Coordinator
An environmental coordinator documents a deviation tied to startup or shutdown activity and routes the report to the right owner. The structured fields help keep the event consistent across field notes, internal review, and permit reporting.

Frequently asked questions

What does this Air Permit Deviation Report template cover?

This template captures the core facts needed when an air permit limit or condition is not met, including the deviation date and time, the affected emission unit, the permit condition reference, excess emissions, probable cause, and corrective actions. It is designed to create a clear audit trail for internal review and external reporting. It also supports follow-up ownership and target completion dates so the issue does not stop at documentation.

When should a deviation report be completed?

Complete it as soon as the event is identified and the basic facts are known, rather than waiting for a full investigation to finish. If your site has a reporting deadline under the permit or applicable rule, this form helps you gather the information early enough to meet it. If the event is still unfolding, use the conditional fields and update the record as more information becomes available.

Who should fill out this form?

It is usually completed by EHS, environmental compliance, operations, or the responsible unit owner, depending on how your facility assigns permit reporting. The best practice is to have the person closest to the event enter the initial facts, then have compliance review the report for accuracy and completeness. That reduces missing details and helps keep the record consistent with the permit file.

Does this template support regulatory reporting under 40 CFR Part 70?

Yes, the template is structured to support documentation commonly needed for Part 70 deviation reporting, including the permit condition reference, deviation timing, excess emissions, and corrective actions. It does not replace legal review or site-specific reporting obligations, because permit language and state implementation details can vary. Use it as the working record that feeds your formal submission process.

What are the most common mistakes when using this form?

Common mistakes include leaving out the permit condition reference, using vague descriptions like "equipment issue" instead of a specific deviation narrative, and failing to record start and end times. Another frequent issue is estimating emissions without stating the units or method used. The form works best when each field is completed with the minimum necessary detail and no unnecessary PII.

Can this template be customized for different facilities or emission units?

Yes, it is meant to be adapted to your permit structure, unit naming conventions, and internal review workflow. You can add conditional logic for event categories, pollutant types, or site-specific follow-up steps, and you can remove fields that are not used at your facility. Keep the form focused on the data you actually need so it stays usable and aligned with data minimization.

How does this compare with handling deviations in email or spreadsheets?

Email and spreadsheets often lose key details, create version confusion, and make it harder to maintain a consistent audit trail. This template standardizes the fields that matter for compliance review, which makes it easier to compare events, assign follow-up, and retrieve records later. It also reduces the chance that a required detail is missed because the reporter was working from memory.

What should happen after the report is submitted?

The report should trigger review, validation, and follow-up assignment, not just storage. A compliance owner should confirm the facts, determine whether additional reporting is required, and verify that corrective actions are tracked to completion. If your process includes an internal notification or ticketing step, connect that workflow so the deviation does not stall after submission.

Related templates

Forms

Uniform Hazardous Waste Manifest Tracking Log

Track hazardous waste shipments, manifest copies, and receipt confirmation in one log. Use it to ...
Forms

Conflict of Interest Disclosure

Annual conflict of interest disclosure form for employees to report outside employment, business ...
Forms

EPA 608 Technician Certification Roster

Track each refrigerant technician’s EPA 608 certification details, proof-of-certification file lo...
Forms

Confidentiality Agreement NDA Form

Capture the parties, scope, term, and signature details for a confidentiality agreement in one pl...
Forms

CGA DIRT Field Submission Form

CGA DIRT Field Submission Form template for reporting excavation damage with incident details, ro...
Inspections

Fall Protection Equipment Inspection

Inspect PFAS gear before use or on an annual competent-person schedule with a clear checklist for...
Sop

Fire Evacuation Procedure

A fire evacuation procedure that tells each role exactly what to do from alarm to accountability....
Hr Policy

Anti-Harassment & Anti-Discrimination Policy

Anti-Harassment & Anti-Discrimination Policy template for defining prohibited conduct, reporting ...

Go deeper on the topic

Related concepts
  • Lockout/Tagout
    Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
  • Job Hazard Analysis
    Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
  • Near-Miss Reporting
    A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
  • AI Governance
    AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
Related guides

Ready to use this template?

Get started with MangoApps and use Air Permit Deviation Report with your team — pricing built for small business.

Get Started
Customize with AI →