What an investment committee pack should actually contain

An investment committee is not asking to see everything a counterparty sent. It is asking a narrower and harder question: can we rely on this file?

That distinction shapes what belongs in a pack, and most packs answer the wrong question at considerable length.

What the committee needs

Five things, in roughly this order of importance.

What was asked for. The requirement list as it actually stood, including items added during the deal rather than only the template it started from. A committee that cannot see the list cannot judge whether the list was right, which is the first thing worth judging.

What came back, and against which item. Not a folder of forty files — the mapping. Item 7 is satisfied by pages 3 to 7 of this document. That sentence is what makes a file auditable, and it is the sentence a folder structure cannot produce.

Who accepted it, and when. An acceptance without a name is an assertion. With a name it is a decision someone stands behind, and the difference matters most on the item that turns out to have been wrong.

What was waived, by whom, and why. On the face of the pack, not in an appendix. A pack with clear waivers is more trustworthy than one with none, because a complex deal with no exceptions is a deal whose exceptions happened somewhere the pack cannot see.

What is still open. Including, honestly, anything outstanding at the point the pack was produced. A pack that presents a partial file as complete is worse than a pack that says three items are outstanding and names them.

What does not belong

Everything received, in folder order. A committee handed forty PDFs and asked to form a view has been handed the deal team's job. The documents are evidence; the pack is the argument.

A completion percentage on its own. It rises steadily, it feels like progress, and the last three items are routinely worth more than the first thirty. A percentage tells a committee what fraction of the work was easy.

Internal commentary. Rejection reasons and analyst notes are written for colleagues and phrased accordingly. They are how a team thinks out loud, and lifting them into a document that circulates is how a candid note becomes a problem.

The staleness question

One thing packs routinely get wrong, and it is easy to fix.

Evidence accepted in week two may not still be evidence by week nine. Management accounts more than a quarter old are not evidence of current trading. A filing history check run six weeks ago is not a check.

If the checklist records how long each kind of evidence stays good for, the pack can flag the items that have aged past it — which is otherwise discovered at committee, in front of exactly the people you least want to discover it in front of.

The one number

Days from opening the deal to IC-ready.

It belongs on the pack because it is the only figure that describes the process rather than the deal, and because a committee that sees it on every pack starts to develop a sense of what normal looks like — which is the beginning of being able to tell when something has gone wrong early enough to do something about it.

Include both halves if you can: how long the counterparty took, and how long items sat with your own reviewers. The second is the half that is usually invisible and usually actionable.

Assemble it from the file, not by hand

The best property a pack can have is that nobody wrote it.

If the checklist carried real state all the way through — items, owners, acceptances, waivers, dates — then the pack is an export. If it did not, the pack is a reconstruction performed under time pressure by someone who wants the deal to close, and reconstructions are systematically kinder to the file than the file deserves.

That is not a comment on anybody's integrity. It is that a person assembling a document at 11pm the night before committee will resolve every ambiguity in the direction of "that was fine", and there will be more ambiguities than they expect.