Due diligence request list tracker

What this question usually means

The rewrite cluster is: request category, owner, due date, received evidence, and open follow-up. People also collapse requests into a single “pending” column. That hides who must act and whether evidence actually landed.

A tracker is a checklist with accountability. If due dates exist but owners do not, the list becomes a wish document. If received evidence is not linked to a file location, you cannot trace questions back to pages.

Materials or prerequisites

Bring the diligence checklist, company materials received so far, risk thresholds and decision criteria, and named owners on sell-side and buy-side. Include prior request emails or room notes if they name due dates or exceptions.

Use the same categories as your scope checklist so the tracker aligns with gap identification. Mixed taxonomies make duplicate requests and false closes.

Step 1: Group requests by category

Corporate, financial, legal, tax, IP, employment, privacy, and any custom lanes your criteria require. One section per category keeps owners and due dates comparable. Avoid one flat list of two hundred lines with no headers.

Step 2: Assign an owner per request line

Every line has one accountable owner — person or role — who can confirm delivery or explain delay. Shared inboxes are roles only if the audit trail still names who responded.

Step 3: Set due dates and dependency notes

Write the date the evidence is needed for the next review gate, not the date someone hoped to ask. If a line depends on another upload, link them so a partial parent does not mark the child received.

Step 4: Attach received evidence to locations

When a file arrives, record file name, version, folder or batch, and the checklist line it satisfies. Partial evidence stays partial until the owner or reviewer accepts completeness. Factrova uses these locations when tracing facts and questions.

Step 5: Keep open follow-up visible

Follow-up is a question or re-request with owner and target date — not a vague “chasing.” Close a line only when evidence is linked or scope is formally narrowed in writing.

Step 6: Sync the tracker in Factrova and sample one category

Describe the tracker in the conversation or paste a structured export. Ask for a readout on one category to verify owners, dates, and evidence links before you load the full room history.

Verification

For any open line, a reviewer can name category, owner, due date, what evidence arrived with location, and the follow-up question. Closed lines show linked files or a recorded scope change. No line should close on verbal assurance alone.

Limits that stay on the tracker

The workspace does not replace legal, investment, accounting, tax, compliance, or transaction advice. A professional reviewer confirms document scope, extracted facts, open questions, and final risk judgments. Factrova tracks supplied request state; it does not send legal hold letters, access live data rooms, or guarantee responses by due date.

Do not treat tracker completeness as deal readiness. Received evidence still needs fact tracing and reviewer judgment on separate paths.

What Factrova does in this workflow

Factrova holds request lines next to document locations and open questions in the conversation. It helps prepare a sourced question list for accountable review — not to replace counsel or investment committee process. Review a diligence sample to validate the tracker shape before full import.