An Arclight Austin Insight
By Lance McNeill, MBA, MPAff
Read the source records
79 pages of selected, redacted City records and a claim-record source table supporting this article. PDF · 15 MB.
Open the evidence packet (PDF) →On the morning of September 24, the Austin City Council approved extensions of 14 nonprofit contracts worth about $4.1 million. According to City records cited by the Austin American-Statesman, a memo from Austin Public Health reached council and mayoral offices at 10:52 a.m., nine minutes after the votes ended. It flagged compliance problems with five of those contracts and saved its sharpest language for the Sickle Cell Texas Marc Thomas Foundation: inflated performance reporting, unallowable costs billed to the City, ineligible clients served, and multiple corrective action plans. By then Council had already approved the foundation's $349,710 extension, 9-2, with Mayor Kirk Watson and Council Member Ryan Alter opposed.1
Chaya Tong laid out that timeline in the Statesman on October 1, and her reporting shows that some offices had information before the vote. Alter told her he asked for performance evaluations and was told the program had not met its metrics. Council Member Vanessa Fuentes said she received a staff briefing and that performance information informed her vote in favor.
The nine minutes made the headline. Records Arclight Action obtained through a public information request point to a much longer delay. City staff wrote down concerns about this contract's cost in 2022 and 2023. Council extended the agreement twice more, and then a third time this September 2026, without those cost concerns appearing in the recommendation Council members were asked to approve.
A box on a reimbursement form
The foundation is paid by reimbursement. Each month it uploads its expenses to the City's grants portal, and an Austin Public Health reviewer works through a short financial checklist before approving payment. Was the request on time? Does the documentation support the amount? Are all the expenses allowable? Are administrative costs versus direct service costs "within approved range and/or reasonable?"
On the June 2022 claim, the reviewer answered no to that last question and explained why: "Cost per client is $1000+ which is extremely high for education and awareness only services." The same review noted that the "ledger didn't match submission and had to resubmit." The claim was approved in August and paid on September 6, 2022.2
The reviewer kept coming back to that box. On the September 2022 claim: "funding for similar programs is 25-50% of this contract." On February 2023: "Other similar contracts with similar outcomes and outputs are funded at 1/3 of what this contract is currently funded at." On April 2023: "This contract is funded at 3-4X the rate that contracts providing comparable services are funded." On June 2023, the box itself was marked "Not Applicable," but the comment beneath it read: "This contract gets 2-3X as much as other similar contracts with better outcomes." Each of those claims cleared a second level of review and was paid.3
Across the 16 claim records from April 2022 through July 2023, the reviewer flagged the contract's cost on five, nearly one in three. All 16 were approved, and all 16 are marked paid.4
Paying those bills did not contradict the comments. Whether an expense is allowable under the contract and whether a program is worth its price are separate questions. Renewal provides an opportunity to address those cost concerns. The comparisons deserve their own scrutiny, too. The production does not include the workpapers behind them, and the phrase "education and awareness only" undersells a contract that also pays for case management and navigation. That mismatch is a reason for City Council to ask APH what the comparisons rested on, and whether anyone above the reviewer ever answered them.
Then the comments stop. The reviewer marked the reasonableness question yes on the July 2023 claim. Beginning with August 2023, when first-level approval passed to a different staff member, that question reads "Not Applicable," with no comment, on all 34 monthly claims in the production through June 2026, including the claims approved after a third reviewer took over.5 The record does not say whether the cost concern was resolved, overruled, or simply no longer asked.
Three more Council votes
While those comments sat in the claim files, the renewals kept coming. Staff exercised options Council had authorized in 2021: $388,567 for April 2023 through March 2024, then $194,283 for April through September 2024.6 After that, Council added options of its own. On August 29, 2024, it approved another year at up to $388,567 on consent, 10-0. On August 28, 2025, it did the same, again on consent and again 10-0. A March 2026 amendment trimmed the 2025-26 budget to $349,710. On September 24, 2026, Council added a year through September 2027, raising the agreement's not-to-exceed total to $3,032,345.7
The recommendations for Council action behind the 2024, 2025 and 2026 votes describe the program, its funding, and its amendment history. None mentions the reviewer's cost comparisons. The 2026 recommendation, printed September 18, says nothing about compliance or performance problems at all. The written account of those problems came in two memos dated September 24, the day of the vote: the APH memo the Statesman reports arrived after the votes, and a budget office memo transmitting the department evaluations.8 Briefings and emails may have covered what the agenda backup left out, and Arclight Action has not yet seen those records. But the recommendation for action is the one document every Council office receives on a consent item, and for three straight votes it was silent on what the claim reviews had said.
What the City finally put in writing
By September 2026 the language had hardened. APH's contract evaluation scored the program 2 out of 5 on performance results and 1 out of 5 on leverage. It described the pattern in a sentence anyone who has managed a vendor will recognize: "Once corrective action plans are completed and temporary improvements are noted, similar issues arise again." The evaluation recommended "Modify." Its notes said staff expected to issue another corrective action plan "requiring repayment" and would "look to resolicit these needed services."9
APH also argued for keeping the services running. Its memo said the foundation "fills a distinct gap in Austin by combining sickle cell education and screening with case management, care coordination, and practical support," services "no single local provider appears to offer together." A City spokesperson told the Statesman that a gap in services "would be very disruptive." For families living with a lifelong disease, that carries real weight. The department paired it with a plan: monthly check-ins and performance evaluations, and a quarterly update from APH contract compliance staff.10
Which leaves the question these records raise. What happens to a warning that gets written into a claim file but never makes it into the Council agenda backup?
I spent almost seven years working for the City of Austin, and much of what goes right in local government depends on a staff member noticing something and writing it down. On this contract, someone did, in five claim reviews between August 2022 and July 2023. The process around those comments never carried them forward. The fullest written account of the contract's problems was dated the day of the September vote, and the APH memo, by the Statesman's account, arrived after it.
What Council can require
Council members cannot read every reimbursement claim, and they should not have to. They can require that renewal backup carry forward unresolved staff findings and say what was done about them. For this contract, that means a written answer on whether the 2022-23 cost comparisons held up, the status and dollar amount of any repayment demand, a list of the corrective actions still open, and a date for the resolicitation APH says it intends to pursue. The quarterly updates should be delivered to Council in public. The continuity argument should come with a transition plan, so that protecting families from a gap in service does not become the reason the next renewal goes through on consent.
The Statesman documented a memo that arrived nine minutes late, but the claim files show cost warnings going back years. These reviewer findings should have at least prompted City Council to have a discussion about this contract before approving it on consent.
Lance McNeill is Founder & CEO of Arclight Action.
Sources
City claim and contract records are from Austin Public Health's response to public information request X026937. Page numbers refer to the PDF of that production. Exhibit letters refer to the supporting-evidence packet published with this article.
- Chaya Tong, "Vote on nonprofit contracts under scrutiny," Austin American-Statesman, October 1, 2026, A1 and A6 Read the Statesman article. The 10:52 a.m. delivery time is the Statesman's reporting from City records; Arclight has not independently obtained the transmission email. September 24 vote: Council minutes, Item 49, EDIMS 483849, p. 13 (Exhibit K). ↩
- Exhibit A. APH production, PDF pp. 886-891; reviewer comments p. 890. Reporting period June 1-30, 2022; reviewed and approved August 3-8, 2022; paid September 6, 2022. ↩
- Exhibits B-E. APH production, PDF pp. 904-909 (September 2022; comment p. 908; approved October 18-19, 2022; paid October 27, 2022); pp. 934-939 (February 2023; comment p. 938; approved March 13-14, 2023; paid March 23, 2023); pp. 946-951 (April 2023; comment p. 950; approved June 5-16, 2023; paid June 29, 2023); pp. 958-963 (June 2023; comment p. 962; approved July 17, 2023; paid July 28, 2023). Each claim record shows first- and second-level approvals. These are reviewer comparisons, not independently reconstructed cost studies. ↩
- Exhibit F, a table of the reasonableness answer, reviewer comment, approval date and payment status for each Navigation claim record in the production sequence from April 2022 through June 2026, APH production PDF pp. 874-1173. Of the 16 claim records from April 2022 through July 2023, 11 are marked "Yes," four "No," and one (June 2023) "Not Applicable" with the adverse comment quoted above. ↩
- Exhibit G. APH production, PDF pp. 964-969 (July 2023 claim; first-level approval August 28, 2023) and pp. 970-975 (August 2023 claim; approved October 3, 2023 by a different first-level approver). The 34 claims from August 2023 through June 2026 appear at PDF pp. 970-1173; see Exhibit F. ↩
- Exhibit H. APH production, PDF pp. 392-393 (Amendment 2) and 401-402 (Amendment 3). The original March 25, 2021 authorization is EDIMS 356489. ↩
- Council minutes, August 29, 2024, Item 119 (EDIMS 437631, p. 25); August 28, 2025, Item 85 (EDIMS 460547, p. 22); September 24, 2026, Item 49 (EDIMS 483849, p. 13) (Exhibit K). Amendment 6, APH production PDF pp. 448-453 (Exhibit H), reduces the agreement by $38,857; City signature dated March 23, 2026. The records reviewed do not establish that the reduction responded to the cost comments. ↩
- Recommendations for Council action: EDIMS 434690 (2024), EDIMS 457090 (2025), and EDIMS 481500 (File 26-2323, printed September 18, 2026) (Exhibit I). APH memo, EDIMS 481853, dated September 24, 2026. Budget office memo on Resolution 20260812-022 with attached evaluation forms, EDIMS 481894, dated September 24, 2026; the records reviewed do not show when it was delivered (Exhibit J). ↩
- EDIMS 481894, PDF pp. 220-221 (printed pp. 217-218) (Exhibit J). The repayment language describes an anticipated action; issuance, amount, collection and closure are not yet verified. ↩
- EDIMS 481853, p. 2 (Exhibit J); Tong, Statesman, A6. ↩