VDR BOUNDARY
Authorization & Evidence Access
Confirm organization and workspace boundaries, permitted participants, roles, and access to the selected deal evidence.
01
SECURITY AND DATA HANDLING
Review the environment before the evidence enters it.
Confidential deal evidence requires more than a generic security statement. Your security and data-processing owners review the actual source path, architecture, providers, access model and output route proposed for the pilot.
THE REVIEW SURFACE
Review the operating path.
The review is tied to the workflow and deployment being proposed. It happens before the team shares deal evidence.
PROVIDER TERMS
Deployment & Provider Handling
Review the actual architecture, configured model providers, data flows, and processing and retention terms for the target environment.
02
DATA RESIDENCY
Retention, Region & Deletion
Agree the applicable hosting region (US / EU), source and artifact retention, deletion behavior, and operational responsibilities.
03
HUMAN GATE
Review & Export Behavior
Confirm human review responsibilities, supported output gates, and the memo export path used for the selected workflow.
04
Institutional Governance
Trace evidence.
Control access.
Underlying is engineered for the confidentiality and compliance demands of institutional private equity and private credit firms.
Zero training on deal data, tenant isolation, and strict analyst verification gates to confidently deploy AI in production diligence.
Organization Isolation
Organization and Deal Room access boundaries
Zero Data Training
Provider training terms confirmed before intake
Role-Based Access Control
Strict deal room & member segregation
Enterprise Identity
Identity-provider requirements reviewed for deployment
Inspectable Citations
Source references analysts can open and check
Review Records
Recorded actions and audit coverage reviewed in scope
BILATERAL ENGAGEMENT PROTOCOL
Clear boundaries before a single file enters.
Every pilot establishes bilateral commitments: your deal team specifies policy and permissions; Underlying documents and enforces the operating path.
01 · CLIENT GOVERNANCE YOUR TEAM CONFIRMS
Permission and policy.
Before any file is ingested, your deal lead and security owners define the operational boundaries.
Which source pack may be processed
[DATA SCOPE]Explicit authorization for specific VDR folders, CIMs, financial models, and diligence files.
Who may access the Deal Room and resulting artifacts
[RBAC GATES]Named analysts, associates, and senior reviewers with least-privilege role permissions.
Required region, retention and deletion treatment
[RESIDENCY]Mandated hosting geography (US / EU), source retention windows, and post-pilot purge terms.
Approved model-provider and data-processing terms
[ZERO TRAINING]Provider processing, retention, and training terms confirmed for the selected endpoints.
The permitted memo export and downstream use
[OUTPUT GOVERNANCE]Authorized Word (.docx) export routes, citation preservation, and committee sign-off gates.
Status: Confirmed prior to data intake
02 · PROVIDER COMMITMENT WE DOCUMENT
The proposed operating path.
We provide verified architectural documentation and contractual commitments in writing.
The actual architecture and provider flow
[ARCHITECTURE]Architecture, data flows, and encryption configuration for the proposed deployment.
Organization, workspace and role boundaries
[TENANT ISOLATION]Documented organization, Deal Room, and role-based access controls.
Source intake and artifact export behavior
[DATA LIFECYCLE]Supported file formats, inspectable source references, and agreed deliverable formats.
Operational responsibilities and support path
[ENGAGEMENT SLA]Named engagement contacts, agreed support responsibilities, and escalation routes.
Evidence for claims made about the environment
[AUDIT TRAIL]Available review records, configuration evidence, and agreed audit coverage.
Status: Confirmed for the agreed deployment
SOURCE PERMISSION FIRST
Confirm source rights before review.
The pilot begins only after the team confirms the right to use the selected evidence, the participants who may access it, and the output the material will support.
Hosting region, retention, deletion, and provider commitments are confirmed through the evidence and agreement for the proposed deployment.
See Underlying in your deal workflow.
See how source review, Findings, and a cited IC draft fit your team’s workflow. We’ll discuss your memo format, review process, and setup requirements.