> 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/library-preparation/amplicon-library-prep/library-preparation-amplicon-library-prep-faq-list/000005436.md).

# Turnaround time, throughput, and workflow requirements for COVIDSeq (RUO)

**What is the turnaround time for library preparation and sequencing?**

Library preparation time varies based on number of samples processed, extraction method, thermal cyclers, and techs available. See the Illumina COVIDSeq RUO Kits Reference Guide for incubation times per step.

1536 to 3072 samples can be sequenced in 12 hours on NovaSeq 6000 system using two SP or S4 reagent kits, respectively, or 384 samples in 12 hours using NextSeq 2000 P2 v3 reagent kits or NextSeq 500/550/550Dx (in Research Mode) High Output (HO) reagent kit.

**What is the recommended number of samples that can be sequenced per run?**

* iSeq 100: 8 samples per flow cell.
* MiSeq v2 flow cell: 30 samples per flow cell.
* MiSeq v3 flow cell: 48 samples per flow cell.
* MiniSeq HO flow cell: 48 samples per flow cell.
* NextSeq 500/550 or 550Dx (in RUO mode) High Output flow cell: 384 samples per flow cell.
* NovaSeq 6000 system SP flow cell: 384 samples per lane, 768 total samples per flow cell.
* NovaSeq 6000 system S4 flow cell: 384 samples per lane, 1536 total samples per flow cell.
* NextSeq 1000/2000 P2 flow cell: 384 samples per flow cell.
* **Note**: Lower pooling numbers are acceptable for surveillance use, depending on lab data needs.

**How many operators are needed for this workflow?**

This highly depends on sample pull through of lab. It is reasonable that one experienced tech could manually process 384 samples in two days, given the appropriate equipment is available (eg, multichannel pipettes, thermal cyclers, etc.). Due to plating requirements and lengthy time of ARTIC PCR, the number of thermal cyclers is often a bottleneck.

**How long can libraries be stored prior to sequencing?**

Up to 30 days at -25°C to -15°C. Illumina recommends sequencing libraries as soon as possible after pooling.

For more information, see[Illumina COVIDSeq RUO Kits Reference Guide](https://support.illumina.com/sequencing/sequencing_kits/illumina-covidseq-ruo-kits/documentation.html)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                              |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5436), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005436%20-%20Library%20Preparation%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/library-preparation/amplicon-library-prep/library-preparation-amplicon-library-prep-faq-list/000005436.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.
