Between the yearly compliance certifications, a Title V facility owes a more frequent accounting of how its monitoring is going: the semiannual monitoring report. Filed twice a year, it summarizes the results of the monitoring the permit requires over the preceding six months and reports every deviation from a permit term that occurred in that window. It is the report that keeps the regulator informed during the year rather than only at its end, and it is distinct from the annual certification in both timing and character. The recurring pain of the semiannual report is the pre-deadline log review, the scramble to comb through six months of monitoring data to find the excursions and deviations that have to be reported. That scramble largely disappears when excursions and monitoring gaps are captured automatically as they happen. This page explains what the semiannual report contains, how it differs from the annual certification, and how continuous capture builds the report as the period unfolds.
Title V semiannual report in one line: A Title V semiannual monitoring report is a report a major air source files twice a year summarizing the results of the monitoring its operating permit requires over the preceding six months and identifying every deviation from a permit term during that period. It keeps the regulator informed of the facility's monitoring and compliance through the year, distinct from the once-a-year compliance certification. Automatically capturing setpoint excursions and monitoring gaps as they occur builds the report continuously instead of through a frantic pre-deadline review of six months of logs.
The semiannual monitoring report has two jobs, and both are about the preceding six months. The first is to summarize the results of the monitoring the permit requires, showing that the facility conducted the monitoring at the required frequency and reporting what it found. The second, and the part regulators focus on, is to identify every deviation from a permit term that occurred during the period. A deviation is any departure from a permit condition, whether an emission limit exceeded, a monitored parameter out of its required range, or a required monitoring that did not happen, and each one has to appear in the report.
The report is not a raw data dump; it is a summary that has to surface the deviations clearly, because the regulator uses it to understand where the facility departed from its permit during the half-year. For each deviation, the report generally conveys what term was deviated from, when and for how long, and often the probable cause and any corrective action, so that the deviation is not just flagged but characterized. A facility that had no deviations still files, reporting that the required monitoring was performed and that no deviations occurred.
Monitoring gaps are a subtle but important category the report has to address. If the permit requires monitoring at a certain frequency and a monitor was down, a reading was missed, or data was lost, that gap is itself a departure from the monitoring requirement and typically has to be reported. Facilities sometimes overlook gaps because nothing exceeded a limit during them, but the absence of required monitoring is itself reportable, and a semiannual report that omits known monitoring gaps is incomplete. Capturing when monitoring did not happen is therefore as important as capturing when a parameter went out of range.
The semiannual monitoring report and the annual compliance certification are related but distinct, and confusing them is a common mistake. The semiannual report is filed twice a year and its job is to summarize monitoring results and report deviations for the six-month period, keeping the regulator currently informed. It is a monitoring-and-deviation report, focused on what the monitoring showed and where the facility departed from its permit during that window.
The annual compliance certification, by contrast, is filed once a year and is a signed attestation by the responsible official to the facility's compliance status with each permit term over the whole year. Its character is a certification carrying legal weight and a personal signature, not just a summary of results. Where the semiannual report tells the regulator what happened over six months, the annual certification is the official standing behind a statement of compliance for the full year, term by term. The semiannual reports and the annual certification cover overlapping ground, since the deviations reported semiannually feed the annual compliance picture, but they are not interchangeable filings.
The practical relationship is that the semiannual reports, filed through the year, and the deviation records behind them, become the raw material the annual certification aggregates. A facility that has filed accurate semiannual reports has already assembled much of what the annual certification needs, because the deviations are already documented. A facility that has been sloppy about its semiannual reporting faces a harder annual certification, because the year-end aggregation has to reconstruct what the semiannual reports should have already captured. Keeping the semiannual reporting rigorous therefore pays off twice, once for each semiannual filing and again for the annual certification.
The characteristic failure mode of semiannual reporting is the pre-deadline log review. As the reporting deadline approaches, someone has to go back through six months of monitoring records, find every excursion where a parameter left its required range, identify every monitoring gap, and assemble them into the report. This is tedious, it is error-prone, and it is exactly the kind of retrospective hunt where deviations get missed, because a brief excursion three months earlier is easy to overlook when combing through a half-year of data by hand. The report is only as complete as the review, and manual reviews of long periods are not reliably complete.
The alternative is to capture the reportable events as they happen rather than hunting for them later. When a monitoring system flags each excursion at the moment a parameter leaves its permitted range, and records each gap when required monitoring does not occur, the report's content accumulates continuously through the six months. By the deadline, the list of deviations and monitoring gaps already exists, built event by event as the period unfolded, so preparing the report is a matter of compiling captured events rather than searching for them. Nothing has to be reconstructed because nothing was left to memory.
A cloud SCADA platform is what makes that continuous capture practical for Title V monitoring. Where a system such as Merobix trends the compliance parameters, raises an excursion when a value crosses a permitted setpoint, and logs the absence of expected data as a monitoring gap, the reportable events for the semiannual report are being collected automatically the entire time. When the deadline arrives, the facility compiles the excursions and gaps the system already captured, with their timing and duration attached, into the report. The frantic log review is replaced by a review of a list that was maintained all along, which both saves the pre-deadline scramble and makes the report more complete, because an automated system does not overlook the brief excursion a tired reviewer misses at the end of a six-month hunt.
It is filed twice a year, with each report covering the preceding six-month period. It summarizes the results of the monitoring the permit requires over that window and identifies every deviation from a permit term that occurred, keeping the regulator informed of the facility's monitoring and compliance during the year. This is distinct from the compliance certification, which is filed once a year.
The semiannual report, filed twice a year, summarizes monitoring results and reports deviations for a six-month period, while the annual compliance certification, filed once a year, is a responsible official's signed attestation to compliance with each permit term over the whole year. The semiannual report is a monitoring-and-deviation summary; the annual certification is a legally weighty signed statement. The deviations reported semiannually feed the annual compliance picture, but the two are separate filings.
By capturing reportable events as they occur instead of hunting for them at the deadline. When a monitoring system flags each excursion the moment a parameter leaves its permitted range and logs each gap when required monitoring does not happen, the list of deviations and monitoring gaps accumulates continuously through the six months. Preparing the report then becomes compiling captured events rather than combing through six months of logs, which is both faster and more complete.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.