How it works

From a folder of documents to a defensible evidence record

DiligenceControl assumes you already have the documents. Its job is to make the state of the evidence — sourced, missing, conflicting, reviewed — impossible to misread.

1. Organize the documents you were sent

Each deal starts from a checklist of requirements: offering memorandum, rent roll, T-12, operating statements, debt terms, and supporting diligence. Every requirement is received, missing, or reviewed — and a missing requirement stays visible instead of being quietly ignored.

2. Record facts with their sources

The multifamily template starts with about fifteen fields. Each one holds a value and unit, a reporting period or as-of date, the source document and version, a page, section, or table reference, a supporting excerpt, a proof label, and a review status. A missing value stays missing — it never becomes zero.

3. Show the arithmetic

Calculated fields such as physical occupancy and net operating income display their formula and the input fields they depend on, so a reviewer can check the math instead of trusting it.

4. Give every gap and conflict an owner

Conflicting figures and missing documents become exceptions with a severity, an owner, and a due date. A written response is not a resolution: accepting a resolution requires linked supporting evidence. Deferring requires a reason, and a deferred issue stays visible and is never counted as resolved.

5. Ask the counterparty

Draft a request against an exception, choose a recipient, and preview it. In this round, sending and responses are simulations inside the workspace — no email is delivered and no external link is created.

6. Record reviews and approvals

A reviewer accepts or rejects an evidence review or an issue disposition. Approval means acceptance of that review or disposition. It is not approval of an investment or a loan.

7. Handle revisions honestly

When a revised document arrives, the earlier version is preserved, changed fields are flagged, prior reviews that depended on them are marked as requiring re-review, and unresolved conflicts stay open until a person addresses them.

8. Assemble an Evidence Package

Generating a package creates a snapshot: deal identity and reporting date, coverage, key fields with proof labels and source references, calculations and inputs, open and deferred exceptions, accepted resolutions, approval and re-review status, the document version list, and an activity summary. Later edits do not change a snapshot you already generated — you generate a new version instead.

Proof labels

Source-confirmed

The value matches the cited document at the cited location. This does not establish that the underlying statement is true.

Customer-confirmed

A person on the deal team asserted this value. It is not yet matched to a document location.

Calculated

Derived from other evidence fields using the shown formula and input references.

Needs review

Recorded but not yet reviewed by a reviewer, or invalidated by a document change.

Roles we are building for

Role definitions are reserved in the data model and shown in Settings. Production authentication and permission enforcement are not enabled yet.

Account owner

Manages the organization, members, and templates. Can do everything an analyst, reviewer, and approver can do.

Analyst

Uploads documents, records evidence fields with source references, creates exceptions, and drafts counterparty requests.

Reviewer

Reviews evidence rows and proposed exception resolutions, and marks work as re-review when a document version changes.

Approver

Accepts or rejects an evidence review or an issue disposition, and signs off on an Evidence Package snapshot.

External respondent

A counterparty contact who receives a request and supplies a response or document. No access to the rest of the workspace.

Read-only viewer

Can read deals, evidence, and packages. Cannot change any record.

What DiligenceControl is not

It does not source deals, recommend or rank investments, make lending decisions, or promise returns. The customer retains responsibility for underwriting and for the decision.

Explore sample deal