District staff brief board on contracting rules, procurement thresholds and contract review process

Portland Public Schools purchasing and contracting staff on Sept. 30 gave the Board of Education an overview of how the district solicits, approves and manages contracts, starting with the legal framework and moving through typical dollar thresholds and the contract intake and approval workflow.

"We are bound by a lot of statutes and rules in how we do procurement at PPS as a public agency," presenter Emily Cortnidge told the board, noting Oregon Revised Statutes Chapter 279 and federal procurement rules apply where federal funds are spent. Staff also described the district's own public contracting rules, which the board adopts and updates.

Why this matters: Contracting rules determine when the board must review and approve spending, how competitive processes are run, how exceptions such as cooperative purchasing or sole-source awards are handled, and how the district manages legal and fiscal risk.

Key points staff presented: - Threshold categories: micro purchases (competition encouraged but not required) are generally under $25,000; a higher personal-services micro threshold was noted for certain contracts up to $75,000. Intermediate procurements run roughly $25,000'$250,000 and generally require at least three quotes or an informal request for proposals. Formal solicitations (advertised ITB or RFP) are used over $250,000. - Board approval: Under current PPS public contracting rules, the board must approve contracts with an estimated value over $150,000; staff recommended the board consider aligning that threshold with Oregon's formal procurement threshold ($250,000), which the board adopted in response to recent legislation. - Construction: projects estimated at $100,000 or more generally enter a formal solicitation process; construction has additional procedural requirements. - Exceptions: cooperative purchasing (piggyback contracts), direct negotiation for specialized services, social procurement where only one source exists, special-class procurements for certain curriculum or software, and emergency procurements. - Contract workflow: departments initiate contracts and use PPS templates; a contracts intake team checks budget holder approval and mandatory training; contract analysts review substantive compliance; authorized signers in the contracting office complete final review and sign; contracts are recorded in the district contract management system and amendments re-enter the workflow.

Board members asked about how often three quotes are obtained (staff said attempts must be documented and that some solicitation types receive fewer responsive bids), whether community members are used to review proposals (used sometimes but subject-matter expertise is the controlling factor) and how contract performance monitoring is enforced (contract managers in departments are responsible for monitoring, with centralized training and escalation to procurement as needed).

Staff said cooperative purchasing is common for supplies and IT equipment to leverage economies of scale; construction purchases rarely use cooperative contracts. The contracting team said it will not process a contract for signature until required vendor setup, budget approvals and mandatory contracts training are completed.

Emily Cortnidge and Paul Williams answered questions from the board and said staff will return with options to align the board approval threshold with the state formal threshold and otherwise support committee work on procurement policies.

Ending: Board members praised the training value of the session and requested follow-up materials; procurement staff said they would return to the board with proposals to adjust thresholds and to provide further detail about contract management and compliance practices.