VDR Kanban: Tracking Due Diligence Tasks
Think of the VDR Kanban as your deal checklist — not a document vault. It tracks what's been handed off, what's still pending, and what's under review. Here's how it works and where it fits in an actual diligence workflow.
What you'll learn
- ✓Understand how the task board maps to a due diligence workflow
- ✓Move tasks through the status pipeline
- ✓Use the board to communicate progress with clients
Step-by-step guide
What the VDR Kanban is and is not
The VDR Kanban is a task tracking board — it shows due diligence items by status. It is not a document storage system or a real virtual data room.
Each task has a title, category, optional due date, and a current status. Tasks move through four stages: Pending → In Progress → Review → Done. That's the full lifecycle.
Think of this as your internal checklist for what the client still needs to prepare, not a document vault. For actual document management, you'd still use your firm's existing VDR or shared drive.
Accessing the VDR board
From the report page, click the VDR button in the action panel. This opens the task board for that specific assessment.
Each task card shows the item title, category (e.g., Financials, Legal, Operations), and current status. If a due date is set, it's shown on the card.
Moving tasks through the pipeline
Click the advance button on any task card to move it to the next status stage. The transition goes in one direction: Pending → In Progress → Review → Done.
There's no way to move a task backward through stages — if a task needs to go back to In Progress from Review, you'd need to note that separately or recreate the task.
Task status changes are saved immediately. There's no undo. If you advance a task by mistake, note it in your client records and track it manually.
Using the board in client conversations
The VDR Kanban works well as a shared progress tracker you can reference on calls with your client. Walk through the board together: what's done, what's pending from their side, what's under your team's review.
It creates a natural structure for status update calls without needing to build a separate spreadsheet for each engagement.