The meeting saw a motion to issue a request for proposals (RFP) for the township manager role, sparking debate among council members. The motion was introduced in light of the current manager’s contract status, which will expire within the year. Proponents of the motion argued that it is standard practice to conduct annual RFPs for professional positions. They emphasized that issuing an RFP does not necessarily mean replacing the current manager but is a prudent step considering the contract timeline.

Opponents of the motion raised concerns about the timing and appropriateness of discussing an RFP, especially with an upcoming election that could influence the council’s composition. They argued for a more discussion involving all council members and the current manager to assess their willingness to continue in the role. One member highlighted the need for a “thorough discussion” and voiced concerns that the decision was being rushed without proper dialogue.

The debate underscored differing philosophies on governance and the intricacies of balancing administrative continuity with accountability. Ultimately, the council voted on the motion, which led to further discussions on the process of handling the RFP and the involvement of the Qualified Purchasing Agent (QPA). Questions about the costs and transparency of the RFP process were raised, prompting another motion to engage an executive search firm to manage the township manager search. This motion passed.

In addition to the township manager discussions, the meeting addressed budgetary concerns. One council member stressed the importance of long-term financial planning, drawing parallels to a five-year business plan. They questioned how the 2026 budget might impact future financial stability, particularly in 2027, citing potential shortfalls in medical expenses and unpredictable revenues. The council deferred detailed answers until the next meeting but assured compliance with legal posting requirements.

The meeting also featured public commentary, with resident Ronda Sparta expressing concerns over the wording of a budget resolution. She advocated for using the term “introduced” rather than “approved” to clarify the budget’s status and raised questions about transparency in budget amendments. Ronda highlighted changes within the budget, such as a $1.3 million reduction in water surplus and a notable increase in a special revenue line item. She pressed for assurance that sufficient funds were allocated for litigation to avoid emergency appropriations that could impact future budgets.

Another participant, Eric Wilson, noted a substantial reduction in utility operating surplus and questioned the rationale for a projected increase in delinquent tax receipts. His inquiry pointed out a $1.4 million decrease in utility revenues, seeking clarity on the financial projections and their implications.

The council introduced Ordinance 2611, aimed at amending the comprehensive land management code to define and prohibit data centers across all township zones. This ordinance, along with Ordinance 2612, which proposed amendments to various sections of the economic development district and related zones, passed unanimously.

The council received positive feedback about a recent traffic improvement at the intersection of Route 15 and Houses Corner Road, which included the addition of a left turn arrow for enhanced safety. This prompted appreciation from the council and highlighted ongoing efforts to address local infrastructure needs.

Further community initiatives were discussed, including preparations for upcoming Fourth of July celebrations and participation in the Rev 250 events. The council noted the importance of issuing a proclamation recognizing the 250th anniversary of the United States, reflecting on missed opportunities for similar acknowledgments in the past. Plans for a Fourth of July house decorating contest and a time capsule project were shared.

Lastly, the council addressed issues related to data security and privacy concerns surrounding Flock cameras. A senator voiced apprehension over renewing the contract due to identified security vulnerabilities, urging caution and further discussion on liability and security measures. The council acknowledged compliance with New Jersey’s privacy act but recognized the need to address potential vulnerabilities in third-party technologies.