Debate over where to budget large IT system costs as county IT seeks cuts to limit FY27 increase

Kootenai County’s information technology staff presented the FY27 IT budget on June 12, 2026, describing contract escalations and one‑time timing issues that together produce a net budgetary increase. The presentation prompted a detailed board discussion about whether major new systems driven by multiple elected officials should be consolidated within the county IT budget or retained in the budgets of the officials who are proposing them.

IT staff identified headline drivers for FY27: a $40,000 projected cost to improve website ADA compliance, timing of an Office 365 subscription invoice, a new digital evidence management system for the Sheriff’s Office (budgeted in the sheriff’s workset at roughly $88,000), and other countywide support contracts that carry modest increases. The team proposed several offsetting reductions and near‑term savings: deferring a year of copier/printer replacements (about $49,000), replacing a costly help‑desk/asset tool with an in‑house OnBase solution (saving roughly $5,000), and removing planned VMware support as the county migrates to a Hyper‑V environment. IT estimated those changes could reduce the net increase by roughly $100,000–$150,000.

The conversation turned to where to record the budget for proposed multi‑office systems. Commissioners asked whether major projects, such as a tax assessment platform or a new enterprise financial system, should be placed in the elected officials’ budgets or moved to IT to make the line-items easier to audit and plan for. One commissioner noted the eventual consolidated figure can obscure the drivers when everything is rolled into a single IT line; another said housing shared systems in IT may improve long‑term visibility and contract management. The board did not take a final vote; staff were asked to preserve visibility into who is driving each project while returning with options for how to present multi‑owner systems in the budget.

IT also noted timing opportunities: paying a Microsoft invoice ahead of a vendor price increase reduced an upcoming line item, and pending quotes for several services could further reduce the projected increase. Staff offered to circulate refined numbers by email.

Next steps: the auditor and IT will reconcile competing spreadsheet versions, enumerate candidate reductions for consideration, and provide a clearer recommendation on where multi‑elected‑official systems should be recorded for FY27 budgeting.