The deal tracking spreadsheet, honestly assessed

The deal tracking spreadsheet is the default first system for almost every commercial real estate team. There are good reasons for this. A spreadsheet is free, universally understood, infinitely customizable, and available the moment someone on the team decides the pipeline needs to be written down somewhere. You do not have to ask anyone for approval to start one. You do not have to train the team to use it. The analyst builds it on a Tuesday afternoon, shares it with the acquisitions principals, and by Wednesday morning the team has a shared view of the pipeline that did not exist the day before. That is a real improvement over the situation without it.

The honest version is that a deal tracking spreadsheet is an excellent tool for exactly one scenario: a team running a small number of deals where one person maintains the pipeline and everyone else consumes it as a read-only report. In that setup, the spreadsheet works. The analyst who owns it has the full context, updates it weekly (or more), and uses the columns as their own personal to-do list. The partners open it before meetings, see what is live, and ask the right questions. This can last for a year or two depending on the deal volume.

The spreadsheet starts to fail in predictable ways. The first symptom is that the analyst starts forgetting to update it. A deal moved from screening to LOI three weeks ago, but the spreadsheet still says screening. Nobody noticed because the deal has been in the LOI stage long enough that everyone just knows it verbally. The spreadsheet has quietly become a trailing indicator.

The second symptom is file chaos. The spreadsheet references the rent roll, but the rent roll is in Drive. Is it the latest rent roll? Nobody knows without clicking through to the folder, finding the most recent file, and comparing it to what the underwriting model uses. Versioning becomes a manual task. On a bad week, the team underwrites against a three-month-old rent roll because nobody double-checked.

The third symptom is that deal context gets lost when anyone rotates off the team. When the analyst leaves, they take the mental model of the pipeline with them. The spreadsheet looks complete from the outside, but half the cells depend on knowledge that lived in the analyst's head. A new analyst inherits the sheet and cannot reconstruct the story. Deals slip quietly.

The fourth symptom is concurrent editing. Two people try to update the same cell at the same time, or one person filters the view and forgets to clear it, or someone copies the sheet to work on 'their version' and now there are two versions and nobody knows which is authoritative. This is when the team has clearly outgrown the spreadsheet, usually somewhere between 10 and 25 concurrent deals depending on the asset class.

If you are running on a spreadsheet today, the goal is to make it as useful as possible for as long as it works, and to recognize the failure signs early. Here is how to structure it well.

Keep the column set small

Limit the spreadsheet to about 15 columns: property name, address, asset class, stage, owner, broker, asking price, estimated value, target cap rate, key date, next action, next action owner, lender status, document link, and notes. More columns than that and maintenance cost exceeds value.

One stage field, plus a 'blockers' column

Spreadsheets cannot represent parallel workstreams well. Accept that and put all the nuance in a 'blockers' column where the owner writes a short sentence about what is holding the deal up. 'Waiting on environmental Phase I' or 'Lender terms under negotiation' is more useful than any amount of stage engineering.

Use a document link column, not attached files

Spreadsheets are not document stores. Link to the folder or file in Drive and accept that version control is a manual discipline, not an automated one.

Run a weekly pipeline review off the live sheet

Do not email a PDF export. Open the live sheet, filter to active deals, and walk through them in the Monday meeting. This forces the sheet to stay current.

Document the naming conventions

Write down how properties should be named, how file links should be structured, and who is responsible for each column. A one-page README at the top of the sheet extends its useful life by months.

The signs that your deal tracking spreadsheet has outgrown its usefulness are consistent across CRE teams. When you see two or more of these, it is time to move.

The team has 10 or more concurrent active deals. The spreadsheet is updated by one person, weekly or less. Deal context is lost when anyone rotates off the team. Files and links in the sheet are out of date or missing. Two or more people have started keeping their own 'working copy.' The sheet is no longer referenced in partner meetings because nobody trusts it.

MotionCRE is designed to take over at this transition point. Every deal has a dedicated workspace with documents, tasks, contacts, and financing. Updates happen in real time as the person doing the work does the work, not in a weekly reporting ritual. The pipeline is always current because there is no separate 'pipeline object' to maintain. Migration from a spreadsheet is straightforward: export the rows, import them as deals, upload the documents into the matching workspaces, and the team is operating on the new system within an afternoon.