> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/design-studio-array/product-guides/assay-design/review-design.md).

# Review Design Summary

When the design completes, DesignStudio shows the design summary in the Review and Order Design screen.

* To download the created files for troubleshooting, select **Download Files**.
* To upload new target files for the design tool to validate, select **Upload New Targets**.\
  \
  The design summary includes the following items:
  * Number of assays submitted.
  * Number of assays designed.
  * Number of assays excluded.
  * Options selected.
  * Content breakdown by species (For Genotyping designs on XT platform).
  * Normalization bins and total bead count for selected species. (Genotyping ONLY).\
    \
    When you are ready to order your products, contact Illumina Customer Care.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/design-studio-array/product-guides/assay-design/review-design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.