> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-faq-list/000003093.md).

# How to obtain a NextSeq 1000/2000 v2 sample sheet?

A v2 sample sheet can be obtained from one of the following options.

1. A v2 sample sheet can be created in BaseSpace using Run Planning, with the following steps.
   * In BaseSpace Sequence Hub, select the **Runs** tab > **New Run** > **Run Planning** > **Local Mode** > **Export Sample Sheet**.
   * For this option, all sample and index information is entered in Run Planning, and is included in the exported v2 sample sheet.
2. A v2 Sample sheet template is available for download [here](https://help.connected.illumina.com/run-set-up/overview).

* * To manually fill the template, use a text editor program to alter the sections according to your chosen instrument or analysis. *Using a spreadsheet editor can cause errors with sample sheet validation and analysis.*\
    See resources below for more information:
    1. [Sample Sheet Structure](https://help.connected.illumina.com/run-set-up/overview/sample-sheet-structure)
    2. [Instrument Settings](https://help.connected.illumina.com/run-set-up/overview/instrument-settings)
    3. [Cloud Analysis Auto-launch Settings](https://help.connected.illumina.com/run-set-up/overview/auto-launch-settings)
    4. [Index Orientation Guide](https://help.connected.illumina.com/run-set-up/overview/index-orientation-guide)
    5. [Resources](https://help.connected.illumina.com/run-set-up/overview/resources)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #3093), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000003093%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-faq-list/000003093.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.
