Allentown budget committee praises finance, moves to tighten budget amendment process and plan five‑year capital review

The Allentown City Budget and Finance Committee on an unspecified date received a quarterly finance briefing and discussed procedural changes intended to make the city’s budget process more transparent and forward‑looking.

“After Q1, not too much variance from previous years,” said Director Patel, summarizing the finance memo and noting that property tax receipts have pushed the city’s cash balance to about $58,000,000. “That will sustain us for the rest of the year with our operating expenditures,” Patel said, and gave a status update on an ongoing migration from Eden to Munis that began in November 2023, with full go‑live targeted by September.

Why it matters: council members said the better bond rating and fiscal stability create opportunities to borrow at lower rates and reinvest in city priorities. Councilperson Pongo thanked Patel and the finance team for the work that produced the favorable rating and said the administration’s management “paints a very positive picture” to residents and investors.

The committee spent the bulk of its time on recommended changes from a budget process review requested under a resolution by Councilperson Bender. Members flagged three near‑term process goals: set clear amendment deadlines and standards, create a documented procedure for submitting and tracking questions during budget season, and develop a more substantive five‑year capital plan for review ahead of budget season.

On amendment timing, staff and council discussed a possible formal cutoff (one suggestion was the second council meeting in November) so that proposed changes arrive in a predictable format. “If we want to do something here, then we have to also then account for it somewhere else,” Pongo said, urging that amendments identify a funding source (tax, existing line item, or other) when they add spending.

To reduce on‑the‑spot questioning and improve transparency, Pongo proposed a shared collaborative document where council questions are logged and answered publicly. Director Patel and staff suggested using a Teams channel to share questions, files and answers across departments so participants can review asynchronously. A committee member raised open‑meeting concerns: “Did we get an answer whether or not there’s any issue with respect to Sunshine law doing that exercise?” The committee agreed it should first flesh out the proposed process and then submit a Legislative Services Request (LSR) to the city attorney (referred to as Maria in the discussion) to confirm legal compliance before implementation.

Committee members also pressed for a clearer five‑year capital plan. Patel said the five‑year operating plan is included with the budget and that staff would spend more time developing the capital plan and brief council members before budget season. The group agreed to convene an internal meeting with department heads in the coming weeks to identify projects for 2027 and beyond; a public briefing would follow after departments and council reach internal consensus.

On timing and deadlines, members discussed establishing an earlier budget approval deadline than the state‑law default of Dec. 31 so finance staff has sufficient lead time to finalize documents. Staff explained the procedural timing for placing charter changes or ballot items—an item must be approved roughly “13 Tuesdays before” the election to meet ballot scheduling rules; the committee cited a past example in which a November ballot measure was passed by council in early June.

The meeting closed with agreement to continue refining the budget narrative and deliverables and to schedule the follow‑up internal planning meeting; no formal motions or votes were taken at the session.

Next steps: staff will work with department heads and council members to draft the collaborative workflow and the capital plan, then seek legal guidance on Sunshine‑law implications before deploying the shared document or Teams channel.