A: Counties can expect the September V1.0 Production Simulation release to include a set of upcoming fixes that OTSI is currently compiling and preparing to share. This will give counties a clear understanding of what changes are included and what they should look for during testing.

Once a bug, defect, or story has been fixed, release notes will be updated so counties know when to go back in and retest the functionality. This provides counties with a clear feedback loop and ensures they can validate the new behavior as part of the Production Simulation release.
 

A: The State is still evaluating the availability of the testing environment after Go‑Live, and no determination date has been identified at this time.
 

A: Participation in the current phase of Production Simulation was based on whether users participated in EUST 3. Our goal for this phase was to start with users who are already familiar with the system’s navigation and processes, so they can help validate updates and identify any remaining issues efficiently. Additional phases of Production Simulation will expand participation to a wider tester group, allowing more users to provide feedback as we progress.

A: All feedback from Production Simulation and EUSTs follows the same process and is reviewed by the same team. All feedback is evaluated collectively alongside all other feedback received.

A: Yes, the EUST 3 feedback items have been compared against the feedback submitted during the first two EUST cycles as the Product Team reviewed each item. As part of our analysis, we reviewed the product backlog all three periods to identify recurring themes, confirm whether previously reported issues had been addressed, and assign appropriate determination type for each feedback item. We understand that some items may still appear during Production Simulation. In many cases, these items are already scheduled for updates in upcoming releases, are in progress, or require further validation to ensure the solution meets user expectations. Production Simulation is intended to provide counties with another opportunity to confirm whether previously reported items have been resolved and to surface anything that still needs attention. Our goal is to ensure counties feel heard and that feedback from all EUST cycles is thoroughly considered as we prepare for rollout.

A: Users were contacted to request the additional information needed to accurately triage and prioritize the issue. If no response was received, the item remained categorized as 'Unable to Replicate' because the project team could not reproduce the issue without further details.

A: These lists were shared as part of the EUST 3 Report Out presentation – please reference this document for the itemization of the essential, refinement, and enhancement development tickets produced by EUST 3 feedback.

Regarding training materials, the Training Team will incorporate updates based on the functionality available at the time materials are finalized. Any changes implemented after training materials are completed will be captured in supplemental job aids, release notes, or updated training content as needed prior to Go‑Live. This ensures training remains accurate and aligned with the final solution.

A: A report will be shared in the following weeks after EUST 3 ends that will compile, analyze, and summarize the EUST 3 feedback to stakeholders. More information about the report will be shared toward the end of EUST 3.

If you have any additional questions regarding EUST 3, please contact the EUST Team.