8-TB2640-PBM - Pharmacy Benefit Manager for SLC School District RFP.pdf

Salt Lake City School District Purchasing Department

Request for Proposal for

Pharmacy Benefit Manager for Salt Lake City School District

Solicitation No. TB2640-PBM

REQUEST FOR PROPOSALS

Pharmacy Benefit Management Services for Salt Lake City School District

Solicitation # TB2640-PBM

This Request for Proposals (RFP), having been determined to be the procurement method to provide the best value to the Conducting Procurement Unit, is designed to provide interested Vendors with sufficient basic information to submit proposals. It is not intended to limit a proposal's content or exclude any relevant or essential data. Vendors are at liberty and are encouraged to expand upon the specifications to evidence service capability. This RFP is issued in accordance with State of Utah Procurement Code, Utah Code Annotated (UCA) Chapter 63G-6a, and applicable Rules found in the Utah Administrative Code (UAC). If any provision of this RFP conflicts with the UCA or UAC, the UCA or UAC will take precedence.

PART 1: OVERVIEW AND INSTRUCTIONS

1.1 PURPOSE OF REQUEST FOR PROPOSAL

The purpose of this Request for Proposal is to solicit competitive sealed proposals from qualified Vendors to provide the Salt Lake City School District (SLCSD) with Pharmacy Benefit Manager (PBM) services.

As described in Section 1.7 and elsewhere within the RFP, technical proposals must be submitted through Bonfire/U3P (Click Here for Bonfire/U3P). Pricing will be submitted separately through the RingmasterRx system.

All vendors intending to submit a proposal must contact Tyler Barnes, SLCSD Director of Purchasing, to request access to the RingmasterRx system. Upon request, vendors will receive an email with instructions for accessing SLCSD data and completing the price proposal portion of the RFP response within RingmasterRx. Please email Tyler Barnes at Tyler.Barnes@slcschools.org.

SLCSD will use the RingmasterRx platform to manage and collect price proposals in response to this RFP. RingmasterRx is a purpose-built pharmacy contracting and analytics system that connects brokers and PBMs in a single, secure environment to support efficient information exchange and full transparency throughout the procurement process.

For this RFP, RingmasterRx will be used to centralize the price proposal information and submission, provide participating PBMs with detailed claims data, and collect standardized responses through a structured financial questionnaire addressing pricing guarantees, exclusions, specialty drug lists, and limited distribution drug lists. The platform will also support consistent, objective evaluation of proposals across both financial and contractual elements.

After a vendor confirms intent to participate, RingmasterRx will send an email invitation with instructions to access the system and submit price proposals.

This RFP is designed to provide interested Vendors with sufficient basic information to submit proposals meeting minimum requirements, but is not intended to limit a proposal's content or exclude any relevant or essential data. Vendors are at liberty and are encouraged to expand upon the specifications to evidence service capability under any agreement.

1.2 BACKGROUND

SLCSD has an enrollment of about 18,500 + students. There are 23 elementary schools, five middle schools, and four high schools. SLCSD has about 3,500 employees comprised of certified, classified, and administration staff.

1.3 PROCUREMENT UNIT, AND RFP SOLICITATION NUMBER

For the purposes of this RFP, the SLCSD Purchasing Department is both the Issuing and Conducting Procurement Units for this RFP. The reference number for this RFP is Solicitation # TB2640-PBM. This number must be referred to on all proposals, correspondence, and documentation relating to this RFP.

1.4 QUESTION AND ANSWER PERIOD

All questions MUST be submitted through the Bonfire platform (https://www.utah.bonfirehub.com) during the designated time for questions (“Q&A period”) listed on Bonfire. Questions submitted through any other channel will not be https://www.utah.bonfirehub.com/ mailto:Tyler.Barnes@slcschools.org https://www.utah.bonfirehub.com/ answered. Questions may be answered in the order they are submitted or compiled into one document and answered via an addendum. Answers disseminated by SLCSD through the Bonfire system shall serve as the official and binding position of SLCSD and will constitute an addendum to this RFP.

Questions, exceptions, or notification to SLCSD of any ambiguity, inconsistency, excessively restrictive requirement, or error in this RFP, MUST be submitted as a question through Bonfire during the Q&A period.

Questions may be answered individually or may be compiled into one document. Questions may also be answered via addenda. An answered question or addenda may modify the specification or requirements of this RFP. Answered questions and addenda will be posted on Bonfire. Vendors should periodically check Bonfire for answered questions and addenda before the closing date. The vendors are responsible for submitting their proposal as required by this RFP, including any requirements in an answered question and/or addendum.

1.5 ADDENDA

Vendors are encouraged to periodically check Bonfire for posted questions, answers, and addenda.

Any modification to this procurement will be made by addendum issued by SLCSD Purchasing. Addenda to this RFP may be issued for the purpose of making changes to the scope of work, scheduling, qualification requirements, criteria, weighting, or other requirements of this RFP.

After the due date and time for submitting a proposal to this RFP, at the discretion of the chief procurement officer or head of a procurement unit, addenda to this RFP may be limited to vendors that have submitted proposals, provided the addenda does not make a substantial change to this RFP that likely would have impacted the number of vendors responding to the original publication of this RFP.

Authorized and properly issued addenda shall constitute the official and binding position of SLCSD.

Any response to this RFP which has, as its basis, any communications or information received from sources other than this RFP or related addenda, may be considered non-responsive and rejected at the sole discretion of SLCSD.

1.6 RESTRICTIONS ON COMMUNICATIONS

From the issue date of this RFP until a Vendor is awarded a contract and the award is published, Vendors are prohibited from communications regarding this RFP with the conducting procurement unit staff, evaluation committee members, or other associated individuals EXCEPT the SLCSD procurement officer overseeing this RFP. Failure to comply with this requirement may result in disqualification.

1.7 SUBMITTING YOUR PROPOSAL

Vendors will submit their Detailed Technical Proposals (see Section 2.3 below) through Bonfire. Additionally, Vendors will submit their price proposals through RingmasterRx.

By submitting a proposal, the vendor acknowledges and agrees that the requirements, scope of work, and evaluation process outlined herein are fair, equitable, understood, and not unduly restrictive. Any exceptions to the content of this RFP must be addressed within the Q&A period. The vendor further acknowledges that it has read this RFP, along with any attached or referenced documents, including the General Provisions.

All vendor costs incurred in the preparation and submission of a proposal, including those incurred during interviews, oral presentations, and/or product demonstrations are the vendor's responsibility and will not be reimbursed.

Proposals must be received by the posted due date and time posted on Bonfire (“deadline”). Proposals received after the deadline will be late and ineligible for consideration.

The RFP will end at the deadline. Do not wait until the last minute. If a vendor is in the middle of uploading a proposal when the deadline arrives, the system will stop the upload process and the proposal will not be accepted by Bonfire.

Therefore, the attempted submission will be considered late and ineligible for consideration.

1.8 CONTRACT AWARD INTENT

The preference of the SLCSD is to make a single contract award. However, the SLCSD reserves the right to award multiple contracts. Multiple contracts may be awarded for service, coverage, or similar capabilities.

1.9 LENGTH OF CONTRACT

The contract resulting from this RFP will be for a period of approximately five and a half (5.5) years. We intend to have the contract expiration date effective at the close of our annual benefits cycle (August 30). Therefore, this contract may be slightly more or less than 5.5 years in totality to achieve this. We intend for the contract end date to be August 30, 2031.

SLCSD reserves the right to review the contract resulting from this RFP on a regular basis regarding performance and cost and may negotiate price during the term of the contract.

1.10 PRICE GUARANTEE PERIOD

All pricing must be guaranteed for the initial one-year benefits cycle. If the SLCSD chooses to extend for a second year, Vendor hereby agrees to hold pricing firm for the second year.

In the third year of the agreement, and should SLCSD agree to extend, any request for a price adjustment must be for an equal guarantee period and must be made at least 180 days prior to the effective date. Requests for price adjustment must include sufficient documentation supporting the request. Any adjustment or amendment to the contract will not be effective unless approved by the SLCSD Purchasing Manager.

1.11 DISCUSSIONS

Discussions may be conducted with the Vendors who submit proposals determined to be reasonably susceptible of being selected for award, followed by an opportunity to make best and final offers pursuant to the Utah Procurement Code, but proposals may be accepted without discussions.

1.12 STANDARD CONTRACT TERMS AND CONDITIONS, EXCEPTIONS, AND NEGOTIATIONS

Any contract resulting from this RFP will include, but not be limited to, the Salt Lake City School District Standard Terms and Conditions (Attachment A).

Exceptions and/or additions to the Standard Terms and Conditions are strongly discouraged. However, Vendors requesting exceptions and/or additions to the Standard Terms and Conditions must be submitted with the proposal.

Exceptions and/or additions submitted after the date and time for receipt of proposals will not be considered. Vendors may not submit requests for exceptions and/or additions by reference to a vendor's website or URL. URLs provided with a proposal may result in that proposal being rejected as non-responsive. Vendors may submit questions during the Q&A period regarding the Standard Terms and Conditions.

SLCSD may refuse to negotiate exceptions and/or additions that are determined to be excessive; that are inconsistent with similar contracts of the procurement unit; to warranties, insurance, or indemnification provisions that are necessary to protect the procurement unit after consultation with the Attorney General's Office or other applicable legal counsel; where the solicitation specifically prohibits exceptions and/or additions; or that are not in the best interest of the procurement unit.

In a multiple award, SLCSD reserves the right to negotiate exceptions and/or additions to terms and conditions in a manner resulting in expeditious resolutions. This process may include beginning negotiations with the Vendor having the least number of exceptions and/or additions and concluding with the Vendor submitting the greatest number of exceptions and/or additions. Contracts may be executed and become effective as negotiations are completed.

If negotiations are required, Vendor must provide all documents in Microsoft Word format for redline editing. Vendor must also provide the name, contact information, and access to the person(s) that will be directly involved in legal negotiations.

Any mandatorily required acceptance of a Vendor’s terms and conditions may result in the proposal being determined to be non-responsive.

An award resulting from this RFP is subject to successful contract terms and conditions negotiation (if required). SLCSD, at its sole discretion, will determine when contract terms and conditions negotiations become unproductive and will result in termination of award to that Vendor and SLCSD may move to the next eligible Vendor.

1.13 PROTECTED INFORMATION

The Government Records Access and Management Act (GRAMA), UCA § 63G-2-305, provides in part that:

the following records are protected if properly classified by a government entity:

(1) trade secrets as defined in Section 13-24-2, the Utah Uniform Trade Secrets Act, if the person submitting the trade secret has provided the governmental entity with the information specified in UCA § 63G-2- 309 (Business Confidentiality Claims);

(2) commercial information or non-individual financial information obtained from a person if:

(a) disclosure of the information could reasonably be expected to result in unfair competitive injury to the person submitting the information or would impair the ability of the governmental entity to obtain necessary information in the future;

(b) the person submitting the information has a greater interest in prohibiting access than the public in obtaining access; and

(c) the person submitting the information has provided the governmental entity with the information specified in UCA § 63G-2-309;

(6) records, the disclosure of which would impair governmental procurement proceedings or give an unfair advantage to any person proposing to enter into a contract or agreement with a governmental entity, except, subject to Subsections (1) and (2), that this Subsection (6) does not restrict the right of a person to have access to, after the contract or grant has been awarded and signed by all parties,…

Pricing may not be classified as confidential or protected and will be considered public information after award of the contract.

Process for Requesting Non-Disclosure: Any Vendor requesting that a record be protected shall include with the proposal a Claim of Business Confidentiality. To protect information under a Claim of Business Confidentiality, the Vendor must complete the Claim of Business Confidentiality form, which is provided as a separate attachment with this solicitation, and include the following information:

1. Provide a written Claim of Business Confidentiality at the time the information (proposal) is provided to the state, and

2. Include a concise statement of reasons supporting the claim of business confidentiality (UCA §63G-2- 309(1)).

3. Submit an electronic “redacted” (excluding protected information) copy of the proposal. Copy must clearly be marked “Redacted Version.”

An entire proposal cannot be identified as “PROTECTED”, “CONFIDENTIAL” or “PROPRIETARY”, and if so identified, shall be considered non-responsive unless the Vendor removes the designation.

Redacted Copy: If a Vendor submits a proposal that contains information claimed to be business confidential or protected information, the Vendor must submit two separate proposals: one redacted version for public release, with all protected business confidential information either blacked-out or removed, clearly marked as "Redacted Version"; and one non-redacted version for evaluation purposes, clearly marked as "Protected Business Confidential."

1.14 INTERVIEWS AND PRESENTATIONS

If it is determined to be in the best interest of the Conducting Procurement Unit, interviews and presentations may be held at the option of SLCSD. SLCSD shall establish a date and time for the interviews or presentations and shall notify eligible Vendors of the procedures. Vendors invited to interviews or presentations shall be limited to those Vendors meeting the minimum requirements and minimum technical score threshold specified in the RFP. Representations made by a Vendor during interviews or presentations shall become an addendum to the Vendor's proposal and shall be documented. Representations must be consistent with the Vendor's original proposal and may only be used for purposes of clarifying or filling in gaps in the Vendor's proposal. Interviews and presentations will be at the Vendor's expense.

PART 2: SCOPE OF SERVICES AND REQUIREMENTS

2.1 DETAILED SCOPE OF WORK AND ADDITIONAL REQUIREMENTS

SLCSD is seeking pharmacy benefit management services. Additional specifications, requirements, census data pricing information, and other details can be found within RingmasterRx. Vendors may NOT suggest alternative plan designs.

The SLCSD will not consider changes to its current plan designs.

The selected PBM must be prepared to provide comprehensive prescription drug benefit administration and clinical management services for the SLCSD, including but not limited to, the following:

• Network Administration: Establish, maintain, and manage retail, specialty, and mail-order pharmacy networks; ensure adequate access, credentialing, and performance oversight.

• Claims Processing & Adjudication: Real-time claims adjudication; eligibility file management;

coordination of benefits; prior claim reversals/adjustments; fraud, waste, and abuse monitoring.

• Formulary & Utilization Management: Develop and manage formularies; implement prior authorization, step therapy, quantity limits, and other utilization controls aligned with Plan Sponsor direction.

• Clinical Programs: Provide clinical interventions and cost-management programs.

• Specialty & High-Cost Drug Management: Specialty pharmacy services and care management;

limited distribution drug handling; management of manufacturer programs; outcomes reporting.

• Rebates & Financial Management: Negotiate manufacturer rebates and other revenue; administer and remit rebates per contract; provide full transparency and audit support; ensure pass-throughs as required.

• Member & Provider Services: Member support pharmacy help desk; communications for formulary changes, PA requirements, and benefit updates.

• Reporting & Analytics: Provide standard and ad hoc reporting, dashboards, and data extracts (including claims detail); support performance guarantees and reconciliation.

• Implementation & Ongoing Account Management: Project management for implementation, testing, and go-live; ongoing account management, issue resolution, and plan design support.

• Compliance & Data Security: Maintain HIPAA/privacy compliance, required certifications, and data security controls; support audits and regulatory reporting as applicable.

The scope of Work is subject to change based on the awarded contract(s).

2.2 MANDATORY MINIMUM REQUIREMENTS/QUALIFICATIONS

This section contains mandatory minimum requirements that must be met in order for an offer to be considered responsive. Vendors shall include a detailed narrative outlining how the proposed solution meets the following minimum mandatory requirements. For ease of evaluation, a Vendor’s proposal must be a point-by-point response, addressing in detail each area of the mandatory minimum requirements and/or qualifications.

Failure to meet any one of the mandatory requirements/qualifications will result in the proposal being rejected pursuant to the Utah Procurement Code and the proposal will not move forward in the evaluation process.

All of the items described in this section are non-negotiable. A rejection of a proposal due to a proposal not meeting mandatory minimum requirements can occur at any time in the evaluation process.

1. Submission Of Attachment C – Minimum Mandatory Requirements Checklist

Vendors must submit this form and agree to all minimum mandatory requirements contained within it. Failure to submit the form or failure to agree to all minimum mandatory requirements will result in disqualification.

2.3 DETAILED TECHNICAL RESPONSE

To determine which proposal provides the best value to the SLCSD, the evaluation committee will evaluate each responsive and responsible proposal that has not been disqualified or rejected using the criteria noted below.

The SLCSD seeks a PBM partner that demonstrates meaningful differentiation in service delivery, responsiveness, and issue resolution for both members (employees and dependents) and the SLCSD (employer).

Vendors should provide concise but substantive responses to the questions below. You are encouraged to focus on practical application, accountability, and service outcomes rather than general descriptions of standard PBM capabilities.

1. Network Distribution

a. Provide an overview of the available networks.

b. Briefly describe the strengths and weaknesses of each available network.

2. Account Management & Employer Support

a. Describe the proposed account management structure for SLCSD, including the roles and responsibilities of each team member. Indicate whether resources are dedicated or shared and provide average tenure for key roles.

b. Explain your employer issue escalation process, including how urgent or high-impact issues (e.g., access disruptions, system errors, or widespread claim issues) are prioritized and resolved. Identify who has authority to approve exceptions or overrides.

c. Describe your ongoing governance and performance management approach, including the frequency and format of service reviews, reporting, and strategic planning meetings.

3. Member (Employee) Customer Service Experience

a. Describe your member customer service model, including call center location(s), hours of operation, and training provided to representatives, particularly for public-sector or school district populations.

b. Explain how you promote first-call resolution for member inquiries related to benefits, claims, and pharmacy access. Include any advocacy or case management support available for complex situations.

c. Provide your standard member service performance metrics, such as speed to answer, abandonment rates, and issue resolution timeframes.

4. Urgent Prescription Access & Time-Sensitive Support

a. Describe how urgent or emergency prescription needs are handled, including processes for emergency fills, early refills, lost medication overrides, or situations where prior authorization has not yet been completed.

b. Explain how members, pharmacies, or prescribers can request real-time assistance when a member is at the pharmacy counter and unable to obtain medication. Include hours of availability and decision-making authority.

c. Describe after-hours, weekend, or holiday support available for urgent prescription access issues.

5. Claims Resolution & Appeals Escalation

a. Describe your claims review and appeals process, including levels of appeal, standard timelines, and communication methods with members and the employer.

b. Identify whether SLCSD will have access to a dedicated escalation or resolution team for complex, sensitive, or high-impact claim appeals.

c. Explain how systemic claim issues are identified, corrected, and monitored to prevent recurrence.

6. Clinical Support & Exception Management

a. Describe how clinical exceptions and medical necessity determinations are evaluated, including peer-to-peer review availability and turnaround times for urgent requests.

b. Explain how your organization balances formulary management with continuity of care, particularly for members with chronic or complex conditions.

7. Implementation, Change Management & Ongoing Disruption Mitigation

a. Describe your implementation approach for new clients, including member communications, pharmacy readiness, and risk mitigation strategies during transition.

b. Explain how formulary changes, utilization management updates, or other plan changes are communicated and managed during the plan year to minimize disruption for members and the SLCSD.

The criteria are not intended to limit a proposal's content or exclude any relevant or essential data. Vendors are at liberty and are encouraged to expand upon the criteria to demonstrate the Vendor’s capability to provide the SLCSD with a solution.

PART 3: INFORMATION REQUIRED IN SUBMISSION OF A PROPOSAL

3.1 PROPOSAL FORMAT

Proposals should be concise and straightforward, and prepared simply and economically. However, there is no intent in these instructions to limit a proposal’s content or to exclude any relevant or essential data.

All materials submitted become the property of the SLCSD. Materials may be evaluated by anyone designated by the SLCSD as part of the proposal evaluation committee. Materials submitted may be returned only at the SLCSD's option.

Organize the proposal using each of the following specific headings. Failure to format the proposal as follows may result in disqualification.

1. Executive Summary.

The executive summary is to briefly describe the Vendor's proposal. This summary should highlight the major features of the proposal. The reader should be able to determine the essence of the proposal by reading the executive summary.

2. Protected Information.

All protected/proprietary information must be identified in this section of the proposal by completing the Claim of Business Confidentiality Form referenced in Section 1.13.

If the Vendor’s proposal contains protected/proprietary information (refer back to the Protected Information section of this RFP for additional information), then Vendor must submit a redacted copy of the proposal at the same time Vendor submits its proposal. The redacted copy of the Vendor’s proposal must be submitted in compliance with other sections of this RFP.

If there is no protected information, write “None” in this section.

Failure to comply with this Section and Section 1.13 of this RFP releases the SLCSD from any obligation or liability arising from the inadvertent release of Vendor information.

3. Potential Conflicts of Interest.

Vendor must identify any conflict, or potential conflict of interest, that might arise during the contract. If no conflicts are identified or expected, write “None” in this section.

4. Exceptions and/or Additions to the Standard Terms and Conditions.

Proposed exceptions and/or additions to the Standard Terms and Conditions must be submitted in this section. Vendor must provide all proposed exceptions and/or additions, including a Vendor’s terms and conditions in Microsoft Word format for redline editing. Vendor must also provide the name, contact information, and access to the person(s) that will be directly involved in terms and conditions negotiations.

If there are no exceptions or additions to the Standard Terms and Conditions, write “None” in this section.

5. Mandatory Requirements.

As described in Section 2.2, Vendor must provide the required narratives that demonstrate compliance with the stated Mandatory Minimum Requirements/Qualifications. Vendor’s failure to meet any one of the mandatory requirements will result in the proposal being classified as non-responsive and will be rejected under the provisions of the Utah Procurement Code.

For ease of evaluation, the Mandatory Requirements section must be a point-by-point response, addressing each area from Section 2.2 as follows:

a. Submission Of Attachment C – Minimum Mandatory Requirements Checklist

6. Detailed Technical Proposal.

As described in Section 2.3, this section should constitute the major portion of the proposal and must be a concise overview of the Vendors assessment of work to be performed, the Vendors ability and approach, and the resources necessary to fulfill the requirements. This section should demonstrate the Vendors understanding of the desired overall performance expectations, deliverables (if any), and outcomes.

Clearly indicate any options or alternatives proposed. In any case wherein the Vendor cannot comply with an evaluation criterion outlined in Section 2.3, such inability must be stated in response to the applicable requirement.

For ease of evaluation, the Detailed Technical Proposal section must be a point-by-point response, addressing each area from Section 2.3 as follows:

a. Network Distribution

b. Account Management and Employer Support

c. Member (employee) Customer Service Experience

d. Urgent Prescription Access & Time-Sensitive Support

e. Claims Resolution & Appeals Escalation

f. Clinical Support & Exception Management

g. Implementation, Change Management, & Ongoing Disruption Mitigation

7. Price Proposal.

Please enumerate all costs, fees, and rates as described within the RingmasterRx system. Pricing will be submitted within RingmasterRx.

Price will be evaluated independently from the Detailed Technical Proposal and must be submitted separately through RingmasterRx. Inclusion of any cost or pricing data within the Detailed Technical Proposal may result in the proposal being judged as non-responsive.

PART 4: PROPOSAL EVALUATION

4.1 PROPOSAL EVALUATION

All proposals in response to this RFP will be evaluated in a manner consistent with the Utah Procurement Code, Administrative Rules, Board policies, and the evaluation criteria in this RFP.

Vendors bear sole responsibility for the items included or not included within the proposal submitted by the Vendor.

Each area of the evaluation criteria must be addressed in detail in the proposal.

4.2 PROPOSAL EVALUATION PROCESS

Stage 1: Initial Review In the initial phase of the evaluation process, the conducting procurement unit will review all proposals timely received.

Non-responsive proposals not conforming to RFP requirements or unable to meet the minimum and/or mandatory requirements will be eliminated from further consideration.

Stage 2: Technical Proposal Evaluation

Responsive proposals will then be evaluated by an evaluation committee appointed by the conducting procurement unit against the proposal evaluation criteria noted in Attachment D. Attachment D establishes the minimum score threshold for this RFP.

Vendors that achieve minimum score thresholds (please refer to Attachment D) will proceed to the Final Stage: Price

Proposal Evaluation. Vendors with a score of less than the minimum required technical points will be deemed non-responsive and ineligible for further consideration.

Final Stage: Price Proposal Evaluation Vendors successful in the technical evaluation will advance to the Final Stage: Price Proposal Evaluation, as noted in Attachment D. Please submit pricing as described within the RingmasterRx system.

4.3 EVALUATION OF PRICE

For purposes of this RFP, price will be evaluated subjectively along with the Detailed Technical Proposals. It will be considered as a total package along with the technical criteria. Pursuant to §63G-6a-707(7)(b), the Procurement Official hereby waives the prohibition on the evaluation committee regarding access to cost/price information. The SLCSD will make a best value determination that takes into account both technical capability and pricing.

4.4 DETERMINATION OF BEST VALUE

The evaluation committee will determine which proposal provides the best value to the procurement unit. Pursuant to UCA §63G-6a-Part 7, the evaluation committee will prepare and submit a written statement that recommends a proposal for contract award, contains the score awarded to that proposal based upon the evaluation criteria contained in the RFP, and explains how the recommended proposal provides best value to the procurement unit.

SLCSD reserves the right to award the contract to a technically qualified vendor(s) with a lower score in the event the high scoring offer is determined to not be the best value offered to SLCSD, based on a cost benefit analysis.

PART 5: PROPOSAL AWARD PROCESS

After the proposal evaluation process is finished, the evaluation committee shall submit the proposals, evaluation scores, and written statement to the procurement official (or designee) for review and final determination of a contract award.

5.1 AWARD OF CONTRACT

In accordance with the Utah Procurement Code, and after the evaluation and final scoring of proposals is completed, the SLCSD shall award the contract as soon as practicable to the responsive and responsible Vendor with the highest total score. However, the RFP may be canceled in accordance with UCA §63G-6a-119.

5.2 PUBLICIZING AWARD

The procurement unit shall, on the next business day after the award of a contract is announced, make available to each Vendor and to the public a written statement that includes:

A. the name of the Vendor to which the contract is awarded, and the total score awarded by the evaluation committee; and

B. the total score awarded by the evaluation committee to each Vendor to which the contract is not awarded, without identifying which Vendor received which score.