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

# Case Progress

Configure the Case Progress pipeline used to show where Cases are within your organization's workflow.

Case Progress represents where a Case currently sits within your organization's workflow.

Each organization can configure a sequence of Progress stages that reflects how work typically moves from intake through completion.

For example, a Case Progress pipeline might include:

* Pending
* Processing
* Preservation
* Collection
* Analysis
* Reporting
* Case Completed

The configured stages appear across the Case as a visual pipeline, making it easy to see where the Case currently sits in the overall process.

### Case Progress as a Workflow Pipeline

Case Progress is designed to represent your organization's operational workflow.

As work advances, users can update the Case to the appropriate Progress stage. The Case Progress bar provides a quick visual representation of that position.

Different organizations may configure very different pipelines depending on the type of work they perform.

A digital forensics lab may organize Progress around collection, examination, analysis, and reporting, while a corporate or legal team may use stages that reflect investigation, preservation, review, or other internal processes.

See [**Cases**](/monolith/using-monolith/case-management/cases.md) for more information about managing Case information and workflow.

### Case Progress vs. Case Status

Case Progress and Case Status are separate concepts.

**Case Progress** answers:

> Where is this Case within our workflow?

**Case Status** answers:

> What is the overall state of this Case?

For example, a Case may have:

* **Status:** Active
* **Progress:** Analysis

The Case can remain Active while moving through multiple Progress stages.

See [**Case Statuses**](/monolith/using-monolith/settings/case-statuses.md) for information about configuring Case Status options.

### Case Progress vs. Completion Metrics

Case Progress is also separate from the **My Progress** and **Total Progress** metrics shown on a Case.

The Case Progress pipeline is manually configured and identifies the current workflow stage.

My Progress and Total Progress are calculated from work recorded within the Case, including supported completion information from:

* Tasks
* Evidence Items
* Quality Assurance Reviews

These metrics provide different information and should not be treated as the same measurement.

### View Case Progress Items

The **Case Progress** settings page displays the stages currently configured for your organization.

Each Progress Item also shows the number of Cases currently associated with that stage.

The order shown in Settings determines the order in which the stages appear in the Case Progress pipeline.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2FEkVcVaDNsbgAAODVXUf1%2FScreen%20Recording%202024-01-25%20at%209.30.18%20AM.gif?alt=media&amp;token=a1667ce1-1ddf-4b82-898e-e7f5139ec08a" alt=""><figcaption><p>Case Progress Bar</p></figcaption></figure>

### Reorder Case Progress Items

Case Progress Items can be rearranged to match the order of your organization's workflow.

To change the order:

1. Locate the Progress Item you want to move.
2. Drag the item to the desired position in the list.
3. Repeat as needed until the stages reflect your workflow.

The order from top to bottom in Settings is reflected from left to right in the Case Progress bar.

This makes it possible to design a workflow that follows the natural sequence of work performed by your team.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2FZxrOdA3MU7DLWBwfu3Ez%2Fdrag1.gif?alt=media&amp;token=58dccf50-fb14-4c94-bd00-4edfdd5459fd" alt=""><figcaption><p>Reorder case progress items</p></figcaption></figure>

### Create a Case Progress Item

To add a new Progress stage:

1. Select **Create Case Progress**.
2. Enter the name of the new Progress Item.
3. Select **Create Case Progress** to save it.

New Progress Items are added to the configured workflow and can then be repositioned using drag and drop.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2FxvUgMDZZ2nbJfJ8aBqbj%2FScreenshot%202024-01-25%20at%209.37.59%E2%80%AFAM.png?alt=media&amp;token=d5dea327-ad83-4a8d-984d-635f7e32a3d7" alt=""><figcaption><p>Create Progress Item</p></figcaption></figure>

Choose Progress names that clearly describe meaningful stages of work.

### Delete a Case Progress Item

Progress Items can be deleted when they are no longer needed.

<figure><img src="https://2683670198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCD1iskOdIm8E2TpCd9iZ%2Fuploads%2F6D2FN5X2HLNTiRGvqgeo%2FScreenshot%202024-01-25%20at%209.38.08%E2%80%AFAM.png?alt=media&amp;token=1b8006d9-4053-475d-b91f-831ef91c227a" alt=""><figcaption><p>Progress Items</p></figcaption></figure>

If Cases are currently associated with the Progress Item being deleted, those Cases must be reassigned to another existing Progress stage before deletion can be completed.

{% hint style="warning" %}
Review the Cases associated with a Progress Item before deleting it. Existing Cases must be reassigned so their current workflow position remains represented.
{% endhint %}

### Recommended Practices

* Configure Case Progress around the major stages of work performed by your organization.
* Keep the pipeline simple enough that users can quickly understand where a Case sits.
* Use Progress stages for workflow position rather than creating additional Case Statuses for every step in the process.
* Arrange Progress Items in the order work normally occurs.
* Use names that are meaningful to the teams working Cases.
* Review the pipeline periodically as your organization's processes change.
* Avoid creating unnecessary stages that make the Progress bar difficult to interpret.

### Related Documentation

* [**Cases**](/monolith/using-monolith/case-management/cases.md)
* [**Case Statuses**](/monolith/using-monolith/settings/case-statuses.md)
* [**Evidence Progress**](/monolith/using-monolith/settings/evidence-progress.md)
* [**Tasks**](/monolith/using-monolith/dashboard/tasks.md)&#x20;