Lake Forest Park budget committee presses finance staff for clearer dashboard reporting as traffic-camera revenue trails forecast

Lake Forest Park's Budget & Finance Committee on Feb. 19 spent much of its meeting pressing staff for clearer, more historically contextualized budget reporting and questioned early shortfalls in traffic-camera revenue.

Julian Anderson, a Lake Forest Park resident, used the public-comment period to urge the committee to make the budget monitoring dashboard more accessible to casual readers, saying: "Perhaps I just haven't found it...Whenever budgeted amounts are reported, what was the amount in the original biannual budget as adopted by the council?" He asked that dashboard tables include columns showing original budget, subsequent amendments and current amounts, and that fund balances (including the tree account) be shown.

Finance Director Bond (referred to in the meeting as Director Bond) replied that the dashboard shows a December 2025 snapshot and explained the reporting cutoff: the city closes an "open period" in January to charge late-reported expenditures back to the prior year. On the dashboard's performance metric, he said, "So the target number is 50%," reflecting that the figures are measured at the midpoint of the two-year biennial budget.

Committee members asked for changes to make the dashboard easier to interpret. Several council members said they want a report that shows where the budget started (original biennial budget), how the mid-biennial adjustments changed that baseline, and how current paid-to-date figures compare to both. Director Bond agreed to produce schedules and explore quarterly or supplemental reports that provide that historical context.

The meeting also turned to traffic-safety camera revenues. Staff told the committee that the traffic-safety fund is at roughly 37% of expected revenue to date for the biennium and that, "yes, we are 13% below where we thought we would be," reflecting that the administration built the 2025-26 budget using limited camera data because the newest cameras went live late in 2024. Staff cautioned the committee that initial budget estimates were educated guesses and that revenue may decline further over time if driver behavior changes.

Director Bond noted that large timing items can also skew month-to-month percentages: an annual insurance invoice due in January is allocated across multiple funds and will make some front-facing percentages jump on the next dashboard. He said the dashboard's front-facing graphics are designed for a quick monthly check, while the "backside" of the dashboard contains line-item budgets and paid-to-date numbers and already includes mid-biennial budget adjustments.

On capital projects, staff highlighted that completed work (for example, a drainage design project on 35th Avenue) had not been trued up in the dashboard and that outstanding invoices from King County for 2025 overlays will change burn-rate reporting when received. Committee members asked for clearer start/end or schedule dates for capital projects so the public can see why some capital bars show low expenditures (projects not yet started) and to align the dashboard with the separate CIP project reporting the council receives.

Several members noted legal and legislative uncertainty is affecting planning. The committee raised a pending state Legislature bill that could change the formula for how much camera revenue the city keeps versus what goes to the state; staff recommended waiting for the bill outcome before making budgetary commitments tied to camera receipts.

The committee recorded one formal procedural action: adoption of the meeting agenda at the start of the session. No ordinances or budget amendments were voted on during the meeting. The committee asked staff to provide (1) fund-balance detail including the tree-related accounts, (2) a template or schedule showing original versus amended budgets with paid-to-date numbers, and (3) capital-project timing details or quarterly narrative to accompany the dashboard.

The committee concluded by agreeing to further work on dashboard format and additional one-on-one or small-group walkthroughs with finance staff; the meeting adjourned at about 7:22 p.m.