moat8
Legal servicesLegal & compliance

Due diligence engine

A review package arrives as hundreds of documents answering a questionnaire nobody has the hours to check line by line. The engine maps every document to every question, returns a coverage status with the quotes behind it, and runs entirely on infrastructure you control.

How it works

You giveThe questionnaire as you already write it, and the package as it arrives — by file or by folder, in DOCX, XLSX, and PDF, scans included.
The system doesThe reading. It parses the questionnaire into machine-readable questions, converts and OCRs the package, evaluates every question against every relevant document, and returns a coverage status with the reasoning, the quotes, and links into the source.
You stay in controlOver every answer the system returns. A comment on any question changes how it is re-run, statuses can be set by hand where the model read something wrong, and uncovered questions compile into the next round of document requests.
You getEvery question answered with its evidence attached, a risk list for the company or asset, and a finished report in your own template.

Inside the system

11 components
01

Projects and access

Each matter runs as a project with a counterparty, a description, and named participants whose permissions the team sets per project.

02

Reference libraries

Your reviewers maintain a reference questionnaire mapping which document types answer which questions, plus a risk base and checklists describing how to evaluate a document for encumbrances, expired permits, and other problem areas.

03

Questionnaire parsing

The DOCX questionnaire uploads and parses into machine-readable questions, with the preamble carried into context so the system understands the matter it is reviewing.

04

Ingestion and OCR

Documents are uploaded by file or by folder. Text PDFs convert straight through; scans route through OCR, and tables and formulas are recognised separately and reassembled into the document text.

05

Question-to-document analysis

Classification, summarisation, table-of-contents extraction, question routing, a relevance gate, verification, and aggregation run across tens of thousands of question-document pairs, distributed across workers with parallelism that adapts to GPU load.

06

Coverage statuses

Each question returns one of four states: fully covered, partially covered, requires review where the system declines to conclude on its own, and not covered where nothing was provided.

07

Cited answers

Every answer arrives with its reasoning, direct quotes, and links into the processed text that open at the exact passage. A finding is checkable in seconds.

08

Reviewer corrections

A comment on any question is taken into account when it is re-run, and statuses can be set manually where the review catches something the model read wrong.

09

Follow-up requests

Uncovered and partially covered questions compile into a follow-up document request, and the next round of documents runs through the same analysis.

10

Risk assessment

Documents are evaluated against your risk base and checklists to produce a risk list for the company or the asset under review.

11

Report generation

Your report template fills with the findings, the preamble data, the document assessments, and the risk results, then exports as a finished DOCX with citations back to sources.

Who it's for

Good fit
Legal teams running due diligence on transactions
Any review where hundreds of documents answer a fixed questionnaire
Practices staffing large matters with junior reviewers at peak
Compliance and audit functions working through document packages
Organisations whose material cannot reach an external service
Reviews where every finding has to be traceable to its source
Not a fit
Packages of a few documents a reviewer can work through directly
Questions that depend on knowledge outside the documents provided

What you can configure

01
Your reference questionnaireWhich document types are expected to answer which questions. This is your method, written down precisely enough for a system to run it.
02
Your risk baseThe checklists and problem areas a document gets evaluated against, per matter type.
03
When it declines to concludeWhat sends a question to requires review rather than to an answer, which is where the system's honesty setting lives.
04
Your reportThe template the findings fill, and the citation format your clients expect to be able to follow.

What we need from you

GPU infrastructureServers that can host the model and the OCR stack. Everything runs inside your perimeter.
Your reference questionnaireThe mapping from document types to questions your reviewers already work from.
Your risk baseChecklists and problem areas, so risk assessment reflects how your team reviews.
One reviewerSomeone who can say whether a status and its citation are right, a few hours a week during the build.

Example use cases

Mapping 500 documents to a 60-question due diligence checklist

Reviewers spend weeks working out which of 60 checklist questions each document answers before analysis can begin. An AI review engine checks every question against every document and returns answers with quotes and a link to the exact passage.

Get the reading done before the review starts.

Book a demo →