Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Human Rights topic
No spam. Unsubscribe anytime.
Committee continues lengthy debate on making human‑rights protections consistent across city code; veterans status added
Summary
The committee discussed an ordinance to harmonize non‑discrimination language across Tulsa’s municipal code, moving existing definitions for sexual orientation and gender identity into a common section and adding veteran status as a protected characteristic.
The Urban Economic Development Committee engaged in an extended June 18 discussion about an ordinance intended to make non‑discrimination language consistent across various chapters of the Tulsa code. Staff described the amendment as a technical and substantive update: moving the 2015 definitions for sexual orientation and gender identity into a common definitions section, adding veteran status as a protected characteristic, extending protections into public accommodation sections, and adding a non‑conflict clause for state and federal law.
Jack, city legal, summarized the requested changes: move the existing definitions from the housing chapter into the chapter’s general definitions, add veteran status, add the characteristics to public‑accommodation prohibitions and other municipal provisions, and make housekeeping edits including gender‑neutral language. “First, they take without modification the definitions of sexual orientation and gender identity which are currently, as of 2015, only in the housing section of the chapter. ... And it moves those definitions to section 101 applicable to the entire chapter and adds a definition of veteran status,” Jack said.
Committee members exchanged extended views. Supporters said the update codifies protections already contained in parts of the municipal code, creates consistent enforcement paths (including human‑rights conciliation procedures administered locally), and would make Tulsa the first city in the state to add veteran status to statutory protections. Speakers cited federal case law (including Bostock) and recent U.S. Supreme Court activity as part of the evolving legal landscape that informs municipal definitions and enforcement.
Other councilors urged caution and asked for more time to review potential implications, especially whether adopting broader protections could affect federal grant funding or invite legal challenge. Several councilors asked for a pause to let newer members digest the changes and to examine potential impacts on grant eligibility; some councilors emphasized that ordinances can be amended later and that municipal policy typically evolves iteratively.
City staff and the mayor’s office of resilience and equity (Nikinda Turner) clarified process and access concerns: Turner said anyone may file a human‑rights complaint with the city’s office and staff are working to expand submission options beyond in‑person or mailed forms to improve access. Legal staff noted that some elements would remain subject to state or federal preemption and the draft includes language to that effect.
The committee discussion covered procedural points (including whether an emergency clause was included in the backup), legal uncertainties about extending federal employment precedents to public‑accommodation contexts, and political considerations. The transcript shows a wide range of council views but no final council vote recorded in the committee meeting.
Why it matters: The draft would standardize and broaden non‑discrimination protections across municipal code sections and add veteran status as a protected characteristic — a change staff flagged as novel for the state — while including a clause to avoid conflict with state or federal law.
What’s next: Continued council deliberation and possible amendments; staff signaled readiness to return with clarifications and implementation details.
