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

# Read the pipeline report

> See how contacts move through your pipeline stages: how many enter each stage, move on, are won or lost, and how long they stay.

**Pipeline** is a tab on **Reports**. Your [pipeline board](https://docs.dmly.io/contacts/pipeline-stages.md) only shows where each contact is right now; this report shows how they got there. For each stage it counts how many contacts entered it, how many moved on, how many went on to be won or lost, and how long a contact typically spends in it.

It only reads. Nothing here moves a contact or changes a stage.

## Before you start: mark your won and lost stages

The report can only count wins and losses if it knows which stages mean them. On the pipeline board, open a stage's settings (the cog on its column) and set **Counts as** to **Won** or **Lost**. Leave every other stage on **In progress**.

**1. Open the pipeline**

Go to **Contacts** and switch to **Pipeline View**.

**2. Open a stage's settings**

Select the cog at the top of the column you close deals in, for example **Customer**.

**3. Choose what it counts as**

Set **Counts as** to **Won**, then **Save**. Do the same with **Lost** for a stage such as **Not interested**, if you keep one. The column header then shows a small **Won** or **Lost** label.

A new workspace's **Customer** stage already counts as **Won**. Stages in a workspace created before this report existed start on **In progress**, so until you mark one the **Won** and **Lost** figures read zero, and the report says so.

## Open the report

**1. Open Reports**

In the sidebar, under **Configurations**, select **Reports**, then the **Pipeline** tab. It sits between **Finance** and **Ads**. You can also select **Pipeline report** at the top of the pipeline board.

**2. Pick your dates**

Set **From** and **To**. Leave both blank and the report covers the last 30 days. Days follow your business's timezone, not UTC.

**3. Filter by teammate**

**Assigned to** narrows the report to the contacts one teammate held, or to **Unassigned** contacts. It uses whoever the contact was assigned to when they entered each stage, so reassigning a contact later does not rewrite who held the earlier stages.

## The cards

| Card | What it counts |
| - | - |
| **Stage entries** | Every time a contact entered a stage in your dates. A contact who passed through three stages counts three times. |
| **Won** | Contacts who entered a stage marked **Won** in your dates. Each person counts once, even if they were moved in and out of it. |
| **Lost** | The same, for stages marked **Lost**. |
| **Win rate** | Won divided by won plus lost. A dash until something has been won or lost. |
| **In a stage now** | Contacts sitting in a stage at the end of your dates (right now, if your dates end today). |

## The stage table

One row per stage, in the same left-to-right order as your board.

| Column | Meaning |
| - | - |
| **Entered** | Contacts who entered this stage in your dates. Hover the number to see how many of them moved back, were removed from the pipeline, or are still in the stage. |
| **Moved on** | Of those, how many have since moved to a stage further right on the board. A move into a **Lost** stage is not counted here; it counts under **Lost**. |
| **Conversion** | Moved on divided by entered. Blank for a **Won** or **Lost** stage, because that is where a deal ends rather than a step it passes through. |
| **Won** / **Lost** | Of the contacts who entered this stage, how many have since reached a **Won** or **Lost** stage. |
| **Avg time** / **Median time** | How long contacts spent in this stage, counting only stays that ended in your dates. |
| **In stage now** | Contacts still in this stage at the end of your dates. |
| **Avg time so far** | How long those contacts have been in the stage so far. |

> [!NOTE]
>
> **Entered, Moved on, Won and Lost follow the same people.** The report takes the contacts who entered a stage in your dates and follows them up to today. Someone who entered on the last day of your dates and moved on the next morning still counts as moved on.
>
> **Times only count finished stays.** A contact still sitting in a stage has no finished time yet, so they count under **In stage now** and **Avg time so far** instead of pulling the average down. The median is the middle stay, which is often a better guide than the average when one deal sat for months.

## When the history starts

DMLY records a contact's stage moves from the day this report was added to your workspace. Earlier moves were never recorded, so they cannot be reported. The report says, at the top, the date its history starts.

Contacts who were already in a stage on that day count under **In stage now**, but nobody knows how long they had already been there, so they are left out of every time figure and are not counted as entering that stage. The report says this too, with the date. Once such a contact moves to another stage, that move is recorded and counted normally.

## What counts as a move

Every way a contact changes stage is recorded: dragging a card on the board, the **Pipeline stage** picker on a contact, the contact form, bulk **Set stage**, the **Update Contact Stage** automation step, the A.I. **Move CRM stage** tool, the API, a CSV import that sets a stage, and creating a contact with a stage.

Three things end a stay without counting as a move, a loss or a finished time:

* **Removing the stage.** Clearing a contact's stage counts as **removed** (in the hover breakdown), and the stay counts as finished.
* **Deleting a stage.** Its contacts move to **No Stage**. Their stays end, but the deleted stage no longer appears in the report.
* **Merging two contacts.** The merged contact keeps both people's history. If they were in different stages, the duplicate's stay ends and is not counted as a finished time.

Deleting a contact removes their history with them, so they drop out of past figures too.

## Export

**CSV** downloads `pipeline-report.csv`: one row per stage with **Stage**, **Outcome**, **Entered**, **Moved on**, **Moved back**, **Removed**, **Still in stage**, **Reached won**, **Lost**, **Conversion %**, **Completed stays**, **Avg days in stage**, **Median days in stage**, **In stage now** and **Avg days so far**. Times are in days, to two decimals. **PDF** gives you the same report as a document. See [Export your data](https://docs.dmly.io/analytics/exporting-reports.md).

Exporting needs the **Export reports** permission; viewing the tab needs any Reports permission. See [Roles and permissions](https://docs.dmly.io/account/roles-and-permissions.md).

## Related

> [card] [Pipeline stages](https://docs.dmly.io/contacts/pipeline-stages.md)
>
> Set up your stages and mark which ones mean won or lost.

> [card] [Export your data](https://docs.dmly.io/analytics/exporting-reports.md)
>
> CSV, PDF and the combined workspace report.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.