Seattle Rules for Procuring Predictive Algorithms

In Seattle, Washington, city departments procuring predictive algorithms must follow municipal procurement rules, technology policy and data-use controls that govern contracts, transparency and vendor due diligence. This guide summarizes purchasing obligations, vendor requirements, risk assessments and where to find official forms and contacts so city buyers and vendors can comply with local rules and request reviews when needed.

Overview

Predictive algorithms used by city departments intersect procurement, information-technology policy, and privacy oversight. Departments typically coordinate with Finance and Administrative Services (Procurement Services) and Seattle IT for sourcing, contract language, and technical review. See procurement guidance and municipal code for general purchasing rules City of Seattle Procurement Services^[1] and the consolidated municipal code for ordinance authority Seattle Municipal Code^[2].

Procurement requirements

Key procurement steps tend to include scope definition, risk assessment for algorithmic harms, vendor due-diligence, contract clauses for data rights and model explainability, and post-award monitoring. Seattle IT maintains technology guidance relevant to sourcing and security reviews Seattle IT policies^[3].

• Scope of work and deliverables specifying model inputs, outputs and performance metrics.
• Vendor evidence of testing, validation datasets, and bias mitigation plans.
• Cost proposals with licensing, hosting and maintenance fees.
• Security and privacy controls, including data handling and breach notification.

Vendor due diligence and contract clauses

Vendors should expect background checks, references for public-sector deployments, and contractual obligations on transparency, performance, and non-discrimination. Typical contract terms include audit rights, data portability, model update protocols, and termination for cause. When city policies require, include reporting schedules and technical appendices that define acceptable error rates and monitoring triggers.

• Contract clauses: audit access, source-of-truth data definitions, and change-management procedures.
• Documentation: validation reports, provenance records, and monitoring logs retained for a defined period.
• Governance: designated points of contact, escalation paths and regular review meetings.

Penalties & Enforcement

Enforcement for procurement noncompliance depends on the controlling procurement rules, contract remedies and any specific ordinance or policy applicable to automated systems. Fine amounts and per-day penalties are not uniformly published for algorithm procurements and are not specified on the cited page Seattle Municipal Code^[2].

• Fine amounts: not specified on the cited page; contract remedies rather than fixed statutory fines are common.
• Escalation: first offence, repeat or continuing breaches are generally handled under contract breach and default procedures; specific escalation ranges are not specified on the cited page.
• Non-monetary sanctions: correction orders, contract termination, withholding of payments, and requirements to remediate system behavior.
• Enforcer: enforcing authority is typically the contract administrator within the procuring department and Finance and Administrative Services (Procurement Services); technical review and security enforcement involve Seattle IT.
• Appeals: contract dispute procedures and bid protest processes apply; specific statutory time limits for appeals are not specified on the cited procurement page.

Applications & Forms

There is no single universal form for procuring predictive algorithms; procurement actions use standard solicitation and contract forms managed by Finance and Administrative Services. Specific forms and submission instructions are available from Procurement Services and the department issuing the solicitation City of Seattle Procurement Services^[1].

Action steps for buyers and vendors

• Buyers: start vendor screening and risk assessment during RFP development.
• Vendors: prepare validation reports, explainability statements and sample contracts.
• Report issues: contact the procuring department or Procurement Services for contract enforcement.

FAQ

Who enforces procurement rules for algorithms?

Enforcement is handled by the procuring department and Finance and Administrative Services (Procurement Services), with technical review by Seattle IT.

Are there fixed fines for algorithm procurement violations?

Fixed fine amounts are not specified on the cited municipal procurement and code pages; remedies are usually contractual.

Where do I find solicitation forms?

Solicitation and contract forms are available from Procurement Services and the issuing department.

How-To

1. Define scope and performance metrics for the predictive system.
2. Conduct a vendor risk assessment and request validation artifacts.
3. Include transparency, audit and remediation clauses in the draft contract.
4. Submit procurement documents to Finance and Administrative Services and coordinate Seattle IT review.

Key Takeaways

• Start algorithm risk assessment early and involve Procurement Services and Seattle IT.
• Contracts should require documentation, audit access and remediation plans.

Help and Support / Resources

• Finance & Administrative Services - Procurement Services
• Seattle Information Technology
• Seattle Municipal Code (Municode)