In August 2026, staff told Council a $20,340 lawnmower purchase was already funded from reserves. The two numbers staff gave for that reserve — $15,000 and $16,000 — don't match each other. In writing, the Municipal Administrator has since confirmed the reserve entry hadn't actually been made yet.
The Township has an actual Reserve and Reserve Fund Policy, updated in 2024, with a specific schedule of accounts Council is supposed to review every year.
Council approves the updated Reserve and Reserve Fund Policy, rescinding the prior 2018 version (R2018-106). The Policy defines a reserve as a discretionary appropriation from net revenue that "has no reference to any specific asset and does not require the physical segregation of money or assets" — and a reserve fund as a segregated, restricted account established by specific by-law or resolution. It also states plainly: transfers to or from a reserve must be approved by Council, by resolution, by policy, or by specific budget allocation.
Council adds Schedule A: a named list of reserve accounts to be reviewed at the close of every budget year, with any surplus transferred to reserve for the uses listed — reviewed annually alongside the regular Budget schedule. Eight specific accounts are listed by General Ledger number across General Government, Fire, and Public Works. The Recreation and Cemetery capital accounts later cited for the lawnmower are not among them.
The Cemetery Committee — meeting as a committee of Council, with the Mayor as Chair and the Administrator as Secretary — moves to request Council authorize $10,000 for the Alsace Cemetery survey and $10,000 for the Nipissing Union fencing project, both "from operating reserves." Total: $20,000.
Council approves the same $20,000 for the same two projects — but now from "General Reserves," not the "operating reserves" the Committee's own motion named two weeks earlier. The 2026 Capital Forecast, meanwhile, plans $35,000 for these projects under a third name: Cemetery C&M — a source R2026-129 states outright is "not applicable." Three documents, three names, two different totals, one project.
Council accepts a quote from J&J Equipment Repair Inc. for a Country Clipper Commercial Zero Turn Mower — $20,340.00 including taxes. Staff explain the mower had already been ordered and received before the vote, and describe $16,000 as already sitting in reserve for it.
At the August 11, 2026 meeting, staff explained the funding history for the mower on the record, before Council voted on R2026-164:
The math staff gave doesn't reconcile on its own terms:
Both figures were presented as the same number. They aren't. The gap is $1,000, and no one at the table asked where it came from.
Staff also confirmed the purchase came before the vote: "we ordered and it came in before we came to council but it does fit within that budget." Council was being asked to approve a purchase that had already been made.
On August 13, 2026, I wrote to Kris Croskery-Hodgins, the Municipal Administrator-Clerk-Treasurer, about reserve figures that don't agree with each other across the Township's own documents — not just for the lawnmower, but across the Budget, the Capital Forecast, and the Reserves Plan.
Is the reserve list in the 2026 Budget Draft Presentation exhaustive, or is there a fuller list of reserve accounts?
The Budget lists "Hummel Bridge Replacement Reserve" under Administration; the Capital Forecast lists the same reserve, differently named, under Public Works.
The 2024 Capital Forecast lists two ½-lawnmower entries; the 2025 version shows only one.
The 2026 entry reverts to "if not required in 2024" a year after the 2025 version said "if not required in 2026." Likely a typo — but typos in a financial forecast are worth asking about.
Is there a resolution or budget item showing when money was actually placed into a reserve account, and what that account is named?
The Cemetery balance made the confusion concrete: the 2026 Budget shows the Cemetery reserve at $46.00 at the end of 2025, projected to reach $2,046.00 by the end of 2026 — not the $7,500 staff would later describe to Council as already set aside for the mower.
The Administrator replied in writing on August 17, 2026 — six days after the August 11 meeting where the purchase had already been approved, and three days before the August 20 Special Meeting where more detail is expected. Two of these answers say more than they seem to on first read.
I asked whether one document should be treated as the source of truth, given the same reserve appears under different names in different places. The response, in full:
I don't agree this is minor. When a reserve is named differently in the Budget and the Capital Forecast, a resident checking a number can't confirm they're looking at the same account — and, as this case shows, staff produced two different totals for the same reserve inside a single explanation to Council. Consistent naming is what makes a public document checkable.
I asked why the 2024 Forecast showed two ½-lawnmower entries, why 2025 dropped to one, and why the wording reverted a year later than it should have. The response confirmed there were, in fact, two separate mowers — and that the forecast had conflated them:
On the wording error specifically: "As explained above, the entries were combined resulting in the error." That's a direct admission the Capital Forecast — the document residents are pointed to for future spending — has carried an uncorrected error for at least two budget cycles.
I asked directly whether a resolution or budget item shows when money was placed into a reserve account, and what it's called. The full response:
That answer came after the August 11 purchase had already been approved and days before the August 20 Special Meeting — meaning, as of this writing, the accounting behind Council's vote still hasn't been made public.
The most direct — and most important — answer addressed the mower funding by name:
Read plainly, the reserve entry for the lawnmower is a future bookkeeping action — not something already sitting in a segregated, named account when Council was told "we have 16,000 in reserve for it." The Policy does allow a reserve to exist without physical segregation of funds. But if the account didn't yet exist in documented form on August 11, the number given to Council that night was, at best, an estimate presented as a completed fact.
Both documents below were presented at the same March 3, 2026 Council meeting: the 2026 Budget's reserve table, and the 2026–2036 Capital Forecast. They describe the same accounts. They don't use the same names.
Both documents were presented at the same meeting. A resident — or a councillor — trying to match a line in one document to the same line in the other has to make assumptions. That shouldn't be necessary. This is the same pattern the Administrator called "easily identified and understood" when I raised it for the lawnmower reserve — six accounts later, and it's still not one name per account.
The 2025 Asset Management Plan has its own capital works table — Table 5.5 — and the Recreation Capital Forecast explicitly cites "AMP Table 5.5" as the source for two of its projects. That citation is a good practice. It's supposed to let a resident check the Forecast number against the adopted Plan. In one case it works. In the other, the name and the figure both drift.
Both rows actually reconcile on the numbers. The first is a straightforward match. The second takes more work: the Recreation Forecast's $87,500 and the Fire Department Forecast's $87,500 are each half of the same project, and together they add up to exactly $175,000 — matching AMP Table 5.5's "Community Centre" figure to the dollar. The money isn't missing.
What's missing is the name. Both departmental forecast entries call the project "Station 1/Comm Centre Exterior." AMP Table 5.5 doesn't mention Fire Station 1 anywhere — the asset it lists is "Community Centre," on its own. A resident who does exactly what the citation invites — turns to AMP Table 5.5 to check the number — has to find both halves in two separate departmental tables, add them, and take it on faith that "Station 1/Comm Centre Exterior" and "Community Centre" are the same asset, since neither document says so directly.
This is the same problem this campaign has already documented for the Asset Management Plan on its own terms — the version residents can read publicly doesn't fully match what Council actually adopted. Here it shows up again, one step further out: even when a later document does the right thing and cites its source, and even when the numbers genuinely add up, the names still drift enough that verifying it takes more work than it should.
This isn't the only place a funding source drifts across Township documents. For these two cemetery projects, there are three.
Motion C2026-03 requests $10,000 for the Alsace survey and $10,000 for the fencing project, both "from operating reserves."
Total: $20,000.
R2026-129 approves the same two projects, now from "the General Reserves" — stating Care and Maintenance Fees "are not applicable."
Total: $20,000.
Lists the same two projects funded by "Cemetery C&M" — the source Council's resolution says doesn't apply.
Total: $35,000.
The Committee's own recommendation and Council's resolution agree on the dollar figure — $20,000 — which is a point in the process's favour. What changed, twice, is the name of the account the money is supposed to come from: operating reserves, then General Reserves, then (in the Forecast) Cemetery C&M. None of those three names appear together on any one document a resident could check against.
The Township's 2026 Budget Draft Presentation includes a reserve balance sheet with more than thirty named accounts, department by department. Not one of them is called "General Reserve" or "operating reserves" either. To be fair, that balance sheet is a summarized, friendly-named view — the Administrator has pointed out there's more detail in the full General Ledger behind it, and this page isn't meant to be a complete chart of accounts. But that's exactly the gap this case keeps landing on: whatever the underlying account actually is, a resident reading the documents the Township publishes — committee minutes, resolutions, the Capital Forecast, the Budget's reserve summary — can't follow the same $20,000 through a single consistent name.
There is one account that's actually been named, in writing, in this whole story: Working Capital — the account Kris pointed to for the lawnmower's year-end reserve entry. It carries a $1,014,580.63 balance on the 2025 books, the largest single line in the Township's entire reserve list. Under the Policy's own definitions, that makes it a reserve, not a purpose-restricted reserve fund — it isn't earmarked for cemeteries, or lawnmowers, or anything specific. If "General Reserves" and "operating reserves" are effectively both pointing back to that same catch-all account, that's worth saying plainly, not leaving implied. A single large, undifferentiated pool like Working Capital can be described almost any way — "general," "operating," or otherwise — without anyone being technically wrong, precisely because nothing about it is purpose-specific. That isn't a flaw in the Policy. It's exactly why the naming discipline this campaign keeps calling for matters more, not less, when the account behind the label is this big and this general.
The Capital Forecast carries its own caveat, repeated in every version of the document: "When adopted, this plan shall be used for the current year. Future forecasts will be utilized as a guide for financial planning." That's a reasonable caveat for a planning document. It isn't a reason for the same funding decision to arrive under three different names before anyone catches it.
This case study will be updated once that report is public. Until then, the open questions above remain open.
None of this requires assuming bad faith. The Township has a Reserve and Reserve Fund Policy that requires Council approval for transfers to or from reserves, and a Schedule A process meant to make specific accounts reviewable every year. In practice, reserve figures are being described verbally to Council, in round numbers that don't reconcile with the Township's own budget documents, for accounts that — by the Administrator's own account — hadn't been formally entered yet.
Schedule A itself is worth a closer look. It lists eight accounts by General Ledger number — three under General Government, three under Fire, two under Public Works — and states that Council will review them "annually with review of the Policy, during the regular Budget schedule." None of those GL numbers appear anywhere in the 2026 Budget Draft Presentation or the Capital Forecast. The accounts show up, if at all, under friendlier names that don't always match Schedule A's own wording either — "PW Emergency Preparedness Materials" in the resolution becomes "Public Works Emergency Management Reserve" in the Budget; "FD OMERS ... for future WSIB First Responder claims" becomes "FD WSIB Presumptive response reserve." There's also no visible artifact in the Budget materials — no note, no line, no resolution — confirming the annual review actually happened. That doesn't mean it isn't happening. But as written, the only way to check is to already have access to the General Ledger, which residents don't. If the review is supposed to happen "during the regular Budget schedule," it should leave a mark on the Budget.
That's the kind of gap that's easy to miss unless someone checks the arithmetic and asks where the reserve actually lives.
This connects directly to a standing problem already documented on the Asset Management Plan case: reserve names, funding methods, and account balances need to be consistent across every Township document that references them — and every reserve transfer needs to be traceable to a specific Council resolution before, not after, it's cited as fact.
A resolution is a formal governance document, not a place for a friendly, catch-all phrase. "General Reserves" and "operating reserves" aren't accounts — they're placeholders standing in for a decision Council hasn't actually specified. If a reserve figure is used to justify a purchase in a public meeting, the resolution authorizing it should name the specific account — by its General Ledger number and description — on the record, before the meeting, not described verbally and reconstructed afterward. That's not a higher bar for staff. It's the bar a resolution is supposed to meet by definition: a specific decision, specifically recorded.
Defines "reserve" and "reserve fund," and requires Council approval — by resolution, policy, or budget allocation — for every transfer to or from a reserve.
Open resolution →Adds a named list of reserve accounts for annual Council review. Recreation and Cemetery capital accounts are not among them.
Open document →The Cemetery Committee's own motion requests $10,000 + $10,000 from "operating reserves" for the same two projects Council later funds from "General Reserves."
Open minutes →Approves the same $20,000 the Committee recommended — now from "General Reserves" instead of "operating reserves" — stating Care and Maintenance Fees do not apply.
Open resolution →Lists "Community Centre" at $175,000 for 2028 — no mention of Fire Station 1. The two $87,500 "Station 1/Comm Centre Exterior" lines split across the Recreation and Fire Department forecasts add up to this exactly; only the name doesn't match.
Open the AMP →Plans $15,000 (fencing) and $20,000 (survey) for the two cemetery projects, both funded by Cemetery C&M — the source R2026-129 later says doesn't apply.
Open document →The summarized reserve list residents actually see — thirty-plus named accounts by department. No account named "General Reserve" appears on it. Cemetery sits at $46.00, projected to $2,046.00.
Open document →Accepts the $20,340.00 J&J Equipment Repair Inc. quote. Staff confirm the mower was pre-ordered and received before the vote.
Open resolution →The full exchange: five written questions, and the Administrator's written response confirming forecast errors and a pending reserve entry.
Open document →The report expected to name the reserve account and transfer date behind the August 11 lawnmower purchase. Not yet public.
Open agenda →Different names for the same account. An admitted error carried across two budget cycles. A reserve entry described to Council as already in place that the Township's own Administrator says was still pending. The fix isn't complicated — name it consistently, resolve it before you cite it, and put it in writing before the vote, not after.