PlacewardStronger Communities Through Informed Action
Projects›Project MidSpan›Issues›Project Control, End User & Buildout

Project MidSpan: Project Control, End User & Buildout

Who owns the site, who is leading development, who would operate the campus, what would be built, and how commitments survive changes in control.

The landowner is known. The ultimate operator and full buildout are not.

Open · Detailed issue review

Current status

SDCL Tennessee Propco LLC is identified as the property owner and plaintiff, and SDCL says it is leading Project MidSpan. The reviewed record does not yet identify the ultimate data-center operator or tenant, a binding end-user agreement, full building program, phased schedule, final investment amount, or permanent employment profile. Those details matter because operating impacts and enforceable commitments can change depending on who actually builds and runs the campus.

Sources:MID-004MID-005MID-009MID-010MID-016

What is documented

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

LegalFiling

SDCL Tennessee Propco LLC is the property-holding plaintiff

The verified complaint identifies SDCL Tennessee Propco LLC as the owner of the approximately 306-acre property and the party challenging Bradley County’s zoning rules.

Sources:MID-004

Third-PartyAnalysis

SDCL says it is leading MidSpan

A Project MidSpan spokesperson told local reporting that SDCL is leading the development alone and that MidSpan is unrelated to Project River.

Sources:MID-005

DeveloperStatement

SDCL has documented prior data-center energy work

SDCL’s corporate materials describe experience financing and developing energy infrastructure for data centers. Its Citi Riverdale case study describes a project it designed, contracted, and project-managed for a European data center. This demonstrates relevant experience but does not establish the MidSpan design, operator, or delivery structure.

Sources:MID-009MID-010MID-016

What is currently represented about the project

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

DeveloperStatement

MidSpan is presented as a distinct SDCL project

SDCL’s local messaging distinguishes Project MidSpan from Project River and presents SDCL as the development lead.

Sources:MID-005MID-007

DeveloperStatement

The project emphasizes sustainable and efficient infrastructure

SDCL’s corporate strategy centers on efficient and decentralized energy infrastructure, and its MidSpan statements emphasize water efficiency, neighbor protections, and project-paid infrastructure. The specific MidSpan contracts and operating standards are not yet public in the reviewed record.

Sources:MID-007MID-009MID-010

Why control and buildout matter

A project can change materially between land acquisition, entitlement, financing, construction, lease-up, and operation.

PlacewardAnalysis

Developer, landowner, tenant, operator, and utility counterparty may be different entities

A credible case file should identify which entity is responsible for land, construction, financing, operation, environmental permits, utility service, taxes, and community commitments rather than treating “the project” as one undifferentiated actor.

Sources:MID-004MID-009MID-010

PlacewardAnalysis

Commitments should survive ownership or operator changes where appropriate

If community protections are important to approval, they are more durable when attached to land-use conditions, permits, recorded agreements, or other enforceable instruments rather than only to the identity or public statements of the current developer.

Sources:MID-005MID-007

What remains unresolved

  • ?Who is the intended data-center operator or tenant?
  • ?Is there a signed lease, offtake, development, capacity, or end-user agreement?
  • ?How many data-center buildings are proposed, at what square footage and IT load?
  • ?What is the phase sequence and expected construction timeline?
  • ?What is the total projected capital investment and permanent employment at each phase?
  • ?Which SDCL entity or affiliates will own, finance, construct, and operate the project infrastructure?
  • ?Could the site or project be sold before or after approvals, and what commitments would bind successors?
  • ?What happens if only part of the campus is built or the intended end user changes?

Evidence needed

Corporate / project structure chart
Property owner, developer, fund or financing vehicle, operator, tenant, utility counterparties, contractors, and responsible permit holders.
Phased master plan
Buildings, square footage, IT load, infrastructure, construction sequence, and target dates.
End-user documentation
Executed lease, development agreement, capacity reservation, or other binding document identifying the operator or customer when available.
Investment and jobs basis
Capital budget, construction workforce, permanent staffing model, employer identity, and phase timing.
Successor obligations
Recorded conditions, covenants, permits, or agreements that continue if ownership or operation changes.

What would change this assessment

The current assessment should move when stronger records, rulings, studies, or enforceable commitments materially change the evidence.

  • →Identification of a signed end user whose operating model materially clarifies power, water, generator, staffing, or buildout assumptions.
  • →A master plan showing a materially different campus scale than current high-level descriptions imply.
  • →A financing or ownership change that alters who is responsible for project commitments.
  • →Binding successor provisions that either strengthen or weaken confidence that community protections would survive a sale or lease.

Records to obtain

These are the highest-value documents to seek through public records, project disclosures, regulatory filings, or the court record.

Secretary-of-state / property records
Entity ownership, registered parties, deeds, mortgages, easements, and later transfers relevant to project control.
Development and lease documents
Non-confidential portions of agreements identifying roles, milestones, end users, or operating responsibility.
Master development schedule
Phase dates, building count, square footage, infrastructure sequence, and dependencies.
Commitment matrix
Each public promise matched to the entity responsible, legal instrument, duration, monitoring mechanism, and successor-binding provision.

How Placeward will verify it

  1. Name the responsible entity for each fact.Avoid attributing a contractor’s, tenant’s, developer’s, or utility’s statement to another participant.
  2. Track ownership and operator changes.Update the case file when land, project entities, financing vehicles, or end users change.
  3. Preserve superseded plans.Earlier buildout claims should remain traceable so later reductions, expansions, or substitutions are visible.
Project issue file

Continue the review

Return to the full issue index or inspect the underlying records in the evidence register.

All Project MidSpan issuesEvidence & Sources