Loading...
compliance

Air Permit Daily Operating Log

Daily log for recording air permit operating parameters, control device checks, permit limit status, and any exceedances. Use it to create a clear audit trail and trigger timely corrective action.

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

Built for: Manufacturing · Utilities · Food Processing · Chemical Processing · Printing And Coatings

Overview

This Air Permit Daily Operating Log template captures the daily facts that matter for an emission unit: when it ran, how much it produced, what fuel it used, whether the control device was working, and whether the operation stayed within permit limits.

Use it when your air permit requires routine operating records, monitoring checks, or prompt documentation of deviations. It is especially useful for boilers, generators, coating lines, scrubbers, thermal oxidizers, and other units where operating conditions affect emissions. The template also gives you a place to record who completed the log, when the monitoring occurred, and what follow-up was assigned after a problem was found.

Do not use this template as a catch-all incident report or a substitute for the permit itself. If your site does not need daily tracking, or if the unit is not covered by an air permit condition, a lighter record may be enough. Keep the form focused on the fields you actually use so operators are not forced to guess, over-document, or enter unnecessary PII. The best version of this log is short, specific, and easy to complete during the shift.

Standards & compliance context

  • This template supports air permit recordkeeping by creating a dated audit trail of operating conditions, monitoring results, and deviation follow-up.
  • Use data minimization and collect only the fields needed to demonstrate permit compliance or explain a deviation.
  • If the log is used in a public-facing or shared workflow, make required fields clear and ensure the form remains usable under WCAG 2.1 AA principles.
  • When a deviation is recorded, include the reporting status and corrective action so the record shows how the issue was handled.

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

Log Details

This section identifies the specific day, site, unit, and person responsible so every entry can be traced back to the right source.

  • Log Date (required)
  • Site / Facility Name (required)
  • Emission Unit / Process Area (required)
  • Completed By (required)
  • Shift

Operating Parameters

This section records the operating facts that often drive emissions and show whether the unit was run within its normal envelope.

  • Operating Hours (required)
  • Throughput / Production Rate
    Enter the daily throughput or production rate if your permit requires it.
  • Fuel Type Used
  • Fuel Usage
    Enter the quantity used for the day in the unit required by the permit.
  • Operating Notes
    Include any operating changes, maintenance impacts, or abnormal conditions relevant to permit compliance.

Control Device and Monitoring

This section captures the status of pollution controls and the monitoring method used to verify performance at the time of operation.

  • Control Device Status (required)
  • Monitoring Method
  • Monitoring Result
  • Monitoring Time
  • Monitoring Comments

Permit Limit Checks

This section documents whether the unit stayed within the permit terms and what limit condition was being checked.

  • Were all applicable permit limits met today? (required)
  • Limit Type
  • Limit Details
    Describe the applicable permit limit and the measured or observed value.
  • Corrective Action Taken

Exceedance or Deviation Reporting

This section records any out-of-limit event, including timing, description, and reporting status, so the deviation is not lost in the daily log.

  • Did an exceedance or deviation occur? (required)
  • Start Time
  • End Time
  • Description of Exceedance / Deviation
  • Reported to Compliance Team?

Follow-Up and Sign-Off

This section closes the loop by showing what actions remain open and who reviewed the record for completeness.

  • Follow-Up Actions
  • Supervisor Reviewed
  • Reviewer Name
  • Review Date

How to use this template

  1. 1. Set up the log with the exact unit name, site name, and permit-specific fields that apply to the emission source you are tracking.
  2. 2. Assign the form to the operator or shift lead who can observe the unit directly and record the operating data at the required time.
  3. 3. Enter the daily operating details, including hours, throughput, fuel type, and fuel usage, using the correct field type for each value.
  4. 4. Record control device status, monitoring method, monitoring result, and monitoring time as soon as the check is performed so the entry stays time-accurate.
  5. 5. If a limit is not met or a deviation occurs, document the limit type, description, corrective action, and whether compliance was notified.
  6. 6. Have the supervisor review the entry, confirm follow-up actions, and sign off with a review date so the record is ready for audit trail use.

Best practices

  • Use conditional logic so exceedance fields appear only when a deviation is marked, which keeps the form short and reduces missed entries.
  • Match each field to the data type, such as date picker for log_date and monitoring_time, numeric input for throughput and fuel_usage, and multi-select only when multiple limit types can apply.
  • Record the monitoring result at the time of the check, not after the shift ends, so the log reflects what was actually observed.
  • Keep permit limit details specific by naming the exact limit, threshold, or operating condition instead of writing vague notes like "within range."
  • Document corrective action in plain language, including what was done, who was notified, and whether the unit returned to normal operation.
  • Limit the form to the minimum necessary fields for the permit and avoid collecting unrelated PII or personal notes.
  • Require supervisor review only where your process needs it, and make the review step visible so the audit trail is complete.

What this template typically catches

Issues teams running this template most often surface in practice:

Operating hours are entered without the corresponding date or shift, making the record hard to reconcile later.
Throughput or fuel usage is estimated loosely instead of taken from the actual meter, batch record, or control system.
Control device status is marked as normal without noting the monitoring method or the time the check was performed.
A deviation is recorded but the permit limit type and limit details are left blank, so the issue cannot be tied back to the permit condition.
Corrective action is described too generally, such as "fixed issue," with no detail on what was done or whether compliance was notified.
Supervisor review is skipped or completed without a reviewer name and review date, weakening the audit trail.
The form includes unnecessary fields that slow completion and increase the chance of incomplete or inaccurate entries.

Common use cases

Boiler Operator Daily Compliance Log
A plant operator records fuel type, fuel usage, operating hours, and control device status for a boiler covered by an air permit. The log helps confirm the unit stayed within the permitted operating envelope and creates a clear record if a burner issue or alarm occurs.
Coating Line Emissions Check
A production supervisor documents throughput, monitoring results, and permit limit checks for a spray booth or coating line. If the control device is offline or a limit is exceeded, the form captures the deviation and the immediate corrective action.
Scrubber Performance Shift Log
An environmental technician uses the template to record scrubber status, monitoring method, and time-stamped results during each shift. This is useful when the permit requires routine checks of pressure drop, flow, or other operating parameters.
Unplanned Exceedance Follow-Up Record
A compliance team uses the deviation section to document when an exceedance started, when it ended, what caused it, and whether it was reported. The follow-up fields help route the issue to maintenance, operations, or environmental review.

Frequently asked questions

What is this Air Permit Daily Operating Log used for?

This template is used to document daily operating conditions for an emission unit, including operating hours, throughput, fuel use, control device status, and permit limit checks. It also captures deviations or exceedances and the follow-up actions taken. The result is a consistent audit trail that supports internal compliance reviews and external inspections.

How often should this log be completed?

It is designed for daily use, typically once per shift or once per operating day depending on how the site runs and what the permit requires. If the permit has shift-based monitoring, complete a separate entry for each shift. If operations are intermittent, log only the days the unit operates, but keep the record format consistent.

Who should fill out this form?

The person who directly observes the unit or reviews the operating data should complete the log, such as an operator, environmental technician, or shift supervisor. A supervisor or compliance reviewer should then sign off if your process requires secondary review. Assigning one accountable owner reduces missing fields and inconsistent entries.

Does this template help with regulatory compliance?

Yes, it supports permit recordkeeping by capturing the operating data, monitoring results, and deviation reporting that air permits commonly require. It is not a substitute for the permit itself, but it helps you document whether the unit stayed within permitted limits and what happened when it did not. Use the template alongside your permit conditions and site procedures.

What are the most common mistakes when using this log?

Common mistakes include leaving required fields blank, writing vague notes like "normal operation," and failing to record the time of a monitoring event or exceedance. Another frequent issue is documenting a deviation without stating the corrective action or who was notified. The template works best when entries are specific, time-stamped, and tied to the actual permit condition.

Can this template be customized for different air permits or units?

Yes, you can tailor the operating parameters, limit checks, and monitoring fields to match the specific emission unit and permit terms. For example, a boiler log may emphasize fuel type and fuel usage, while a coating line log may focus on throughput and control device status. Keep only the fields you actually use to follow the minimum-necessary principle.

How does this compare with using a spreadsheet or ad hoc notes?

A structured template reduces missed fields, makes reviews faster, and creates a more reliable audit trail than scattered notes. It also helps standardize what operators record across shifts and sites, which improves usability and consistency. Ad hoc notes often omit the exact limit, monitoring method, or follow-up action that compliance teams need later.

What should happen after a deviation is recorded?

The log should show whether the deviation was reported to compliance, what corrective action was taken, and whether follow-up is still open. If your site has an escalation process, the log should point the reviewer to the next step, such as maintenance, incident review, or permit condition verification. That keeps the record useful beyond the day of the event.

Ready to use this template?

Get started with MangoApps and use Air Permit Daily Operating Log with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?