Government Statement
Project River: Permits, Enforcement & Monitoring
A review of the permits, agencies, operating conditions, monitoring systems, reporting requirements, enforcement tools, and remedies that would govern Project River.
A safeguard is strongest when the responsible agency, measurement method, reporting schedule, and remedy are all explicit.
Open · Detailed issue review
Current status
Project River will involve multiple land-use, environmental, utility, transportation, and construction approvals if it proceeds. The reviewed record identifies TDEC air and water public-participation systems and proposed PUD conditions, but it does not yet contain a complete final permit matrix mapping every project component and phase to its required approval, monitoring obligation, responsible regulator, and enforcement mechanism.
What is documented
Records and statements that can be tied to an identified source.
Developer Statement
Project River describes proposed PUD operating requirements
Project River’s September 15 materials describe proposed conditions involving setbacks, noise, truck routing, onsite power, and onsite process water. Those conditions are not the same as environmental permits and should be tracked through final adoption.
Sources:RIV-014
What the project says
These statements are attributed to the project or its participants and are not automatically independent findings.
The proposed PUD is intended to create binding local conditions
Project River describes PUD 77 as a vehicle for enforceable development requirements. The strength of those protections depends on final text, measurement standards, reporting, inspection authority, and remedies.
Sources:RIV-014
Permitting and enforcement context
Different project components may be governed by different agencies and approvals. A useful permit matrix should show what must happen before grading, construction, commissioning, and operation for each phase.
State environmental permits remain separate from local land-use approvals
TDEC air and water processes can impose requirements independently of municipal annexation, zoning, or PUD actions.
Monitoring and remedies determine whether conditions are practical
A numeric limit is most meaningful when the measurement method, frequency, data access, responsible authority, correction deadline, and enforcement consequences are clear.
What remains unresolved
- ?What complete set of local, state, federal, utility, transportation, building, environmental, and construction approvals is required for each phase?
- ?Which applications have actually been filed, accepted as complete, noticed, drafted, issued, appealed, or modified?
- ?What studies must be accepted before grading, construction, commissioning, or operation?
- ?Which limits require continuous monitoring, periodic testing, self-reporting, inspections, or third-party verification?
- ?Which data will be public, how quickly, and in what format?
- ?What agency or local body investigates complaints and what correction deadlines and penalties apply?
- ?What project changes trigger permit modification, renewed modeling, additional public notice, or a new land-use review?
Evidence needed
Master permit matrix
Every required approval by phase, agency, statutory/regulatory basis, filing status, decision date, expiration, and dependency.
Application and permit files
Applications, technical studies, agency questions, revisions, draft permits, public comments, final permits, and appeal records.
Monitoring matrix
Each enforceable condition mapped to instrument, frequency, location, responsible party, calibration/QA requirements, reporting, and public access.
Enforcement matrix
Inspection authority, complaint pathway, corrective-action deadlines, penalties, stop-work or operating remedies, and escalation process.
Material-change rules
Defined triggers for renewed engineering, permit modification, public notice, zoning review, or other approvals when the project changes.
Supporting detail
Go deeper without losing your place
Expand chronology, community concerns, research priorities, verification methods, and related guidance as needed.
Community concerns in the record3 items
These entries document concerns raised by residents or outside advocates. They are not presented as proven factual conclusions.
Whether safeguards will be enforceable
Community commentary has emphasized that voluntary promises should not substitute for measurable, enforceable conditions with clear remedies.
Whether permit information will be public early enough
Residents have asked for applications, studies, agency comments, and draft conditions to be available before key decisions and comment deadlines pass.
How future changes would be handled
Community discussion has raised concern that changes in fuel, technology, end user, water demand, or scale could outgrow assumptions in earlier approvals unless material-change triggers are explicit.
Additional considerations3 items
Potential advantage of a clear permit matrix
A transparent cross-agency matrix can make responsibilities, deadlines, public comment opportunities, and operating obligations understandable before construction starts.
Potential risk of fragmented oversight
If conditions are scattered across agencies and agreements without one traceable record, gaps or inconsistent assumptions can be harder for the public and decision-makers to identify.
The verification question
Each safeguard should be traceable from proposal to enacted condition to monitoring data and, if necessary, enforcement action.
Verification approachMethod
- Build the permit inventory.Identify every approval and the project phase or activity it governs.
- Track status from filing to final action.Distinguish contemplated permits from filed applications, draft permits, final permits, modifications, and appeals.
- Map every condition to monitoring.For each material limit, identify who measures it, how often, where, with what method, and where the data is reported.
- Track enforcement outcomes.Preserve complaints, inspections, violations, corrective actions, penalties, and changes to permit conditions over time.
Research addendum · October 1, 2026
PFPI audit: use third-party calculations to test permits, not replace them
PFPI’s analysis identifies technical pathways that should be checked when permit applications become public. The agency filings will be the stronger source for what the project is actually seeking permission to build and operate.
Placeward Analysis
Air-permit review should reconcile the public technology descriptions
When a TDEC air application appears, it should be compared directly with the project website, Azure materials, PFPI calculations, and EPA reference factors. Material differences in fuel, conversion technology, operating hours, controls, stack design, or emission assumptions should be logged rather than silently harmonized.
Placeward Analysis
Water and stormwater permits should be evaluated separately from the “self-supplied water” claim
Even if routine process water ultimately comes from recovered biomass moisture, land disturbance, stormwater, wastewater, treatment residuals, spills, and other water pathways remain distinct regulatory questions. Permit status and enforceable limits should be taken from TDEC records.
This addendum compares PFPI’s analysis with stronger or more direct sources and identifies which claims are supported, assumption-dependent, unresolved, or unverified. PFPI’s conclusions remain third-party analysis rather than project facts.