Request states and reminders
What each founder request state means for your team and for the founder, when reminders go out, what they list, and what happens after the due date.
States
| State | What it means | The founder sees |
|---|---|---|
| Draft | Not sent yet. Only your team can see it | Nothing |
| Sent | Sent to the founder, who hasn't started yet | New |
| In progress | The founder has started answering | In progress |
| Submitted | The founder sent their answers. Review each item | Sent to the fund |
| Changes requested | Sent back to the founder with notes on some items | Changes requested |
| Complete | Every item is accepted. No more reminders | Complete |
| Overdue (shown beside the state) | Still waiting on the founder after the due date. The founder can still answer | The due date, as before |
| Expired | Only requests closed by the old rule, before due dates became targets. Set a new due date to reopen | Expired |
| Revoked | The founder's link no longer works | The request is no longer available |
When the founder may send answers in parts, a request stays In progress after each part, with the answers sent so far ready to review. It moves to Submitted when the last required answer arrives.
While a request is Sent, In progress or Changes requested, the founder's application status shows Information requested. When none is waiting on them, it goes back to what it was.
Reminders
You choose the cadence when you compose the request: Weekly (the default), Every 3 days or No reminders.
- Reminders go only while the request waits on the founder: Sent, In progress or Changes requested.
- They never go after the founder submits, once it's complete, or after it's revoked.
- Passing or closing the deal revokes every request still waiting on the founder (Sent, In progress, Changes requested), with its pending emails, in the same step. Answers already submitted stay, and drafts stay for your team. No request can be sent on a passed or closed deal until someone reopens it.
- Each reminder, Reminder: [title] for [your fund], lists only the questions still open and has a Continue answering button. A follow-up question that doesn't apply (its condition isn't met) is never listed.
- The first reminder comes 3 or 7 days after sending. Sending items back restarts the count.
- After the due date, reminders go at most weekly (even on Every 3 days), and stop three weeks after it. Then the request stays Overdue for your team to decide: set a new due date, or revoke it.
Delsivo checks every hour and never sends the same reminder twice.
Due dates are targets
A due date ends at the end of that day in your fund's time zone. It is a target, not a lock: founders are often busy, and a late answer is still worth having.
- If it passes while the request waits on the founder, the request shows Overdue to your team on the deal's Requests tab, the Requests page and the request itself.
- The founder's link stays open, and they can keep answering and send their answers, until someone at your fund revokes the request.
- Use Change the due date to set a new target. The founder sees it at once; no email is sent.
- A request closed by the old rule shows Expired. Use Reopen with a new due date to give the founder more time.
See Review a founder's answers.
Frequently asked questions
The founder submitted but one answer is wrong. Do reminders start again?
Only after you flag the item and click Send back to the founder. Then reminders follow the same cadence, listing the questions still open.
Can I change the reminder cadence after sending?
Not yet. Choose it in the composer before you send.
Something unclear or missing? Tell us