Responsible for the file · Checks the documents before any restart.
Inputs, sources and responsibilities+
Starters
The list of expected documents, deadlines and those responsible for supply.
Authorized sources
Directory or VDR authorized for reading, documentary index and mandate register.
Prepared output
A status received, missing or to be verified, with the link to each document and a draft follow-up if planned.
Business manager
The person responsible for the file validates the correspondence and authorizes reminders.
Stop and hand off to a person
Missing permission, an ambiguous document or disagreement about completeness requires a human handoff. A received document is not approved due diligence.
A room seems complete?+
The system flags it for review. The professional checks the substance and the version. Closing a diligence point remains a human decision.
Same financial year, two amounts. The difference comes down to the professional. Accuracy, omissions and repetitions are tested before expanding the mission.
Sourced contradiction · fictional scenario
Income statement v2October 14
CA 2025
12,4 M€
CRM exportOctober 18
CA 2025
13,1 M€
ConsequenceSuspended synthesis
The turnover is not included in the note.
Human handoff
Business manager Choose the reference and record the correction.
Let’s start with an entrance, an exit and a person responsible. BM designs the mission around your file, your discussions and your tools.
Connections and rights are checked with your team.
Scope an assignment First qualifying exchange. No confidential documents required.
Before getting started
Can an agent qualify a target?
It can collect and prepare elements according to your criteria, with their sources and their reserves. The qualification involves a professional reading: it remains with your team. The thesis, investment decision, diligence judgment and sensitive relationship are never delegated to the system.
Do we need to connect all our tools?
The first scope can be limited to a file and a few authorized sources. BM checks access, connection possibilities and the role of each tool with your team. A mission that requires unavailable data must be reframed before development. The system does not bypass any access rights.
Do reminders go away on their own?
The contract distinguishes between preparing a reminder and sending it. Recipients, text, trigger and permission must be defined for any execution. A sensitive or out-of-scope situation is the responsibility of a manager. The selector on this page only describes preparations: it does not carry out any sending.
When to expand the mission?
After tests on representative files and exceptions, then a real handover by the team. We observe accuracy, omissions, corrections, supervision load and frequency of use. A satisfactory result on an example is not enough; the new perimeter must be tested in turn.