A living, source-based case file for the proposed industrial energy campus on Lower River Road in Bradley County, Tennessee.
Approximate location of the proposed Project River site and selected surrounding features relevant to public review, including major roads, waterways, nearby residential and agricultural areas, and other local context. Prepared by Placeward from publicly available geographic and project information for orientation and analysis. Boundaries and locations are approximate. This map is not a survey and should not be used for engineering, legal-boundary, or permitting purposes. Inclusion of a nearby feature does not by itself indicate that the project will affect it.
Illustrative context map · approximate project area · not a survey · not to scale
Project River is a proposed large industrial-energy campus near Lower River Road and the Hiwassee River. Public descriptions combine natural-gas generation, woody-biomass generation, and a likely high-load industrial customer such as a data center. The project remains a proposal; published capacity, investment, employment, water, and economic figures are forecasts or design claims unless separately documented.
Case file updated October 1, 2026. Where sources conflict or have changed over time, the newer or more authoritative record is identified rather than silently merged.
Plain-language answers to the questions newcomers most often have about Project River. Each answer links to the deeper evidence review.
There is not one single reason, and not everyone is opposed. Public comments and local reporting show recurring concerns about the project’s scale and technical uncertainty, annexation and representation, transparency and timing, and possible effects involving water, air emissions, forestry, truck traffic, noise, lighting, and neighboring property.
The documented criticism is mainly about process: whether residents outside Cleveland have enough voice, whether annexation and land-use decisions could move faster than the supporting studies and records, and whether project promises would become enforceable conditions. The city later suspended direct Project River meetings while a third-party engineering review is pursued.
Current project materials describe a roughly 850-acre industrial-energy campus with up to 1,500 MW of onsite generation: 1,000 MW of natural gas and 500 MW of woody biomass. The campus is intended to serve a large high-load industrial user, but the end user is not confirmed in the reviewed public record.
Azure Engineering’s Project River profile describes roughly six million tons of biomass consumption per year for the proposed biomass system. That scale is why the exact fuel mix, sourcing radius, existing wood demand, harvest practices, transportation, and independently verified supply assumptions matter.
“Closed loop” means water or another cooling fluid is recirculated; it does not mean the system never needs outside water. Project River says recovered water from biomass drying would supply routine process and cooling needs, but the public record still lacks a complete phase-by-phase water balance covering initial fill, a gas-only first phase, treatment losses, blowdown, outages, drought conditions, and emergency demand.
No final Project River approval is established in the reviewed record. The city suspended direct Project River meetings pending third-party engineering review, and land-use decisions, environmental permits, utility arrangements, and other approvals follow separate processes.
Recent changes to the public record, with direct links to the detailed reviews they affect.
The Partnership for Policy Integrity estimates annual biomass demand at roughly 6.7 million tons and raises concerns about feedstock supply, truck traffic, air emissions, water use, and watershed impacts. Cross-checking those claims against developer statements and independent data shows that the proposed biomass scale is nationally significant, while the exact fuel requirement and regional forest-market effects remain assumption-dependent. A broader characterization of the Hiwassee watershed as one of the nation’s most polluted was not independently verified.
Read the PFPI technical audit →
RIV-038RIV-039RIV-040RIV-041RIV-042RIV-043RIV-044RIV-045RIV-046RIV-047
The City of Cleveland annexation page had listed a separate Wright Brothers Construction request involving approximately 385.58 acres on Lower River Road, proposed General Commercial zoning, and a September 28 hearing. The final September 28 City Council agenda did not list that request.
The City of Cleveland announced that direct meetings concerning Project River were being suspended while a third-party engineering review is pursued. The special-called September 21 Planning Commission meeting was later shown as canceled in the city record.
Open the full evidence review for the issue you care about. Status labels show where each review currently stands.
Public commentary is useful evidence of what people are concerned about, support, oppose, or want decision-makers to address. It is not automatically evidence that the underlying factual claim is true.
residents outside Cleveland question city control over land and impacts currently located in Bradley County.
recurring questions focus on the unprecedented integration of very large biomass, gas, water-recovery, and potential data-center systems.
water, air emissions, forestry, truck traffic, noise, lighting, habitat, and neighboring property effects are persistent themes.
residents have asked for studies, maps, applications, corporate due diligence, and time to review records before consequential votes.
supporters at the Sept. 12 meeting emphasized job creation and local wage opportunities.
the project team argues that large private investment could expand the city/county tax base and support public services.
proponents describe demand for regional wood products and energy infrastructure as an economic opportunity.
These records would resolve a large share of the most important open questions before stronger conclusions can be drawn about the project’s design, impacts, costs, and enforceable protections.
Primary records outrank summaries. Applications are not approvals; proposed conditions are not enacted law; forecasts are not outcomes.
Developer statements are attributed. Placeward does not treat a company claim as independently verified merely because it is specific.
Community concerns remain visible. They are labeled as concerns until supported by independent evidence.
Legal allegations are handled cautiously. A lawsuit or filing shows that a claim was made, not that a court found the claim true.
New information can change the file. Superseded claims and earlier designs should remain traceable rather than disappearing.
