Matthew McSheehy, Greenfield Councilmember

Directions Website

Matthew McSheehy, Greenfield Councilmember I am a father, a husband, and yes, also a Greenfield, Minnesota City Council Member.
They do not reflect opinions of the city or council.

These are my own views, shaped by a belief that public service means standing up for those without a voice. What do I want to do while in office:
Reduce the tax burden for the residents without compromising the rural nature of Greenfield.
Help those who wish to build commerce in our city achieve their goals.
Achieve fairness in governance.
Leave Greenfield a better place than it was when I took office.

How do I measure success:
“Did I base my decisions on facts, fairness, and the long-term good of the city?”
“Did I listen honestly, even when I ultimately disagreed?”
“Did I communicate my reasoning as clearly as I can?”

What will I try to keep in mind: The absence of praise ≠ absence of support.

GREENFIELD CITY COUNCIL RECAP — OCTOBER 20, 2026Tuesday night had two meetings: a work session on how city staff pay is ...
10/22/2026

GREENFIELD CITY COUNCIL RECAP — OCTOBER 20, 2026

Tuesday night had two meetings: a work session on how city staff pay is set, then the regular council meeting. Here's what matters for residents.

THE SHORT VERSION
• Staff pay study: An independent study by Abdo found Greenfield's pay ranges are within about 1% of comparable cities on average. Its recommended pay structure wouldn't change anyone's current pay, so it costs nothing to adopt. Separately, a 3% raise for all staff in 2027 would cost about $19,800. At present the city staf are recommending a 4% Market Rate adjustment. No decision has been made by the council yet; the budget is finalized in December.
• Recycling: Same hauler, new contract. Republic Services (which bought Randy's) was selected for 3 years starting Jan. 1, 2027, at $5.85 per household per month in year one. Staff said that's slightly below today's rate.
• Policing: The Hennepin County Sheriff's contract was renewed for 2027–2028 at $309,724 and $319,016.
• County Road 50 (Rebecca Park Trail): A full rebuild is planned for 2028, plus a new trail, a left-turn lane at Quail Ridge Trail, and culvert repairs. The Council backed the county's state grant application. The county says no Greenfield cost is expected at this stage.
• Ballfields: A $60,994 payment was voted down because it included two change orders ($7,036) the Council never approved. A clean payment request will come back, and the Council will set a policy on approving change orders.
• Early voting is open at City Hall, with weekend hours (dates below).

STAFF PAY: THE QUESTIONS I ASKED
I've been asking since last September how annual raises work here. Here's what came out:
• The yearly raise, which the city calls a market rate adjustment (MRA), is a practice, not a written city policy or a state law. It's applied to all staff each Jan. 1 through the budget, and the employee handbook doesn't mention it. Abdo said nearly every Minnesota city does the same and called it a budget decision, which leaves it to the Council to judge whether the amount is justified. Abdo also said most cities set the number by checking what peer cities are doing, not by a clear link to inflation or the cost of living here admitting that public sector has been far out pacing private sector in pay adjustments.
• I questioned whether the 19 "comparable" cities really compare to Greenfield. Some, like Medina, Maple Grove, Plymouth and Albertville, are larger with a bigger tax base. Abdo itself said union contracts in public works and police have pushed market rates up across the region, and non-union cities like ours get pulled along. City staff agreed we're affected by cities that have unions. When the comparison group's pay rises, our MRA follows.
• Two of our Public Works employees are at the top of their pay range, so the MRA is the only raise they can get, no matter how well they perform. I suggested a tiered pay scale, like the entry, senior and lead levels common in the private sector. When you reach the top of one tier, you move up by meeting the job description of the next. Abdo agreed that's the right way to build career progression, as long as the higher tier carries real added duties and not just a new title.
Later in the discussion, Council Member Wald raised that same problem. He said the review system is frustrating for employees at the top of their range, and for the managers reviewing them, because "they're only going to achieve the COLA." He suggested a different fix, a simpler review for those employees. We may differ on the fix, but we agree on the problem.
That's how this should work. When questions get asked and answered in the open, the facts make the case and common ground shows up on its own.
To be clear, nobody on the Council wants to cut anyone's pay. We want to keep good employees, and we want residents to be able to see how raises are calculated and how our pay compares. I still believe the MRA needs greater scrutiny and will push for that before the end of the budget cycle.

OTHER DECISIONS
• Commerce Drive: Approved a revised site plan for a landscaping business that moved its building to its other lot and made it larger. One condition requires the two lots to be combined into one. I'd prefer they stay separate, so the empty lot could someday go to another business and add to our tax base. I also asked about the city's original sale terms, and the city attorney confirmed the city kept a right to take the land back if the project didn't move forward. I voted yes after staff confirmed that splitting lots in commercial and industrial districts is a quick, expedited process, so combining them now doesn't close that door.
• Recycling bins: Republic offers 35, 65 or 95-gallon carts, and a second cart costs extra. Current bins aren't expected to be swapped out, but you can ask for a replacement if yours is worn out.
• Law enforcement: In 2025 the Sheriff's Office provided about 4,592 patrol hours against roughly 3,000 contracted. I also asked for better monthly reporting that includes warnings, not just citations.
• Work plan: Added the Greenfield Road cost reconciliation and a change-order approval policy.

DATES TO KNOW
• Early voting at City Hall: regular hours, plus Sat. Oct. 24, Sat. Oct. 31 and Sun. Nov. 1, 9 a.m.–3 p.m.
• Election Day: Tue. Nov. 3
• Next council meeting: Wed. Nov. 4
• Planning Commission public hearings: Tue. Nov. 10 (BLEC property plat, limited manufacturing in rural residential areas, produce stands)
• Election canvass: Tue. Nov. 10, 6 p.m.
• 2027 budget finalized: December
Public comment is open at every regular meeting, in person at City Hall (7738 Commerce Circle) or online. Questions? Reach out to me anytime.
— Matthew McSheehy, Greenfield City Council

This is a screen shot directly from the city website. The city will not be open Friday for early voting. The city is ope...
10/12/2026

This is a screen shot directly from the city website. The city will not be open Friday for early voting. The city is open normal business hours unless directed by the County. That is how there are the random long hours on Tuesdays and the 2 Saturday's. This is directly from the City Administrator Scott Weske.

⚖️ 📊 Greenfield City Council Recap — October 6, 2026 📊 ⚖️This is my own summary as one councilmember, not the official m...
10/08/2026

⚖️ 📊 Greenfield City Council Recap — October 6, 2026 📊 ⚖️

This is my own summary as one councilmember, not the official minutes, and it includes my read on some items. It's drawn from the meeting packet and my notes, since the video transcript isn't available yet.

⚖️ The headline: Greenfield Road is over half a million past its original funding, and Council has never adopted a plan to cover it

On September 15, I said the project estimate shown on page 20 of the City Engineer's cost summary overstated what Council originally approved. That makes the overrun look smaller than it is. Council tabled the item and asked me to work with the City Administrator to document it. I did, and sent the source documents to staff.

What the record shows:

- Council approved and awarded the project in 2024 based on an engineer's estimate of $5,292,342 (April 30 and June 4, 2024 memos; Res. 24-23 and 24-26).
- The construction contract grew about 10%, from the $4.27M low bid to roughly $4.72M.
- The total project now stands near $5.54M. That's about $250,000 over the approved estimate and roughly $568,000 beyond the original funding sources.

Why this matters: costs rose in steps, and at each step Council approved the increase without deciding how to pay for it.

- In 2024, the project grew by about $109,000 for prevailing wages.
- Later, increases came from added material quantities, which Council approved.
- No funding plan was adopted at any of those points.
- During this fall's levy discussions, the majority again declined to address it, and the Mayor told me he didn't believe my figures.

During council reports, Councilmember Wald said the plan was always $5.362 million, that the prepaid assessments were always part of it, and that counting them puts the gap closer to $250,000. Councilmember Bronczyk suggested taking it up at the work session, and the Mayor agreed. I asked to respond briefly and wasn't given the floor, so I'll address it here.

Here's the response I wasn't able to give. Based on the city's own documents, the prepaid assessments (about $513,000) can't cover the gap:

- The 2024A bond (Res. 24-31) is repaid by special assessments plus the city levy.
- Res. 25-38 says the assessments are collected to finance the bond payment due December 2026.
- The prepaid money sits in Fund 324, the bond's debt-service fund.

Prepaid assessments don't create new money. They go toward the scheduled bond payments, which lowers what the levy has to cover each year. If those dollars are spent on the overage instead, the bond payments still come due, and future budgets have to make up the difference through the levy.

If there's a council action designating the prepayments for cost overruns, I'd like to see it, and I'll correct the record if so. I haven't found one.

Why this matters beyond one road: The wastewater treatment facility and the water tower repairs and capacity expansion are coming. Both will likely need financing, and together they're much bigger than the Greenfield Road project. If our practice is to approve cost increases without a funding plan, and then cover the gap with money set aside to repay debt, we'll carry that habit into multi-million-dollar projects. I'd rather we set the right practice now, on a $500,000 question:

1. When a project's costs grow, Council decides how to fund the increase at the time it's approved.
2. Money collected to repay a bond goes to the bond.

Residents deserve to know how this will be paid for before the final levy is set in December.

Thanks to Scott, who inherited this project mid-stream and worked with me to reconcile the Hakanson Anderson engineering billing invoice by invoice. It ties out.

Disclosure: I own property on Greenfield Road and am assessed on this project like my neighbors.

Other business

Delinquent utilities certification (Res. 26-48): $30,965.22 in unpaid utility charges certified to property taxes. A resident asked that the $25 certification fee be charged once per account, not once per delinquent fund. I asked staff to explain that for the public. Bianca explained that each service is a separate enterprise fund, and the fee covers staff collection time plus a late penalty. This year staff added June reminders for the first time, on top of the January postcards and a notice before the hearing. I also asked whether we could make it easier for residents to check if they're on the list, which is already in the agenda by property ID. Staff will look at the right approach. Approved unanimously.

Here’s the important part: you still have until Thursday, November 5, 2026 [30 day from Res. 26-48] to pay a delinquent utility balance before it's certified to your property taxes and interest applies.

Ordinance 2026-08, repealing Chapter 74 (off-highway vehicles): This cleans up an outdated chapter. Chapter 75 still regulates private riding areas. I asked whether the resident who raised the original complaint had been notified, and staff confirmed the matter was resolved. Approved unanimously.

Vendor claims, $138,949.77: Approved unanimously.

Public Works clothing policy: Approved unanimously.

Work plan: Since Council asked me to work with the City Administrator on the Greenfield Road reconciliation, I suggested adding it to the work plan. Added.

As always, reach out with questions.

— Matthew McSheehy, Councilmember, City of Greenfield
This is not an official City of Greenfield post. The views expressed are my own.

⚠️ Greenfield 2027 Preliminary Budget & Tax Levy — an update ⚠️Every couple of weeks I try to give residents a plain-lan...
09/17/2026

⚠️ Greenfield 2027 Preliminary Budget & Tax Levy — an update ⚠️

Every couple of weeks I try to give residents a plain-language account of what the council decided and why. Here's my update on the September 15 meeting. As always, these are my views as one council member, and I'd encourage anyone to watch the full meeting on the city's YouTube channel and reach your own conclusions.

The 2027 preliminary budget passed 4–1. I was the no vote.

I want to explain that honestly, because a no vote deserves a reason.
Here's the plain version of my concern. On the same night we approved the final payment for the Greenfield Road project, it became clear the project has cost significantly more than the funding put in place to pay for it. That project was built on three funding sources: a $3 million state grant, which could only be used for road construction; a city bond; and special assessments paid by benefiting property owners. Together those were meant to cover the whole project. Based on the accounting the City Administrator has been preparing, the total has come in over half a million dollars above all three of those sources combined.

That overage has to come from somewhere. It comes from one of a few places: our reserves, additional borrowing that we'd pay back with interest, or the tax levy. Those are the options, and every one of them touches you. That's why I wasn't willing to set our levy ceiling for next year on the same night, before we understood how this gets paid for.

The mechanics are what make the timing matter: the council certifies a preliminary levy to the County by the end of September, and a final levy in December. Between now and then, the number can be lowered but generally cannot be raised. So, September sets the ceiling. But if we needed room to cover this overage, Tuesday was the night to protect it.

So, I asked the council to pause and get the full accounting before we certified. That request didn't carry, and the levy was certified at just over an 11% increase. Several of us on the council want to bring that number down. I do too — but not by pretending the obligations we've already taken on don't exist. This project was approved and paid for on commitments made by this council and previous ones, and those bills are real. Accounting is not magic. The accounts have to balance, and I'm not yet confident about how they do.

I want to be fair about where things stand. The City Administrator has been doing exactly the reconciliation I asked for, and I want to credit that work — his review is what now confirms the gap is both real and significant. He has also told me he does not believe additional borrowing or a special meeting will be necessary, and that the city is pursuing roughly $750,000 in reimbursement from the state. I take that seriously and I'm glad for it, but that was not information we had on Tuesday night. The figures are still being reconciled and I expect them to firm up in the coming weeks. My concern Tuesday night was never that the sky is falling — it was about sequence. I'd rather understand a cost before I vote on it than vote first and sort it out later. The latter is where the vote landed.

Here's what I'm watching as this gets finalized:
• that the shortfall is covered in a way that's transparent and documented, and
• that we don't quietly shift costs onto other, unrelated funds just because a balance happens to be available there.

I've asked that a full, reconciled accounting of the project be provided to the entire council with enough time to correct the certification before the end of the month, if the numbers warrant it — and, either way, before the December budget is adopted, so all five of us and you are working from the same set of numbers. When that's available, I'll share what I can.

On how these questions were handled

I'm going to be direct about something, because I think it bears on the trust residents place in this council. I raised three specific, substantive questions Tuesday, and I want you to know what they were and what happened to each.
First, I asked why the project cost figure the council actually voted on — $5,292,342, the number in the engineer's own April 30 and June 4, 2024 memos when we ordered the project and awarded the contract — does not appear in the project's official cost history presented to the council Tuesday night. This is an accounting I've been asking the city engineer for, regarding the firm's handling of the most expensive project in Greenfield's history. Rather than an answer,

Councilmember Bronczyk asked whether I was trying to "impeach a witness," and the mayor characterized the discrepancy as "usually a misunderstanding on your part" and suggested I was "misguiding the public here that there's something nefarious going on." I'm not. I'm asking why the number the previous council voted on didn’t match the record the city engineer presented as part of an audit I requested.

Second, I raised that staff had found roughly a $7,000 gap between the engineer's own cost figures and what the city's records show was actually paid to the firm. That was recast as me demanding "some kind of an audit," and set aside. To be clear: those were numbers I requested ahead of the meeting, and the city administrator provided them. Checking whether an engineering firm's figures match what the city actually paid is something I'd expect every member of this council to want done.

Third, I asked how the project's shortfall would be funded and what it means for your tax levy. Rather than answer, I was given a lecture on how cities set their levies — something a councilmember in his second year doesn't need explained. The lecture wasn't an answer; it was a way to avoid one. When I tried to bring the discussion back to the funding question, I was repeatedly cut off, the discussion was moved on, and the matter was tabled — before the levy vote.

I come to these meetings having done hours of research and having sent staff detailed questions in advance. Tuesday, those questions were too often met with interruptions rather than answers.

I'd echo CM Wald's suggestion that residents watch the meeting video and judge for themselves. What you'll see is that other members spoke and debated freely, while my attempts to raise and clarify these points were repeatedly interrupted, redirected, and at times talked down to. That kind of treatment makes a clean exchange difficult — but the questions themselves were simple, and they stand: these were legitimate questions about public money, and none of them was answered before we voted.

A chair sets the tone for whether hard questions get real answers or get deflected. When valid financial questions are treated as attacks rather than addressed on the merits, the person who loses isn't the councilmember asking them — it's the residents who never get the answer. I'll keep asking mine regardless. But you deserve a council where the questions get answered, not managed.

I ran for this seat to ask questions like these, even when they're uncomfortable and even when I'm the only one asking. I'll keep reporting back as the December budget takes shape.

Questions? I'm always glad to hear from residents — reach me anytime.
— Matthew McSheehy, Greenfield City Council

Greenfield City Council Recap — September 1, 2026My personal summary of the work session and regular meeting as one coun...
09/02/2026

Greenfield City Council Recap — September 1, 2026

My personal summary of the work session and regular meeting as one councilmember — not the official minutes, and it reflects my read on some items. Drawn from the meeting video and packets.

⏰ Why Sept 15 matters: The Council adopts the preliminary 2027 levy on September 15. Once certified to the county, that number becomes the ceiling — the final levy in December can only go down from there, never up. So Sept 15 sets the maximum residents could be asked to pay.

WORK SESSION (discussion only — no votes)

2027 Levy & Budget. Draft preview levy is $3,200,070, up $231,231 (7.79%) over 2026, with the tax rate moving 33.77% → 34.18% (~0.41%). LGA is still $0. Main cost drivers: police contract ($310K), fire contracts ($289K, ~+$27K), a 4% employee COLA, a 10% health-insurance increase, more bond debt service, and ~$15K in software/computer services.

Wastewater Treatment Facility — the item I pushed hardest on. A $40,000 placeholder sits under "feasibility" for urgent plant repairs (failing metal walkways, exposed electrical, UV compliance). I put a resident concern on the record: aren't these costs supposed to be covered by the user fees of those who benefit? Staff confirmed — yes, but they never have been. Rates have barely covered operations (sometimes run negative), so replacement has never been funded. The Council discussed booking any general-fund money spent here as an IOU, formalized by resolution and repaid starting ~2028, so it's transparent and future councils honor it. The real near-term repair figure is likely $120K–$150K, not $40K.

My take: The Mayor twice steered the discussion away from the WWTF back to the budget. This is where he and I differ most. Treating the plant as a distraction is backwards — if we keep deferring it, we can't build out the areas zoned for utilities, and without utilities we can't attract the commercial/industrial growth that would take the tax burden off homeowners. Which leads directly to 👇

Our tax base is the problem. I presented a fact sheet: Greenfield's commercial/industrial share of the tax base is only ~11%, vs. a ~19% median across 35 comparable cities. That means ~89% of the operating levy falls on residents. A smaller city like Maple Lake carries ~34%. Growing our commercial base requires developing residential properties like Bleck and Montgomery close to the schools. This is how we relieve residential taxpayers.

Capital Improvement Plan ($180K PW line) — the night's biggest debate. Bronczyk questioned pre-funding equipment we don't plan to buy this year, preferring to keep money with taxpayers until needed. The Mayor compared a CIP to leasing (you always need a working tractor). Staff noted we're "behind the eight-ball" from years of bond-when-needed. My point: the $180K as structured, is really in-year budgeting, not a true CIP. We need incremental small infusions to offset depreciation of capital equipment — but a real CIP is essential for the WWTF to get good bond terms if we have to replace it. Landing point: a middle-ground, partially-funded approach.

Also discussed: Software — I pulled out the actual Civic Plus figures the city administrator had provided me ahead of the meeting: roughly $10,000 up front plus a ~$5,300 recurring annual fee. That agenda-building software is a "nice to have," and with the recurring cost I don't think it's needed at this point. If the administrator's real goal is the accounting package (moving off Banyon to a cloud system), then that's the conversation worth having — but first we need to see how it would work with our card processor (Nuvei) before committing. Road funds — the earmarked accounts (seal coating, crack sealing, dust control, etc.) keep "seed money" to smooth the levy year to year. Roads — I asked that the $395K road line identify specific roads rather than stay a placeholder (one candidate: the city gravel road to the dog park, W Lake Sarah Dr).

Water/Sewer funds: slow, quarterly rate increases through 2027 to cover operations; projected to roughly break even. Vandeputte asked whether the $40,000 debt-service figure now on Industrial Park Water was the same $40,000 discussed earlier under the WWTF feasibility line — a fair question, since two identical numbers were doing very different jobs. Staff confirmed they are not the same: this one is a correction so the water fund actually pays its own bond/debt, which the enterprise funds had never been accounting for (contributing to funds running negative and distorting past rate studies). That's separate from the earlier $40,000 placeholder to repair the existing plant — and that repair figure is itself understated, since the real near-term cost is closer to $120K–$150K. Worth watching: the same round $40K number showing up on both the general-fund and enterprise-fund sides for unrelated purposes made the data harder to follow, and I'll be looking for the actual repair estimate to be carried at its true figure rather than a placeholder.

REGULAR MEETING — Votes

✅ Utility rates / 2026 fee schedule (Ord. 2026-06) — phased quarterly increases + new tiered water usage (state-required). No public speakers. Passed unanimously.

✅ Greenfield Road Pay Estimate #9 — $551,850.17. City holds $47,183.65 retainage. $12,500 in liquidated damages (25 days late) are disputed by the contractor and were not deducted — we've kept the right to net them from retainage. I flagged ~$310K in quantity overruns made without discrete change-order votes (engineer disagreed, said they were known/approved) and renewed my request for the contractor's full cost audit (promised next time). MnDOT still hasn't inspected to release the final ~$60K. Passed unanimously.

✅ Vista Green final plat (Res. 26-45). 5 lots on ~25 acres. Applicant asked to exempt the retained ~130-yr-old farmhouse from park/siren fees and to cut the park fee $3,500→$2,500. Result: existing-home park-dedication exemption granted, siren fee kept, park fee held at $3,500. Passed (Vandeputte nay — park fees are the sole park funding source).

✅ Draft recycling RFP — competitive bids for a new contract (current one ends 2026). Passed unanimously.

Quick hits: Ball-field improvements on schedule (done before Thanksgiving); Bleck property preliminary plat expected soon (Met Council approved the comp-plan amendment); Kurt Street construction starting shortly (~4 weeks); comp-plan public engagement is live — please participate (city homepage, bottom-left) or here: https://greenfieldmn.gov/planning. Sheriff's Office reported solid west-side coverage and ~11 deputies in training. Vandeputte raised interest in a future compost/brush site for residents.

Questions? Reply here or reach out anytime.

For those used to seeing my council updates in the Greenfield MN Residents Facebook group: it appears the admins have ch...
08/20/2026

For those used to seeing my council updates in the Greenfield MN Residents Facebook group: it appears the admins have changed course, and my posts are no longer welcome there.

I've made a real effort to follow every request the admins have made — including simply directing residents to this page and declining to engage with negative comments from the mayor's supporters. Despite that, the admins, who are also vocal supporters of the current mayor, have decided to remove all my past posts and now changing the groups rules to block all political posts. That decision came right around the time I announced I'd be running for mayor. I'll let you draw your own conclusions about the timing.

Whatever the reason, it won't change what I do here. This page will remain a reliable place to get straightforward recaps of what happens at council meetings, and I'll always point you to the official city videos so you can judge the full context for yourself.

Thanks for following along here. I'm grateful to have a way to keep you informed directly.

Matthew McSheehy
Greenfield City Council

Greenfield City Council Recap — August 18 Work Session & Regular MeetingTwo meetings Monday night: a budget work session...
08/20/2026

Greenfield City Council Recap — August 18 Work Session & Regular Meeting

Two meetings Monday night: a budget work session and our regular council meeting. Here's what came up and where things landed.

2027 Budget & Levy — early look
Staff brought the preliminary 2027 budget to us earlier than in past years, which gives the council real time to dig in rather than rubber-stamping numbers at the deadline. The preliminary levy is proposed at a 7.8% increase (a 1.54% tax-rate increase). Last year's started much higher before the council worked it down.

I don't think 7.8% is where we should land. My view: we should measure the levy against what residents are actually experiencing — cost-of-living increases — not just how we compare to other cities. I pushed staff to work it down toward that benchmark, and I raised several specific line items:
• Computer services, up ~$41,000 (about a 60% jump). A big piece is new agenda-building software. Staff has done good work on our agendas, but "good product" and "worth the cost" are different questions. I asked for the actual quote and a cost-benefit breakdown — and staff was candid that this software likely won't ever pay for itself. That's the kind of honest answer that lets us make a smart call before spending.
• Workers' comp looked like a 100%+ spike at first — but that was just line items being consolidated. The real increase is about $4,000. Worth clarifying so nobody's alarmed by a number that isn't real.
• Dust control. We dropped from 15 miles to 11 miles of gravel road, but the budgeted amount didn't drop to match. I pushed to confirm what's left in that fund and bring the number down. Colleagues agreed we shouldn't over-budget here.
• Legal services are running at 110% of budget this year. The single largest driver is one outside investigation, which accounts for roughly 55% of the entire legal budget — about $28,000 of residents' money. I was the only council member to vote against commissioning that outside investigator. For the record: the complaint was raised against me, and I was still willing to let the council reach its own judgment without spending $28K on an outside investigation, because I believed the cost was unjustified. The council then went beyond the investigator's own findings — which tells you what that exercise was really about. I flagged the overage so we're not caught short at year-end.

On equipment, the approach I support is simple: don't replace things on a rigid 10-year clock. If a truck or tractor is running fine, stretch it — that's how a household saves money, and a city can do the same. Several vehicle replacements were pushed further out for exactly that reason, and money already set aside went unspent and stays in the fund.

The bigger picture on your tax bill
Here's what I keep coming back to, and I've done the homework on it. I pulled the 2024 property-tax data (League of Minnesota Cities / MN Department of Revenue) for the 35 comparable cities the city administrator shared with the council and compared how much of each city's tax base is commercial and industrial.
Greenfield's commercial/industrial base is about 11% of our total tax base — roughly half the 19% median for the group. Because every parcel is taxed at the same rate, that share is also the share of the levy each class pays. In plain terms: commercial property covers only about $304,000 of our city levy, while roughly 89% — about $2.5 million — sits on homeowners.

That's the real structural pressure on your tax bill. When a city has a healthy commercial base, that share of the burden comes off residents. We don't have that yet — and I don't think the answer is simply raising the levy year after year. Growing our commercial base is one of the few real levers we have to ease pressure on homeowners over time. That's the case for responsible development at sites like Bleck and Montgomery, where meaningful commercial growth could actually happen here. And it ties directly to the wastewater discussion below: without treatment capacity to support that growth, it has nowhere to go. Levy pressure, commercial development, and wastewater capacity are one connected question, not three separate ones.

Capital Improvement Plan — planning beyond equipment
I fully support building a real 5-year CIP, but I pushed for it to go beyond just equipment. The current draft is focused on trucks, trailers, and similar items. I asked the council to expand it to the infrastructure that will actually drive our finances over the next decade: the wastewater treatment facility, the water plant, road paving, trails, and park maintenance — as specific line items, not vague totals.

This matters for a concrete reason. If Greenfield decides to build out its own wastewater capacity rather than regionalizing, a documented CIP isn't optional — it's what a bank requires to negotiate a bond on decent terms. Planning for these big-ticket items now is what keeps us from chasing the levy up and down every time something major comes due. The goal is a 5-year plan adopted alongside the final budget.

Regular Meeting — the produce-stand permit (4910 Rebecca Park Trail)
A resident who runs a small seasonal strawberry-and-produce stand came forward voluntarily to confirm she was in compliance — and got routed into a full interim-use-permit process, public hearing and all, costing her $250 plus escrow for a stand that draws maybe five to ten cars a day for about three weeks a year.
I asked that the resident be refunded the full amount. The whole council agreed this was over the top. I pushed on two things: the inconsistency in how our rural-residential rules get applied from property to property, and getting this resident her money back rather than penalizing someone for trying to follow the rules. The council approved the permit so she can keep operating, directed staff to fix the ordinance so future residents don't hit this, and agreed to refund her fee.

Let me be clear about where I stand, because it's been mischaracterized: I want Greenfield to be a small-business-friendly city. A family selling strawberries three weeks a year is exactly the kind of small agricultural operation that makes this community what it is, and we should be making that easier, not charging people for it. Wanting a fair, consistent, honestly-applied code is not the same as wanting to tax every business in town — it's the opposite.

A note: This recap reflects my own views and observations as one member of the council. It is not an official statement of the City of Greenfield or the council as a whole. I'd encourage every resident to watch the full meeting videos and draw your own conclusions — the work session and regular meeting recordings are available on the city's website and are the complete, official record of what was said.

As always, reach out with questions.
Matthew McSheehy
Greenfield City Council

Address

8845 Greenfield Road
Greenfield, MN
55357

Alerts

Be the first to know and let us send you an email when Matthew McSheehy, Greenfield Councilmember posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Shortcuts

Share