Step 2: Running Report QoR Assessment - Step 2: Running Report QoR Assessment - 2026.1 English - UG938

In this step, you run the report_qor_assessment command on the open design. This step can be performed after any stage of the implementation process: synth_design, opt_design, place_design, phys_opt_design, and route_design. It provides an assessment score that indicates the likelihood of the design closing timing, as well as a quick first analysis returning items that need to be further investigated.

1. With the design open, click Reports > Report QoR Assessment....
2. In the Report QoR Assessment dialog box, select Report Passing Metrics, then click OK.
   
   
   The equivalent Tcl command is:

   report_qor_assessment -exclude_methodology_checks -name qor_assessments -max_paths 100 -full_assessment_details

   This opens the assessment report, which contains three main sections:
   • Assessment summary
   • Difficult timing paths requiring investigation
   • Objects with DONT_TOUCH properties that prevent tool optimizations
3. In the first section of the report, select RQA Summary.
   
   

   This section shows the score marked as "2 - Implementation may complete. Timing will not meet". It also recommends running report_qor_suggestions. The RQA command detects when suggestions are available and provides guidance to review them.

4. Select Assessment Details.
   
   

   This section lists the items that have led to the assessment score of 2. Because the option to Report passing metrics was selected, items marked as OK are shown. Typically, only items marked REVIEW are displayed. In this example, you can see WNS and TNS metrics marked for review, as well as paths exceeding their net/LUT budget.

   Timing paths usually reflect the values that are achievable in the best-case scenarios. Not all paths can meet these values. Net and LUT budget checks substitute net or LUT values with more typical values and penalize paths that are more challenging due to a netlist profile or a resource being less sparse. As a result, two checks performed under this item. Review all of these paths before continuing.

5. Select Net/LUT budget under Challenging Timing Paths.
   
   

   Scroll across the screen to view all reported path characteristics. The following items are of particular interest:

   Net Check Slack

   The slack when the path is substituted with higher net delay values.

   LUT Check Slack

   The slack when LUTs are substituted with higher LUT delay values.

6. Double-click on the path to open the Timing Path report. You can also press F4 to view a schematic. All of these items use standard Vivado cross-probing. At this stage, you can also explore other sections in the report.
7. In the Design Runs window, select impl_1, expand the Implementation Run Properties window, and click the Properties tab. Locate the MIN_RQA_SCORE property.
   
   

   When the MIN_RQA_SCORE property is set, an implementation run is terminated if RQA is executed and the assessment score is less than the value specified. As the minimum RQA score is 1, MIN_RQA_SCORE must be set to 2 or greater to have an impact.

   Edit the value of MIN_RQA_SCORE and set it to 3.

8. Next, the implementation run generates a QoR Assessment report.
   In the implementation Run Properties window, go to the Reports tab. In the Report Strategy drop-down menu, select the Timing Closure Reports Strategy.

   Note: This is one method to configure the run to generate the report. Other methods are:

   1. Creating a custom report strategy.
   2. Adding report_qor_assessment to a Tcl hook. This must run the report in the run directory to be effective.
9. Launch the impl_1 run.
   After opt_design is complete, the report_qor_assessment command runs. If the score is below the threshold, the run should terminate. The following message appears in the Design Runs status column:
   
   
   The log file contains the following message:

   
   INFO: [runtcl 7-1] RQA Score (opt_design): 2.000  (RQA score tolerance: 3)
   ERROR: [runtcl 8-1] Flow terminated - RQA score value 2.000, is below RQA_MIN_SCORE 3 at opt_design step. Please evaluate the QoR Assessment report for more information on the score and next steps to take.
   

   The following message appears when the flow successfully passes the check:

   
   INFO: [runtcl 7-1] RQA Score (opt_design): 2 (RQA score tolerance: 2)
   INFO: [runtcl 9-1] Flow continues - RQA score threshold met after 'opt_design' step

10. To revert the changes, update MIN_RQA_VALUE to 1, set the Report Strategy back to Vivado Implementation Default Reports, and reset the run.