A Title V operating permit gathers all of a major air source's applicable requirements into one document, and once a year the facility has to certify, term by term, whether it complied with them. The Title V annual compliance certification is that statement. It is signed by a responsible official who attests, under the weight of federal law, to the facility's compliance status with each permit condition over the year, identifying where the facility was in continuous compliance and where it deviated. The certification is only as strong as the monitoring behind it: an official signing a certification wants to be attesting to something the facility can prove, not offering a good-faith guess. That is why continuous parametric monitoring matters so much here. This page explains what the annual certification is, how it aggregates a year of monitoring and deviations, and why continuous records turn the certification into an evidence-backed signature rather than an attestation of faith.
Title V compliance certification in one line: A Title V annual compliance certification is a yearly statement, signed by the facility's responsible official, certifying the facility's compliance status with each term and condition of its Title V air operating permit over the reporting year, and identifying whether compliance was continuous or intermittent for each. It aggregates the year's monitoring data and any deviations into a single attestation carrying legal weight. Continuous parametric monitoring records let the official back that certification with evidence rather than signing on good faith.
The defining feature of a Title V permit is that it consolidates every applicable air requirement for a source into one enforceable document, and the annual compliance certification is the mechanism that closes the loop by requiring the facility to report, once a year, how it did against all of them. The certification goes term by term through the permit's conditions and states the facility's compliance status with each: whether it complied, and whether that compliance was continuous throughout the year or intermittent. It is not a summary impression of overall performance; it is a condition-level attestation.
The signature belongs to a responsible official, a specifically defined senior person with authority to bind the facility, and that person's signature carries real legal consequences. Certifying compliance that did not exist, or failing to disclose deviations, is a serious matter because the certification is a formal statement to the regulator relied upon for the permit program's enforcement. The responsible-official requirement exists precisely so that a person with authority and accountability stands behind the certification, which is why officials are careful about what they are willing to sign.
Because of that accountability, the certification also has to identify the method used to determine compliance for each term, tying the attestation back to the monitoring, recordkeeping, and reporting that support it. The official is not just asserting compliance; the certification links each compliance statement to the basis for it. This is what separates a defensible certification from a hopeful one: the compliance claim for each term rests on a specified determination method, and the credibility of the whole certification depends on those methods actually having produced reliable records over the year.
The annual certification does not stand alone; it is the culmination of a year of monitoring and of the deviation reporting that happens throughout the year. Over twelve months a facility accumulates monitoring data for the parameters its permit requires it to track, along with records of every deviation from a permit limit or condition. The certification aggregates all of that into a single statement, so the official signing it is effectively summarizing whether, across the whole year and across every term, the facility met its obligations and where it fell short.
Deviations are the crux of the aggregation, because the certification has to reflect them honestly. A deviation is any departure from a permit term, whether an emission limit exceedance, a monitoring gap, or a failure to meet an operating parameter, and the certification has to identify the periods of compliance and non-compliance for each term rather than smoothing them over. An official cannot certify continuous compliance for a term that deviated; the certification has to disclose the intermittent compliance and the deviations behind it. This is why the year's deviation record has to be complete and accurate before the certification can be prepared.
The aggregation problem is real because a year is a long time and the permit has many terms, each with its own monitoring and its own potential deviations. Assembling an accurate, term-by-term compliance picture at the end of the year means having reliable records of the monitoring and every deviation across all of them, organized so that the official can see, for each term, whether compliance was continuous or where it lapsed. A facility that has not kept that record straight through the year faces a difficult reconstruction to produce a certification it can stand behind.
The difference between an evidence-backed certification and a good-faith one comes down to whether the facility can prove the compliance it certifies. Many permit terms are demonstrated not by measuring emissions directly but by monitoring parameters that indicate the control is working, the approach at the heart of compliance assurance monitoring: keeping a control device or process within a range of operating parameters that corresponds to compliant performance. Continuous parametric monitoring records those parameters throughout the year, so the facility can show that the control stayed within its compliant range rather than merely asserting that it did.
When those parametric records are captured continuously and retained, the responsible official signs a certification supported by data. For each term whose compliance is demonstrated by a parameter staying in range, the record shows whether it did, and any excursion outside the range is captured as a candidate deviation to be evaluated and, if a deviation, disclosed. The official is no longer attesting to a belief about the year; the official is attesting to a compliance status the monitoring record substantiates, which is exactly the position a person signing a legally weighty certification wants to be in.
A monitoring platform is what makes continuous parametric records practical and turns the annual certification into an aggregation of evidence. Where a cloud SCADA platform such as Merobix trends the compliance parameters continuously, flags excursions as they happen, and retains the history, the year's compliance picture is built as the year unfolds rather than reconstructed at its end. The official preparing the certification can see, term by term, the parametric record and the excursions, so the periods of continuous compliance and the deviations are both grounded in captured data. The certification becomes an evidence-backed signature: the official certifies what the monitoring shows, and the monitoring shows it because it was recording all year, which is precisely the assurance a Title V annual certification is meant to carry.
It is signed by the facility's responsible official, a specifically defined senior person with the authority to bind the facility, and that signature carries legal consequences. Certifying compliance that did not exist or failing to disclose deviations is a serious matter because the certification is a formal statement relied upon for enforcement. The responsible-official requirement ensures a person with authority and accountability stands behind the attestation.
The certification has to go term by term through the permit and state whether compliance was continuous or intermittent for each, disclosing every deviation from a permit limit or condition rather than smoothing them over. A deviation can be an emission exceedance, a monitoring gap, or a failure to meet an operating parameter, and the official cannot certify continuous compliance for a term that deviated. This is why a complete and accurate deviation record across the whole year is needed before the certification can be prepared.
Many Title V terms are demonstrated by keeping a control device or process within a range of operating parameters that corresponds to compliant performance, so continuous parametric monitoring records whether those parameters stayed in range throughout the year. That record lets the responsible official certify compliance backed by data, with any excursion captured as a candidate deviation to evaluate and disclose. The certification becomes an attestation to what the monitoring shows rather than a good-faith belief about the year.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.