Charlotte City Law: Vendor Requirements for AI Bias Audits
In Charlotte, North Carolina, public-sector purchases of automated decision systems are subject to municipal procurement rules, information-technology standards, and contract terms that affect vendor obligations for AI bias audits. This guide explains what vendors should expect when responding to City of Charlotte solicitations, how bias-audit requirements are typically framed in procurement and IT contracts, and where to raise compliance questions with city departments. Where the municipal code or published procurement templates do not specify a numeric penalty or a named audit form, this guide notes that fact and points to the offices that enforce contract and procurement compliance.
Scope and Applicability
City contracts for software, analytics, and automated decision systems can require vendors to perform or submit independent AI bias audits, supply documentation of model training data, and enable transparent testing by city staff. Such requirements most commonly appear in:
- software-as-a-service and licensing agreements for decision-support systems;
- procurement solicitations (RFP/RFQ) that include technical and ethical evaluation criteria;
- contracts with data-sharing, privacy, or security exhibits that reference testing or audit obligations.
Vendors should treat bias-audit requirements as part of the contracting deliverables and budget for third-party testing, documentation, and remediation where requested.
Penalties & Enforcement
The City of Charlotte enforces vendor obligations through contract remedies, procurement actions, and, where applicable, administrative processes. Specific monetary fines tied solely to failure to perform an AI bias audit are not specified on the cited city pages; instead, enforcement typically uses the remedies available under the governing contract and procurement rules.
- Monetary fines: not specified on the cited page.
- Escalation: typical progression is notice, cure period, then termination or debarment; exact timeframes are not specified on the cited page.
- Non-monetary sanctions: contract suspension, termination, withholding of payments, requirement to remediate biased outputs, and referral to the City Attorney for breach claims.
- Enforcer: Procurement Services and the City IT/Technology office oversee compliance and contract administration; contract enforcement may involve the City Attorney's Office.
- Inspection and complaints: vendors and members of the public may file service requests or procurement complaints through official city channels listed below.
- Appeals/review: procurement protest and contract dispute procedures exist under the city's procurement rules; specific appeal deadlines are not specified on the cited page and will be set out in the solicitation or contract documents.
- Defences/discretion: contract provisions commonly allow cure periods, remediation plans, and exceptions where the vendor can show a reasonable excuse or compliance efforts; availability depends on contract language.
Applications & Forms
The City does not publish a dedicated "AI bias audit" form; compliance is managed through standard procurement submissions, contract exhibits, and vendor responses to RFP technical requirements. Vendors should submit proposed audit reports and test artifacts as attachments to deliverable milestones in the contract or as specified in the solicitation.
Vendor Contract Language to Expect
When preparing proposals, vendors commonly encounter clauses that require:
- documentation of model design, data provenance, and mitigation measures for known biases;
- third-party or independent audits of model performance and fairness metrics;
- cost estimates for audit work and remediation included in the bid;
- security and privacy safeguards for any shared data used in audits.
FAQ
- What triggers an AI bias audit requirement on a Charlotte contract?
- Audit requirements are triggered by solicitation or contract language for systems that make automated decisions or materially influence city programs; check the RFP and contract exhibits for explicit audit or testing clauses.
- Who enforces audit requirements and where do I report concerns?
- Procurement Services and the City IT/Technology office administer supplier compliance; procurement complaints and service requests are submitted through official city channels listed in Resources.
- Are there standard metrics or a required audit methodology?
- The city does not publish a single mandatory methodology; contract documents may specify required metrics, reporting formats, or accepted audit vendors on a case-by-case basis.
How-To
- Review the solicitation and contract exhibits to identify any audit or testing deliverables.
- Prepare a scope-of-work for bias testing that maps to the city's stated requirements and budget.
- Arrange independent testing or assign internal validated teams, and document methods, datasets, and results.
- Include remediation plans and cost estimates in your proposal to address identified issues.
- Deliver audit reports as contract milestones and retain evidence for inspection for the contract term and any retention period specified in the agreement.
Key Takeaways
- Charlotte treats bias-audit obligations as contract deliverables tied to procurement and IT standards.
- Specific monetary fines for failing to perform an AI bias audit are not published on city pages; enforcement uses contract remedies.
- Procurement Services and the City IT office are the primary points for questions, compliance, and complaints.
Help and Support / Resources
- City of Charlotte - Procurement Services
- City of Charlotte - Information Technology
- City Clerk - Charter & Code / Ordinances
- City Service Requests & Reports