What happens to your city tax bill when the city you live in loses a lawsuit it saw coming and passed anyway?
That is the question sitting underneath every headline about the data center fight on Carmen Avenue East. For most of the past six months, the story has been told as a fight between neighbors and a developer. It is really a story about a filing date, a state statute, and a city council that voted to protect residents from a data center and may end up billing those same residents for the privilege.
The number the city put on its own decision
In early August, Inver Grove Heights city leaders got a figure from their own attorneys that reframed the entire debate: if the city loses its legal fight with the data center developer QLevr, the loss could cost the city roughly $20 million. Mayor Brenda Dietrich translated that into household terms at the same meeting, noting that a typical resident's city taxes would climb from $1,833 to $3,053, an annual increase of about 67 percent, according to KSTP's reporting on the meeting.
That is not a hypothetical fine buried in a legal filing. It is the same city council that spent June fighting to keep the data center out now weighing whether keeping the fight alive is worth nearly doubling a household's city tax line.
Why the ban itself became the exposure
Here is the part that most coverage has glossed over: the moratorium is not risky because it blocks a data center. Cities pass data center moratoriums regularly while they study zoning and infrastructure questions. This one is risky because of when QLevr applied relative to when the ban took effect.
QLevr submitted its site application for a 54,000-square-foot data center at the former Travel Tags building on Carmen Avenue East, near Fleming Field Airport, on March 3, 2026. Under Minnesota Statute 15.99, once a completed application is filed, the city has 60 days to act, extendable to 120 days, after which only the applicant can grant more time. Miss that window without an extension and the project is automatically approved by default.
The city didn't start considering a moratorium until May 11, more than two months after QLevr's clock had already started running. QLevr's attorneys have argued in writing that state law protects an application filed before a ban exists, and that any decision on their project based on anything other than the zoning code already on the books exposes the city to what a law firm representing QLevr called damages that "may exceed $150 million." The moratorium wasn't a preemptive study period. It was a ban written around one specific, already-pending application, which is precisely the kind of targeted government action that tends to lose in court.
How six weeks became a legal liability
The timeline matters because it shows how little room the council actually had to maneuver once QLevr's application clock started.
| Date | What happened |
|---|---|
| March 3, 2026 | QLevr files its site application for the Carmen Avenue East data center |
| March 26, 2026 | QLevr holds a public neighborhood meeting on the project |
| May 11, 2026 | Council initiates a moratorium on data center development, covering QLevr's pending application |
| May 27, 2026 | Council delays a vote after QLevr's law firm threatens litigation |
| June 8, 2026 | Second reading of the moratorium passes 3-2 |
| June 22, 2026 | Meeting recesses for a closed legal session; vote pushed to June 26 |
| June 26, 2026 | Council passes the one-year moratorium 3-2 at an 8 a.m. session, including QLevr's project |
| Early August 2026 | City staff put a $20 million price tag on losing the resulting lawsuit; council moves to exclude QLevr from the ban |
Two more ordinance readings still stand between that August move and a final resolution. Nothing here is settled yet, which is exactly the point: a decision made in six weeks under legal threat is now being unwound just as carefully, one reading at a time.
What residents were actually asking the council to weigh
The organized opposition wasn't vague anxiety about a corporate neighbor. Residents circulated an Environmental Assessment Worksheet petition, which under state rules requires only 100 signatures to force a 30-day environmental review. They collected more than 700, a sevenfold margin over the threshold, and the petition landed on the city's desk the Thursday afternoon before the rescheduled Friday morning vote.
The specific concerns residents raised at council meetings tracked closely with what QLevr's own filings describe:
- Power draw: the facility is expected to use about 5 megawatts of electricity, an amount Xcel Energy has said would run on a dedicated line built and paid for by QLevr rather than drawn off the existing residential grid.
- Water use: QLevr says its closed-loop cooling system would use roughly the same amount of water as one to two single-family homes, a claim residents pressed the company to substantiate at multiple meetings.
- Noise and proximity: several residents live directly behind the proposed site near the airport industrial corridor, and city attorneys said they had separately negotiated noise reduction commitments and additional landscape buffers with QLevr as part of the process.
One resident, Heather Thornton, told the council during the August discussion that the extra readings gave the community more room to weigh in, saying the process of "sharing our input is one of the most important things that we've learned" about how the city works together this year.
The reversal no one is calling a retreat
By early August, the calculation had shifted from "should this data center be built" to "can the city afford to keep fighting about it." A city attorney told the council that QLevr's lawsuit would be dropped entirely if the city simply excluded QLevr's already-pending application from the moratorium, leaving the year-long ban in place for any future data center proposals but letting this one proceed under the zoning rules that existed when it was filed.
The council voted to move in that direction, but the ordinance still needs two more readings before it is final. That is not a small technicality. Under city code, an ordinance can be amended at any reading, and the version that matters legally is whichever one passes at the third and final reading. Anyone who has been following this assuming the moratorium fight is over is working from outdated information.
What to watch if you live here
If the council finalizes the carve-out, the practical outcome is narrower than either side's rhetoric suggested back in June: QLevr's specific project proceeds under existing zoning, while the broader one-year moratorium stays in place for any other company that might want to build a data center in Inver Grove Heights before the city finishes studying the issue. If the council instead holds the line and keeps QLevr inside the ban, the $20 million exposure the city's own attorneys described becomes the number to watch, not the data center itself.
Either way, the mechanism that got the city here is worth remembering the next time a moratorium debate comes up in this corner of Dakota County. A ban written to stop one specific, already-filed application is legally different from a ban written to pause an entire category of development while a city studies the question. Inver Grove Heights found that difference the hard way, and the bill, whether it lands on the data center or on the tax rolls, is still being written.
If you're weighing what any of this means for a property near the Carmen Avenue corridor or elsewhere in Inver Grove Heights, or you simply want a second set of eyes on how local development news like this tends to play out over time, Sally English is glad to talk it through. Let's Connect.
