> 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/planning.md).

# Project Planning

Sketching, scheduling, and launching projects, studies, and assays before the work starts

The **Project Planning** page shows everything your organization is running, and everything it is about to run, as a single tree of projects, studies, and assays. Use it to sketch out upcoming work, put dates and owners against it, and then launch it when you're ready.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FbNsCCHS6G9iZkBMvtauo%2Fimage.png?alt=media&amp;token=a157e44e-facf-4992-b9de-5f0887ed1ac0" alt=""><figcaption></figcaption></figure>

Planned work can sit in Lab Atlas for weeks before anyone starts it. Your team can see what's coming, the dates roll up so you can check a project's schedule holds together, and no storage folders or ELN entries are created until the work actually begins.

Click **Planning** in the sidebar, between **Activity** and **Projects**, to open the page. Every member of your organization can use it. Each person sees only the records they're allowed to see.

## How planned work moves forward

Every project, study, and assay you plan goes through the same steps.

{% stepper %}
{% step %}

### Draft

A rough idea, visible only to you. A draft has a name and a place in the tree, but no code or other attributes yet. Use drafts to try out a plan before showing it to anyone. Drafts don't appear in [Activity](https://docs.labatlas.com/using-lab-atlas/activity.md), and nobody is notified about them.
{% endstep %}

{% step %}

### In Planning

The plan is shared with the team. Moving a draft to **In Planning** gives it its code (for example `PRJ-101`), makes it visible to everyone who can see its parent, and notifies its owner and members. Nothing has been set up yet: no storage folder and no ELN entry.
{% endstep %}

{% step %}

### Active

The work has started. **Activating** a record creates its storage folder and any ELN entries, and sets its start date to today if one hasn't been recorded. From here, it behaves like any other project, study, or assay.
{% endstep %}
{% endstepper %}

Records only move forward. Once a record is In Planning, it can't go back to being a draft, and an active record can't return to planning. If a plan is dropped, archive the record instead (see [Archiving](#archiving)).

{% hint style="info" %}
You don't have to use Planning. The **New Project**, **New Study**, and **New Assay** forms still let you choose **Start now** to create and activate a record in one step. To create a planned record from those forms, choose **Plan for later** instead.
{% endhint %}

## The project tree

The page lists projects, with their studies nested underneath and assays under those. Each record's tasks are listed last under it. Projects start expanded and everything below them starts collapsed. A collapsed row shows a count of what it contains, such as *3 studies · 1 planning · 2 tasks*.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2F2QBQfHOe5bFaOtfRdLls%2Fimage.png?alt=media&amp;token=2ea8d6d3-fe40-4a97-aea9-4810e2eef327" alt=""><figcaption></figcaption></figure>

Each row shows:

* **Name** — with the record's code (drafts show **Private** instead) and a lock icon if the record is locked.
* **Status** — Draft, In Planning, Active, and so on.
* **Owner** — the person responsible for the record.
* **Projected** — the planned start and end dates. Tasks show their due date instead.
* **Last updated**

Switch between **Tree** and **Timeline** at the top of the page. The [Timeline](https://docs.labatlas.com/using-lab-atlas/planning/timeline.md) shows the same records as bars on a calendar.

### Finding records

Use the toolbar to narrow the tree:

* **Filter by name or code**
* **Owner**: **Anyone**, **Me**, or a specific person.
* **Status**: a specific status, or **Not yet active** to see everything still in Draft or In Planning.
* **Sort**: **Projected start** (the default), **Name A–Z**, **Recently created**, or **Recently updated**. Lab Atlas remembers your choice.
* **Show tasks** / **Hide tasks**. Tasks only appear when the Status filter is set to all statuses.

When a filter matches a record deep in the tree, its parents stay visible, greyed out, so you can see where the match sits. **Clear filters** resets everything except your sort order. **Collapse all** folds the tree back to projects.

{% hint style="info" %}
You can work through the whole tree with the keyboard. Use the up and down arrows to move between rows, right and left to expand or collapse, and **Enter** to open a record. **Shift + F10** opens the row menu.
{% endhint %}

## Adding planned work

Hover over a project or study row to show **+ Study**, **+ Assay**, and **+ Task** buttons. The same options are in the row's **…** menu. A new row appears in the tree for you to type a name into. Choose **Draft** (the default) or **In planning**, then press **Enter** to save it and start the next one. Press **Esc** to stop.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FoEj4ghLAXWJvbRW2ybxd%2Fimage.png?alt=media&amp;token=bafcc8d3-83c7-44de-abc2-1bf9f36443f1" alt=""><figcaption><p>The planning record contect buttons. Click the '...' button for more options.</p></figcaption></figure>

Anything under a draft must also be a draft. You can't add studies, assays, or tasks under a locked record, and you can't add assays to a study that is still being set up.

**To plan a new project**, click **New Project** at the top of the page. Choose **Plan for later**, and save it as either a draft or **In Planning**. Super Users and above can also use the **+ Project** link under the tree, which creates a draft. A project needs a code before it can move to In Planning, and you can set this in the details panel while it's a draft.

## Editing a record

Click a project, study, or assay to open its details panel on the right. There you can change:

* The **name** and **description**.
* The **owner** (see [Owners](#owners) below).
* The **projected start** and **projected end**. Once a record has real start and end dates, those are shown instead.
* A project's **visibility** and, while it's a draft, its **code**.
* An assay's **assay type**, while it's still being planned.
* **Activation settings**: where the record's storage folder and ELN entries will go when it's activated. See [Activating records](https://docs.labatlas.com/using-lab-atlas/planning/activating-records.md).

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FzuROfHFBHggW1WYa2hxn%2Fimage.png?alt=media&amp;token=c456326a-a9a1-4a76-8909-1733e3b48cb7" alt=""><figcaption><p>Editing a draft study</p></figcaption></figure>

Nothing saves until you click **Save Changes**, and **Cancel** discards your edits. Click **Open** to go to the record's full page. For draft records, this will take you to the full form page to complete the record creation.

Click a task to open the same task panel used on the [Tasks](https://docs.labatlas.com/using-lab-atlas/tasks.md) page, where you can update, complete, or delete it.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2F2MZvuE2g67LYIjCf4YIg%2Fimage.png?alt=media&amp;token=958bb58a-041e-46e6-b767-1dab15e16cf5" alt=""><figcaption><p>Creating a task</p></figcaption></figure>

### Dates roll up

A parent's projected dates always cover its children. If you give a study an end date later than its project's, the project's end date moves out to match. The details panel warns you before you save, for example: *"Saving will extend PRJ's projected end to 12 Mar 2027."*

Draft dates don't count until the draft moves to In Planning. Because a projected date can't be cleared once set, pick a new date instead.

### Owners

Every record has one **owner**, the person accountable for it. The owner must be a member of the project, either directly or through one of the project's teams, so the picker only lists project members. If you pick someone who isn't yet a member of that study or assay, Lab Atlas asks to confirm and adds them. The new owner gets a notification.

Only the current owner or an Organization Admin can change the owner. The owner can't be removed from the record's members; transfer ownership first.

## Moving a draft to In Planning

When a draft is ready to share, open it and click **Move to In Planning**. Its parent must already be In Planning or active. Only the person who created the draft can do this.

The record gets its code, becomes visible to the team, and its owner and members are notified.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FHLDb2uXF5Sp6770wFM9g%2Fimage.png?alt=media&amp;token=de923d55-042a-4270-b1be-6fc8c2c20da5" alt="" width="375"><figcaption><p>Click the button at the bottom of the panel to move a draft record to 'In Planning'</p></figcaption></figure>

## Duplicating

To reuse an existing plan, open the row's **…** menu:

* **Duplicate record** copies the record as a new private draft next to the original, named *Copy of …*.
* **Duplicate branch** copies the record and every study and assay beneath it. This is offered only when there are studies or assays to copy.

A copy keeps the owner, description, assay type and fields, members, projected dates, and activation settings. Tasks are copied as open, unassigned, and without due dates. The code, lock, actual dates, notes, files, and Activity are not copied. Other people's drafts in the branch are left out.

Copies are always your own private drafts, so you can adjust them before anyone else sees them.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FrCGeW8n3m6SuIU08Evm9%2Fimage.png?alt=media&amp;token=c6141fb7-18e6-4c5c-8134-8e3b76b80aae" alt="" width="563"><figcaption><p>You can duplicate individual records or whole branches from the contect menu.</p></figcaption></figure>

## Locking a record

Lock a record to stop it changing: for example, once a study is finished and signed off, or while a plan is under review. Use **Lock** in the details panel's **⋮** menu, or in the record page's **Actions** menu. A lock covers the record and everything beneath it.

Locked rows show a lock icon. Their details panels can't be edited, and they say which record holds the lock. Locked bars on the [Timeline](https://docs.labatlas.com/using-lab-atlas/planning/timeline.md) can't be dragged. See [Locking Records](https://docs.labatlas.com/using-lab-atlas/locking-records.md) for what a lock prevents and who can set one.

<figure><img src="https://2057412998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FglJC7nRAfEL7RcemHr0z%2Fuploads%2FaEFNF5mkelcGt6slquek%2Fimage.png?alt=media&amp;token=432c5c53-22b1-4d25-8fc2-253bbeadcef4" alt="" width="563"><figcaption></figcaption></figure>

## Archiving

Use **Archive** in the row's **…** menu to retire a record that's no longer going ahead. The record and everything under it is hidden, and can be restored later.

To get rid of a draft entirely, use **Delete draft** instead. This permanently deletes the draft and everything under it. Only the draft's creator or an Organization Admin can delete it.

## Who can do what

| Action                                                      | Who                                                                                                        |
| ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| See a record on the Planning page                           | Anyone who can see it elsewhere in Lab Atlas. Drafts are visible only to their creator.                    |
| Plan, edit, duplicate, or activate a **study** or **assay** | Anyone who can contribute to its project.                                                                  |
| Plan, edit, duplicate, or activate a **project**            | **Super Users and above** who can contribute to it.                                                        |
| Move a draft to In Planning                                 | The draft's creator only.                                                                                  |
| Delete a draft                                              | The draft's creator, or an Organization Admin.                                                             |
| Change the owner                                            | The current owner, or an Organization Admin.                                                               |
| Lock or unlock                                              | The record's owner, or an Organization Admin. For a project, the owner must also be a Super User or above. |

### For administrators

* **Other people's drafts stay hidden on the Planning page, even for Organization Admins.** To review them, use the **Include other members' drafts** switch on the Projects, Studies, or Assays list. From there an Organization Admin can open or delete another person's draft, but only its creator can move it to In Planning.
* **Activation depends on your integrations.** Set a default storage location for the organization, and connect Benchling or CDD Vault if records should get ELN folders and entries. A problem with a storage integration will stop projects that use it from activating. See [Activating records](https://docs.labatlas.com/using-lab-atlas/planning/activating-records.md#for-administrators).
* **Planning shows up in Activity.** Moving a record to In Planning, activating it, a failed activation, and changes to owners and projected dates are all recorded in the **Planning** group on the [Activity](https://docs.labatlas.com/using-lab-atlas/activity.md) page. Lock and owner changes are also recorded in the [Audit Log](https://docs.labatlas.com/managing-your-organization/audit-log.md).
