Project River: Governance, Transparency & Public Process

A review of public notice, records access, meeting sequence, independent review, disclosure, enforceable commitments, and whether participation occurs while decisions remain open.

Transparency is most useful before consequential decisions become difficult to change.

Open · Detailed issue review

Current status

Project River has prompted substantial scrutiny of when government bodies first received project information, what records and studies are public, how annexation and zoning proceedings are sequenced, and whether community participation occurs early enough to matter. The city’s September 18 notice suspended direct Project River meetings while a third-party engineering review is pursued.

Sources:RIV-001RIV-012RIV-021RIV-022RIV-024RIV-027RIV-032

What is documented

Records and statements that can be tied to an identified source.

GovernmentStatement

The city suspended direct Project River meetings pending engineering review

On September 18, the City of Cleveland announced that direct Project River meetings were being suspended while the Wright family engaged a third-party engineering firm and that the September 21 meeting was canceled.

Sources:RIV-001

GovernmentStatement

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

The City Agenda Center identifies the meeting as canceled. A canceled meeting should not be represented as a vote or approval.

Sources:RIV-032

Third-PartyAnalysis

Two public project meetings occurred in September

Local reporting documents September 1 and September 12 project meetings, including project presentations, questions, supporters, and opposition.

Sources:RIV-021RIV-022

GovernmentStatement

Tennessee public-record law governs access to existing government records

The Tennessee Office of Open Records Counsel provides guidance on requests for existing public records and applicable limitations. Public-record law does not require government to create a new study merely because the public requests one.

Sources:RIV-012

What public officials and project participants have said

These statements are attributed to the project or its participants and are not automatically independent findings.

Third-PartyAnalysis

City officials described the September 21 event as presentation-focused rather than a vote

Local radio reporting attributed statements to city officials that the scheduled September 21 event was intended for presentation rather than a final vote and that additional community engagement was expected.

Sources:RIV-024

DeveloperStatement

The project has presented proposed PUD requirements as binding safeguards if adopted

Project River says proposed PUD 77 conditions would create enforceable operating requirements once finalized and enacted. Proposed conditions remain distinct from adopted law.

Sources:RIV-014

Public-process context

A transparent process requires more than public meetings. It requires enough information, time, procedural clarity, and access to underlying records for the public and decision-makers to evaluate material claims before action.

GovernmentStatement

Records access and decision procedure are different tools

Public-record requests can reveal existing documents, while planning, zoning, annexation, permitting, and council procedures govern how decisions are noticed, heard, recommended, and adopted.

Sources:RIV-012RIV-032

PlacewardAnalysis

Proposed safeguards should be tracked through final enactment

A public commitment becomes materially stronger when its final text, responsible authority, measurement method, reporting obligation, enforcement mechanism, and remedy are clear and adopted before reliance on it.

Sources:RIV-014RIV-029RIV-031

Community concerns in the record

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

CommunityConcern

Whether important information arrives too late

Community commentary has repeatedly called for engineering, environmental, corporate, financial, and boundary information to be public before consequential land-use decisions are made.

Sources:RIV-022RIV-027RIV-031

CommunityConcern

Whether residents outside the city are adequately heard

Residents near the project but outside Cleveland have raised representation concerns because city actions may affect a broader surrounding community.

Sources:RIV-021RIV-022RIV-027RIV-031

CommunityConcern

Whether separate proceedings are easy to confuse

Annexation, zoning, PUD conditions, environmental permits, utility arrangements, and separate Lower River Road actions can follow different procedures and timelines. Community discussion has emphasized the need for clear separation.

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

What remains unresolved

  • ?When did each city, county, utility, and state entity first receive a Project River-specific proposal, study, application, or request?
  • ?Which consultant scopes, engineering studies, staff reports, legal analyses, correspondence, and meeting materials will be public before proceedings resume?
  • ?Who selected and is paying the third-party engineering reviewer, and what are the scope, qualifications, conflicts, deliverables, exclusions, and release terms?
  • ?Which public hearings, notices, recommendations, and votes remain before any current annexation, zoning, or PUD action can become effective?
  • ?Which project commitments will be incorporated into enforceable ordinances, permits, agreements, or bonds rather than remaining voluntary statements?
  • ?How will material changes in project scale, technology, end user, fuel, water demand, or emissions be disclosed and reviewed?
  • ?What version-history and correction record will be maintained for major public claims and government documents?

Evidence needed

Master procedural timeline
Every filing, notice, meeting, cancellation, withdrawal, recommendation, vote, ordinance, permit action, and effective date.
Independent-review scope and report
Reviewer identity, qualifications, conflicts, contract, funding source, scope, underlying data, exclusions, findings, and public-release plan.
Government correspondence and staff files
Project-specific communications, applications, staff memoranda, consultant work, legal analyses, and presentation materials subject to applicable law.
Final commitment matrix
Each developer promise mapped to an ordinance, permit, agreement, measurement method, responsible agency, reporting schedule, remedy, and effective date.
Public participation calendar
Upcoming hearings, comment periods, decision points, and deadlines with clear explanation of what each body can and cannot decide.

Potential advantage of an independent review

A well-scoped, genuinely independent engineering review that is released publicly can improve the factual basis for later decisions.

Potential risk of process without usable information

Public meetings offer limited accountability if key studies, contracts, legal bases, or technical assumptions are unavailable until after major decisions.

The verification question

Placeward would track what was known, when it became public, what decisions remained open, and which commitments became enforceable.

How Placeward will verify it

  1. Reconstruct the decision timeline.Date every material filing, meeting, notice, study, public statement, recommendation, vote, and cancellation.
  2. Track the record behind each decision.Link decision points to the studies, staff analysis, consultant work, legal basis, and public comments available at that time.
  3. Separate promises from enacted requirements.Follow proposed safeguards through final ordinance, permit, contract, or other enforceable form.
  4. Maintain a change log.Preserve superseded project claims, revised designs, corrected facts, and later changes so the public record remains traceable.