How to track a commercial real estate deal pipeline

To track a commercial real estate deal pipeline, give every active deal its own workspace, define stages around the work your team actually does, and update the pipeline in real time as each task is completed rather than in a weekly batch. The rest of this guide covers the structure, fields, and workflow that make that hold up as deal volume grows, starting with why most pipelines fall apart.

Commercial real estate deal teams universally struggle with pipeline tracking. Most teams start with a spreadsheet and graduate to a shared document, maybe a Trello board, and eventually a half-configured CRM they bought for something else. None of these systems survive contact with real deal volume.

The reason is structural. A CRE deal is not a single record with a handful of fields. It is a tree of objects: the deal itself, with its economics, asset class, and stage; a workspace of documents, including the offering memorandum, rent roll, T-12, inspection reports, and environmental assessments; a roster of contacts spanning the broker, seller's counsel, lender, property manager, and environmental consultant; a set of workstreams covering financial, physical, legal, and environmental due diligence plus financing; and an audit trail of conversations and decisions. A row in a spreadsheet cannot hold any of this. It can only summarize one person's mental model of where the deal stands.

The second reason pipelines fail is that they are not updated in real time. The person doing the work (the analyst running underwriting, the associate coordinating inspections, the principal negotiating with lenders) is not the person updating the pipeline. Someone else is. Usually the acquisitions lead. Once a week. On Sunday night. By Monday morning, the pipeline is already stale.

The third reason is that pipelines get built around reporting instead of around work. Teams design their pipeline to answer one question, 'what will I show my investment committee this month?', and end up with fields like 'IC-ready date' and 'expected close date' that are maintained for the IC meeting but have nothing to do with how the deal actually moves. The pipeline becomes a sales tool for internal stakeholders instead of an operating system for the deal team.

If you want a pipeline that survives, you need to build it around the deal as a real object, with real workspaces for the work that happens on each deal, with real-time updates from the people doing the work. Anything less decays within months.

The best CRE deal teams treat the pipeline as an operational system, not a reporting tool. The pipeline is where the work happens, not a summary of where the work has happened.

There are four characteristics that distinguish a working pipeline from a decorative one:

1. Every active deal has a workspace

A workspace is a dedicated place for the documents, tasks, contacts, and notes related to a specific deal. When the analyst is running underwriting, they open the workspace and find the OM, rent roll, and T-12. When the associate is scheduling inspections, they find the property manager contact and the prior inspection reports. When the principal is negotiating with lenders, they find the lender quotes side-by-side. The workspace is the source of truth for the deal, and the pipeline is a view into every workspace.

2. Fields are designed for the work, not the report

Pipeline fields should reflect the state of the deal from the perspective of the team doing the work. 'Rent roll received,' 'Environmental report in review,' 'Lender quote outstanding,' 'IC memo drafted.' Each field corresponds to a discrete state that someone on the team can update as they do the work. Avoid fields like 'expected close date' that are guesses made for external audiences. They encourage lying.

3. Updates happen in real time by the person doing the work

The pipeline is updated by the team member who just did the thing. The analyst marks underwriting as complete when they finish underwriting. The associate marks the inspection as scheduled when they schedule it. The principal marks the LOI as submitted when they submit it. If updates are batched for a weekly meeting, the pipeline is a lagging indicator. If updates happen in real time, the pipeline is the live state of the team's work.

4. The pipeline is a filter, not a report

The weekly deal meeting is a filter applied to the pipeline, not a separate document. Filter by 'in DD,' 'closing within 30 days,' or 'assigned to John.' The conversation is grounded in the live data. No one is sitting at the table reading from a stale slide deck.

MotionCRE is built around the principles described above. Every deal has a workspace with document storage, task tracking, and contact management. The pipeline is a live view into every workspace. Drag and drop deals across stages, filter by any field, and see the full deal context with a single click.

Because MotionCRE was built specifically for commercial real estate, the pipeline fields are already designed for CRE deals. Purchase price, cap rate, unit count, square footage, asset class, broker, lender, and deal stage are all native. No custom field configuration required.

The system is designed for real-time updates. The analyst running underwriting uploads the T-12 directly into the deal workspace, which updates the deal card. The associate scheduling inspections logs the task, which updates the workstream status. The principal negotiating with lenders adds quotes to the financing tracker, which updates the deal's financing column. Every team member is updating their own work as they do it, and the pipeline reflects the live state of every deal.