What the Council can still do
Many residents have concluded that reversing the data-center zoning is not realistic. That is a reasonable read of the law. But it is not the end of the options. The avenue that remains open — and that is squarely within the Council’s authority — is to govern how the use is built and operated: noise, setbacks, buffering, screening, independent studies, and the utility/development agreement. This page lays out the specific, lawful measures and the public sources behind each.
Why “reverse the zoning” keeps hitting a wall — and where the real opening is
City Hall has told residents the zoning can’t be changed unless the property owner requests it, and that the city could be sued if it acts. That is not a brush-off — it is grounded in Texas law, and it points to where the effort should actually go.
- Vested rights — Tex. Loc. Gov’t Code §245.002. When a developer files a qualifying application, the city must judge it “solely on the basis of… requirements in effect at the time” the first application in the series was filed (§245.002(a)–(a-1)), and that freeze runs across every later permit in the series — site plan, plat, building permit (§245.002(b)). The data-center use was approved on the Elevon parcels in 2022 and the hyperscale standards were added in 2024, so an ordinance that now removes the use can be challenged as a vested-rights violation.
- Takings risk — Mayhew v. Town of Sunnyvale, 964 S.W.2d 922 (Tex. 1998). Stripping an already-approved use can also be tested as a regulatory taking. The court upheld a down-zoning there but left the door open the other way on different facts — enough that a city’s attorneys will counsel caution.
- The annexation lever cuts the same way. If the city pushes the landowner out, the land can shift to unincorporated Collin County, which has no zoning authority at all — the Commissioners Court cannot block development by zoning. That would be worse for residents, not better.
Tomorrow’s agenda (June 16) — how to use what’s actually on it
Source: City of Lavon, June 16, 2026 Regular Meeting Agenda (posted June 10, 2026).
| Item 4 — Citizens Comments | Three minutes per person. You do not need the topic to appear elsewhere on the agenda. This is the venue for the asks below. A podium-ready script is at the bottom of this page. |
|---|---|
| Item 6.A — data-center meeting | “Discussion and action regarding a meeting to discuss potential data center use in the City.” This schedules a future meeting. Ask that it be a real, noticed working session on enforceable standards — with a public hearing and draft ordinance language — not just another open-ended discussion. |
| Item 6.D — a landscape-plan condition, on this corridor | The Council is clarifying a conditional approval of a commercial project’s landscape plan at 1030 S. SH 78 (the SH 78 / SH 205 intersection). This is proof, on tomorrow’s agenda, that the city already conditions development here. Point to it: apply that same discretion — screening, buffering, landscaping, equipment enclosure — to the data-center site plan. |
| Item 6.I — citizen-comment procedures | The Council is considering changes to how citizen comments work. Attend and watch this; protect the three-minute comment right. |
| Items 5.C / 5.D — North Wastewater Treatment Plant | City wastewater infrastructure at 360 Elevon Parkway is being built and accepted by the city. That matters: the city controls water and wastewater service — a real leverage point (see avenue 5). |
The concrete avenues
1. A real noise ordinance — the city already started this
On May 28, 2026, the City Manager wrote to a resident that “staff will begin research regarding the request for an amendment to the regulations regarding noise.” As of the June 16 agenda, no noise amendment is yet scheduled for a vote. Ask the Council to direct staff to bring a draft to a vote on a date certain. A resident’s May 24 written request already proposed the targets: 55 dBA daytime / 45 dBA nighttime at residential property lines, plus low-frequency (dBC) limits for cooling-system hum, plus independent pre- and post-construction noise studies.
Peer models to cite. Chandler, AZ (Ordinance No. 5033) pins enforcement to a measured pre-construction baseline — post-construction noise may not exceed it — with annual monitoring for five years and a generator-testing protocol. Prince William County, VA removed its nighttime HVAC exemption specifically to reach data-center cooling and is adding dBC/octave-band limits. Plano, TX already caps residential nighttime at 55 dBA — so 55/45 is in line with a Texas peer.
2. Setbacks, buffering, and screening
Ask the Council to strengthen the development standards for the use (legally distinct from removing it): larger setbacks from homes, dense landscaped buffers, opaque screening walls, and full enclosure of cooling and generator equipment. Fairfax County, VA (Sept. 2024) requires data-center buildings to sit at least 200 ft from a residential lot line, ground equipment and generators at least 300 ft, and full enclosure of cooling/ventilation/power equipment — a concrete model to point at.
What’s already in the code to build on. Lavon’s 2024 amendment (Ord. 2024-12-01) already sets dimensional limits on this use: a maximum building height of 85 feet — but only toward the interior of the site. Within the first 50 feet adjacent to single-family residential, the height steps down to 30 feet, alongside a 25/100-ft setback pattern and a 15-ft landscape buffer. So homes at the boundary are not facing an 85-ft wall at the property line. That existing step-down is the floor to build from: a city that already sets a height cap, a residential step-down, setbacks, and a buffer can be asked to strengthen the buffer, screening, and equipment enclosure further. (Source: City of Lavon Ord. 2024-12-01; see the Record page, dimensional standards.)
3. Independent pre- and post-construction studies
Require, as a condition of site-plan approval and before any certificate of occupancy or use permit: an applicant-funded, independent noise study (and, where relevant, water-use, traffic, and air-quality studies), with results made public. Fairfax requires the pre-construction study before site-plan approval and the post-construction study before the use permit issues.
4. Site-plan, landscape, and permitting conditions
Item 6.D tomorrow shows the city conditioning a commercial landscape plan on this corridor — the discretion exists and is used routinely. Permits in the vested series that the developer has not yet filed remain subject to the city’s current standards; site-plan and landscape review is where the city attaches conditions on screening, lighting (shielded/dark-sky fixtures), generator placement, and equipment enclosure. Ask the Council and Planning & Zoning to apply the full set of existing standards to the data-center site plan — strictly, on the record, condition by condition.
5. The utility / development agreement — often the strongest lever
A hyperscale data center needs an enormous amount of water (for cooling) and power, and the city controls water and wastewater connections and the development agreement. Ask that any city-provided utility capacity or service be conditioned in the development agreement on the noise, setback, screening, study, and operational standards above. A development agreement is negotiated and contractual — it is not blocked by the vested-rights or zoning wall, and it is where real, enforceable commitments get written. (The Elevon “Amended and Restated Development Agreement” has already appeared on council agendas — it is an active document.)
6. Operational and environmental conditions
Backup-generator testing-hour limits and emissions controls (diesel generators are an air-quality issue); construction-hour limits; truck-route and traffic-impact conditions; and public water-use reporting. Chandler, AZ mandates a generator routine-maintenance/testing protocol and five years of monitoring as part of its data-center ordinance.
A three-minute Citizens-Comment script you can adapt
“We understand reversing the zoning isn’t realistic — the use is vested. So we’re asking you to do what you can do, and what you already do for every other project on this corridor: govern the standards. Specifically: (1) bring the noise ordinance staff has been researching since May to a vote on a date certain — 55 day / 45 night with low-frequency limits and independent pre- and post-construction studies; (2) prepare a development-standards amendment strengthening setbacks, buffering, screening, and equipment enclosure; (3) apply every existing site-plan and landscape condition to the data-center plan, the same way you’re conditioning the landscape plan in Item 6.D tonight; (4) condition city water and wastewater service on those standards through the development agreement; and (5) make the future meeting in Item 6.A a real public working session on enforceable standards, with a hearing and draft language. None of this removes the use. All of it is within your authority.”
Adaptable Citizens-Comment statement, June 16, 2026
Confirm directly before relying on any single figure
- City of Lavon Planning Department: the exact setback, height, and building-size figures in the 2024 hyperscale ordinance; and whether any data-center site-plan or permit application has been filed (that determines what is vested versus still subject to current standards).
- The June 16 agenda packet for the backup documents behind Items 6.A and 6.D.
Primary sources
- City of Lavon — Council agendas & minutes archive; June 16, 2026 agenda.
- Tex. Loc. Gov’t Code §245.002 (vested rights) — statute.
- Mayhew v. Town of Sunnyvale, 964 S.W.2d 922 (Tex. 1998).
- Fairfax County, VA — 2024 data-center zoning amendment (county release).
- Chandler, AZ — Data Center Ordinance No. 5033.
- Prince William County, VA — Code Ch. 14 (Noise) and the March 2025 noise-ordinance update presentation.
- Plano, TX — Code of Ordinances, Ch. 14, Art. V (Noise).