Key takeaways
- Stage changes, passes, overrides, merges, sent requests and file access are recorded with person and time.
- Passes and overrides can't be saved without a reason.
- Reopening a passed deal keeps the original decision rather than rewriting it.
- Audit and security logs live in a separate logs database, kept for one year.
Planned feature: not in Delsivo yet, and details may change before it ships.
What the deal audit trail records
| Event | What is stored |
|---|---|
| Stage change | From and to stage, person, time, reason |
| Pass or Revisit | Person, time and the required reason |
| Criterion override | Original result, new result, person and reason |
| Rubric re-run | Rubric version, model and prompt version, and the earlier run kept |
| Duplicate merge or dismissal | Records involved and who decided |
| Request sent or revoked | Recipients, approver, time |
| File upload, open or download | File version, person and time |
| AI suggestion accepted or dismissed | The suggestion, the person and the outcome |
Why reasons are stored with decisions
Six months after a pass, someone asks why. Without a record, the answer is whatever the partner remembers. With one, the deal shows the reason given at the time, who gave it and what the evidence looked like then. That matters when a company comes back, when a founder asks for feedback, and when your team reviews its own process.
Reopening a passed deal never edits the original decision. It adds a new entry, so both the pass and the decision to look again stay on the record.
How to read a deal's history
- 1Open the deal and go to Activity.
- 2Filter by type, such as decisions, overrides or file access.
- 3Click an entry to see the details, including the reason and any linked evidence.
- 4Follow links to the claim, rubric version or file version the entry refers to.
Where the logs are kept
More on how data is separated and protected is on security.
- Audit and security events are written to a separate logs database, not alongside deal data.
- Audit and security logs are kept for one year.
- AI call logs are kept for 90 days and hold no document text.
- Each fund's records are kept apart, and access follows the same permission check as the rest of the workspace.
Who sees the audit trail
Your fund's team members with access to the deal see its activity. Founders don't see internal history; they see their own application, requests and files. Guests, once guest access arrives in the first release, see only what is shared with them, and their access is itself recorded. Every change in the deal review queue and every override in the thesis fit report appears here.