How to Build a Due Diligence Presentation for an Investment Committee

A due diligence presentation summarizes diligence findings for the people deciding whether a deal proceeds. It runs roughly 15 to 25 slides covering deal overview and thesis, financial findings, commercial and market findings, legal and compliance exposure, operational and IT review, risks with proposed mitigations, and a recommendation. Build it from the findings report itself so every figure on screen traces to a workpaper, lead each section with the conclusion, and keep the detailed schedules in an appendix you open only when challenged.

Diligence produces hundreds of pages. The investment committee gets an hour. The compression from one to the other is where deals get misjudged, in both directions: a real problem buried on slide 19, or a manageable issue presented so starkly it kills something workable. This is how to do the compression without losing the thing that matters, which is that every claim can be traced back.

What is due diligence?

Due diligence is the investigation a buyer or investor runs on a target company before committing, to verify what the seller has represented and to find what they have not. It spans financial, commercial, legal, tax, operational, IT, and increasingly cyber and ESG review, and it is conducted under a deadline set by the transaction rather than by how long the work would ideally take.

The output is a findings report, and the report is written for the record. The presentation is written for a decision. Those are different documents with different jobs, which is why summarizing well matters.

What are the components of due diligence?

The workstreams below are the standard set on a mid-market transaction. Each one gets a section in the deck, sized to the risk it actually surfaced rather than to the hours it consumed.

How to conduct due diligence so the deck writes itself

Teams that produce clean readouts do one thing consistently: they write findings as conclusions while the work is happening, not at the end. Each workstream lead maintains a short running statement, the finding, the quantified impact, the evidence reference, and the proposed deal response. Do that from day one and the presentation is an assembly job. Skip it and you spend the last 48 hours reverse-engineering conclusions out of workpapers under time pressure, which is exactly when errors enter.

The legal workstream is worth flagging separately, because it is the one most often still in flight when the deck is due. Change-of-control clauses, assignment restrictions, and open litigation each need a position, not a status. Where a matter turns on how a specific provision has actually been read, a fast pass through how courts have treated that kind of clause gives counsel something concrete to characterize the exposure with, rather than the deck carrying an unresolved "under review" into the committee room.

Lead every section with the conclusion

The most common structural mistake is presenting diligence the way it was performed: scope, then procedures, then findings, then implications. Nobody in the room cares about your procedures until they disagree with your conclusion.

Invert it. Each section headline states the finding as a sentence: "Adjusted EBITDA is $14.2M, $2.1M below management's presented figure, driven by three recurring items treated as one-time." The supporting analysis sits below it, and the schedule sits in the appendix. A committee member who accepts the headline moves on; one who does not knows precisely where to push.

Quantify, then say what to do about it

A finding without a number is an opinion, and a finding without a proposed response is a problem handed to somebody else. Every material item should carry both: the dollar impact or the range, and the deal mechanism that addresses it, which is usually a price adjustment, a specific indemnity, an escrow, a closing condition, or an accepted risk.

That last option is legitimate and underused. Some findings are real, quantified, and fine. Saying so explicitly builds more credibility than a deck where every issue is a red flag.

How to answer due diligence questions in the room

Committee questions cluster in three types. The provenance question, where did that number come from, needs a source you can reach immediately. The sensitivity question, what if retention runs worse than assumed, needs a range you calculated beforehand. The judgment question, would you do this deal, needs a straight answer.

Prepare for the first by making provenance mechanical rather than memorized. If each slide carries its own source reference in the speaker notes, the answer takes five seconds instead of a promise to follow up, and following up is how a committee starts wondering what else is soft.

Build the deck from the findings report

Retyping diligence conclusions into slides is the single riskiest hour of the whole engagement. A transposed figure in a workpaper is an error; the same figure transposed onto a slide in front of an investment committee is a misstated fact that people commit capital against.

Generating the deck from the report removes the transcription step entirely. Upload the findings report to Docslide's due diligence deck flow and it extracts the section structure, shows you that outline before generating a single slide, then builds the deck with quality-of-earnings bridges, working-capital trends, and concentration tables rebuilt as native editable PowerPoint charts carrying your actual figures, and the supporting analysis moved into speaker notes with a reference to the source section. When a committee member challenges an adjustment, the provenance is on the slide you are already showing.

A Word findings report goes through Word to PowerPoint, a vendor due diligence PDF through PDF to PowerPoint, and the model through Excel to PowerPoint. On the Pro plan your firm .potx means every deal readout arrives in the same template and section order, which is how a committee reviewing four transactions a quarter compares them fairly. Docslide structures and designs what your diligence already found. It does not form conclusions, calculate adjustments, or generate findings; the deck is a first draft the deal lead reviews and owns.

What belongs in the appendix

Detailed adjustment schedules, the full contract review log, customer-by-customer revenue detail, the complete risk register, and the data request tracker. None of it gets presented. All of it needs to be one click away, because the credibility of a 20-slide summary rests entirely on the visible existence of the 200 pages behind it.

The practical takeaway

Build the readout from the findings report, not from memory. Lead each section with the conclusion, quantify every material item and pair it with a deal response, keep the schedules in an appendix, and make provenance mechanical so any challenged number resolves in seconds. A committee is not really evaluating your slides. It is evaluating whether the work behind them holds when somebody pushes on it.