> For the complete documentation index, see [llms.txt](https://docs.labatlas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labatlas.com/using-lab-atlas/studies.md).

# Studies & Assays

Creating and working with studies

## Overview

[Studies](https://docs.labatlas.com/introduction/key-concepts.md#studies) and [Assays](https://docs.labatlas.com/introduction/key-concepts.md#assays-and-assay-types) are the primary units of work in Lab Atlas and make up the bulk of record keeping, but how you choose to define and utilize them is entirely up to you ([we do provide some guidance](https://docs.labatlas.com/using-lab-atlas/frequently-asked-questions.md#how-should-i-define-studies-and-when-should-i-add-new-ones)). You generally want to think of assays as well-defined activities that have a standard protocol, which are expected to be completed within a short amount of time by only one or two people. Studies are a bit more open-ended and may cover a longer period of time & include more people, but should still have a clearly-defined goal.

When you are ready to perform some wet- or dry-lab work on a new study or assay, Lab Atlas should be the first place you go before getting started. The reason for this is that Lab Atlas will take care of some of the repetitive first steps in preparing the systems you are required to work within. When a study starts, Lab Atlas creates a few things for you:

* A unique [Code](https://docs.labatlas.com/introduction/key-concepts.md#study-and-assay-codes) that can be used to identify your study in the lab or in other systems.
* A folder and summary notebook entry in your linked electronic laboratory notebook system (eg. Benchling).
* A folder in your linked cloud storage service (eg. SharePoint or Amazon S3) for capturing documents & results.
* An optional source code repository in a connected Git server (eg. GitLab) for managing data science notebooks.

If you choose **Start now** when you create a study, all of this happens as soon as you save it. If you choose **Plan for later**, the study gets its code straight away, but nothing else is set up until it's activated.

## Planned and started studies

A study doesn't have to start the moment you create it. You can plan it ahead of time, and it then moves through the same steps as any planned record:

* **Draft**: a private sketch that only you can see. It has no code yet.
* **In Planning**: shared with the team and given its code. No storage folder or ELN entry exists yet.
* **Active**: the work has started, and its folder and notebook entries have been created.

Every study has an **Owner**, the person accountable for it. Planned studies also have a **projected start** and **projected end**, so your team can see when the work is expected to happen.

See [Planning](https://docs.labatlas.com/using-lab-atlas/planning.md) for how planned work moves forward, and [Activating Records](https://docs.labatlas.com/using-lab-atlas/planning/activating-records.md) for what happens when a planned study starts.

You can reference the below diagram for an example workflow for when and how to use Lab Atlas:

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FO1bFJRXr912Ov3kPOvsq%2Fimage.png?alt=media&amp;token=67db734d-3bd1-4abf-a7c2-d8516347c47c" alt=""><figcaption><p>Example study workflow</p></figcaption></figure>
