We see this on every deal: the lead underwriter builds a case, the LOI gets signed, and somewhere between underwriting and closing the deal’s assumptions evaporate. Teams lose visibility between lead underwriting and closing because no one owns the handoff, data lives in silos, and there’s no enforced record of decisions. Fix those three things and you stop paying for surprises after close.
1) The handoff is treated like an event, not a process
Most shops treat the handoff from the lead underwriter to closers and asset managers as a single meeting or an email dump. That’s the first mistake. A meeting or an inbox is not a durable process: it leaves room for interpretation, lost attachments, and unstated assumptions.
What actually happens: underwriting assumes someone else will carry forward a condition. Closers assume underwriting nailed covenant timing. Asset managers assume the loan or purchase docs captured contingencies. Nobody checks a common list. Nobody signs a single, authoritative decision memo that travels with the file.
Practical fix: make the handoff a checklist-driven workflow with required fields and signatures. Require the lead underwriter to export the model and upload that exact file into the deal record, attach a one-page decision memo listing assumptions, key sensitivities, and open items, and mark unresolved items as exceptions routed to the accountable owner. Treat the handoff as a workflow that cannot complete until those items are closed or explicitly accepted.
2) Your systems are singularly bad at being the single source of truth
Why spreadsheet deal tracking breaks at 20 active opportunities: spreadsheets, email threads, Slack messages, and multiple shared drives make a perfect storm. Each tool contains fragments of the deal. No one looks in all of them. That’s how a crucial rent roll or environmental note disappears.
Don’t confuse a fancier dashboard with a single source of truth. Dashboards report metrics. Your source-of-truth is the deal file: the canonical model, the executed LOI (with revisions), the diligence packet, and the decision memo. If those live in different places, visibility dies — see how disconnected docs slow LOIs & due diligence.
Practical fix: require every deal to have one canonical folder and a filename convention tied to a deal ID. Use document metadata or tags to capture deal ID, version, and owner. If you can’t standardize on a single platform immediately, at minimum require the canonical folder to contain copies of every file needed for closing — no more links to links.
3) People think documents equal decisions
A signed LOI or an uploaded appraisal doesn’t explain why a risk was accepted. That reasoning lives in people’s heads. When those people move on, the logic goes with them.
Decision-level documentation is the guardrail here. A brief decision memo — two paragraphs — that states the thesis, critical assumptions, material exceptions, and who is accountable closes the loop. It doesn’t need to be long. It needs to be required and attached to the file before the closing trigger is pulled.
Mini-case: underwriting accepted a tenant recapture clause as manageable, but that acceptance only existed in a Slack note. At closing, the repo team treated the clause as a default trigger and rework followed. A one-paragraph memo would have saved time and reputational cost.
Also remember the real cost of storing deal notes in email — when key decisions live only in threads, they rarely travel with the deal.
4) No one owns escalation and exceptions
Exceptions are where deals die or where risk slips through. If nobody is accountable for exceptions, they become assumptions. You can’t expect asset managers to discover underwriting exceptions during monthly reporting — by then it’s late.
Make exceptions first-class citizens: record who logged it, its severity, the mitigation in place, and the due date to resolve. That’s operational observability — not a KPI slide deck but a live view of open risks with owners and deadlines. This is exactly why manual task tracking creates pipeline blind spots.
Practical fix: triage exceptions weekly. Run a short meeting that reviews only open, unresolved exceptions. Limit attendees to owners and the lead underwriter (or their delegate). Close or escalate every item. If something remains unresolved for two cycles, require executive signoff to proceed.
5) Closing teams often get too little underwriting context
Closers are asked to translate underwriting into legal and operational terms, but they’re frequently handed documents without the underwriting context that explains which items were negotiated, compromised, or intentionally left out. The result: lawyers re-litigate items or insert protections that change economics, and operations spend time chasing clarifications post-close.
Practical fix: build a closing pack that contains not just documents, but underwriting context. The pack should include the canonical model, the one-page decision memo, a list of resolved vs unresolved diligence items, and an exceptions log. Require the closer to sign off that the pack is complete before legal drafts final documents.
Mini-case: a deal that slipped because of a missing assumption
We underwrote a small retail-to-mixed-use conversion. The lead underwriter modeled a phased lease-up assumption and carved out a short-term rent guarantee for a major tenant. That carve-out was discussed in person and on a phone call, but it wasn’t written into the LOI or the decision memo. The closer’s checklist didn’t surface it because the rent guarantee language lived in a separate email thread.
At closing, the owner thought the guarantee was part of the deal; the borrower thought it wasn’t. Lawyers spent days rewriting language. Closing delayed. The borrower demanded rate relief. We paid unexpected legal fees and reputational cost.
Lesson: verbal agreements do not travel. If it matters to underwriting, it must be captured, labeled, and included in the closing pack.
How to build continuity: a short playbook
We use a simple rule set that stops most visibility loss. It’s low-tech and enforceable. See also operational habits for consistent CRE deal flow.
- Mandate a one-page decision memo for every non-trivial deal.
- Require the canonical model file be the exact file used by the closer.
- Force exceptions to be logged with an owner and due date before closing triggers are pulled.
- Standardize a closing pack that contains documents plus underwriting context.
- Run a weekly exceptions triage meeting with accountable owners.
Checklist: what to implement this week
- Create a deal ID convention and enforce it across folders and filenames.
- Draft a one-page decision memo template and make it required for deals above your internal threshold.
- Implement an exceptions tracker (a simple shared sheet will do) and require owners and due dates.
- Set a policy: no closing pack, no legal draft. Require closer signoff on pack completeness.
- Run your first exceptions triage meeting within seven days and close one long-standing exception at that meeting.
Visibility isn’t glamorous. It’s discipline. If you want fewer surprises after close, stop relying on memory, email, and ad-hoc rituals. Make the handoff a measurable process, pick a canonical file, document decisions, and treat exceptions like defects. Do that and you’ll stop losing visibility between lead underwriting and closing.
How this maps to CREflow workflows
If you want to operationalize the playbook above, map three common pains to CREflow features that enforce the behavior:
- Missed next steps and handoffs: Configure Deal records and use deal-stage workflows so the handoff is a controlled step. Use Deal Stage Triggers to create action items for closers and assign them to owners so nothing is implicit.
- Scattered deal data: Attach the canonical model, executed LOI, and the one-page decision memo directly to the Deal and the linked Property so the canonical files travel with the record. Property Lifecycle Information and tags help surface whether an asset is "In Deal" and which deal it’s tied to.
- Untracked exceptions: Route follow-ups and unresolved diligence items into the Action Center so you get a prioritized, filterable queue for weekly triage. Action items created by triggers appear with source context and show the responsible owner and due date.
These references point to features inside CREflow that solve the exact pains discussed above: making the handoff a workflow, keeping canonical files with the deal, and creating a live exceptions queue to triage weekly. Use the Deal Detail activity timeline to keep the decision memo and discussion visible to everyone who opens the file.
If you want to put this into practice quickly, consider a pilot: pick three active deals, attach the canonical model and decision memo to each Deal record, and run one exceptions triage using the Action Center. After one cycle you’ll see which rules need tightening.