Project River: Boundary, Annexation & Land Use

A parcel-by-parcel review of jurisdiction, annexation, urban-growth-boundary status, zoning, and the land-use approvals connected to Project River.

Sequence matters. Parcel geometry, legal authority, and the exact action being requested matter more.

Open · Detailed issue review

Current status

The public record documents several annexation and land-use actions in the Lower River Road / Frontage Road area, but those records do not by themselves establish that every action was undertaken for Project River or that every tract is legally part of the same approval path. The central task is to match each parcel to its ownership, corporate-limit status, urban-growth-boundary status, annexation method, zoning request, and current procedural status.

Sources:RIV-002RIV-003RIV-004RIV-005RIV-006RIV-021RIV-028RIV-033RIV-034RIV-035RIV-036

What is documented in the record

These items are supported by identified city, county, statutory, or dated reporting sources.

GovernmentStatement

A 4.93-acre Frontage Road annexation was pursued in 2024

Cleveland City Council records describe an approximately 4.93-acre tract at 9227 Frontage Road, Tax Map 014 Parcel 051.00. The annexation analysis states that the tract was outside the city’s then-existing Urban Growth Boundary and that annexation by referendum was proposed, with CH Highway Commercial zoning.

Sources:RIV-003

GovernmentStatement

A separate 5.75–5.8 acre Frontage Road annexation followed in 2025

The September 16, 2025 Planning Commission agenda lists a plan of service, annexation resolution, and CH Highway Commercial zoning request for about 5.75 acres at Frontage Road, Tax Map 014 Parcels 055.00 and 056.01. Bradley County minutes later document an interlocal agreement concerning the non-contiguous annexation of approximately 5.8 acres owned by Bruner One, LLC.

Sources:RIV-004RIV-005

Third-PartyAnalysis

The Project River team described annexation and planned-unit zoning as part of the project path

Local sourced reporting from the September 1 community meeting says the development team described annexation into Cleveland and planned-unit-development zoning as necessary to obtain city water and sewer service and to make the property marketable for the proposed campus.

Sources:RIV-021

GovernmentStatement

A separate 385.58-acre Lower River Road request was publicly listed, but not on the final Sept. 28 agenda

The City of Cleveland annexation page had identified a separate Wright Brothers Construction request involving approximately 385.58 acres along Lower River Road with proposed General Commercial zoning and a Sept. 28 hearing. The final Sept. 28 City Council agenda did not list that request. Placeward treats it separately from Project River and does not infer a vote, approval, denial, or reason for the agenda omission.

Sources:RIV-002RIV-036

GovernmentStatement

The September 21 special-called Planning Commission meeting was officially marked canceled

The City of Cleveland Agenda Center and calendar identify the September 21, 2026 special-called Planning Commission meeting as canceled. A canceled meeting is not an approval, denial, or vote on the Project River requests.

Sources:RIV-032

What the project says about land use

These are project-side descriptions of the intended approval structure and should be read as attributed statements rather than independent legal conclusions.

DeveloperStatement

The project says it accepted proposed PUD 77 requirements

Project River announced on September 15 that the Wright family had accepted the city’s proposed PUD 77 requirements subject to finalization. The project describes the PUD as a way to place additional operating restrictions and commitments into an enforceable city ordinance.

Sources:RIV-014

DeveloperStatement

The project has said PUD zoning is the preferred structure

Project River states that a PUD is not required “in this instance” but says the project and city view the PUD structure as the most appropriate way to establish site-specific requirements. That statement is the project’s legal and policy characterization, not a court or agency determination.

Sources:RIV-014

Legal framework and disputed interpretations

Placeward does not resolve contested annexation law. It identifies the governing provisions, the documented facts they depend on, and the competing interpretations that remain to be tested.

GovernmentStatement

Tennessee law generally ties annexation to contiguity, owner consent, notice, and a plan of services

Tennessee Code § 6-51-104 provides the general annexation framework. It allows annexation of adjoining territory and also provides a limited path for certain non-contiguous territory that is entirely within a municipality’s Urban Growth Boundary and is intended for industrial, commercial, future residential, or governmental use, with written owner consent and additional service/interlocal requirements.

Sources:RIV-006RIV-034

GovernmentStatement

A separate statute addresses limited expansion of an Urban Growth Boundary

Tennessee Code § 6-58-118 allows a municipality to expand its Urban Growth Boundary without reconvening the coordinating committee or obtaining county approval only if the tract is contiguous to a same-owner tract already annexed by the municipality, is being provided water and sewer service, and the owner consents by notarized petition.

Sources:RIV-033RIV-034

Third-PartyAnalysis

SELC disputes whether the Project River tract satisfies the asserted annexation path

The Southern Environmental Law Center has argued that the main Project River tract does not satisfy the legal requirements relied upon for annexation and Urban Growth Boundary expansion. Those are SELC’s legal arguments; Placeward does not present them as a court ruling or final agency determination.

Sources:RIV-028RIV-033

PlacewardAnalysis

Earlier annexations do not prove a coordinated Project River strategy by themselves

The timing and geography of the 2024 and 2025 Frontage Road actions are relevant to reconstructing the boundary history. The records reviewed so far do not, by sequence alone, establish motive, coordination, or that those earlier actions were undertaken specifically to enable Project River.

Sources:RIV-003RIV-004RIV-005RIV-029

Boundary and land-use chronology

This abbreviated timeline isolates the land-use events most relevant to the boundary question.

Jan 2024

9227 Frontage Road annexation analysis

City records describe an approximately 4.93-acre parcel outside the then-existing UGB and a proposed annexation by referendum with commercial zoning.

Sources:RIV-003

Mar 2025

Amended county growth plan ratified

Cleveland City Council Resolution 2025-26 ratified the amended Twenty-Year Growth Plan for Charleston/Cleveland/Bradley County, including an expansion of Cleveland’s Urban Growth Boundary.

Sources:RIV-035

Sep 2025

5.75-acre Frontage Road request

Planning Commission materials list a plan of service, annexation resolution, and CH zoning request for two Frontage Road parcels.

Sources:RIV-004

Dec 2025

County interlocal agreement

Bradley County minutes reference an interlocal agreement for the non-contiguous annexation of approximately 5.8 acres on Frontage Road.

Sources:RIV-005

Sep 1, 2026

Project team explains annexation / PUD path

At the first public meeting, the development team described annexation and planned-unit zoning as part of the path needed to market and serve the proposed campus.

Sources:RIV-021

Sep 15, 2026

Developer accepts proposed PUD requirements in principle

The project announced acceptance of proposed PUD 77 requirements subject to finalization.

Sources:RIV-014

Sep 21, 2026

Special-called Planning Commission meeting marked canceled

The official City Agenda Center and calendar identify the special-called meeting as canceled. Cleveland-Bradley Free Press separately reports that six formal campus requests were withdrawn that day; Placeward has not located a primary withdrawal filing in the current official source set.

Sources:RIV-023RIV-032

Sep 28, 2026

Previously noticed 385.58-acre request omitted from final agenda

The City annexation page had listed a separate commercial annexation involving approximately 385.58 acres and a Sept. 28 hearing, but the final Sept. 28 City Council agenda did not include that request.

Sources:RIV-002RIV-036

Community concerns in the record

These entries document concerns raised by residents or outside advocates. They are not presented as proven factual conclusions.

CommunityConcern

Representation and jurisdiction

Residents have questioned whether people living near the proposed campus but outside Cleveland would have meaningful representation in city land-use decisions that could affect them.

Sources:RIV-022RIV-027RIV-031

CommunityConcern

Whether earlier boundary actions were connected

Community commentary has questioned whether earlier Frontage Road annexations and growth-boundary changes were intended to create a path toward the Project River site. The chronology is documented, but motive has not been established by the records reviewed so far.

Sources:RIV-003RIV-004RIV-005RIV-027RIV-029

CommunityConcern

Conflating separate tracts and approvals

Residents and researchers have raised concern that the separate commercial annexation, Project River campus requests, PUD conditions, and other land-use actions can be easily confused. Each action needs its own parcel list, legal basis, notice, hearing, and decision record.

Sources:RIV-002RIV-021RIV-027RIV-029

What remains unresolved

  • ?What exact tax parcels make up the current Project River campus footprint, and who owns each parcel today?
  • ?Which of those parcels were inside Cleveland’s corporate limits and Urban Growth Boundary on each relevant filing date?
  • ?Which annexation mechanism is being relied upon for each tract: ordinary contiguous annexation, non-contiguous annexation under § 6-51-104(d), Urban Growth Boundary expansion under § 6-58-118, referendum, owner consent, or another path?
  • ?What evidence establishes legal contiguity where contiguity is required?
  • ?What water and sewer service existed for each tract at the time any § 6-58-118 request was filed?
  • ?What owner consents, petitions, plans of service, interlocal agreements, staff reports, and legal memoranda exist for the current campus requests?
  • ?What is the current operative text and procedural status of PUD 77, and which parcels would it govern?
  • ?What legal effect, if any, do recorded easements or other property interests have on owner-consent requirements? That question requires qualified legal review or a court determination, not inference from the public debate.

Evidence needed

Parcel-level boundary map
Tax parcel IDs, owners of record, acreage, legal descriptions, city limits, Urban Growth Boundary, zoning, and proposed project boundary on one dated map.
Historical UGB and corporate-limit snapshots
GIS layers, adopted growth-plan maps, annexation effective dates, and ordinances/resolutions showing how the boundary changed over time.
Complete annexation files
Petitions, owner consents, plans of service, resolutions, notices, staff reports, interlocal agreements, and supporting exhibits for each tract.
Utility-service evidence
Dated records showing whether and when water and sewer service was being provided to tracts for which § 6-58-118 is invoked.
Title and easement records
Current deeds, recorded easements, access rights, and other interests that may matter to ownership or consent questions.
Current zoning / PUD record
The latest PUD 77 text, zoning map, staff comments, conditions, revisions, and the record of any recommendation or vote.
City / county legal analysis
Any written staff, counsel, MTAS, CTAS, or outside-counsel analysis used to determine annexation authority and procedure.
Decision log
A dated list of every filing, withdrawal, cancellation, hearing, recommendation, vote, and effective date so separate proceedings cannot be conflated.

How Placeward will verify the boundary question

  1. Define the parcel set.Start with parcel numbers and legal descriptions rather than project marketing maps or generalized acreage.
  2. Reconstruct the boundary at each date.Overlay corporate limits and Urban Growth Boundary records as they existed when each request was filed.
  3. Match each parcel to its legal path.Identify the exact statute, petition, consent, plan of service, and interlocal requirements applicable to that tract.
  4. Separate annexation from zoning.Annexation changes municipal boundaries; zoning and PUD actions govern allowed land use. Neither should be treated as a substitute for environmental or utility permits.
  5. Track only completed procedural acts as completed.Applications, proposed conditions, scheduled hearings, and staff drafts remain distinct from adopted resolutions, enacted ordinances, and effective annexations.