How to run an investment committee process that holds up under pressure

Decide which gates require committee approval

Before you schedule a single meeting, write down which decisions the committee owns. Everything else in the process hangs off this list. At most firms the investment committee consists of three to seven senior partners with collective authority over capital, and the process routes a deal through two or three gates on its way from screening to closing.

The gates exist because the money at risk changes character as a deal advances. At gate one the firm is risking pursuit costs. At gate two it is risking the deposit. At gate three it is wiring equity. Each gate deserves a vote proportional to what is being risked.

Small firms often collapse gates two and three into one vote. That works if the vote happens before the deposit goes non-refundable. The single most expensive process failure in acquisitions is a deposit that went hard without anyone formally deciding it should.

Write down the dollar thresholds too. Many firms let the deal lead approve pursuit spend under a fixed number, say $10,000, and route everything above it to committee. A threshold in writing keeps the committee focused on decisions that matter.

Standardize the memo so every deal reads the same

The memo is the unit of work in an IC process, and it is expensive. A full institutional memo takes 15 to 20 hours to prepare, and the raw material arrives as a seller-oriented offering memorandum with no standard structure, which the deal team has to translate into the firm's decision format.

A standard outline cuts that cost and, more importantly, makes deals comparable. When every memo puts sensitivities in section five and risks in section seven, a committee member can evaluate deal 40 the same way she evaluated deal 4. This outline follows the ten-section institutional structure that most firms converge on. Copy it into your system as the firm template.

1. Executive summary. Deal, price, thesis, headline returns, and the specific approval requested, on one page.

1. Property overview. Unit or suite mix, vintage, condition, and capital needs.

1. Location and market. Submarket supply pipeline, rent and occupancy trends, demand drivers.

1. Business plan. Core, value-add, or opportunistic strategy with a dated execution timeline.

1. Financial analysis. Sources and uses, pro forma, IRR, equity multiple, DSCR, and sensitivities on exit cap and rent growth.

1. Comparable analysis. Rent comps and sale comps that support the basis.

1. Risks and mitigants. What breaks the deal and what protects against it, stated plainly.

1. Exit strategy. Hold period, exit assumptions, and what happens if the market disagrees.

1. Structure and legal. JV terms, fees, financing structure, tax considerations.

1. Appendices. Model output, rent roll, third-party reports, maps.

The gate one version covers the same ten headings in compressed form. Keeping the headings identical across gates lets the committee see exactly what changed between pursuit and final approval, which is usually where the interesting questions live.

Set a standing cadence and protect it

An IC that meets only when someone calls a meeting becomes the slowest step in the deal process. The fix is a standing calendar that deal teams can plan around. Here is a cadence that works for a small or mid-size shop running 5 to 15 active pursuits. Copy it and adjust the days.

Two rules make the calendar work. First, the materials deadline is real. A memo that misses Monday noon waits a week unless a contractual deadline forces an ad hoc session. Second, members read before they arrive. A committee that reads the memo live in the room is a book club, and the deal lead should say so.

The 24 to 48 hour circulation window is the minimum for a genuine pre-read. Firms that circulate the night before get reactions instead of deliberation.

Run the meeting like a control function

The deal lead presents for 10 minutes maximum, focused on the thesis, the three biggest risks, and the specific approval requested. Everyone in the room has read the memo, so restating it insults the process. The rest of the slot is challenge. Good committees interrogate the assumptions with the widest error bars, usually exit cap rate, rent growth, and the renovation budget.

Voting rules belong in writing before they are needed. Some firms require unanimity on the theory that one experienced dissenter is usually seeing something real. Others use majority with the CIO holding a veto. The output of any vote is a yes, a no, or a yes with conditions, and the third outcome is both the most common and the least managed.

Treat a conditional approval as three records, never one. The decision, the conditions with owners and deadlines, and the verification. A committee that approves a deal subject to a $400,000 price reduction and a resolved easement, then lets those conditions live in someone's notebook, has not actually controlled anything.

Record decisions where the deal lives

The written record is the product of the whole process. Two years from now, someone will need to reconstruct what was approved, at what price ceiling, with what conditions, and whether they were met. If the answer is scattered across meeting notes, email threads, and a shared drive, the process failed even if every individual vote was sound.

The practical standard is one record per deal that holds the memo versions, the votes, the conditions, and the evidence that conditions were satisfied. In MotionCRE, each pursuit runs in a deal workspace that already contains the files, key dates, contacts, and due diligence checklist the memo draws from, so assembling the IC package is a writing task instead of a document hunt. Stage-transition approvals on the pipeline board enforce the gates mechanically. A deal cannot move from underwriting to LOI submitted until the required approval is recorded, which converts your gate list from a policy into a physical property of the pipeline.

Do the math on what the process costs without that structure. A firm that takes 25 deals to committee per year, at two memo-producing gates each, produces roughly 50 packages. At 15 to 20 hours per full package and perhaps a third of that for gate one versions, the firm spends 800 to 1,000 analyst hours a year on IC materials. If a quarter of each package's prep time is spent locating current versions of the model, the reports, and the rent roll, that is 200 to 250 hours a year lost to retrieval, roughly six working weeks of an analyst's time spent looking for things the firm already has.

The failure modes to design against

Three patterns undermine committees, and the process above is built to prevent each one.

The rubber stamp. Every deal passes because the real screening happened informally before the meeting. The committee adds delay without judgment. Fix it with written criteria and by letting the memo, in the standard format, be the basis of the discussion rather than hallway consensus.

The ambush. The memo lands the night before, members react in the room, and the loudest voice wins. Fix it with the hard materials deadline and the pre-read rule.

The vanishing condition. Approvals with conditions get treated as approvals. Fix it with the monthly conditions review on the standing calendar and with conditions logged on the deal record, each with an owner and a deadline.

If your weekly pipeline meeting and your IC currently blur into one session, split the agendas even if the attendees overlap. The pipeline meeting manages work in progress; the IC controls capital. The weekly acquisitions pipeline meeting covers the first session, and the calendar above covers the second. A firm that runs both, with written gates and a standard memo, has an investment process. Everything else is a group of people who talk about deals.