Baltimore Algorithm Transparency Rules for City Contracts
Baltimore, Maryland requires public procurement and municipal agencies to consider transparency and accountability when acquiring or deploying automated decision systems in city contracts. This guide summarizes where transparency expectations arise in procurement, who enforces them, what vendors must disclose, and practical steps for city staff, vendors, and residents to find records or raise concerns. It focuses on city-level sources and official contacts so readers can verify obligations applied to contracts, proposals, and technology procurements in Baltimore.
Procurement rules and city data policies are the primary instruments contractors should consult; the City of Baltimore procurement office publishes contract procedures and vendor requirements on its official site Baltimore City Procurement[1], and the city’s data and information technology offices maintain open-data and technology governance resources Baltimore City Data Services[2].
Legal scope and procurement expectations
Baltimore does not appear to have a dedicated "algorithm transparency" ordinance located on the cited procurement or data pages; therefore, requirements typically derive from procurement solicitation terms, contract clauses, and agency-specific data policies. Solicitations may require disclosure of automated or algorithmic components, documentation of model inputs, and data handling safeguards. When a solicitation references algorithmic systems, expect clauses addressing documentation, monitoring, and nondiscrimination.
Penalties & Enforcement
Enforcement for noncompliance with procurement or contract transparency provisions is handled through the City procurement process and contract remedies; specific monetary fines or statutory penalties for algorithm transparency violations are not set out on the cited procurement or data pages. Where a contract includes compliance remedies, the procurement office and the contracting agency may pursue contract remedies, termination, or withholding of payment.
- Fine amounts: not specified on the cited page [1].
- Escalation: first/repeat/continuing offence ranges - not specified on the cited page [1].
- Non-monetary sanctions: contract breach remedies, corrective action orders, suspension/termination of contracts, and requirement to submit remediation plans.
- Enforcer: Baltimore City Procurement and the contracting agency (e.g., Department, Mayor's Office or Office of Information Technology); complaints and procurement appeals follow city procurement procedures [1].
- Inspection and complaint pathways: file a procurement complaint through the City procurement office or report data governance concerns to the city data office [1][2].
- Appeals and review: specific appeal time limits are not specified on the cited procurement page; follow the procurement solicitation’s protest/appeal provisions when available [1].
Applications & Forms
The City generally uses standard procurement documents for bids, proposals, and contract compliance. The cited procurement page lists procurement contact points and solicitation processes but does not publish a named "algorithm disclosure" form. Where solicitations require documentation, vendors must submit technical proposals and any required certifications through the solicitation’s submission portal or the listed procurement contact [1].
Common compliance elements required in contracts
- Disclosure of algorithmic components and system purpose.
- Documentation of model inputs, training data provenance, and performance metrics.
- Bias and nondiscrimination assessments and mitigation plans.
- Maintenance, versioning, and change-notice procedures.
- Monitoring, auditing rights, and data access for city oversight.
Action steps for vendors and city staff
- Vendors: disclose algorithmic features in proposals and submit documentation requested in solicitations.
- City staff: include clear transparency clauses in RFPs and require audit access when awarding contracts.
- Residents: request contract records or file a procurement inquiry with the procurement office if algorithm use affects public services.
FAQ
- Does Baltimore have a specific law requiring algorithm transparency in city contracts?
- The city’s procurement and data pages do not show a standalone ordinance specifically titled for algorithm transparency; requirements usually stem from solicitation terms and contract clauses. [1][2]
- Who enforces transparency and how do I file a complaint?
- Enforcement is through the Baltimore City Procurement office and the contracting agency; file procurement protests or report concerns using the procurement contact procedures on the official procurement page. [1]
- Are there standard forms for algorithm disclosures?
- There is no publicly posted, city-wide algorithm disclosure form on the cited pages; solicitations may attach required documentation at the time of bidding. [1]
How-To
- Identify the solicitation or contract number related to the technology purchase.
- Review the RFP/Purchase Order for transparency, audit, and data access clauses.
- Contact Baltimore City Procurement or the contracting agency to request specific documentation or to file a protest.
- If necessary, use the city’s public records procedures to request contract attachments, technical proposals, or data governance documents.
Key Takeaways
- Transparency obligations for algorithms usually come from procurement clauses, not a single ordinance.
- Vendors should disclose algorithmic features in proposals and be prepared to provide documentation.
- Procurement remedies and contract terms are the primary enforcement mechanisms in Baltimore.