Attachment B-1: Additions to Scope of Work USBE260005CT

This addition to the Scope of Work is between the Utah State Board of Education (“USBE”) and Avant Professional Services (the “Contractor”) for Dual Language Immersion Assessments. Changes may be made to the scope of work only by an amendment to the agreement as described herein.

1. Contract Preservation and Existing Obligations

A. Except as specifically modified by this amendment, all terms and conditions of Contract USBE260005CT remain unchanged and in full force and effect. This amendment does not modify, waive, limit, or supersede any obligation contained in Attachment A, including but not limited to provisions relating to data privacy, security, confidentiality, acceptance, warranties, audits, indemnification, ownership of data, termination, remedies, and compliance with applicable law.

B. The parties acknowledge that this Amendment is intended solely to add the deliverables described herein. Nothing in this Amendment shall be interpreted as reducing, replacing, or limiting Contractor's existing obligations under the Contract. Payment under this Amendment shall not establish a precedent that future maintenance, defect remediation, compatibility updates, reporting improvements, usability enhancements, dashboard modifications, data exchange updates, or other obligations reasonably related to Contractor's existing contractual responsibilities require additional compensation.

C. Nothing in this Amendment alters or limits Contractor's obligations regarding data privacy, security, confidentiality, FERPA compliance, incident response, breach notification, or protection of student data. All data exchanged under this Amendment shall be handled in accordance with the Contract and applicable law.

D. The correction of defects, performance deficiencies, programming errors, failed integrations, reporting errors, security deficiencies, accessibility deficiencies, compatibility issues, or failures to meet the requirements of the Contract, this Amendment, approved specifications, or represented functionality shall not constitute a change in scope and shall be corrected by Contractor at no additional cost.

E. Delays shall be addressed through good-faith schedule adjustments. No additional compensation or change order shall be binding unless approved through a written amendment executed by both parties. A contract amendment is required only when a requested change materially increases Contractor's effort, cost, schedule, or deliverables beyond those expressly identified in the Contract and this Amendment.

2. “Test Status Solution” - Test Status filtering (Not Started / In Progress) to the Test Taker Search page:

USBE is engaging the Contractor to add Test Status filtering (Not Started / In Progress) to the Test Taker Search page for both Teacher and Administrator users, enabling staff to quickly identify students who have not yet begun or are currently in progress on their tests (the “Test Status Solution”).

A. Project Approach

Deliverables will be created in phases (referred to as milestones in this SOW) according to the requirements documented in Appendix A&B.

B. Communication Plan

The Contractor shall:

a. Review objectives, plans, and risks with USBE.

b. Provide a weekly, written update with USBE to communicate status, schedule, open issues, and risks.

c. Provide a closing document to USBE after the Test Status Solution is delivered.

d. Ensure additional communication (e.g. weekly calls, User Acceptance

Testing, status emails) that may be required, depending on Solution complexity.

C. User Stories

User stories briefly and simply describe the Test Status Solution’s users, what features they need, and why. They are the foundation for the Test Status Solution’s requirements, milestones, and test cases.

1 As a Teacher or Administrator, I can filter test takers by a status of Not

Started or In Progress so that I can identify and follow up with students who have not yet completed their tests.

2 As a Teacher, I can filter the student list on a section to show only students with a Not Started status so that I can ensure all eligible students begin their tests.

3 As a Teacher, I can filter the student list on a section to show only students with an In Progress status so that I can monitor and support students currently taking their tests.

4 As an Administrator, I can filter students at the school or district level by Not Started or In Progress status so that I can ensure timely test completion and score processing, including for Seal of Biliteracy applicants.

D. Development Timeline & Milestones

The Contractor’s base estimate is 60 business days to complete all project development work and testing (i.e., user interface design, development, quality assurance, and user acceptance testing for all milestones). Detailed descriptions of the Test Status Solution’s milestones and deliverables are included in Appendix A&B.

E. Assumptions The Test Status filter applies to the Not Started and In Progress statuses only.

Additional statuses are not in scope. The Teacher filter is scoped to students within their assigned sections; the Administrator filter is scoped to their authorized school or district. Target delivery is back to school 2026.

F. Risks & Concerns The Contractor and USBE agree to monitor any risks identified for this project throughout the engagement and address them in accordance with the original contract and this Amendment.

This Test Status Solution requires that the Test Status field (Not Started / In Progress) is consistently populated in the underlying data model for all relevant sections. If status data is incomplete, the filter results may be inaccurate.

Additionally, separate UI implementations are required for the Teacher and Administrator dashboards. Any change that materially modifies the deliverables expressly identified in this Amendment or the original contract Scope of Work may require a written amendment executed by both parties.

G. Security Concerns

The following security considerations apply to this engagement. Both parties are responsible for maintaining compliance with applicable data privacy laws and their respective internal security policies.

This Test Status Solution surfaces student test status information to Teachers and Administrators. No new data is collected or stored by this Test Status Solution; it filters on existing status data. Authentication is governed by existing institutional SSO policies.

H. Limitations & Exclusions Because this Test Status Solution affects the core STAMP product, the following restrictions apply:

a. The status filter will apply to the Test Taker Search page in the teacher and administrative dashboards only.

b. Additional status filtering options within the teacher and administrative dashboards are not included.

c. This Test Status Solution does not provide access to additional student information or require additional student information.

I. Hosting, Maintenance, and Support Costs

No additional hosting, maintenance, or support feed outside the original contract or this Amendment will be required or charged for this Solution.

J. User Acceptance Testing

User Acceptance Testing (UAT) is USBE-performed validation after development and internal quality assurance testing are complete. UAT ensures that user stories and requirements defined in this SOW and Appendix A&B are delivered. The UAT process is as follows:

a. The Contractor schedules UAT dates.

b. The Contractor provides UAT instructions and test cases to USBE.

c. The Contractor stages milestone deliverable(s) to an environment that

USBE can access.

d. USBE shall validate if the Test Status Solution is functioning as specified in this agreement if requested by the Contractor.

e. The Contractor and USBE shall jointly review reported issues to determine whether they constitute defects, failures to meet agreed requirements, or requests for additional functionality. Disputes regarding classification of an issue shall be resolved in accordance with the Contract.

K. Acceptance & Delivery A milestone is considered accepted when USBE acknowledges that it is performing as designed (i.e. either no defects were found or fixes/changes authorized by USBE during UAT are completed).

Acceptance shall occur only upon written confirmation by USBE that the applicable deliverable meets the requirements of this SOW. Failure by USBE to respond shall not constitute acceptance. Nothing in this SOW limits USBE's rights under the Contract, including Attachment A’s Acceptance and Rejection provisions.

After the last milestone is accepted, the Test Status Solution will be delivered

(e.g., moved to USBE’s production environment). If delivery is delayed by USBE for more than 60 days after the final milestone is accepted, additional time for re-testing may be required before the Test Status Solution can be put into production.

L. User Documentation

A basic user guide describing the Test Status Solution’s functions will be produced by the Contractor. Work on the user guide will begin after the Test Status Solution is accepted by USBE, and it will be delivered within 2-4 weeks.

No other user documentation for the Test Status Solution is included with this

SOW.

M. Maintenance & Support The Contractor agrees to provide maintenance and support to the Test Status Solution as detailed below. Support request responses will be handled according to the service level in the USBE's purchased support package.

INCLUDED EXCLUDED

The Contractor’s Support Desk answers USBE’s questions.

The Contractor prioritizes and fixes bugs reported to Support. Bugs are:

• Features or processes not performing as defined in this SOW.

• Solution outages. User access issues.

The Contractor hosts the Test Status Solution; includes scheduled tasks.

Any modifications to the Test Status Solution other than bug fixes, including but not limited to Solution changes to utilize feature enhancements or new features for the Contractor’s core products.

Using changes to an integrated application.

• Adding these at USBE request requires a separate SOW.

• The Contractor may opt to apply these changes (at no charge to USBE) to meet its business needs and maintain the Test Status Solution’s functional integrity.

For purposes of this Amendment, defects include failures to perform in accordance with the Contract, Amendment, approved requirements, approved design specifications, data integrations, reporting requirements, accessibility requirements, security requirements, and expected functionality represented by Contractor during development and testing.

APPENDIX A

Project Milestones

Milestone 1: Design

USER STORIES

INCLUDED

1. As a Teacher or Administrator, I can filter test takers by a status of Not Started or In Progress so that I can identify and follow up with students who have not yet completed their tests.

DELIVERABLES Finalized user interface design mockups for the Test Status filter on both the Teacher and Administrator views of the Test Taker Search page.

Note: Approved design mockups shall be used for implementation planning purposes only and shall not modify or supersede the Contract, Scope of Work requirements, Solicitation requirements, or Contractor proposal commitments unless memorialized through a written amendment.

The Contractor Requirements:

a. Provide a UI/UX design resource.

b. Create visual mock-ups for the deliverables identified above which reflect the requirements in the remaining milestones.

c. Present mock-ups for review and iterate once (if necessary) to integrate USBE feedback.

USBE Requirements:

a. Provide a primary stakeholder to review and approve mockup designs.

b. Provide any feedback needed to complete the mockup.

c. UAT consists of review and approval of the final draft of UI mockups for the Teacher and Administrator Test Status filter interfaces.

Milestone 2: Development & QA

As a Teacher or Administrator, I can filter test takers by a status of Not Started or In Progress so that I can identify and follow up with students who have not yet completed their tests.

DELIVERABLES Fully developed and deployed Test Status filter (Not Started / In Progress) on the Test Taker Search page for both Teacher and Administrator roles in the USBE environment.

a. Develop the Test Status filter per approved design mockups for the Teacher UI (section-level) and Administrator UI (school/district-level).

Conduct internal QA testing to validate correct filtering behavior for both Not Started and In Progress statuses across both user roles.

i. Deploy the completed Test Status Solution to the USBE environment and confirm successful operation prior to USBE

UAT.

a. Provide timely access to the USBE test environment. Designate Teacher and Administrator stakeholders to participate in UAT and provide sign-off on the filter functionality for both user roles.

ii. Confirm that Test Status data (Not Started / In Progress) is fully and consistently populated in the data model prior to development kickoff.

APPENDIX B

User Access

The following table defines user access to the application.

Custom roles based on standard Contractor roles have the same access as standard roles.

All administrator roles are treated equally for access purposes.

ROLE CAN ACCESS LAUNCH POINT

Administrator Yes Test Taker Search Page Student list

Teacher Yes Student list

Proctor Yes Student list

Student No N/A

Parent [Mira]

No N/A

3. “Sortable Columns Solution” - Visible and sortable columns for Grade

Level, School, Teacher, and Class to the administrator's Test Taker Search dashboard:

USBE is engaging the Contractor to add visible and sortable columns for Grade Level, School, Teacher, and Class to the administrator's Test Taker Search dashboard, eliminating the need for administrators to cross-reference the SIS to verify student placement and testing eligibility (the “Sortable Columns Solution”).

A. Project Approach

Deliverables will be created in phases (referred to as milestones in this SOW) according to the requirements documented in Appendix C&D.

B. Communication Plan

The Contractor shall:

a. Review objectives, plans, and risks with USBE.

b. Provide a weekly, written update with USBE to communicate status, schedule, open issues, and risks.

c. Provide a closing document to USBE after the Sortable Columns

Solution is delivered.

d. Ensure additional communication (e.g. weekly calls, User Acceptance

Testing, status emails) that may be required, depending on Solution complexity.

C. User Stories

User stories briefly and simply describe the Sortable Columns Solution’s users, what features they need, and why. They are the foundation for the Sortable Columns Solution’s requirements, milestones, and test cases.

1 As an Administrator, I can view Grade Level, School, Teacher, and Class columns in the Test Taker Search dashboard so that I can quickly verify that eligible students are testing at the correct locations and in the correct teacher's classes without leaving the the Contractor platform.

2 As an Administrator, I can sort the Test Taker Search results by School so that I can review students by their school testing location.

3 As an Administrator, I can sort the Test Taker Search results by Teacher so that I can verify each student is assigned to the correct teacher for their test.

4 As an Administrator, I can sort the Test Taker Search results by Grade Level so that I can confirm testing eligibility by grade.

5 As an Administrator, I can sort the Test Taker Search results by Class so that I can confirm eligible classes are able to test students.

D. Development Timeline & Milestones

The Contractor’s base estimate is 60 business days to complete all project development work and testing (i.e., user interface design, development, quality assurance, and user acceptance testing for all milestones). Detailed descriptions of the Sortable Columns Solution’s milestones and deliverables are included in Appendix C&D.

E. Assumptions

The new columns (Grade Level, School, Teacher, Class) are scoped to the Administrator view of the Test Taker Search dashboard only. Teacher-facing views are not in scope for this SOW. Data displayed in these columns is sourced from the existing SIS integration; the Contractor is not responsible for data accuracy if SIS sync is incomplete. All four columns will be sortable.

Target delivery is back to school 2026.

F. Risks & Concerns

The Contractor and USBE agree to monitor any risks identified for this project throughout the engagement and address them in accordance with the original contract and this Amendment.

This Sortable Columns Solution depends on Grade Level, School, Teacher, and Class data being accurately and consistently populated via the SIS integration. If SIS data is incomplete or not syncing correctly at the time of development, the new columns may display missing or inaccurate values.

USBE should confirm SIS data integrity prior to development kickoff.

G. Security Concerns

The following security considerations apply to this engagement. Both parties are responsible for maintaining compliance with applicable data privacy laws and their respective internal security policies.

This Sortable Columns Solution surfaces student-level data including School, Teacher, Class, and Grade Level to Administrator users. The Contractor shall comply with all applicable data privacy, security, confidentiality, and student data protection requirements set forth in the Contract. Role-based access controls must ensure that only authorized Administrators can view this information, scoped appropriately to their school or district. No new data is collected or stored by this Sortable Columns Solution; it surfaces existing SIS-synced fields already present in the data model. Authentication is governed by existing institutional SSO policies.

H. Limitations & Exclusions

Because this Sortable Columns Solution affects the core STAMP product, the following restrictions apply:

a. The additional columns and filtering behavior will apply to the Test Taker Search page in the administrative dashboard only.

b. Additional columns and filtering options within the administrative dashboard are not included.

c. This Sortable Columns Solution does not provide access to additional student information or require additional student information.

I. Hosting, Maintenance, and Support Costs

No additional hosting, maintenance, or support feed outside the original contract or this Amendment will be required or charged for this Solution.

J. User Acceptance Testing

User Acceptance Testing (UAT) is USBE-performed validation after development and internal quality assurance testing are complete. UAT ensures that user stories and requirements defined in this SOW and Appendix C&D are delivered. The UAT process is as follows:

a. The Contractor schedules UAT dates.

b. The Contractor provides UAT instructions and test cases to USBE.

c. The Contractor stages milestone deliverable(s) to an environment that USBE can access.

d. USBE shall validate if the Sortable Columns Solution is functioning as specified in this agreement if requested by the Contractor.

e. The Contractor and USBE shall jointly review reported issues to determine whether they constitute defects, failures to meet agreed requirements, or requests for additional functionality. Disputes regarding classification of an issue shall be resolved in accordance with the Contract.

K. Acceptance & Delivery

A milestone is considered accepted when USBE acknowledges that it is performing as designed (i.e. either no defects were found or fixes/changes authorized by USBE during UAT are completed).

Acceptance shall occur only upon written confirmation by USBE that the applicable deliverable meets the requirements of this SOW. Failure by USBE to respond shall not constitute acceptance. Nothing in this SOW limits USBE's rights under the Contract, including Attachment A’s Acceptance and Rejection provisions.

After the last milestone is accepted, the Sortable Columns Solution will be delivered (e.g., moved to USBE’s production environment). If delivery is delayed by USBE for more than 60 days after the final milestone is accepted, additional time for re-testing may be required before the Sortable Columns Solution can be put into production.

L. User Documentation

A basic user guide describing the Sortable Columns Solution’s functions will be produced by the Contractor. Work on the user guide will begin after the Sortable Columns Solution is accepted by USBE, and it will be delivered within 2-4 weeks. No other user documentation for the Sortable Columns Solution is included with this SOW.

M. Maintenance & Support

The Contractor agrees to provide maintenance and support to the Sortable Columns Solution as detailed below. Support request responses will be handled according to the service level in the USBE's purchased support package.

INCLUDED EXCLUDED

The Contractor Support Desk answers USBE’s questions.

the Contractor Professional Services prioritizes and fixes bugs reported to Support. Bugs are:

• Features or processes not performing as defined in this SOW.

• Solution outages. User access issues.

The Contractor Professional Services hosts the Sortable Columns Solution;

includes scheduled tasks

Any modifications to the Sortable Columns Solution other than bug fixes, including but not limited to Solution changes to utilize feature enhancements or new features for the Contractor’s core products.

Using changes to an integrated application.

• Adding these at USBE request requires a separate SOW.

• The Contractor may opt to apply these changes (at no charge to USBE) to meet its business needs and maintain the Sortable Columns Solution’s functional integrity.

For purposes of this Amendment, defects include failures to perform in accordance with the Contract, Amendment, approved requirements, approved design specifications, data integrations, reporting requirements, accessibility requirements, security requirements, and expected functionality represented by Contractor during development and testing.

APPENDIX C

Project Milestones

Milestone 1: Design

1. As an Administrator, I can view Grade Level, School, Teacher, and Class columns in the Test Taker Search dashboard so that I can quickly verify student placement and testing eligibility without leaving the Contractor platform.

DELIVERABLES Finalized user interface design mockups for the Grade Level, School, Teacher, and Class columns in the Administrator Test Taker Search dashboard, including column sort behavior.

Note: Approved design mockups shall be used for implementation planning purposes only and shall not modify or supersede the Contract, Scope of Work requirements, Solicitation requirements, or Contractor proposal commitments unless memorialized through a written amendment.

The Contractor Requirements:

a. Provide a UI/UX design resource.

b. Create visual mock-ups for the deliverables identified above which reflect the requirements in the remaining milestones.

c. Present mock-ups for review and iterate once (if necessary) to integrate USBE feedback.

a. Provide a primary stakeholder to review and approve mockup designs.

b. Provide any feedback needed to complete the mockup.

c. UAT consists of review and approval of the final draft of UI mockups for the new sortable columns in the Administrator Test Taker Search dashboard.

Milestone 2: Development & QA

1. As an Administrator, I can view Grade Level, School, Teacher, and Class columns in the Test Taker Search dashboard so that I can quickly verify student placement and testing eligibility without leaving the Contractor platform.

DELIVERABLES Fully developed and deployed Grade Level, School, Teacher, and Class columns in the Administrator Test Taker Search dashboard, with sort functionality, in the USBE environment.

a. Develop and implement the Grade Level, School, Teacher, and Class columns per approved design mockups, including sortable column headers. Conduct internal QA testing to validate accurate data display and sort behavior across all four fields.

i. Deploy the completed solution to the USBE environment and confirm successful operation prior to USBE UAT.

a. Provide timely access to the USBE test environment. Designate an Administrator stakeholder to participate in UAT and provide sign-off confirming that Grade Level, School, Teacher, and Class data displays and sorts correctly.

i. Confirm that Grade Level, School, Teacher, and Class data is accurately and consistently populated via the SIS integration prior to production kickoff.

APPENDIX D

User Access

The following table defines user access to the application.

Custom roles based on standard the Contractor roles have the same access as standard roles.

All administrator roles are treated equally for access purposes.

ROLE CAN ACCESS LAUNCH POINT

Administrator Yes Test Taker Search Page

Teacher No N/A

Proctor No N/A

Student No N/A

Parent [Mira]

No N/A

4. Budget:

Solution Implementation Cost Estimated Duration

The Test Status Solution $60,000.00 60 Days

The Sortable Columns Solution $40,000.00 60 Days

5. Cost Breakdown:

The Test Status Solution Implementation Costs

DESCRIPTION LIST DISCOUNT FINAL

Milestone 1: Design $5,000 ($1,000) $4,000

Milestone 2: Development & QA $60,000 ($4,000) $56,000

Milestone 3: — — — —

Milestone 4: — — — —

TOTAL $65,000 ($5,000) $60,000

The Sortable Columns Solution Implementation Costs

DESCRIPTION LIST DISCOUNT FINAL

Milestone 1: Design $5,000 ($1,000) $4,000

Milestone 2: Development & QA $40,000 ($4,000) $36,000

Milestone 3: — — — —

Milestone 4: — — — —

TOTAL $45,000 ($5,000) $40,000