Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Data Center Revenue topic
No spam. Unsubscribe anytime.
Leesburg staff outline options for $3.4M data‑center equipment tax: reserves, paving, debt payoff among choices
Summary
Town staff advised council that the FY25 $3.4 million data‑center computer equipment tax is volatile and recommended a diversified, largely non‑recurring use—revenue stabilization reserves, targeted paving, and debt reduction—while warning against using it for recurring programs without bolstered reserves.
Town finance staff presented the council with options for the unplanned $3.4 million in FY25 data‑center computer equipment tax revenue and recommended a cautious, diversified approach that prioritizes one‑time or scalable uses and reserves to guard against future volatility.
“We focus on the 6‑year CIP period,” a staff presenter said, explaining the town's long‑term sustainability analysis that assumes an average $4,000,000 per year in data‑center computer equipment tax revenue for planning purposes. Staff emphasized that the FY25 payment is preliminary, that recurring expenditures already exceed recurring revenues, and that using a volatile revenue source for ongoing expenditures increases fiscal risk.
Staff recommended several possible allocations for the FY25 amount: establishing a revenue stabilization (data‑center) reserve to smooth year‑to‑year volatility; dedicating funds to existing debt service (Davenport recommended at least $2 million annually for existing debt in the long term); increasing the paving program (staff estimated roughly two lane miles for a specified paving allocation); swapping cash into the CIP to reduce future debt obligations; and creating or bolstering reserves for stormwater or other anticipated mandates. Staff also proposed prioritizing non‑recurring or scalable uses and advised that any recurring use should be supported by a reserve equivalent to the recurring amount.
Council members raised cautions and questions. Several asked how a faster‑than‑expected campus build‑out by data‑center operators could affect revenue stability. Staff explained that an accelerated build‑out could push the town to peak recurring revenue sooner but also could precipitate a faster decline if upgrades or replacements are delayed; because the town learns actual collections only in April (after tax assessments), such shifts can create budget timing risk.
Council members also highlighted two major unknowns not yet incorporated into long‑range forecasts: the costs the town may face from state and federal stormwater mandates, and the financial effects of ongoing collective‑bargaining negotiations with town employees. Staff said both represent fiscal pressure and that council will need to prioritize among competing needs.
Staff noted options if council wished to pursue a vehicle personal property tax rate reduction: each $0.25 decrease in the vehicle tax rate would reduce revenue by about $900,000, and staff did not recommend a reduction because it would have multiyear recurring impacts. If council chose a reduction, staff recommended establishing a reserve equal to the recurring amount or deferring some revenue into FY27 to offset the FY27 budget impact.
No final council decision was made at the work session. Staff said the FY25 payment will be brought back during budget deliberations and that any tax‑rate change or final allocation should be decided in the February budget process to allow staff to incorporate audit and assessment information.
Ending: Council agreed to continue deliberation at the next meeting and to revisit stormwater and collective‑bargaining cost estimates before committing any recurring uses of data‑center revenue.
