Redmond staff propose procurement overhaul, council asks for more data before approving higher signing limits

City of Redmond finance staff on Tuesday presented a plan to overhaul purchasing operations and proposed changes to when contract amendments and multi‑year contracts must return to the City Council for approval.

The presentation, led by Kelly Cochran, finance director, and purchasing staff Haritha Nara and Adam O'Sullivan, laid out recent workload metrics for the purchasing division and a package of policy changes intended to increase efficiency, improve compliance and reduce project delays. Cochran described the meeting's purpose as “to touch base really on the scope of work that we are creating in order to inform, the process improvement work.”

Why it matters: The proposals would shift how the city counts contract value for council review, change signing authority limits for the mayor, and standardize treatment of contract amendments — all of which determine how much council oversight the public sees for spending decisions.

Key details from staff

Haritha Nara, a city purchasing staff member, said the purchasing team is small — a supervisor and three senior purchasing agents — and handles a large workload. She reported the division issued about 2,080 purchase orders in 2024 (about 173 per month) and cited roughly $27.6 million in PO spend for that year; she also said POs recorded in the city's D365 financial system totaled about $27.7 million and that the team handled about 933 invoices per month. Nara said the team issued about 50 formal solicitations in 2024 and has implemented electronic bidding and Concur card reconciliation to speed processing.

Staff outlined planned initiatives for 2025–26 including sealed (formal) bidding improvements, updated contract boilerplates and templates, a vendor portal as part of the D365 Phase 2 implementation, expanded training and resource guidelines, and a citywide spend‑analytics system that would produce DEI and environmental sustainability reports.

Policy proposals presented

Adam O'Sullivan, purchasing manager, summarized two linked policy proposals: (1) a clarified contract amendment policy that would specify when cumulative amendments trigger council review, and (2) new contract signing authority limits tied to the total contract amount rather than an annual amount. Under the proposed signing limits, mayoral approval authority would rise to $150,000 for professional services (including technology), $150,000 for instructional and artistic services (up from $75,000), $150,000 for architectural and engineering services (up from $50,000), and $700,000 for public‑works contracts (up from $300,000). Staff said sole‑source approvals would not change.

Council reaction

Council members generally supported switching from an "annual" basis to a "total project" basis for evaluating thresholds, but many said they were not yet comfortable with the proposed dollar amounts without more context and examples.

Councilmember Fields pressed staff to show how saved staff time will produce measurable public value and recommended metrics that assess whether the city is "buying the right things" and getting competitive pricing over time. Fields said: "What's also important is what you do with the time savings." Cochran and O'Sullivan said the spend analytics work is intended to enable that outcome.

Several council members asked how staff set the proposed thresholds. O'Sullivan said staff compared Redmond to nearby jurisdictions and adjusted for inflation since the last thresholds were changed in 2018. He cited neighboring examples including Issaquah, Arlington, Bellevue and, for reference only, Seattle.

Councilmember Nueva Camino and Vice President Forsyth expressed particular concern about the size of the increases for public works and professional/technology services and asked for examples of contracts that would no longer come to council under the new limits. Councilmember Stewart said the clarification on amendments "seems very reasonable" and noted that items that grow because of successful partnerships can be a good way for council to see progress. Councilmember Anderson asked staff to clarify how multiple funding sources for a single project would be treated for threshold calculations; staff responded that funding is already approved in budget processes and the thresholds would apply to the contract amount.

Next steps and direction

Council members and staff agreed on two next steps: (1) staff will return with data showing how many and which contracts in recent years would be affected by the proposed thresholds, plus examples of the kinds of projects involved; and (2) staff will refine policy language and offer alternative threshold options (including splitting technology professional services from other professional services) and reporting or notification options so council retains visibility for projects below new thresholds. O'Sullivan summarized the intent: “we're just seeking clarity around when a contract amendment would go to council for approval.”

Staff also said the D365 Phase 2 vendor portal and future contract‑management software are expected to support improved reporting and oversight; staff committed to bring a proposal back once they have the detailed data and draft policy language.

Ending

Council did not adopt any policy changes at the study session; staff were directed to return with detailed data, examples and revised policy language for further council review. Cochran thanked the council for feedback and said the department will continue its project planning and bring milestone reports to council as the work progresses.