Cottage Grove is growing. Between 2023 and 2025, the village issued building permits for 122 single-family homes and 195 multi-family units. The village has plans for new residents’ roads, utilities, and parks. The question of where they will gather indoors is less settled, and more pressing than it might appear.

The Village Knows the Gap Exists

In October 2025, the village submitted a letter to the Wisconsin Department of Administration’s Grants for Local Projects program in support of the police station project. The letter states that Cottage Grove, now nearing 10,000 residents, is one of the largest municipalities in Dane County without a community center, senior center, library, teen space, or dedicated third space. It acknowledges that the lack of accessible public spaces remains a significant barrier to achieving the village’s vision of a safe, connected, and vibrant community.

That is the village’s own characterization, in an official document submitted to the state. The village itself has acknowledged the gap.

What the Comprehensive Plan Says

The village’s comprehensive plan is the governing document that guides long-range growth and development. Chapter 7 revolves around Community Facilities and Utilities. Section E outlines goals, objectives, and policies. Goal 7 directs the village to work jointly with the Monona Grove School District to provide adequate recreational facilities. Goal 8 calls for using the Park and Open Space Plan to determine the location and size of future park facilities.

Indoor community gathering space does not appear anywhere in the document: no goal, no objective, no policy. Parks are a reasonable part of any community facilities plan, and they provide outdoor gathering space. Cottage Grove currently has no publicly operated indoor gathering space that residents can use year-round without reservation, rental fees, or program registration. Recreation programming through the village’s Parks and Recreation Department generally requires registration and associated fees.

What the CIP Says

The village’s 2026-2035 Capital Improvement Plan funds 12 projects over the next decade. Those projects cover a fire ladder truck replacement, a police station, road reconstructions, intersection improvements, bike path connections, a park shelter replacement, and a future EMS/Fire Station. There is no line item for a community center, a multipurpose gathering facility, or any publicly operated indoor space for residents. Fourteen additional projects are rated but unfunded. Community gathering space does not appear there either.

What Currently Fills the Gap

Cottage Grove has restaurants and bars. It has parks. Flynn Hall is available for rent. What the village does not have is a public library, a community center, a senior center, or a teen space.

The village’s Parks and Recreation Department found it necessary this summer to issue a public reminder that park shelters require advance reservations and are not available on a first-come, first-served basis. The incident that prompted the reminder, involving a group that refused to vacate a reserved shelter, was significant enough to generate a police response.

Bryn Mawr Presbyterian Church operates the village’s only food pantry, now serving nearly 600 people, as well as a community garden with some produce supplying the food pantry. These are not village services. They are provided by a private congregation whose continued presence depends on factors entirely outside the village’s control.

The Proposed Answer

The grant application points to the new police station as part of the village’s response to the community space gap. The proposed project includes a 150-person hybrid meeting room with access to outdoor green space and a kitchenette. The letter describes it as addressing a critical need.

Whether it fully addresses the need the village itself described (no community center, no library, no senior center, no teen space, in a community approaching 10,000 residents) is a question worth asking.

A Conversation the Community Has Already Had: Twice

This is not a new issue. Cottage Grove voters rejected a library referendum in the spring of 2025. A prior referendum on the same question also failed. In both cases, advocates made community space a central part of their argument. Those results reflect real community decisions, and this post is not an effort to re-litigate them.

The village’s 2024 Community Satisfaction Survey asked residents the maximum property tax increase they would support for services not currently provided. For a community center, 49% opposed any tax increase to fund one; for a library, 48%. Opposition was higher for a senior center (58%), an aquatics center (51%), and public transit (77%).

The Question

The village’s comprehensive plan makes no provision for indoor community gathering space beyond parks. The CIP has no line item for it. The village’s own grant application states that Cottage Grove is one of the largest municipalities in Dane County without a community center, senior center, library, teen space, or dedicated third space. The village’s Parks and Recreation Department recently reminded residents that shelters require reservations and are not first-come, first-served. A church provides services the village does not. A meeting room in a police station is the current answer on the table.

Cottage Grove is growing. How is this need going to be addressed?

Most days, children in the Westlawn neighborhood walk or bike to school without incident. The neighborhood was designed to support it. Sidewalks connect homes to paths, paths connect to streets, and the overall layout reflects the kind of walkable design that appears in the Village’s comprehensive, bicycle, and pedestrian plans.

But two streets in the neighborhood, Pheasant Run and Mourning Dove, stop short of connecting to each other. A narrow strip of land owned by the Town of Cottage Grove sits between them. The gap is approximately 100 feet.

Because Westlawn currently has only one vehicle inlet and outlet at Damascus Road, that gap has consequences beyond inconvenience. Drivers must route through surrounding streets and onto County Road BB (Cottage Grove Road), a road already under significant pressure during school arrival and dismissal hours. Emergency responders face the same detour. And the families who already use an informal footpath through that strip, because the connection is the obvious and direct route, are doing so without an ADA-accessible surface.

One Town board member visited the site during the morning school commute and counted seven children using the informal paths between 7:15 and 8:00 a.m. on a single morning.

The Village has not been inactive on this. The connection has been formally approved, with the Village agreeing to pay for and maintain it. Joint-use sidewalks were included in the most recent iteration of the plan. The proposal has gone to the Town twice. Both times, the Town board declined to move forward.

The public record from the Town board’s last discussion of this issue was on September 25, 2025 (link to meeting minutes). The primary concern raised was neighbor preference. Several adjacent residents contacted their board member to say they chose the neighborhood because of the dead-end, and three residents spoke in opposition at the meeting. A board member also raised questions about stormwater infrastructure and road widening costs, though those concerns applied most directly to a full road connection rather than the pedestrian path the Village was proposing. The board voted 4-1 to take no action. The dissenting member had attempted to broker a middle ground: approve one of the two path connections in exchange for the Village addressing a separate stormwater issue on Nightingale Lane. That motion did not receive a second.

That framing is worth noting. The choice before the board was not whether to fund or build anything. The Village had already agreed to cover costs and maintenance. The question was whether to allow a pedestrian connection on Town land, at no expense to Town taxpayers, in an area children are already crossing on foot every day.

Municipal boards weigh many factors, including jurisdiction, precedent, and long-term land use considerations. Those are legitimate areas of deliberation. But the current result is that a 100-foot strip of land is producing longer emergency response routes, additional traffic load on a county highway, and an informal path that no one designed and no one maintains. In the meantime, the gap remains. So do the children walking through it.

Dane County recently voted not to renew its contract with Flock Safety, the license plate reader company used by the Dane County Sheriff’s Office. The resolution’s author, Supervisor Chad Kemp, was direct about the reasoning: “Nothing about this action suggests that our deputies have misused this system. But the sheriff’s office has not been able to affirmatively confirm that the agencies it shares data with, or Flock itself, are not misusing the information collected by cameras in Dane County.” Board Chair Patrick Miles described Flock as “a proven bad actor” on Fourth Amendment grounds.

At the same time, the Village of Cottage Grove continues to expand its own Flock camera network. A village board member recently asked whether the village’s contract actually protects resident data. It is a good question, and the national record on Flock suggests it deserves a direct answer.

What Flock Is

Flock Safety manufactures and operates automated license plate reader cameras. The cameras capture every vehicle that passes, recording the plate, location, and timestamp. That data is stored in Flock’s system and, depending on how a contract is configured, can be shared with other law enforcement agencies, locally, statewide, or nationwide.

As of 2025, Flock operates in over 5,000 communities across 49 states and performs over 20 billion vehicle scans per month. It is not a small vendor. The company has raised nearly $1 billion in venture funding and is backed by Andreessen Horowitz. At least 221 Wisconsin law enforcement departments use Flock cameras or automated license plate readers.

The technology does produce results. Flock has documented contributions to stolen vehicle recovery and criminal investigations, and many agencies describe it as one of their most effective tools. That is real, and it is worth acknowledging. The argument here is not that those benefits are fictional. It is that they do not resolve the question of whether the contractual and architectural protections around resident data are adequate.

The False Comparison

A common response to privacy concerns about tools like Flock is some version of: you already share your data with Facebook, your phone tracks your location, so what is the difference?

The difference is architecture. Facebook and your cellphone carrier are not designed to give law enforcement agencies rapid, low-friction access to your data as a core feature of their product. Flock is. The entire value proposition of Flock’s nationwide network is that thousands of law enforcement agencies can query each other’s data with minimal friction. Getting data from Facebook or a carrier requires affirmative legal steps by law enforcement. While Flock’s system includes permissioning and audit controls, it is designed to make cross-agency querying operationally easy once that access is granted. That is not analogous to a private company holding your data. It functions as a form of surveillance infrastructure built specifically for government access.

What the National Record Shows

Flock’s stated position is that customers own their data and control who accesses it. The documented record is more complicated.

According to public reporting and audit records, including ACLU reporting on California agency access and local audit findings obtained through public records requests, agencies that configured their systems for local access only discovered that a vendor-side issue or system behavior had enabled nationwide queries beyond what agencies believed they had configured. In California, federal agencies including ICE and CBP accessed local Flock databases through a mechanism local departments did not authorize and, in some cases, did not know existed. One audit found over 364,000 unauthorized accesses of the Ventura County Sheriff’s database in roughly one month. San Francisco PD’s database was searched by out-of-state agencies over 1.6 million times in seven months.

A Texas officer used Flock’s national network to search for a woman suspected of having a self-administered abortion, entering “had an abortion, search for female” as the search reason. Flock initially characterized this as a welfare check. Subsequent public records requests revealed the investigation was a death inquiry and that the safety justification was added retroactively after press coverage.

These are not hypothetical risks. They are documented outcomes.

The Contract Is the Problem

Flock’s marketing says customers own 100% of their data. What the standard template contract actually grants is a broad license for Flock to process and share that data for law enforcement purposes, which may extend well beyond what residents assume based on interface settings. Restricting that requires affirmatively rewriting the contract language, something most small municipalities lack the legal resources to do or even know to ask for. While processing license language is common in software agreements, in this case it intersects with a product specifically designed for cross-agency data sharing, raising real questions about how far that sharing extends in practice.

In February 2026, Flock updated its Terms and Conditions. Independent legal analysis found the update made things worse for customers, not better. It introduced mandatory arbitration under Georgia law, stripped language that could have limited data monetization, and preserved Flock’s broad license rights while maintaining the “customers own the data” marketing language.

This is not a settings problem. The settings sit on top of a contract that may not protect residents regardless of what those settings say.

Privacy Is the Concern, Not Just Bad Actors

What makes Flock different from other law enforcement tools is not simply that misuse is possible. Every database system carries that risk. What distinguishes Flock is that it enables large-scale, cross-jurisdictional querying of historical movement data, something traditional law enforcement systems were not designed to do. A credentialed officer within the Flock network, depending on sharing configuration, can query the movements of a vehicle across thousands of jurisdictions without a warrant requirement built into the system itself. That is a structural privacy concern that exists independent of whether any individual officer behaves responsibly.

The documented misuse record is worth understanding in that context. A Milwaukee police officer used Flock to run his dating partner’s plate 124 times over a two-month period and the partner’s ex-boyfriend’s plate 55 additional times, listing “investigation” as the reason each time. The Braselton, Georgia police chief was arrested for using Flock cameras to stalk and harass multiple private citizens. The former police chief of Sedgwick, Kansas used Flock to track his ex-girlfriend’s vehicles 228 times over more than four months. In Wisconsin, the Wauwatosa Police Department conducted nearly 1,900 Flock searches in six months with the sole listed justification being “investigation.”

While these cases represent a small fraction of total usage, they illustrate the types of misuse that the system’s architecture makes possible at scale. Audit logs exist to catch misconduct after the fact, but the search reason field routinely shows entries like “investigation” or “susp.” At 450,000 searches per month across the national network, case-by-case oversight is not realistic.

What the Village Should Ask

The Village of Cottage Grove has its own Flock contract, separate from the county. Wisconsin has no specific statewide LPR statute, meaning guardrails are largely defined by contract terms and agency policy rather than uniform law. The February 2026 Terms and Conditions update did not improve that situation.

The question is not whether to use license plate reader technology. It is whether this vendor’s contract architecture provides the protections residents would reasonably expect. A few specific questions the village board should be able to answer: Does the village’s contract mirror Flock’s standard template, or was it negotiated to remove Flock’s broad license rights? What are the village’s current data retention and sharing settings, and who has authority to change them? Has the village conducted an audit of who has accessed its Flock data and under what stated justification?

If the village chooses to continue using Flock, the focus should be on tightening contract language around data sharing, limiting retention periods, and requiring independent auditability of access across the network.

In practice, local police departments treat their Flock usage policies carefully because they understand the political sensitivity. The village is not likely to casually change its data retention settings or sharing configuration. But as Supervisor Kemp noted at the county level, the issue is not whether local officers are trustworthy. It is whether anyone can affirmatively confirm that Flock and its network partners are not misusing the data. That protection should be anchored in enforceable contract terms, not rely primarily on institutional goodwill. Audit logs and internal policies provide some accountability, but they operate through after-the-fact review rather than enforceable limits on access.

Dane County’s decision not to renew is a reasonable moment for the village to ask these questions. The village board seated following the April 7 election is a reasonable body to ask them.

Disclosure: The author of this blog post voted to approve the village’s Flock contract while serving on the village board, and more recently voted as a Dane County Supervisor to end the county’s Flock contract. That experience with both decisions informs this post.

Tuesday’s election brought real engagement from Cottage Grove residents, and the results reflect that. Chris Stoa, Casey Erlandson, and JP Villavicencio will be seated on April 22, inheriting a full agenda: growth, infrastructure, public safety. None of those questions got resolved on April 7. They got assigned to a new set of hands.

The question worth asking now is what it takes for those hands to do the work well. Elections decide who governs. Process determines how well they govern.

Why local elections are worth paying attention to

Historically, April local elections see low turnout despite the outsized impact these positions have on daily life.

In most years, fewer than one in three registered voters in Cottage Grove participate in local April elections. Roads, public safety, parks, utilities, growth. The decisions that shape daily life are made by officials chosen by a fraction of the community. That’s a reason to stay engaged after election day, not just before it.

What a functioning board actually looks like

A well-functioning board is something worth describing, not just demanding. It starts with preparation. Trustees who read the staff reports, understand the agenda, and arrive ready to deliberate make better decisions and shorter meetings. That benefits everyone in the room, including residents who showed up to speak.

It continues with clarity of roles. Trustees set policy and direction; staff implement it. When that line holds, accountability is clean. When it blurs, things get murky fast.

And it depends on structure. Most municipal boards operate using a modified version of Robert’s Rules of Order, not to create rigidity, but to ensure fairness and efficiency. Process keeps meetings moving, ensures all voices are heard appropriately, and produces a clear public record of what was decided and why.

That last part matters more than it might seem.

At a recent Village Board meeting, a trustee moved to “table” an agenda item. The motion passed. The item disappeared from active consideration. And almost no one in the room noted that the wrong procedural tool had been used.

Under Robert’s Rules of Order, a motion to lay something on the table has a specific and limited purpose: to temporarily set aside an item so the board can handle something more urgent. It is not a method for postponing a decision. It is not a way to send something back to committee. Those outcomes each have their own motions: postpone to a date certain, refer to committee, postpone indefinitely. Each produces a cleaner, more auditable record of what the board actually decided and why.

The distinction matters because the minutes matter. A postponement sets a date. An indefinite postponement is a recorded decision to let something die. A motion to table leaves an item in procedural limbo. Each tells a different story. Residents reading those minutes deserve to know which story is actually being told.

What happened at that meeting is in the public record. The point isn’t to relitigate it. The point is that no one corrected it in the moment. Not the presiding officer – whether that’s the Village President at a board meeting, the President Pro Tem in their absence, or a chair running a committee – not the attorney serving as parliamentarian, not any other trustee at the table. That’s how procedural drift happens. Not through bad faith, but through a shared habit of treating process as background noise.

The good news is that drift is correctable. A board that takes process seriously from the start builds good habits quickly. The incoming trustees have an opportunity to set a higher standard, and the existing structure (staff, legal counsel, established rules) is there to support them.

What CG Forward is watching

We’ve written about what it takes to be a good trustee (https://cgforward.org/2026/04/01/what-good-trustee-judgment-looks-like/). The election resolved who holds the seats. What comes next is whether the board functions as a governing body.

CG Forward will keep covering Village Board meetings as the new board takes shape sharing what gets decided, how it gets decided, and why it matters for residents. The goal isn’t to find fault. It’s to make local government legible to the people it serves.

This is the last post before Tuesday. It feels like the right moment to say plainly what this blog is and what it is not.

CG Forward is not a campaign. It does not endorse candidates, accept donations, or tell anyone how to vote. It exists because local government decisions are made with real consequences for real people, and those decisions deserve more than rumors, reactions, and recycled talking points.

The goal has always been simple: document how the Village actually works and make that information clear and accessible. 

That means writing about levy limits and what they actually constrain. It means explaining the difference between operating expenses and capital investment. It means asking what a comprehensive plan is for and whether the board is actually using it. None of it is flashy. All of it matters. It is the work that determines whether this village is managed well or poorly over the next decade.

Local elections are easy to ignore. Turnout is low. The issues feel abstract until they are not. But the decisions made at that table shape what gets built, what gets maintained, and what gets deferred. They determine whether growth pays for itself or gets subsidized by existing residents. They set the terms for how this village manages the next decade. That is worth paying attention to.

What CG Forward stands for is the idea that voters deserve better than that. Not perfect government. Not government that never makes hard calls or unpopular decisions. But government that does the work, understands what it is deciding, and can explain its reasoning to the people it serves.

If you have been reading this blog through this election cycle, you have seen what that standard looks like in practice. You have seen what the Capital Improvement Plan says and what it does not. You have seen what levy limits allow and what they don’t. You have seen what questions a prepared trustee asks and what it looks like when someone is encountering a proposal for the first time at the dais.

CG Forward will keep writing after this election, whoever wins. The work does not stop on April 8. The scrutiny should not either.

Serving as a Village Board Trustee is not just about a title. It is about the work, the responsibility, and the commitment to a community that trusts you to make thoughtful, informed decisions on its behalf.

And at the most basic level, it requires time. Real time. Not just showing up to meetings, but putting in the hours beforehand to read materials, understand the issues, and come prepared. It is not unusual for this role to take 15 to 20 hours a week when done well. That is the baseline for being effective, not exceptional.

The job before the vote

Good trustees do their homework before the meeting, not during it. They read the packet. They follow up with staff. They arrive with questions already formed, which means the questions they ask in public are usually the second or third version: refined, specific, directed at the thing that actually matters.

A trustee who is encountering a proposal for the first time at the dais is not deliberating. They are reacting. Those are different things, and the quality of the decision usually reflects which one is happening.

Humility is not optional

No one person is an expert in everything that comes before a Village Board. Trustees are asked to weigh in on finance, public safety, infrastructure, development, utilities, and more. The only way to do that responsibly is to respect the people who do this work every day. Village staff and professional consultants bring years of experience and technical knowledge. They care about this community and take pride in their work. A good trustee listens, asks questions, and learns from that expertise rather than dismissing it.

What fiscal literacy actually looks like

Understanding municipal finance is not the same as having an opinion about spending. Fiscal literacy shows up in specific ways.

A trustee who understands levy limits does not promise to cut taxes without explaining what service or capital project absorbs the reduction. They know the levy is not a dial you turn. It is tied to net new construction and prior-year base, constrained by state law.

A trustee who understands capital planning distinguishes between operating expenses and capital investment. They do not treat a fire truck replacement as a budget indulgence. They understand deferred maintenance accumulates, and that the cheapest version of any infrastructure decision is usually the one made on schedule.

A trustee who understands debt does not treat low debt as the goal. They ask whether the debt serves a purpose, what the repayment structure looks like, and whether the underlying project was prioritized through a formal process. Debt is a tool. How it is used matters more than how much of it exists.

The difference between skepticism and obstruction

Healthy skepticism is an asset on any board. Asking hard questions, requesting data, wanting to understand second-order effects: these are signs of engagement, not resistance.

The behavioral difference worth watching: a skeptical trustee updates their position when the evidence warrants it. They can be persuaded by analysis. They distinguish between a project they dislike and a project that is actually flawed.

A trustee who votes no consistently regardless of the specifics is not being fiscally cautious. They are substituting a posture for a process. Those two things can look similar from the outside. Over time, they produce very different villages.

Maturity on a board shows up in the harder moments: when a vote goes the other way, when staff recommends something you opposed, when the data does not support the position you walked in with. A trustee who can accept those outcomes and keep working is doing the job. Maturity on a board is not about age. It is about whether a person can tell the difference between a decision they lost and a decision that was wrong.

What to listen for

When a candidate speaks, a few questions are worth holding in mind.

Do they cite specific documents, the Capital Improvement Plan (CIP), the utility plan, the comprehensive plan, or do they speak in generalities? Generalities are easy. The plan is public.

Do they describe tradeoffs, or do they only describe the downside of what they oppose? Every decision in municipal government involves a tradeoff. A candidate who never acknowledges that is either not reading the material or not being honest about what they find there.

Do they explain what they would do, or only what they would stop? Accountability runs in both directions. A trustee who defines their role as blocking things has made a choice about what governing means.

Judgment is visible if you know where to look

The record matters. Meeting minutes are public. Votes are recorded. Agendas and packets are posted. The strongest trustees are often visible long before they ever take a seat at the board table: they volunteer in schools, serve on local committees, and have built relationships rooted in trust. That kind of connection grounds decision making in real experience and keeps the focus where it belongs, on the people who call this place home.

Voters do not have to take anyone’s word for it. The evidence is there. The question is whether the people asking for your vote have been paying attention to it.

“Responsible growth” is a phrase that comes up often in local politics, and for good reason. It reflects something most residents genuinely share: a desire to grow thoughtfully, protect what makes Cottage Grove worth living in, and make decisions that hold up over time. But responsible growth requires an honest accounting of what saying no to development actually costs, not just what it avoids.

The Structural Reality

As we covered in our February piece on Wisconsin levy limits, the Village cannot simply raise property taxes to meet rising costs. What we can collect is tied directly to net new construction. If the tax base does not grow, our capacity to fund services does not meaningfully grow either.

That does not eliminate the need for disciplined spending decisions. It means that even well-managed budgets cannot keep pace with rising costs without some level of tax base growth. Growth is not just a political preference. Within Wisconsin’s levy limit structure, some level of tax base growth is necessary to keep pace with rising costs over time.

What’s Actually on the Docket

When people call for a committee to examine the Village’s debt and capital spending, it’s worth stepping back and looking at what we’re actually talking about. It is easy to call for less spending. It is harder to say less of what.

The Village’s current 2026-2035 Capital Improvement Plan funds 12 projects over the next decade. The highest-priority item, rated A+ by the full board, is the Ladder 1 replacement. Based on guidance from the Fire Department and the age of the truck, the board determined that deferring it would create greater long-term cost and operational risk. The Police Station, now underway, reflects a similar judgment: the department had outgrown its space, and the board settled on a $16 million project designed to serve the community for 15-20 years after careful deliberation on scope.

The remaining funded projects are road reconstructions, intersection safety improvements, bike path connections, a park shelter replacement, and a future EMS/Fire Station. These are not aspirational wish-list items. They represent the routine maintenance and infrastructure investment a functioning village has to sustain.

There are also 14 projects currently rated but unfunded, not scheduled, not prioritized, and unlikely to be completed in this planning window. Projects that many residents would consider legitimate needs remain on that list precisely because resources are constrained. Deferring funded projects would not eliminate their cost. It would shift it forward, often at a higher price and with greater service impact.

Taken together, the capital plan reflects a set of projects focused on core infrastructure and service needs, rather than discretionary expansion.

Tax Incremental Financing (TIF) Districts and the Timing of Growth

Because of Wisconsin’s TIF structure, the Village has less immediate flexibility than it might appear on paper. TIF temporarily redirects new tax revenue generated within a district back into that district’s development costs, rather than flowing directly into the general fund. In simple terms: some growth helps later, not immediately. TIF is a useful development tool, but it changes the timing of when growth benefits the general fund. You can see the Village’s active TIF districts here.

This makes new development outside TIF districts, and the eventual expiration of existing ones, especially important to the Village’s long-term fiscal position.

How Responsible Growth Actually Works

None of this means approving every project that comes forward. Each project gets evaluated on its merits. That is precisely why the Village has the tools it does: a comprehensive land use plan, a utility service plan, professional staff, expert consultants, and a full committee and commission structure.

Three recently considered developments illustrate what that evaluation looks like in practice:

*Approximately $630K of the annual impact supports Village services; the remaining ~$370K per year is available to reduce the tax burden on existing residents. Build-out estimated at six to ten years.

These figures reflect projected tax base contribution under the modeling assumptions used in the Village’s financial planning. Actual outcomes depend on build-out timing, service demand, and economic conditions, which is exactly why each project goes through a structured review process rather than a blanket approval.

What Happens When Growth Stalls

When development does not occur, whether residential, commercial, or redevelopment, the tax base does not expand. Costs, however, continue to rise. That gap has to go somewhere.

In practice, it shows up as deferred maintenance, stretched equipment replacement cycles, delayed infrastructure projects, and service levels that become harder to sustain. A stagnant tax base also means existing residents absorb a larger share of costs over time. Fixed obligations spread across a smaller base means higher per-household burden, with less flexibility to respond to new needs.

Not developing does not mean standing still. It means falling behind on infrastructure maintenance and service capacity, and catching up later is almost always more expensive than staying current.

The Honest Tradeoff

Responsible growth is not a choice between development and preservation. It is a choice between managing growth deliberately or absorbing the fiscal consequences of not doing so. Saying no has costs just as saying yes does. The difference is that the costs of inaction tend to be slower, less visible, and more expensive. Over time, they show up in road conditions, response times, and the per-household cost of maintaining the services residents expect.

The tools are in place. The plan is public. The tradeoffs are real.

Two ideas are circulating in this election that deserve a serious response. Not a dismissive one. An actual one.

So let’s take them seriously. Actually follow them all the way through.

“Growth Pays for Growth”

The instinct behind this phrase is sound. New development should not arrive as a free rider, leaving existing residents to absorb the costs of expanded roads, utilities, and services. That principle is correct. Good news: That’s already how Cottage Grove operates.

Development here contributes upfront, through utility fees, building permits, park fees, and impact fees tied to capital costs. It contributes annually through property taxes that fund public safety, schools, and debt service. The HeyDay development alone is projected to generate roughly $900,000 per year in property tax revenue, which we’ve broken down in detail here: https://cgforward.org/2026/03/17/growth-already-pays-for-growth/.

That doesn’t mean growth covers every cost in every year. No system does. But it does mean the Village already has an established framework that requires development to contribute materially to the infrastructure it uses.

So if that principle is already embedded in how the Village works, what is the slogan actually asking for?

That’s where things get complicated. Because “growth pays for growth” as a campaign position isn’t just a description of how fees work. It’s an argument for adding a new law enforcement impact fee on top of the existing framework. And that’s where the simple answer breaks down.

Courts require impact fees to be tied to a clearly measurable, proportionate benefit to new development. That’s straightforward for pipes and roads. It is far harder to demonstrate for staffing-driven facilities like police, where costs are driven as much by service expectations as by population. A well serves a measurable number of households at a measurable flow rate. A police facility’s size involves judgment calls about staffing levels, service standards, and growth projections, all of which are partially discretionary. That subjectivity doesn’t make the facility unnecessary. It makes the fee legally and methodologically fragile in ways that water and sewer fees are not. The detailed case against the law enforcement impact fee is here: https://cgforward.org/2026/02/27/the-cost-of-cottage-groves-new-impact-fees/.

There’s a deeper problem too. Wisconsin’s levy limit structure means that growth isn’t just a cost center. It’s one of the few mechanisms a village has to expand its fiscal capacity at all. When net new construction rises, the allowable levy increases. When it stalls, the ceiling drops, permanently. That’s not an argument for growth at any cost. It’s an acknowledgment of how Wisconsin’s levy structure actually works. A community that makes itself meaningfully more expensive to develop than its neighbors doesn’t just slow growth. It shrinks its own future revenue path. That dynamic is explained in full here: https://cgforward.org/2026/02/25/wisconsin-levy-limits-the-hidden-grow-or-shrink-rule/.

The slogan captures part of the picture. Growth does contribute. But it leaves out operating costs, levy dynamics, housing affordability, and regional competitiveness. Those aren’t footnotes. They’re the story.

“We Need a Debt Reduction Committee”

Again, the instinct is reasonable. Residents who want elected officials to take debt seriously are asking exactly the right thing. Municipal debt deserves scrutiny. It should be transparent, strategic, and aligned with long-term community goals.

But here’s the question worth asking before creating any new structure: what would this committee actually do that isn’t already being done?

Cottage Grove’s finances are audited annually by an independent CPA. The Village carries an AA credit rating from S&P Global, a designation that reflects sound financial management and strong capacity to meet obligations. The board already reviews debt as part of its budget process. The Village’s outstanding general obligation debt sits at roughly 47% of its legal statutory ceiling, placing it in the middle range of comparable Dane County communities. The full picture of how municipal debt works, and how it differs from personal or business debt, is here: https://cgforward.org/2026/03/07/debt-is-a-tool-why-comparing-village-debt-to-personal-debt-is-misleading/.

The real question isn’t whether we should have debt. It’s whether we are using it thoughtfully. Are we prioritizing the right projects? Are we aligning borrowing with long-term plans? Are we balancing today’s needs with tomorrow’s obligations? These are the discussions that already take place through the budget process, capital planning, and ongoing financial oversight.

A new committee would have no independent authority to reduce debt. It cannot set the levy. It cannot amend the budget. It cannot override board decisions. Any new structure should be evaluated not just on intent, but on whether it adds new decision-making value beyond what the current process already provides.

What’s missing isn’t another committee structure. It’s ensuring the existing tools are fully understood and effectively used by the people sitting at the board table. Those tools already exist: budget review, audit oversight, and public engagement.

What Both Ideas Share

“Growth pays for growth” and “We need a debt reduction committee” are not the same argument. But they share the same architecture: a real concern, attached to a proposed solution that doesn’t quite fit the problem.

That gap, between a legitimate worry and a workable answer, is where local governance actually happens. It’s the space that requires trustees to understand levy limits, capital planning, impact fee law, debt ratios, and service cost dynamics simultaneously. Not perfectly. But well enough to ask the right questions, recognize the tradeoffs, and make decisions that hold up over time.

Cottage Grove’s fiscal challenges are real. They deserve more than a bumper sticker and more than a new committee. They deserve people at the table who have done the reading.

It’s also worth saying what we’re actually working toward. Smart growth isn’t just about adding rooftops. It’s about what development actually brings to the community. A brew pub. A sports complex. A neighborhood where new residents want to put down roots. Growth, when done with intention, isn’t just expansion. It’s enrichment.

When you hear a simple answer to a complex problem, the right response isn’t skepticism of the answer. It’s curiosity about whether the person giving it understands the question.

At the December 1, 2025 Cottage Grove Village Board meeting, trustees discussed a proposed pre-annexation agreement related to the Neumann Homes development. The proposal involves a single-family residential subdivision being considered off Myer Road on the east side of the Village. You can watch the board meeting here: https://www.youtube.com/watch?v=I2QoWYzxvyQ.

Because there has been significant public reaction to that discussion (particularly to comments made by several trustees) it’s worth slowing the conversation down and clarifying what was said, what stage the process is in, and why some of the framing matters.

This post is not about whether the project should ultimately be approved. It is about how early-stage proposals are evaluated and how public statements by elected officials shape that evaluation.

What Was (and Was Not) Being Decided

The item before the Board was a pre-annexation agreement. This step does not:

• Annex land into the Village
• Approve zoning
• Approve a plat or site plan
• Authorize construction

Instead, a pre-annexation agreement acknowledges that a proposal is potentially consistent with the Village’s comp plan and allows the developer to proceed through the formal review process, which includes:

• A neighborhood meeting
• Traffic impact analysis
• Plan Commission hearings
• Zoning decisions
• Plat approval by the Village Board

Each of those steps includes additional public input and discretionary votes.

Statements from the Meeting Record

Several statements from the meeting are relevant to understanding the later discussion.

Earlier in the meeting (approximately 33:45), Trustee Severson stated: “I have no interest in this.”

Later, during discussion of the pre-annexation agreement (approximately 1:32:30), Trustee Severson raised concerns about:

• Developer conduct
• Whether the process was appropriate
• Whether the proposal was being rushed

Comments from Trustee Doll during the same discussion raise a related but distinct issue: expectations about when solutions must be fully resolved.

During the pre-annexation discussion, Trustee Doll expressed concern that significant questions remained unanswered and suggested hesitation in allowing the proposal to move forward without more complete resolution of issues such as infrastructure, impacts, and layout. The underlying position appeared to be that a proposal should present a near-complete or “right” solution before advancing.

That perspective is understandable. Wanting clarity before proceeding is a reasonable instinct, particularly when long-term consequences are involved. But at the same time, it highlights a tension inherent in the planning process:

• Pre-annexation is designed to determine whether a proposal is eligible to proceed, not whether it is final.
• Many of the details being raised are explicitly intended to be refined later through required steps such as traffic impact analysis, neighborhood meetings, Plan Commission review, zoning hearings, and plat approval.

Expecting a fully optimized solution at the outset effectively collapses multiple stages of review into one, which can unintentionally raise the bar beyond what the process itself requires. When that happens, early engagement (something often encouraged of developers) can be penalized rather than rewarded.

This distinction matters for public understanding. A proposal can be both:

• Incomplete, and
• Appropriate to advance to the next stage

Those are not contradictory positions under Wisconsin planning law or Village practice.

Why This Context Matters

It is entirely appropriate for a trustee to oppose a proposal on policy grounds. Trustees are elected to exercise judgment, and disagreement is a normal part of governance.

At the same time, it is helpful for residents to distinguish between two different types of objections:

1. Substantive opposition
   • “I do not support this development.”
   • “I don’t believe this is the right project or location.”
2. Procedural objections
   • “The process is flawed.”
   • “The developer is acting improperly.”
   • “This is being rushed or forced through.”

When a trustee states early in the meeting that they have no interest in a proposal, that provides important context for later procedural critiques. It does not invalidate those critiques, but it does help the public understand whether concerns are rooted in process deficiencies or in opposition to the project itself.

The Developer’s Role at This Stage

Based on the meeting record, the developer:

• Appeared before the Board earlier than required
• Engaged prior to filing a formal annexation petition
• Offered to fund and dedicate infrastructure at their own expense
• Described outreach to adjacent property owners
• Did not request zoning, plat approval, or annexation at this meeting

Residents may still oppose the project (and many clearly do) but the record reflects an early, discretionary review rather than a final or binding decision.

Why Process Framing Matters

Public trust depends on clarity about what stage a decision is in and what remains undecided. When early-stage discussions are framed as irreversible or procedurally improper, residents may reasonably believe that decisions are being made behind closed doors, even when the formal process has not yet begun.

Clear distinctions between policy disagreement and process critique help residents engage more effectively and hold officials accountable without misunderstanding the scope of what is actually before the Board.

Questions for the Community

Rather than arguing conclusions, this moment raises broader questions worth considering:

• How should trustees communicate opposition while still engaging in early-stage review?
• What level of detail should be expected at pre-annexation versus later stages?
• How can residents better track where discretion exists (and where it does not) in the development process?

These questions matter regardless of where one stands on this specific proposal.