# Team performance in Reports

> Reports, Team shows each person's deals owned and advanced, first reply, tasks on time, reviews and outcomes, built from work already recorded.

Source: https://delsivo.com/help/pipeline-and-committee/team-performance · Updated 2026-11-07

## Key takeaways

- Reports, Team has one row per Admin, Partner and Analyst for the period you choose, built from work Delsivo already records.
- Each column counts a step a partner asks about, such as deals advanced, first reply on inbound, tasks on time, answers reviewed and outcomes.
- Committee votes are never shown. The only committee number is how many reviews came in by the packet's due date.
- Admins and Partners see everyone and a top three for one measure; an Analyst sees only their own row next to the team median.
- Admins can export the table as CSV, and every export is recorded in the activity log.

**Team** in Reports shows who moved the pipeline in the period: who advanced deals, how quickly founders on their inbound heard back, whether tasks and committee reviews came in on time, and how far the deals they own got. Click **Reports** in the sidebar, then the **Team** tab.

Every number comes from work your team already does in Delsivo: stage moves, tasks, founder requests, interview reviews, claim labels, committee memos and reviews, and decision messages. Nobody fills in anything for it.

## Choose the period

The **Period** above the tabs applies here too: **Last 30 days**, **Last 90 days**, **Last 6 months**, **Last 12 months** or **All time**. On the Team tab the period starts at midnight in your fund's time zone, so a task finished just after midnight on the first day counts.

## The leaderboard

Admins and Partners see a card with the top three people for one measure, worded plainly, for example **Most deals advanced in the last 30 days**. Switch the measure with **Deals advanced**, **First reply**, **Tasks on time**, **Answers reviewed**, **Claims resolved** or **Picked up**.

- People with nothing to show for a measure don't appear.
- **First reply** lists the lowest median, and only people with at least three answered inbound deals, so one quick pass doesn't lead.
- People with the same number share a rank.

Read it alongside the table: a high count isn't always better work.

## The columns

Hover over or tab to any column heading for its definition. Click a heading to sort by it; click again to reverse. Work is credited to the person who did it, and outcomes to the deal's owner today.

| Column | What it counts |
|---|---|
| **Deals owned** | Deals they own today that arrived in the period, moved in it, or still wait in an open stage |
| **Advanced** | Deals they moved forward to a later stage in the period. Passes, revisits, reopening a passed deal and steps back don't count. Hover for how many reached each stage, and the line shows when the moves happened |
| **First reply** | Median days from arrival to the team's first move, on inbound deals they own that arrived in the period, with how many are still waiting |
| **Picked up** | Deals they took from the inbound queue, plus intake emails and WhatsApp pitches they turned into deals |
| **Tasks on time** | Tasks finished by their due day in the period, out of those with a due day, with how many of their open tasks are overdue now |
| **Requests sent** | Founder requests they wrote that were sent in the period |
| **Answers reviewed** | Founder answers they accepted or sent back for changes |
| **Interviews reviewed** | Interviews they rated or whose AI assessment they reviewed, with the number of ratings. Never the ratings themselves |
| **Claims resolved** | Claims they labelled Corroborated or Disputed |
| **IC memos** | Committee memos they started |
| **IC reviews on time** | Committee packets due in the period where they were a reviewer, and how many they submitted by the due date |
| **Decisions sent** | Pass, not now and invest messages they wrote that were sent to founders after approval |
| **Outcomes** | Of the deals they own that arrived in the period: how many reached First meeting, Diligence, Committee, and Invested |

The last row, **Team median**, is the middle value of each column across the deal team, counting people with zero. First reply uses the people who have one.

Notes, views and messages aren't counted. They measure activity, not progress.

## Who sees what

| Role | What they see |
|---|---|
| Admin, Partner | Every Admin, Partner and Analyst, the team median and the leaderboard |
| Analyst | Their own row and the team median. No one else's name or numbers |
| Committee member, Member | No Team tab |

Committee members don't get a row: the table is for the people who work the pipeline. Delsivo support, when you've given read-only access, can open the Team tab but can't export.

## Export the table

Admins see **Team** under **Export**. It downloads the table for the period you chose as a CSV file. Every export is recorded in [the activity log](/help/team-and-settings/exports-and-activity-log) with who exported, the period and how many rows. For the pipeline numbers themselves, see [Pipeline reports and exports](/help/pipeline-and-committee/pipeline-reports).

## Frequently asked questions

### Can anyone see how I voted in committee?
No. The Team tab only counts whether your review came in by the packet's due date. Votes, scores, comments and recusals are never shown or exported.

### Why does a partner have few deals advanced?
Advances are credited to whoever made the stage move. If an analyst moves the deal after the partner meeting, the analyst gets it. The deal's outcomes still count for its owner.

### Does Delsivo rate people?
No. The Team tab shows counts and medians from your own fund's work. There are no scores, badges or comparisons with other funds, and it doesn't measure the quality of a memo or a call.