Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Economic Development Pilot Policy topic
No spam. Unsubscribe anytime.
Council hears proposed formal PILOT policies; staff proposes delegation of routine deals to Industrial Development Board
Summary
City staff presented formal Payment-In-Lieu-of-Taxes (PILOT) policies intended to standardize eligibility, create public hearings and reporting, and delegate some routine, lower-value approvals to the Industrial Development Board (IDB). Councilmembers pressed for annual reporting and questioned delegation authority and several matrix criteria.
City and economic-development staff presented a draft policy on Jan. 7 to formalize the City of Chattanooga’s Payment-In-Lieu-of-Taxes (PILOT) practices, standardize eligibility criteria, and clarify how routine requests would be handled.
Why it matters: The PILOT program is one of the city’s main economic incentives. Formal policies would set eligibility thresholds, monitoring procedures, public hearings and reporting, and would change who can approve routine deals — potentially speeding approvals while prompting questions about retention of council oversight.
Senior advisor Sherita Allen (Economic and Workforce Development) told the council staff had spent months meeting with stakeholders and auditors to build a matrix of eligibility and evaluation criteria. Staff proposed codifying common practices: holding school taxes harmless, protecting stormwater fees, requiring an economic-impact analysis and a public hearing, and retaining an economic-development fee that funds small-business support programs. The draft policy would also define minimum thresholds that determine whether projects come before council or can be delegated to the Industrial Development Board (IDB).
Key policy elements presented by staff included: a scoring matrix in which projects that meet baseline eligibility receive points for additional benefits (higher wages, greater capital investment, LEED certification, community benefits commitments); a minimum eligibility threshold of four points to qualify for a PILOT; a general minimum-wage requirement of at least 80% of Hamilton County’s most recent annual average wage for eligible projects; a 10-year maximum incentive period except when council approves otherwise; and minimum project-size thresholds that staff said were intended to screen out routine deals from council review (examples cited: manufacturing projects with at least $20 million in capital investment; a stated office minimum on the slide that was read aloud as $5,000,000,000 — council members asked staff to confirm that figure and to correct any drafting or typographical errors).
On delegation of authority, staff recommended that routine, “transactional” pilots that meet the published thresholds and fall within targeted industries (advanced manufacturing, professional services, freight/logistics, software/IT, future technology and related clusters) be delegated to the IDB for approval, while larger or strategically significant projects would still require council consideration.
Council members offered mixed reactions. Several members pressed for an annual report to council on the status of all active PILOT agreements — how many projects exist, years remaining, and percentage of job requirements met — and sought stronger clarity about community-benefit categories (for example, what counts as “exceptional corporate stewardship,” how community support would be evaluated, and what qualifies as a meaningful apprenticeship program). Councilmember Gerald Henderson expressed opposition in principle to delegating any taxing authority away from the council; others said delegation could be acceptable for clearly defined, lower-value cases if oversight and transparency safeguards are included.
Staff said county and chamber partners already produce annual PILOT reports (the chamber provides a pilot summary each year and Hamilton County posts a spreadsheet) and committed to producing a clearer annual report for council with compliance status details. Staff and council members also asked the administration to refine the matrix scoring definitions to avoid vague categories and to confirm numerical thresholds (wage baselines, capital thresholds) so the matrix yields consistent outcomes.
What’s next: Staff said they will circulate clarified policy language and supporting materials, including a cleaned-up compliance report and a corrected thresholds table. Councilmembers asked staff to present options that preserve council oversight while reducing duplicative meetings for routine approvals (for example, limiting delegation to clearly defined “transactional” pilots and shortening the number of required committee hearings).
