Bellingham reporting traces exclusionary AI drafting into a utility-software procurement

Purchasing, utility operations, finance, legal reviewers and IT may need help making solicitation requirements defensible. Ask who verifies technical claims, how restrictive criteria are justified, and whether reviewers can see how drafts developed. Offer a bounded review of a sample of requirements and the approval workflow. The value hypothesis is clearer traceability and fewer unsupported restrictions, not an assumed reduction in procurement cost or litigation. This article does not establish that AI determined the winning bid, that a particular vendor acted improperly, or that wrongdoing was adjudicated. Avoid turning an unresolved historical report into allegations about a prospect or named supplier.

The relevant system is document drafting and review, not utility-billing automation itself. Retain versions, source references, author changes and approval records in the existing procurement repository. Prerequisites are an agreed requirement taxonomy and authorized access to source documents. Use a sandbox to test whether a reviewer can trace a restrictive requirement to an actual operational need, including a deliberately unsupported vendor comparison. Restrict sensitive bid or internal material from unapproved model services. Proposed proof of value should demonstrate traceability and reviewer challenge, without automatically publishing solicitations or scoring bidders. No chatbot guardrail should substitute for an accountable procurement decision.

The purchasing manager should own a documented review gate supported by an independent technical reviewer and counsel where needed. Begin with a small sample of draft requirements, gather their rationale, train authors, and practice returning unsupported language for revision. Dependencies include record access, protected review time and agreement on who resolves disputes. Proposed acceptance requires every restrictive requirement in the sample to have a documented need, verified technical support and reviewer disposition before release. Keep this separate from claims of legal compliance. Risks include rushed approvals, copied vendor descriptions and missing draft records. Periodically inspect completed procurements to see whether the process is actually followed.