The Village can (and is positioning to) approve it without a Comprehensive Plan Amendment (CPA) and without triggering any state coordinated review. It’s going the pure local route—pre-application → staff review → Planning, Zoning & Appeals Board (PZAB) hearing → Village Council approval via major site plan / development order (the Village’s version of a PUD/PD process). No state clock starts.

Why no CPA is needed here (and why that matters)

• Existing land use & zoning already allow it: The parcel is in the Light Industrial Future Land Use designation under the Village’s Comprehensive Plan, and the zoning district allows heavy industrial development. Data processing centers / digital infrastructure facilities are consistent with that (they’re treated like manufacturing/storage/warehousing uses).
• Village staff has confirmed this in public records and recent Council discussions—no large-scale CPA or FLU map amendment is required for Silver Fox 606 itself. (They did just do a separate large-scale CPA for 5,722 acres of FPL land nearby to change it to Light Industrial, but that was a different project.)
• Because the proposal is consistent with the adopted Comprehensive Plan, the Village can handle everything locally under its Land Development Regulations (no cross-reference to s. 163.3184(4) or s. 380.06 DRI thresholds kicks in).

Exact process timeline for Silver Fox 606 (Village of Indiantown)

This matches the “no-CPA” path we talked about earlier, but tailored to Indiantown’s code:

1. Pre-application (already done)
   • Silver Fox 606 LLC held a pre-app meeting with Village Community & Economic Development staff as early as May 2025.
   • Still in the “pending site plan submission” stage as of the January 2026 Council agenda packet. No formal application filed yet.
2. Staff review / completeness
   • Once the full major site plan package is submitted (plans, traffic study, environmental info, etc.), staff reviews it internally. No state involvement.
3. PZAB public hearing (first hearing)
   • Scheduled for PZAB (the Village’s Local Planning Agency). This is advisory/recommendation only.
   • Public notice required; this is where residents can speak.
4. Village Council final hearing(s) & approval
   • After PZAB recommendation, it goes to the Village Council for final approval of the site plan / development order.
   • Council can approve it as a Planned Development (PD) overlay or straight major site plan—either way, it’s a local development order.
   • No transmittal to FloridaCommerce, no 30-day agency comments, no ORC report, no 45-day NOI. Zero state coordinated review.
5. Post-approval
   • Then building permits, concurrency checks, etc.—all still local.

Contrast: What would have triggered state review?

If the current FLU had been Agricultural or Conservation (or if the intensity/density didn’t match), they would have needed a large-scale CPA first. That CPA would have triggered the full state coordinated review process we outlined at the very beginning (10-day transmittal after Council’s first hearing, 60-day ORC, etc.). But because everything lines up already, they skip that entirely.

Current status (as of late March 2026): Still very early—pre-app only, under staff review. No hearings have been noticed yet on the public agendas, but the project is moving forward on the local-only track. Public comments at the February 2026 Council meeting already referenced it, so residents are aware.

This is textbook “approve without CPA using the local PUD/site-plan equivalent.” It’s why developers love parcels that are already zoned and planned for industrial uses—it saves 6–12+ months and avoids state-level objections.

Since the project is consistent with the existing Light Industrial future land use and zoning, it stays on the local-only approval track we discussed (major site plan / development order through PZAB and Village Council—no CPA, no state coordinated review under s. 163.3184(4)). That means the Village evaluates all these impacts directly through its Land Development Regulations, SFWMD permits, and required studies (traffic impact analysis, environmental assessments, etc.).

Here’s a clear breakdown of the known and potential impacts based on public records, news reporting on the pre-application/site-plan materials, and resident concerns as of late March 2026. The project is still very early (pre-app complete, site plans under staff review; no public hearings noticed yet).

1. Environmental / Wetlands / Wildlife Impacts (Biggest Flashpoint)

• Wetlands: Roughly 230 acres (about 40% of the 606-acre site) are wetlands. The proposal would directly impact/build on a significant portion of them. The developer plans two man-made lakes (likely for stormwater management and possibly cooling water).
• Protected Species: Site surveys (shared with South Florida Water Management District) documented:
  • Wood storks
  • Sandhill cranes
  • Gopher tortoises
  • A bald eagle nest
• Experts have flagged this as part of a broader pattern where large data centers in Florida are becoming a “new threat to wildlife” because of the scale of land conversion in rural/agricultural areas.
• Mitigation: The Village/SFWMD will require wetland permitting, mitigation banking or on-site preservation, and species relocation/protection plans before approval. No state-level DRI review applies here, so it’s handled locally + SFWMD.

2. Water & Energy Use (Resident #1 Concern)

• Water: Data centers (especially AI/high-density ones) are extremely water-intensive for cooling. Indiantown’s agricultural/rural setting already relies heavily on the same aquifer. The two planned lakes would help manage on-site stormwater and possibly supply some cooling, but public comments highlight fears of large-scale groundwater withdrawal or increased demand on the local system. Exact gallons-per-day figures aren’t public yet (still in staff review), but this is the top worry expressed by residents at recent Village Council meetings.
• Energy/Power: Massive draw expected. The site is adjacent to FPL infrastructure (230 kV transmission line + 13 kV distribution), and the plans include an on-site FPL substation. The developer is covering the full cost of the substation and any upgrades—no taxpayer concessions requested. Broader Florida data-center debates include risks of higher electric rates or grid strain, but this site’s proximity to power plants is marketed as a plus.

3. Economic / Jobs Impacts (The Upside)

• Jobs: Developer projections show ~400 permanent jobs once fully operational (plus construction-phase employment). Phased build-out: Phase 1 = main data center; Phases 2–3 add four additional two-story buildings (total ~2.2 million sq ft across an AI lab + data halls). Target operational start: as early as June 2027.
• Tax Base / Revenue: Heavy industrial use on 606 acres would significantly boost the Village’s property-tax and non-ad valorem revenue. No special incentives or tax breaks appear to have been requested.
• Regional Context: Positioned as potentially “Florida’s first AI data center” on the Treasure Coast—bringing high-tech infrastructure to a historically agricultural area.

4. Community / Quality-of-Life Impacts

• Rural Character: Residents are vocal about losing the “small-town, rural feel” of Indiantown. The 50-ft-tall buildings and industrial-scale campus on previously vacant land would visibly change the landscape.
• Light / Noise Pollution: Community Facebook groups and meetings have raised concerns about 24/7 operations, security lighting, and generator noise (common at data centers).
• Traffic: A full Traffic Impact Analysis is required as part of the major site plan. Silver Fox Lane / surrounding roads (SR 76, etc.) would see increased truck/construction traffic during build-out.
• Other: No major concessions asked from the Village, which some see as positive (no giveaways), while others worry about long-term strain without broader infrastructure upgrades.

Current Status & Next Steps (as of March 29, 2026)

• Still pre-hearing. Site plans are with Village staff for completeness review.
• Once ready: PZAB public hearing (recommendation) → Village Council final hearings → approval/denial as a local development order.
• Public can speak at both hearings; written comments also accepted. Wetlands/species issues will be the main focus of any opposition.

Bottom line: Because it fits the existing comprehensive plan, the Village has full local control to approve, condition, or deny based on these impacts—no automatic state override. The trade-off is classic: economic boost + jobs vs. environmental footprint and rural-character loss in a place that’s stayed mostly agricultural.

A Village Council member can absolutely vote against the Silver Fox 606 major site plan (or vote to approve it only with conditions) if they have a reasoned belief, based on evidence in the public record, that the Land Development Regulations (LDRs) do not adequately address or mitigate the project’s scale.

Here’s exactly how that works in Indiantown for this project:

1. This is a major site plan (a development order), not a rezoning or CPA

• Because the 606-acre parcel is already zoned Light Industrial and consistent with the Future Land Use designation, the approval is handled entirely under the Village’s LDRs (Chapter 12, Article 12 – Development Review and Procedures, adopted 2020).
• The process: Staff review → PZAB public hearing (recommendation only) → Village Council final hearing and vote.
• The Council’s decision is quasi-judicial, meaning each member must vote based on the evidence presented at the hearing(s) and the specific approval criteria in the LDRs — not personal opinion or popularity.

2. The exact LDR approval criteria that give Council members discretion on “scale”

From Indiantown’s Land Development Regulations (Sec. 12-8 and related sections), the Village Council shall consider these factors when deciding to approve, approve with conditions, or deny a major site plan:

• The development conforms to the Comprehensive Plan and serves a public benefit warranting approval at the time it is considered.
• The development will have a favorable impact on the environmental and natural resources of the Village, including:
  • Means and estimated cost to minimize adverse impacts.
  • Whether alternatives could reduce impacts.
  • Whether any irreversible or irretrievable commitment of natural resources will occur.
• Compatibility with surrounding uses, traffic, public facilities, and infrastructure.
• No undue burden on roads, water/sewer, drainage, etc.

If a Council member can point to competent substantial evidence in the record (e.g., the applicant’s own traffic study, wetland delineation, water-use projections, or expert testimony from residents/engineers) showing that the scale (2+ million sq ft, 606 acres, significant wetlands conversion, high water/energy demand) creates impacts the current LDRs do not fully address or mitigate, they have a lawful basis to vote “no” or to require additional conditions/mitigation.

3. Practical reality for Silver Fox 606

• The project is still in the pre-hearing / pending major site plan stage (as of the latest Village Council agenda packets in early 2026). No public hearing has been scheduled yet.
• At the hearing, the applicant must prove compliance with the criteria above. Opponents (residents, experts) can present contrary evidence on scale-related issues (wetlands loss, water draw, traffic, rural character).
• A Council member who believes the code’s standards are insufficient for a project of this magnitude can vote against it if they tie that belief to the evidence and the LDR criteria — exactly as the law and Village code require.

4. Important limits (Florida law protects against arbitrary denials)

• The vote cannot be based on whim, politics, or “I just don’t like data centers.” It must be supported by facts in the record.
• If denied without such evidence, the developer could challenge the decision in circuit court (via certiorari review or consistency suit under § 163.3215, F.S.), and the denial could be overturned.
• However, courts give the local government deference when the record contains conflicting evidence — so a well-documented “no” vote based on scale/impact concerns is very defensible.

Bottom line: Yes, any Council member can vote against Silver Fox 606 if they conclude — on the basis of evidence presented — that the project’s scale exceeds what the existing LDRs can reasonably handle without unacceptable impacts. That is precisely why the public hearings exist.

Should all that fail and the thing is approved then we go here

As “aggrieved or adversely affected” residents of Indiantown (or anyone with standing under Florida law), you have clear legal avenues to ask the courts (and, in limited ways, state agencies) to temporarily halt Silver Fox 606 construction.

However, because this is a local-only major site plan (no CPA, no DRI/state coordinated review), the main “halt” power is not automatic and does not kick in during pre-application or PZAB review. It opens after the Village Council issues the final development order. Here is the exact timeline and the legal “cause” you would need, based on current Florida Statutes and Indiantown’s Land Development Regulations (as of March 29, 2026).

1. During the Local Approval Process (You Can Influence — But Not Halt)

• PZAB public hearing (recommendation only) and Village Council final hearings (usually two readings): These are your first and best chance to be heard. You (or experts you bring) can submit sworn testimony, studies, photos, etc., showing the project’s scale exceeds what the Comprehensive Plan or LDRs can handle (wetlands, species, water, traffic, etc.).
• The Council can deny or condition the approval at this stage if the evidence shows it fails the LDR criteria we discussed earlier.
• No court or state “temporary halt” is available yet — the project is still just a pending application.
• When this happens: Still pre-hearing as of today. Monitor the Village website and agendas (indiantownfl.gov) — the first PZAB hearing is expected soon based on March news reports.

2. After Village Council Approval — Court Temporary Injunction (Your Main Tool)

This is the point where citizens routinely ask courts to temporarily stop a project.

• Exact trigger: Within 30 days after the Village Council renders (issues in writing) the final major site plan approval (the “development order”).
• Legal vehicle: Florida Statute § 163.3215(3) — “Standing to enforce local comprehensive plans through development orders.”
  • Any “aggrieved or adversely affected party” (residents, property owners nearby, businesses, environmental groups, etc.) can file a de novo lawsuit in Martin County Circuit Court.
  • You ask for declaratory relief, injunctive relief, or other relief to prevent the Village from taking any further action on the development order.
  • You can (and should) simultaneously file an emergency motion for temporary injunction (Florida Rule of Civil Procedure 1.610) to halt construction while the case is pending.
• What “cause” (legal grounds) you need to win a temporary halt: The judge will require you to prove all four classic injunction elements (courts grant these sparingly):
  1. Likelihood of success on the merits — Strong evidence that the approval materially alters the use/density/intensity on the 606 acres in a way that is inconsistent with Indiantown’s Comprehensive Plan (Future Land Use Element, Conservation Element, etc.) or the LDRs (e.g., inadequate mitigation for 200+ acres of wetlands, protected species impacts, water-use conflicts).
  2. Irreparable harm — Construction would cause permanent or hard-to-reverse damage (e.g., filling wetlands, harming wood storks / gopher tortoises / bald eagle nest, aquifer drawdown) that money damages cannot fix.
  3. No adequate remedy at law — Once bulldozers start, you can’t “un-build” the damage.
  4. Public interest — Halting the project serves the public (protecting rural character, environment) more than letting it proceed.
  Courts give local governments some deference, but if your evidence is strong (expert reports, photos, SFWMD data already on file), judges do grant temporary injunctions in these cases.
• Cost / Practical note: You’ll likely need a lawyer (or a group that can fund one). Attorney fees can sometimes be recovered if you win.

3. State-Level Temporary Halt (Separate but Powerful)

Even if the local site plan is approved, the developer still needs state/federal permits:

• SFWMD Environmental Resource Permit (ERP) and Water Use Permit (for the wetlands, lakes, and massive cooling water demand).
• DEP permits if any sovereign submerged lands or other state resources are involved.
• U.S. Army Corps (federal wetlands).

When you can act: Once the developer applies for these permits (usually right after or during site-plan approval), you can:

• File a formal administrative challenge to the SFWMD/DEP (hearing before an administrative law judge).
• If denied or conditioned, the project stops until resolved.
• Or join a court challenge seeking to enjoin the permits.

Cause needed: The permits would cause unlawful environmental harm (violating state water quality standards, species protection rules, etc.). The wetlands/species data already in the public record (from your March 2026 news coverage) gives you a head start.

Bottom Line for Silver Fox 606 Right Now (March 29, 2026)

• Nothing is approved yet → your immediate power is public comment at the upcoming PZAB and Council hearings.
• The court window for a temporary injunction opens within 30 days after Council approval.
• State permit challenges become available as soon as SFWMD/DEP applications are filed.

If you want to be ready, start documenting evidence now — compile the wetlands maps, species surveys, traffic/water studies, and any inconsistencies with Indiantown’s Comprehensive Plan. That record is what a judge will look at when you ask for the halt.