# Pass with a reason, then track passed deals against milestones

> Pass and revisit tracking is planned for a later Delsivo release. Today's design already requires a reason when a deal moves to Passed. The later feature lets you track passed deals: record milestones that would change your mind, such as three pilot conversions, compare founder updates against them, and get an alert linked to the change. Reopening a deal is always a person's decision.

Source: https://delsivo.com/features/pass-and-revisit · Updated 2026-11-06 · Planned, not available yet

## Key takeaways

- Planned for a later release. Passing with a recorded reason is part of the core deal lifecycle.
- Milestones are written at the time of the pass, in plain words.
- Founder updates are compared to those milestones, and alerts link to what changed.
- Reopening keeps the original decision. Nothing reopens on its own.

## How to track passed deals without losing the history

A pass is a decision with a reason, not a deletion. The deal keeps its deck versions, claims, interview and requests, and the pass rationale sits on the record with who decided and when. The suggested lifecycle has two side states, Passed and Revisit, and authorised users can reopen a passed deal without rewriting the original decision.

## Writing revisit milestones

Milestones are the specific evidence that would make the deal worth another look. Good ones are measurable and tied to the reason you passed.

| Pass reason | Revisit milestone |
| --- | --- |
| Pilots not converting | Three pilot customers converted to paid contracts |
| Too early for our cheque | A priced round led by another investor |
| Single founder, no technical lead | A technical cofounder or senior hire joins |
| Thesis mismatch on geography | Revenue from a market in our thesis |

## From founder update to a reopened deal

1. A founder sends an update through your portal, or an analyst adds one.
2. Delsivo compares it to the recorded milestones and suggests which, if any, look met, citing the update.
3. An alert reaches the deal owner with a link to the underlying change.
4. The owner reviews the evidence and decides whether to move the deal to Revisit or reopen it.
5. The reopening is logged with its own reason. The first pass decision is kept as it was.

## What the later design leaves out

- No automatic reopening, and no message to the founder without approval.
- No scraping of founders' social posts. Updates come through your portal or your team.
- Pass emails stay written and approved by your team.

## Frequently asked questions

### Can I record a pass reason in the pilot?

The deal lifecycle in the pilot design requires a reason for a pass. Milestones, update comparison and alerts are planned for a later release.

### Will founders know their milestones?

Only if your team tells them. Milestones are internal notes on the deal unless you choose to share them in your pass message.

### Does a met milestone reopen the deal?

No. It creates an alert for a person to review. Reopening is always a recorded human decision.

### Can the same company apply again?

Yes. Duplicate detection suggests linking the new application to the passed deal, and an analyst confirms the merge so history is kept.

## Related pages

- [Duplicate startup applications](https://delsivo.com/features/duplicate-detection)
- [Weekly partner pipeline brief](https://delsivo.com/features/partner-briefings)
- [Revisit passed startups](https://delsivo.com/use-cases/revisiting-passed-deals)
- [How it works](https://delsivo.com/how-it-works)