Building a Title V compliance matrix that holds up in an inspection

Why a matrix

A Title V permit gathers every applicable requirement for a facility into one document, and most compliance problems are tracking problems: a monthly calculation nobody owned, a quarterly observation that moved with a staff change, a report that depended on a record nobody kept. A compliance matrix turns the permit into a list of tasks you can assign, check, and certify.

Break conditions into single requirements

One permit condition often holds several requirements: a limit, the monitoring that shows compliance, the record, and the report. Give each its own row. A row should be one thing a person can do and prove.

• The requirement, in the permit's words
• The condition number and the underlying rule citation
• How compliance is demonstrated (calculation, monitoring, inspection, test)
• Frequency and the due date rule (for example, the permit's deadline after period end)
• Owner and backup
• The record that proves it, and where it is kept

Expand the requirements incorporated by reference

Permits often say a unit must comply with an NSPS or NESHAP subpart and stop there. The subpart and its general provisions bring their own monitoring, testing, notification, recordkeeping, and reporting requirements. Add rows for them; they are as enforceable as the permit's own text.

Connect it to reports and certifications

Periodic monitoring reports must identify every deviation in the period (40 CFR 70.6(a)(3)(iii)(A)), and the annual compliance certification asks for the method used to determine compliance with each term (40 CFR 70.6(c)(5)). If each row already names its method and record, both reports become an exercise in reading the matrix.

Keep it current

Update the matrix at every permit action: administrative amendments, minor and significant modifications, renewals, and new underlying rules. Date each version. An out-of-date matrix is worse than none, because people trust it.