Editor's note: This story was updated after publication with additional information from the city.
A $5 million package of third-party consulting contracts was pulled from City Council consideration after the item drew scrutiny from some elected officials over its cost and lack of clarity.
It's the second time that contracts for the same group of 17 consultants were withdrawn ahead of an authorization vote this year. Council member Mike Siegel, who flagged the contracts for further review this week, said the move represented a "victory for transparency and accountability" at City Hall.
What happened
A recent city solicitation for the consulting support drew dozens of interested firms, 17 of which were recommended for funding back in the spring. However, a May authorization for those contracts was withdrawn by staff before council considered it. At the time, Siegel had sought to reduce what was then a $7.5 million contract item and require additional reporting on the city's approach.
Council members were once again poised to vote on the multi-year, 17-vendor contracting package on Sept. 10 for up to $5 million. The city didn't respond to questions about why the May item had been withdrawn, why the proposed funding was cut by one-third in the September item or how services would've been affected by that reduction as of press time.
Before the Sept. 10 vote, council member Ryan Alter had called for added reporting on the contracts and a $2 million reduction. And Siegel asked his colleagues for a closer review of the spending item and said he'd vote it down, with the intent of seeking more information and breaking up the package for potential future approval.
On Sept. 9, staff reported the item was instead being withdrawn. An Austin Financial Services spokesperson said the move was made "to allow the City additional time to review the item."
City staff previously stated the consultants were needed as city management pursues projects like its "shared service optimization," launched last year to improve local government efficiency and find cost savings. Austin would face "significant delays in accessing specialized expertise" for that process without the contracts, staff had reported.
"Decisions to use City staff or outside consultants are made based on the specific needs and circumstances of each project. Given the size and complexity of the City, there is not a single approach that applies to every project or department," the spokesperson said.
While Austin often requires third-party assistance, Siegel said he believed the approach to this batch of contracts didn't allow for full oversight.
“There are contracts that we need to enter into to provide outside expertise. But I want that to be the exception, not the rule," he said in an interview before the item's withdrawal. "To me, when the city manager brings 17 contracts all at once for one big lump sum amount of $5 million without any detail about what the individual vendors are going to provide, that’s way across the line."
The city didn't respond to a request to clarify what specific work the vendors would've performed under the contracts by press time.
The context
Austin spent more than $100 million on consulting across most departments last year. The practice drew attention in recent months after an internal audit found city departments often weren't justifying or evaluating that third-party support.
Partially in response to the audit, council called for a broad review of city contracts and grants in May. That led to more detailed reporting this summer on the tens of millions of dollars budgeted for consultants in Austin's spending plans.
Council members have authorized a variety of new or expanded consultant spending this fiscal year, including:
$340,000 for Austin Water finance services
$1.45 million for Austin Emergency Management pandemic cost recovery support
$1.75 million for Austin Human Resources market reviews and pay evaluations
$3 million for Austin Planning advisory support
$5.69 million for citywide public safety consulting
Consultant spending levels were also considered during the city's annual budget review in August, when officials moved to limit third-party contracting costs to cover anticipated social service reductions. Those millions of dollars in cuts ended up being reversed, and council members also moved to slightly lower Austin's consultant costs in fiscal year 2026-27 to help fund other priorities.
Siegel said the September batch of contracts didn't include enough detail to approve, and that he'll continue to prioritize funding for public services over consulting work.
"I don’t want there to be any excuse for cutting social services," he said. "Before we authorize millions of dollars for McKinsey [& Co.] or some other international consulting firm—that doesn’t really know the details of our city and might propose changes that have nothing to do with our local context—let’s look at our city staff, who have a ton of expertise, and let’s ask them to carry the work of the city forward.”
Also of note
The council-requested grant and contracting review from earlier this year was proposed by Mayor Kirk Watson and featured several directives for city management to consider.
Those included setting a new standard approach for structuring consultant contracts; implementing a new needs assessment requirement for consulting contracts; updating Austin's contracting rules to more clearly identify when subcontracting takes place; and producing semi-annual reporting on subcontracting activity.
The financial services spokesperson said much of that work is being implemented in the coming fiscal year 2026-27, which starts in October.
"The City continues to implement Resolution 20260521-052, including developing a standardized approach to management consulting engagements and new subcontracting procedures, reporting requirements and templates. This work will be rolled out in FY 2027 and completed by the end of the year, as required by the resolution," they said. "A consulting needs assessment has also been developed and is currently being tested. It will be required for all consulting sourcing requests beginning in FY27."
The spokesperson also noted that the September contracting package was the result of a solicitation completed before council's resolution was passed, meaning the new requirements wouldn't apply.
