The Audit & Finance Committee of the Austin City Council voted Feb. 3 to recommend a revised decision tree for evaluating potential general obligation bond proposals to the full council.
Mayor Pro Tem moved that the committee forward "Version 2" of the decision tree with one change: the upper-right rectangle should read, "Is this consistent with policy related to the number of years or substantial completion of estimated voter-approved bonds remaining to be issued." Councilmember Alter seconded the motion and the committee approved the recommendation by unanimous consent.
The committee spent the bulk of its discussion on how the decision tree should treat an existing financial policy that bars a bond election unless two years or fewer of voter-approved bonds remain to be issued. Councilman Walter said that the two-year threshold "not clear" in practice and worried that a single department with a longer spending plan could hold up broader city action unless the policy accounts for differing departmental delivery schedules.
Staff advised the committee to separate a formal change to that financial policy from the framework used to evaluate bond proposals. As stated by the chair, the motion was designed to ask the full council whether the decision tree is consistent with existing policy or with a "substantial completion" interpretation so staff could bring proposed policy language back before Feb. 26.
Committee members also pushed to include clearer urgency and transparency criteria in the framework. Assistant City Manager and other staff recommended operational tools so the public and council can see each project's dollar spend, construction status and obligations, and staff agreed to develop better dashboards and to provide updated policy language in the coming weeks.
The committee made no final change to the two-year policy itself; it directed that the decision tree be the lens used when the full council considers whether to advance a bond proposal and asked staff to prepare recommended policy language and implementation tools ahead of the Feb. 26 council meeting.
The committee adjourned at 2:27 p.m.