Underwriting checklist: screening to IC approval

Start with gates that match real investment decisions

A useful CRE underwriting checklist separates initial screen, deep-dive underwriting, and IC package approval because each stage answers a different investment question. This is also a training mechanism. New analysts should be able to see how CRE underwriting checklist affects price, leverage, NOI, exit value, or approval risk without reverse-engineering a senior analyst's spreadsheet. The standard is not polish; it is traceable judgment under deal pressure. When that standard is written into the workflow, a new hire can learn the firm's underwriting logic from live files instead of tribal memory.

The checklist should name the artifact required at each gate so analysts know whether the next step needs a one-page screen, a reconciled model, or a committee-ready recommendation. The practical test is whether a principal can trace the conclusion back to evidence without opening five separate files. If IC approval workflow changes the model, the memo should show the before-and-after assumption, the date of the source, and the decision gate affected by the change. This matters most when a late broker update, lender quote, or rent roll revision forces the team to decide whether the recommendation still holds.

Make the deal screening process binary where possible

The first screen should use explicit thresholds for NOI, asset type, vintage, market eligibility, seller motivation, and preliminary basis so weak fits do not consume model-building time. For reviewers, this should reduce the questions that normally stall IC prep: where the number came from, whether the comp set is still current, and whether the downside case reflects the latest diligence. That is where underwriting quality control becomes useful to the committee rather than decorative. A strong packet should make the unresolved risk obvious enough that the committee can debate risk appetite, not hunt for missing support.

Exception handling should require a named sponsor and a written reason so leadership can distinguish disciplined flexibility from quiet process drift. The practical test is whether a principal can trace the conclusion back to evidence without opening five separate files. If IC approval workflow changes the model, the memo should show the before-and-after assumption, the date of the source, and the decision gate affected by the change. This matters most when a late broker update, lender quote, or rent roll revision forces the team to decide whether the recommendation still holds.

Assign sign-off authority before work begins

Each gate needs one accountable reviewer because shared informal approval creates ambiguity when a deal stalls or advances with unresolved issues. For reviewers, this should reduce the questions that normally stall IC prep: where the number came from, whether the comp set is still current, and whether the downside case reflects the latest diligence. That is where underwriting quality control becomes useful to the committee rather than decorative. A strong packet should make the unresolved risk obvious enough that the committee can debate risk appetite, not hunt for missing support.

Named sign-off also gives the team a record of who cleared the screen, who approved the deep-dive model, and who accepted open conditions before IC. For reviewers, this should reduce the questions that normally stall IC prep: where the number came from, whether the comp set is still current, and whether the downside case reflects the latest diligence. That is where underwriting quality control becomes useful to the committee rather than decorative. A strong packet should make the unresolved risk obvious enough that the committee can debate risk appetite, not hunt for missing support.

Run a fast initial screen before opening a full model

Gate one should capture property name, address, asset type, unit count or square footage, trailing NOI, asking guidance, target market status, and a pass or advance rationale. For reviewers, this should reduce the questions that normally stall IC prep: where the number came from, whether the comp set is still current, and whether the downside case reflects the latest diligence. That is where underwriting quality control becomes useful to the committee rather than decorative. A strong packet should make the unresolved risk obvious enough that the committee can debate risk appetite, not hunt for missing support.

That screen creates useful institutional memory because the team can later see why a familiar deal was killed instead of re-underwriting the same opportunity from scratch. In a live acquisition file, make this visible in the workpaper: the source artifact, the assumption it changes, and the reviewer who owns the next action. That keeps deal screening process connected to the actual OM, rent roll, T-12, debt quote, or comp set instead of leaving it as unsupported memo language. The same evidence should then flow into the model exhibit and IC narrative so nobody has to reconcile three versions of the story on the morning of committee.

Use deep-dive underwriting to reconcile the source package

Gate two should require rent roll tie-outs, T-12 normalization, operating expense benchmarking, debt quote updates, and comp-supported valuation bracketing before narrative drafting begins. Do not bury this in narrative. Put the rule next to the underwriting field it governs, then carry the same evidence into the memo exhibit. In CRE workflows, the expensive failures usually come from small disconnects between model tabs, source documents, and the recommendation language. Closing those gaps turns the article's advice into an operating control that can survive analyst turnover and partner follow-up questions.

Every adjustment to NOI, capex, vacancy, rent growth, taxes, insurance, or exit value should point back to a source file so reviewers can audit the model without forensic spreadsheet work. The practical test is whether a principal can trace the conclusion back to evidence without opening five separate files. If IC approval workflow changes the model, the memo should show the before-and-after assumption, the date of the source, and the decision gate affected by the change. This matters most when a late broker update, lender quote, or rent roll revision forces the team to decide whether the recommendation still holds.

Turn the IC approval workflow into a decision record

The final package should include sensitivity tables, pass triggers, unresolved diligence items, approval conditions, and a vote record tied to responsible owners. For analysts, the output should be a concrete checkpoint: what was reviewed, what exception remains open, and whether the deal can move to the next stage. That turns turn the ic approval workflow into a decision record from a writing standard into a control the team can reuse on the next acquisition. It also gives senior reviewers a cleaner way to challenge judgment without reopening every spreadsheet tab or source PDF from scratch.

Conditional approvals need a closure tracker because deals often stall after committee when insurance, financing, legal, or environmental conditions lack clear ownership. In a live acquisition file, make this visible in the workpaper: the source artifact, the assumption it changes, and the reviewer who owns the next action. That keeps deal screening process connected to the actual OM, rent roll, T-12, debt quote, or comp set instead of leaving it as unsupported memo language. The same evidence should then flow into the model exhibit and IC narrative so nobody has to reconcile three versions of the story on the morning of committee.

Track checklist performance after each committee cycle

Leadership should review deals screened, deals advanced, time in stage, memo revision count, late model changes, and approval condition closure time to see whether the checklist is actually improving decisions. Do not bury this in narrative. Put the rule next to the underwriting field it governs, then carry the same evidence into the memo exhibit. In CRE workflows, the expensive failures usually come from small disconnects between model tabs, source documents, and the recommendation language. Closing those gaps turns the article's advice into an operating control that can survive analyst turnover and partner follow-up questions.

If the team is moving faster but revision count rises, the screen may be too loose or the deep-dive artifacts may be reaching IC before they are ready. Do not bury this in narrative. Put the rule next to the underwriting field it governs, then carry the same evidence into the memo exhibit. In CRE workflows, the expensive failures usually come from small disconnects between model tabs, source documents, and the recommendation language. Closing those gaps turns the article's advice into an operating control that can survive analyst turnover and partner follow-up questions.

Use quality control to catch source and assumption drift

Underwriting quality control should sample source ties against final memo outputs so rent roll changes, T-12 adjustments, and debt terms do not drift between model tabs and narrative sections. For analysts, the output should be a concrete checkpoint: what was reviewed, what exception remains open, and whether the deal can move to the next stage. That turns use quality control to catch source and assumption drift from a writing standard into a control the team can reuse on the next acquisition. It also gives senior reviewers a cleaner way to challenge judgment without reopening every spreadsheet tab or source PDF from scratch.

The control should be lightweight enough to run on live deals but strict enough to stop unsupported numbers from reaching the investment committee. For reviewers, this should reduce the questions that normally stall IC prep: where the number came from, whether the comp set is still current, and whether the downside case reflects the latest diligence. That is where underwriting quality control becomes useful to the committee rather than decorative. A strong packet should make the unresolved risk obvious enough that the committee can debate risk appetite, not hunt for missing support.

Feed closed-deal outcomes back into the checklist

Post-close and post-IC feedback should update screening thresholds, model checks, and approval conditions when actual outcomes expose a repeated underwriting blind spot. The practical test is whether a principal can trace the conclusion back to evidence without opening five separate files. If IC approval workflow changes the model, the memo should show the before-and-after assumption, the date of the source, and the decision gate affected by the change. This matters most when a late broker update, lender quote, or rent roll revision forces the team to decide whether the recommendation still holds.

That feedback loop turns the checklist into a living operating system instead of a static template that gets stale as markets, lenders, and committee standards change. For analysts, the output should be a concrete checkpoint: what was reviewed, what exception remains open, and whether the deal can move to the next stage. That turns feed closed-deal outcomes back into the checklist from a writing standard into a control the team can reuse on the next acquisition. It also gives senior reviewers a cleaner way to challenge judgment without reopening every spreadsheet tab or source PDF from scratch.

Execution steps for deal screening process and IC approval workflow

Add CRE underwriting checklist checks to the intake packet, not only to the final memo. The first screen should capture the core source files, open diligence gaps, and the next decision owner before an analyst spends hours refining the model.

Set acceptance criteria before each stage starts. For deal screening process, that means naming the artifact required to advance the deal, such as a reconciled rent roll, refreshed comp set, debt quote, or source-linked assumption table.

Use a change log for every material edit to price, leverage, NOI, capex, exit value, or recommendation language. The log should capture old value, new value, source, rationale, and approver so IC approval workflow stays auditable.

Tag recurring exceptions by asset class, market, and section of the packet. When the same issue appears across deals, convert it into a checklist item, reviewer prompt, or default assumption rule instead of solving it from scratch again.

Run monthly calibration against live outcomes: screen-to-LOI conversion, memo revision count, assumption overrides, committee objections, and closed-deal performance. Those metrics show whether underwriting quality control is changing decisions, not just documentation.

Define escalation thresholds in plain language. If extraction confidence is low, comps are stale, source data falls back, or a key assumption breaches the firm's historical range, the workflow should require named human review before the packet advances.

Governance reinforcement for underwriting quality control

Quarterly retrospectives should compare this playbook against real deal outcomes: which assumptions moved after IC, which objections repeated, and which sections still required late rewrites. If speed improves while sourcing quality weakens, tighten the gate instead of celebrating the cycle-time gain.

Make these checks visible to leadership in the same dashboard used for pipeline reviews. CRE teams need to see where capacity, risk, and memo quality are changing together so the next process fix is tied to evidence from live acquisitions.