What reports does a Title V permit require?

At minimum: monitoring reports at least every 6 months under 40 CFR 70.6(a)(3)(iii)(A), prompt reporting of deviations under 70.6(a)(3)(iii)(B), and an annual compliance certification under 70.6(c)(5). Permits and state programs add specifics, and many states use their own formats such as semi-annual monitoring report forms.

Who signs Title V reports?

A designated Responsible Official must certify submissions, based on information and belief formed after reasonable inquiry, that they are true, accurate, and complete, per 40 CFR 70.5(d). That certification carries personal legal weight.

How fast must deviations be reported?

Promptly, as defined by the permit and state program. Many programs set specific clocks by deviation type, and some require rapid initial notice for certain events with written follow-up. The permit's own language controls, so it must be tracked, not remembered.

The Title V Reporting Calendar: Semi-Annual Reports, Deviation Reports, and the Annual Certification

Every Title V facility lives on a reporting calendar, and the calendar does not negotiate. Twice a year, the monitoring report. Whenever something deviates, the deviation report, on a clock. Once a year, a certification signed by a named human being who is legally accountable for its accuracy. The information in these reports is almost never new; it is the facility's own records, assembled and reconciled. Which is exactly why the work is so absorbing: assembly under deadline is where errors breed.

The semi-annual monitoring report

40 CFR 70.6(a)(3)(iii)(A) requires monitoring reports at least every six months, identifying all deviations from permit requirements. States implement this through their own formats; Pennsylvania's semi-annual monitoring report is one example of the genre. The report walks the permit's monitoring conditions: what each condition required, what the records show, and where the record fell short. Building one manually means walking every condition against six months of data, twice a year, forever.

Deviation reporting

70.6(a)(3)(iii)(B) requires prompt reporting of deviations, with the permit and state program defining prompt. The definitions vary by program and by deviation type, some events carry rapid initial-notice clocks with written follow-up, and the only safe practice is treating each deviation clock as a tracked condition of its own. A deviation that was handled well operationally can still become a violation if the report is late.

The annual compliance certification

Once a year, under 70.6(c)(5), the facility certifies its compliance status with every term and condition: continuous or intermittent compliance, the methods used to determine it, and any deviations. The Responsible Official signs under 70.5(d), certifying truth, accuracy, and completeness based on reasonable inquiry. This is the document that concentrates the whole program's quality into one signature. An RO signing over a spreadsheet is certifying the spreadsheet.

What assembly looks like from a live register

Every one of these reports is a projection of the same underlying record: conditions, monitoring data, deadlines, deviations. Keep that record live and cited, and the reports stop being built and start being generated.

In AirComply, the semi-annual report drafts itself from the tracked monitoring record: each condition's requirement, the data against it, and any gaps, with citations to both permit and record. Deviations logged during the period arrive already characterized, with their reporting clocks tracked from the event. The annual certification assembles the year's status condition by condition and stages it for the Responsible Official with a verification checklist, because the signature, and the reasonable inquiry behind it, is human work the platform exists to support, not replace.

The result is a reporting calendar that costs days instead of weeks, and a record where the RO can trace every certified statement to its source before signing. That trace is what we mean by nothing submitted on AI authority. Watch a report assemble itself, then check its citations.