Skip to main content
Research library
Private EquityM&A Due DiligenceWorkflow Design

Automating IC Memo Preparation While Reducing Unsupported Claims

A review-led approach to preparing investment committee memo drafts: approved sources, checked calculations, visible gaps, and human approval before use.

Article brief

Author
Dotnitron
Published
October 6, 2026
Read time
2 min read

Key takeaways

  • Source boundaries, retrieval checks, calculation tests, and human review help reduce unsupported claims; they do not eliminate model errors.
  • A citation needs to support the claim, not simply link to a file.
  • Missing, conflicting, unreadable, and out-of-scope information should remain visible.
  • Memo templates, export behavior, and change tracking need evaluation for the agreed implementation.

AI can help prepare an investment committee memo by extracting facts, assembling source-linked findings, and drafting within an approved structure. It cannot guarantee a correct investment view. Reviewers still assess completeness, materiality, assumptions, and whether the sources support each claim.

Define the memo and the source boundary

Agree the sections to prepare, authoritative sources, access rules, output fields, and reviewer responsibilities. Record document versions and exclusions. A missing file or unanswered question should be visible rather than filled with plausible prose.

Separate extraction from calculation

Identify the facts and definitions needed for each metric. Use checked calculations where possible, retaining the relevant period, currency, filters, source location, and transformation. Generated SQL or formulas still need tests; deterministic execution does not prove that the selected data or definition was correct.

Check whether citations actually support the draft

A source link is a navigation aid, not proof of accuracy. Reviewers should check the passage or table, nearby qualifications, and any conflicting source. File, page, sheet, or cell references depend on the parser and viewer supported by the implementation.

Keep a review gate before delivery

Present draft findings, supporting material, uncertainty, and open questions together. Reviewers decide what to accept, change, reject, or escalate. Only approved material should enter the final memo through the agreed export process.

Treat updated files as a review event

When a source changes, record the version and identify outputs that may need re-evaluation. Automatic dependency tracking is a capability to scope and test, not something every implementation should be assumed to provide.

Evaluate the complete workflow

Compare drafts with representative reviewed work. Track unsupported or missed findings, citation errors, calculation errors, reviewer effort, and output-format fit. OpenAI’s evaluation guidance emphasizes the importance of documenting the task, tools, test setup, and scoring method: OpenAI: third-party evaluation foundations

Discuss a defined first scope

Dotnitron can help design and implement memo preparation around your sources, templates, tools, and reviewer process. Capabilities and acceptance criteria are agreed per engagement; no error-free output or automatic final approval is promised. Learn more at Dotnitron due diligence document review.

Use this guide

Turn the article into a working session.

Pick one workflow from the article and map it against your own team. Write down the input sources, current manual steps, reviewer decisions, output format, and the metric that would prove the workflow is worth automating.

  • What work should agents prepare before a human reviews it?
  • Which documents, data sources, tools, or approved system connections would the workflow need?
  • What output would make a reviewer say, this saves real time?

Have something in mind?

Bring us the work you want to improve.

Tell us about your process, product idea, or information challenge. We will help you assess a practical first step, with scope and timing agreed for your project.