What was said
Stormwater Task Force, January 29, 2026
the recording · 2:01 long, about 15,808 words spoken · captions carried this meeting moderately welllunenburgbudgetproject.org — written by the Lunenburg Budget Project, an independent tool for residents. Not affiliated with the Town of Lunenburg, the School Committee or the school district. The data this page is computed from: /data/recording-minutes.json
The town published an agenda for this meeting. No minutes have been published; the recording is the only record, and what follows is a guide to it.
The short version
- ▶ 1:35:44The task force agreed to split town meeting action in two: bring the storm water bylaw to the May annual town meeting first, and hold the fee and rate structure for a later special town meeting.
- ▶ 1:46:26The draft bylaw and governance options -- a five-member elected board, a three-member elected board, or an appointed commission -- go to the Select Board ahead of its February 10 session.
- ▶ 1:56:37The board set a run of dates: Finance Committee on February 5, Select Board on February 10, a public information session March 5, and the task force's own next meeting February 19.
- ▶ 14:18The group leaned toward moving billing from quarterly to annual and looking at piggybacking it on the tax or sewer bill to cut postage costs.
- ▶ 43:32No formal vote was taken on the budget or fee numbers; members debated at length how much fee detail to show the Finance Committee, without resolving it.
Why it matters — our reading
- This is the early groundwork for a new stormwater utility fee that would eventually appear as its own charge on property owners, separate from the tax rate itself.
- Splitting the bylaw vote from the fee vote means the May town meeting decision on structure and governance would come before residents see a final rate or fee schedule.
- How the bill is delivered -- annual versus quarterly, and whether it rides along with the tax or sewer bill -- affects when and how the charge shows up for a household.
Watch next
- Select Board bylaw and governance discussion, February 10
- May annual town meeting: storm water utility bylaw vote
budgetcapitalfeeshiringlegalpolicyroads and dpwstaffingtown departmentstown meetingwater sewer
Present: the chair (self, name not stated) (chair); Bill (member / presenter (appears to oversee storm water for DPW)); Mark Muzzi (member); John Beiel (member); Renee Mi (member); Timothy Willsmer (member, remote); Jenny Pewtherer (member (addressed by name during discussion)); Jarice / Charice (engineering consultant, Weston and Sampson, remote). 3 of 8 matched to the board’s posted roster; the rest, in italics, are the caption model’s hearing and may be wrong.
Votes
No substantive votes heard. 1 procedural.
The money
- ▶ 4:29MS4 permit penalties
Bill highlighted penalties in the MS4 permit; the consultant said Concord was fined for non-compliance under the 2003 permit but no community has been fined under the current permit.
as heard:$50,000
- ▶ 6:22Operating budget addition for catch basin cleaning and sweeping
Bill said adding catch basin cleaning and sweeping to the operating budget would cost about this much per year.
as heard:$240,000
- ▶ 6:53Existing storm water line in operating budget
Bill said the current storm water line in the operating budget is this amount and covers compliance reporting plus other MS4 setup work.
as heard:90,000$25,000
- ▶ 7:43Combined operating-budget total if sweeping/cleaning added
Adding the new sweeping/cleaning cost to the existing line would bring the operating-budget total to this figure, still not enough to meet all MS4 minimums (e.g., twice-yearly sweeping in some areas).
as heard:330,000
- ▶ 10:42Proposed storm water utility budget, grand total
Bill presented a proposed utility budget covering new personnel, indirect costs, typical expenses, and vendors.
as heard:$421,000
- ▶ 13:29Vendor/MS4 compliance subtotal
Bill said adding up the three vendor lines for MS4 compliance work comes to a subtotal, which is lower than the full combined operating-budget target discussed earlier, and the gap was discussed at length later in the meeting.
as heard:261,000
- ▶ 13:50Billing volume and postage
The utility would issue several thousand bills a year; quarterly billing was estimated to cost much more in postage than annual billing, prompting discussion of billing once a year or piggybacking on the tax or sewer bill.
as heard:over 4,000$18,000
- ▶ 23:02Office supplies and postage cost estimate
Bill said his office-supplies estimate was probably high since the utility is brand new, and noted the current cost per stamp.
as heard:1,50074 cents78 cents
- ▶ 17:02Fringe benefits for new hire
Bill estimated fringe benefits (Medicare, retirement, health insurance, life insurance) for the new storm water engineer/GIS manager position at up to a stated rate.
as heard:31%
- ▶ 17:23Utility share of Bill's own salary/benefits for oversight
Bill clarified the utility would pay a portion of his own salary and fringe benefits for time spent overseeing the utility, not a stipend or raise.
as heard:15%
- ▶ 20:35Indirect costs for town billing/finance support
Bill based indirect costs on the percentage the sewer commission pays the town for handling its billing, adjusted for the utility's different billing frequency.
as heard:2.9 91%$6,000
- ▶ 23:44Late payment / demand letter fee
Bill said a share of customers do not pay on time and would receive a demand invoice; a fee on that was discussed, similar to the sewer's practice.
as heard:25%$10
- ▶ 25:08Street sweeping frequency and cost
The consultant explained streets in phosphorus-impaired watershed areas must be swept twice a year rather than once; Bill's original estimate assumed once a year and used an estimated road mileage that discussion suggested was too low.
as heard:80closer to 100
- ▶ 34:14Reconciling operating-budget MS4 target with proposed subtotal
A member walked through the gap between the combined operating-budget figure discussed earlier and the vendor subtotal Bill presented, asking Bill to explain the difference.
as heard:330,000261
- ▶ 40:03Bottom-line utility budget figure
A member asked whether the bottom-line total for the utility was a specific figure Bill had shown.
as heard:421613
- ▶ 40:03Preliminary fee-schedule bottom line
Bill said a preliminary fee-schedule bottom line based on old GIS data roughly matched the budget target but he distrusted the underlying data and wanted to delete or heavily caveat that slide.
as heard:417
- ▶ 48:20Target annual fee for single-family homeowner
Members discussed keeping the eventual single-family fee target under a stated round amount and debated whether to round the preliminary tier price up for safety margin.
as heard:$1006075%$50
- ▶ 1:06:53Fee compared to other bills
A member drafted messaging comparing the storm water fee to cable or smartphone bills; another cautioned against comparing it to a cup of coffee.
as heard:$50
- ▶ 1:07:33Utility overhead percentage
A member noted the overhead of running a small stand-alone utility is significant, estimating roughly a third of the budget goes to overhead rather than direct MS4 work.
as heard:30 something%
- ▶ 1:12:07Storm damage cost example
Bill cited a single September storm that cost the town a substantial sum in cleanup and repairs, used to argue for the value of stormwater investment, though he did not think better maintenance would have prevented that particular event.
as heard:$80,000
- ▶ 28:13Urbanized area acreage and watershed
Bill read from the town's own report that a large share of the urbanized area acreage in Lunenburg is within the Nashua River watershed, which is phosphorus-impaired and drives the twice-yearly sweeping question; a portion of remaining acreage does not drain to the town's MS4.
as heard:7791 acres5679 acres
Settled without a vote
- ▶ 14:18Move away from quarterly billing toward annual (or less frequent) billing to reduce postage costs, and look into piggybacking billing on the property tax bill or sewer bill.
- ▶ 32:41The new storm water engineer/GIS manager hire will be responsible for building a full catch-basin inventory and developing a cleaning/sweeping schedule and optimization plan.
- ▶ 1:35:44Take a two-step approach at town meeting: bring the storm water utility bylaw to annual town meeting first, and bring the actual fee/utility structure to a later (special) town meeting.
- ▶ 1:46:26Send the draft bylaw to the Select Board ahead of the February 10 meeting, along with governance-structure options (five-member elected board, three-member elected board, or an appointed board/commission) for their input.
- ▶ 1:56:37FinCom presentation set for February 5; Select Board bylaw presentation set for February 10; next Task Force meeting set for February 19.
- ▶ 1:59:04Public information session set for March 5 at 7:15 p.m. at the library to introduce the storm water topic, education, and the bylaw.
- ▶ 1:57:18Post the February 10 Select Board session as a joint/posted meeting in case a quorum of the Task Force attends.
Where the time went
Minutes of recording by subject, from the topic spans below. A topic with two subjects counts toward both.
- budget53 min · 43%
- policy45 min · 37%
- fees40 min · 33%
- roads and dpw33 min · 27%
- town meeting31 min · 26%
- legal30 min · 25%
- water sewer26 min · 22%
- staffing19 min · 16%
- public comment17 min · 14%
- capital13 min · 10%
The whole meeting, in order
- ▶ 0:00Opening, Open Meeting Law notice, and roll callinformational · 2:04 long
- ▶ 2:04Public commentno public comment offered · 0:20 long · public comment
- ▶ 2:24Introduction to MS4 permit requirements and non-compliance penalties, using Concord's fine as an exampleinformational · 4:08 long · water sewer, policy, budget
- ▶ 6:32Current $90k operating-budget storm water line vs. proposed addition for sweeping/catch-basin cleaning; whether it meets MS4 minimumsinformational, action item to compile exact MS4 requirement list · 9:08 long · budget, water sewer, roads and dpw
- ▶ 15:40New personnel: storm water engineer/GIS manager position, salary range, fringe benefits, and Bill's own partial salary allocation to the utilityinformational · 4:54 long · hiring, staffing, budget
- ▶ 20:34Indirect costs for town billing/finance support, legal counsel costs, office space and suppliesinformational · 3:52 long · budget, legal
- ▶ 24:27Catch basin cleaning and street sweeping scope, frequency tied to phosphorus-impaired watershed, urbanized-area road mileage uncertaintyreferred back to Bill to check the map and mileage · 8:56 long · water sewer, roads and dpw, budget
- ▶ 33:23Catch basin cleaning scope: urbanized area only vs. whole town, sump-fill monitoring requirement, need for full catch-basin inventoryinformational · 4:17 long · water sewer, roads and dpw
- ▶ 37:40Reconciling the $90k operating line, the proposed utility budget, and what would happen to the operating-budget storm water line once a utility existsinformational · 2:22 long · budget, capital
- ▶ 40:02Preliminary fee-schedule and ERU data, including newly received but unreviewed vendor GIS data on impervious surfacesinformational, flagged as unreliable/preliminary · 3:30 long · fees, budget
- ▶ 43:32Debate over whether to show preliminary fee numbers to Finance Committee, and whether to round estimates up or downno consensus reached; leaning toward showing a conceptual fee-tier structure without hard numbers · 5:33 long · fees, budget
- ▶ 49:05Messaging strategy for presenting fees: framing versus other rising costs, avoiding numbers people will fixate on, positive vs. negative framinginformational · 16:39 long · fees, public comment
- ▶ 1:05:44Utility budget vs. continued operating-budget funding: overhead of a stand-alone utility, outsourcing vs. in-house equipment/labor, road-damage/pavement ROI messaginginformational · 10:16 long · budget, capital, roads and dpw
- ▶ 1:16:00Abatement and credit programs for BMPs, staffing capacity to administer them, gaps in checking O&M compliance, possible collaboration with incoming Land Use Directorinformational, flagged for future policy discussion · 14:10 long · policy, staffing, fees
- ▶ 1:30:10Draft bylaw review: governance structure options (elected vs. appointed storm water commission), rate-setting authority, town counsel's guidance that the bylaw needs only a simple majorityreferred to Select Board for input on governance structure · 14:50 long · policy, legal, town meeting
- ▶ 1:45:00Plan for Select Board presentation on the bylaw, and sequencing with Finance Committee and town meetingdecided informally: two-step town meeting approach (bylaw first, fee structure later) · 11:37 long · town meeting, policy, legal
- ▶ 1:56:37Scheduling: FinCom (Feb 5), Select Board (Feb 10), next Task Force meeting (Feb 19), public information session (March 5), and confirming town meeting date (May 2)dates set · 4:43 long · town meeting
- ▶ 2:01:20Adjournmentvoted · 0:20 long
What the captions could not carry
- The exact wording of the roll call exchange around 'Bill, Bill, I don't do you right' / 'No' is unclear — whether it indicates Bill was absent, late, or something else was meant.
- The identity of the chair (the person who says 'and here for myself') is never stated by name.
- The precise vote count on the adjournment motion is not stated, only 'all in favor' and an audible 'I'.
- Long stretches of overlapping cross-talk during the fee-schedule and messaging discussions make individual speaker attribution unreliable.
- The exact figure for indirect costs (heard as '2.9 91%') is garbled and its precise value is uncertain.
- Whether 'Jenny' is a Task Force member, staff, or another attendee is not established by the captions.
These are ours, and they are not the record
OUR MINUTES OF A RECORDING, written by a language model from machine captions. Two derived layers stand between this file and the meeting. Cite the video at the timestamp, never this file. Figures are as heard and may be wrong; names may be wrong; where the town published minutes, those are the record.
Written 2026-09-27 by scripts/write_recording_minutes.py (sonnet) from sources/data/youtube-transcripts/stormwater-task-force/2026-01-29-YILiAdLFKlM.json — 3,257 caption segments, sha256 97754191df89…. All recorded meetings.
Every other report
Every analysis this project has written, in one index, is at reports.