> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revilico.bio/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Pipeline Projects Effectively

> Organize pipelines, notes, and files by target using Revilico OS Projects, and track campaign status on a shared Kanban board with timeline view

## Overview

As your research scales across multiple targets, keeping track of which pipelines belong to which campaign — and where each one stands — can get messy fast. **Projects** in Revilico OS give you a dedicated hub for organizing everything related to a single target or initiative: pipelines, notes, files, and campaign status, all in one place.

This tutorial walks through creating a project, organizing pipelines and notes within it, and using the built-in Kanban board to track your campaign status from kickoff to completion.

<div style={{position: "relative", paddingBottom: "54.375%", height: 0}}>
  <iframe src="https://www.loom.com/embed/25da5043c86a4443921c163936f9419c" frameBorder="0" webkitallowfullscreen="true" mozallowfullscreen="true" allowFullScreen={true} style={{position: "absolute", top: 0, left: 0, width: "100%", height: "100%"}} />
</div>

[Managing Research Projects and Campaign Status — Watch Video](https://www.loom.com/share/25da5043c86a4443921c163936f9419c)

***

## When to Use This Workflow

Use Projects any time you're running research against multiple targets or initiatives and need a single place to organize the pipelines, files, and notes tied to each one — for example, keeping an **EGFR** project separate from a **BRCA1** project, each with its own campaigns, documentation, and status tracking.

***

## Step 1: Create a Project

<Steps>
  <Step title="Create a new project">
    Create a project and give it a clear name — typically the target or initiative it represents (e.g., `EGFR`, `BRCA1`, or a working name like `Testing` for a demo).
  </Step>

  <Step title="Understand the project hub">
    Once created, this project becomes the hub for everything tied to that target — pipelines, campaigns, notes, and files all live here going forward.
  </Step>
</Steps>

***

## Step 2: Organize Pipelines Within a Project

<Steps>
  <Step title="Open the command center">
    From within a project, use the command center to drag and drop in the pipelines or campaigns you want to maintain under that project.
  </Step>

  <Step title="Review pipeline details">
    Each pipeline entry shows details like the pipeline type (e.g., static docking screen), its name, and when it was conducted.
  </Step>

  <Step title="Open a pipeline">
    Click into any pipeline to view it directly.
  </Step>

  <Step title="Browse all projects">
    Click **Projects** to see and click through every project and its associated reviews. Selecting a project pops its data out into the central panel.
  </Step>
</Steps>

***

## Step 3: Share Projects and Manage Notes

<Steps>
  <Step title="Share with your team">
    Share a project with your team to give everyone an overview of all the files and pipelines associated with it.
  </Step>

  <Step title="Create and organize notes">
    Create new notes or folders within the project, or drag and drop existing notes in directly, to keep documentation and context alongside the work itself.
  </Step>

  <Step title="Attach project files">
    Drag and drop data associated with the target into the project through the data editor panel.
  </Step>
</Steps>

***

## Step 4: Track Campaign Status with the Project Board

Each project includes a Kanban-style board for tracking the status of every campaign tied to that target.

<Steps>
  <Step title="Open the project editor">
    Click to edit the project. Here you'll see all of the campaigns tied to it, where you can download data, view analytics, or add more pipelines.
  </Step>

  <Step title="Add a card for a prospective screen">
    Add a card for a screen you're planning — for example, a static docking screen against your target of interest. Give it a name (e.g., `Static Docking Screening`) and set its status to **To Do**.
  </Step>

  <Step title="Document the plan in the card description">
    Use the card description to log the campaign's background, notes, and protocols — for example, noting that you're running an EGFR screening campaign with two million compounds from a specific library (e.g., Enamine's REAL library) — so the rest of your team has full context.
  </Step>

  <Step title="Select an engine and assign an owner">
    Select the engine the campaign will use (e.g., RevPocket) and assign the card to a team member.
  </Step>

  <Step title="Create the card">
    Create the card. It can now be moved around the board by your team as work progresses.
  </Step>

  <Step title="Attach a pipeline once it's run">
    Once a screen has been run, attach its pipeline to the card — the pipeline doesn't need to be fully processed; it can be attached at any stage. This keeps the card's status tied directly to the underlying pipeline.
  </Step>

  <Step title="Add cards for pipelines already run">
    You can also add a card for a pipeline that already exists within the project — for example, labeling it `Test Again`, setting a target date, and assigning it to yourself or a teammate. These display slightly differently from prospective cards, since they represent completed runs rather than planned ones.
  </Step>

  <Step title="Move cards through your workflow">
    Move cards across statuses (e.g., **To Do → In Progress → Done**) as work is completed, giving your whole team a live, shared record of what's been done and what's still outstanding.
  </Step>

  <Step title="Use the timeline view">
    Switch to the timeline view to see campaign dates laid out visually and stay on track with deadlines across the project.
  </Step>
</Steps>

***

## Why This Matters

Projects turn a scattered set of pipelines, files, and notes into a single, organized campaign hub:

* One place to find every pipeline, note, and file tied to a given target
* A shared Kanban board that keeps your whole team aligned on what's planned, in progress, and done
* A running log of campaign background, protocols, and decisions — not just raw pipeline outputs
* A timeline view for staying on schedule across multiple concurrent campaigns

***

## Next Steps

* [**2D Structure MedChem Review**](/tutorials/medchem-review/2d-structure-medchem-review) — Triage RevBind results into a collaborative Compound Review session
* [**2D/3D Structure MedChem Review with Poses**](/tutorials/medchem-review/2d-3d-structure-medchem-review-with-poses) — Downselect compounds with 3D pose-level review
* [**RevScreen - Static & Flexible Docking**](/tutorials/rev-bind/static-flexible-docking) — Generate the pipelines you'll track within a project
