City council auditors ask who must be consulted before expanding a 311 generative assistant citywide. Which consultation set best reflects stakeholder considerations?

Consulting privacy, security, service operations, legal/records, and impacted resident-service owners best reflects stakeholder considerations before expanding a 311 generative assistant citywide. Citywide scale multiplies data exposure, incorrect guidance risk, retention and public-records obligations, SLA impact on contact centers, and equity effects across neighborhoods. Those duties sit with named municipal owners; their input shapes go/no-go criteria, logging, red-team findings disposition, and rollback plans. Broad but relevant consultation is a governance control, not courtesy theater.

Consulting only the marketing team that designed the chatbot’s avatar fails because branding ownership is not privacy, security, or records authority. Consulting only the GPU cloud reseller’s account executive fails conceptually: a supplier can advise on capacity and pricing but does not own resident trust, legal discovery, or municipal service outcomes. Consulting only intern developers who wrote sample prompts fails because junior builders lack authority for citywide risk acceptance and may not represent operational or legal constraints.

Exam caveat: stakeholder consultation must be timely and documented; collecting signatures after irreversible citywide launch does not satisfy the intent of informed expansion decisions.

Operational check: before expansion, record consultation with privacy, security, operations, legal/records, and service owners; capture residual risks they raise; and confirm marketing/vendor/intern input is supplementary, not sole governance input.