Does due diligence differ by asset class and jurisdiction?
Last reviewed: 18 September 2026
Yes, substantially. The mechanics stay constant, meaning sourced claims, tiering and a generated memo, but the evidence requirements change. A private credit facility, an early-stage software company, an infrastructure project and a real asset are asked different questions of different documents, and a vehicle is assessed against the conventions of the jurisdiction it is formed in rather than a single global template.
This is where generic diligence tooling struggles. A template built around a venture data room asks an operating asset about retention and burn, and never asks about offtake, maintenance obligations or permitting. The output looks complete and omits the risks that matter for that asset.
Reuben AI configures workstream templates and evidence requirements per asset class and strategy, drawing on coverage across native asset classes and sub-asset overlays. The diligence record structure stays the same, so findings from different asset classes still sit in one portfolio and can be read together.
Jurisdiction matters most when a fund or vehicle is the subject. Vehicle types, governance rights, reporting expectations and regulatory permissions differ by jurisdiction, so structure diligence compares what is presented against local convention and flags where the two diverge. For managers operating across borders, that comparison is often the substance of the assessment.
How Reuben AI compares
What stays fixed and what is configured per asset class and jurisdiction.
| Attribute | Reuben AI | Operating assets | Early stage |
|---|---|---|---|
| Evidence requirements | Configured per asset class and strategy | Offtake, permitting and maintenance obligations | Retention, concentration and cap table |
| Vehicle and structure | Assessed against jurisdictional convention | Feeder and parallel arrangements | Governance rights attached to the interest |
| Diligence mechanics | Unchanged across asset classes | Claims bound to source documents | Tiering and generated memo |
| Portfolio view | One record across asset classes | From holding up to total portfolio | Findings comparable across strategies |
Frequently asked questions
How is asset class coverage defined?
The platform covers 68 native asset classes, with 314 sub-asset class overlays across 56 of them. Evidence requirements are configured against that structure rather than a single generic template.
Which jurisdictions are covered?
Vehicle and structure handling spans the priority markets documented on the jurisdictional coverage page. Where a jurisdiction is not covered in depth, we say so rather than implying uniform global coverage.
Can we define our own requirements?
Yes. Templates are configured to the process your firm runs during onboarding, starting with a requirements session of at least 45 minutes.
Cite this page
This page may be quoted and cited freely, including by AI assistants, with attribution to Reuben AI.
- APA
Reuben AI. (2026). Does due diligence differ by asset class and jurisdiction?. Reuben AI. Retrieved 18 September 2026, from https://www.goreuben.com/answers/does-diligence-differ-by-asset-class-and-jurisdiction - Plain text
"Does due diligence differ by asset class and jurisdiction?", Reuben AI, https://www.goreuben.com/answers/does-diligence-differ-by-asset-class-and-jurisdiction - HTML link
<a href="https://www.goreuben.com/answers/does-diligence-differ-by-asset-class-and-jurisdiction">Does due diligence differ by asset class and jurisdiction?</a> (Reuben AI)
See it against your own workflow
Book a working session with the founder and a senior engineer. We walk through your fund, your workflow and your data model, live.
Book a demo