You're running a submarket with three active prospects on the same asset. One sent an LOI in email, one called and said they'd send something, and a third handed a printed LOI at a tour. If you can't quickly answer "which LOI is current" and "who needs to be notified by Friday," you're leaking time and money. This piece explains how to track LOIs commercial real estate the way an operator does — clean, fast, and defensively.
The core idea
Track LOIs the way you run deals: a single source of truth for deal management, short status updates, and ironclad version control. Treat the LOI like the project it is — not a paragraph in your inbox. If you don't centralize, you get mis-timed option notices, repeated counter-offers, and deals that die quietly.
1) One source of truth: a single place for every LOI
Stop using five places: email, text threads, a spreadsheet, a folder named "Final-Final," and your head. Pick a single repo and make the team use it. That repo can be a transaction management platform, a disciplined folder structure in your cloud drive, or your firm's deal system — whatever your team will actually open. If you need tool guidance, consider software built to track offers, LOIs, and closing tasks so capture is consistent and discoverable.
What that repo must do:
- Store every LOI version and the supporting documents next to the property record.
- Link attachments to the relevant asset and the relevant party so file context is never lost.
- Show the current status at a glance on the asset or deal card.
Why this matters: when someone asks for the "latest LOI," you either produce it in 30 seconds or you start a debate that costs you negotiating leverage. The faster you answer, the quicker you can press the counter or pull the asset off market.
2) Use a strict, minimal status workflow
Complex workflows are a trap. Use five statuses at most: Submitted, In Review, Negotiating, Executed (or Converted), and Dead. Make those statuses visible on the asset card and mandatory to update when a change happens.
Rules to enforce:
- Every LOI upload requires a status selection and a one-sentence note. Example: "Counter received — rent, TI increased; buyer asks for 30-day exclusivity."
- Only one person can mark a status as "Executed." That prevents accidental double-counting and clarifies who closed the deal.
- When status changes to Negotiating, attach the latest redline or email so anyone can follow the thread without digging.
Why short statuses work: long custom fields get ignored. One sentence forces discipline and makes your weekly pipeline review useful instead of a pile of noise.
3) Capture negotiation history, not just final files
People confuse archiving with version control. True version control means every counter, every email summary, and every verbal commitment is recorded with a timestamp and actor. That saves you when disputes happen, gives you the timeline to forecast close probability, and prevents disconnected documents from slowing LOIs & due diligence (see our guide).
Practical steps:
- When a counter-offer comes by email, paste the email text into the LOI record and attach the file. Don't rely on the email existing elsewhere.
- For phone calls, add a one-line note immediately: time, who said what, next steps. Keep it factual.
- Keep an audit trail. If your tool can't create one, do it manually with a log file named "history.txt" and append each event with date/time and initials.
Mini-case: we had a deal where an investor verbally agreed to a rent schedule on a Tuesday, then later claimed the agreement was the original number. Because we logged that call and attached the follow-up LOI, we avoided a negotiation loop that would have lost 72 hours and half our leverage.
4) Track critical dates and option windows like your pipeline depends on them (because it does)
Critical dates kill deals: exclusive negotiation windows, due diligence periods, option notice deadlines, and LOI expirations. Create persistent alerts for these dates and make them visible on the asset card and your team calendar. Don’t leave them buried in email.
Best practice: tie each important date to an assigned task (not just a reminder). That task should show the owner, a due date, and a required resolution (accept, counter, extend, or withdraw).
If your workflow uses a centralized queue, surface those tasks in a team Action Center so follow-ups are prioritized with calendar work. That way expiring LOIs appear alongside other daily priorities instead of drifting in someone’s inbox.
Example to avoid: unsolicited LOIs often lack competition and can be lowball offers. Track when those LOIs arrive, set an ownership task, and run a parallel market test instead of accepting a quiet offer outright.
5) Measure what matters: conversion and why deals die
Most teams count LOIs. That's a start, but measure conversion rates and record a single, primary reason when an LOI dies. Short, consistent failure reasons (pricing, timing, financing, title issues, tenant use) let you spot systemic problems instead of repeating the same mistakes.
Keep KPIs simple and actionable:
- LOI-to-executed conversion: how many LOIs reach execution.
- Average time in Negotiating: long negotiations tie up capital and attention.
- Primary kill reason for Dead LOIs: pick one, update the field, and review monthly.
Don't build a dashboard for vanity. Use the data to ask different questions: is our pricing wrong? Are our terms too inflexible? Are we giving away leverage too early?
Mini-case: fast LOIs vs. disciplined tracking
Some brokers now generate LOIs from mobile tools in under 45 seconds. Speed is great for volume, but fast LOIs that aren't pushed into your central repo are worse than no LOI. We had a campaign where mobile LOIs flooded our inbox for three days. Half never made it into our system and one turned into a dispute about exclusivity. The lesson: if you accept fast LOIs, make the capture step mandatory — either the broker saves it to the repo immediately or the LOI doesn't get priority.
Implementation playbook — do this in your first week
- Pick your repo and communicate it to the team. No exceptions for convenience.
- Define the five-status workflow and the one-sentence log rule. Write it in a 1-page SOP.
- Enable alerts for expirations and option windows. Tie alerts to tasks and ownership.
- Start logging negotiation history from today. Backfill the last 30 days for active deals.
- At your next pipeline review, add a column for "primary kill reason" and enforce it for Dead LOIs.
Where a CRE-specific tool helps
If missed checklists and unclear closing ownership are your pain points, a CRE-specialized system can reduce those risks quickly. Use transaction checklists to keep due-diligence items visible; configure deal-stage triggers so moving a deal creates the right follow-ups; and keep deal comments with @mentions for clear ownership and fast answers.
- Transaction Checklists: centralize who must complete what before closing.
- Deal-stage automation (deal stage triggers): create tasks automatically when a stage changes.
- Deal comments & @mentions: call someone out in the file so they get notified and can act.
For a practical next step, track your acquisitions pipeline in CREflow to see how these elements map to real workflows.
Key takeaways
- Centralize every LOI and force a single source of truth.
- Keep status taxonomy small and make updates mandatory.
- Log negotiation history immediately — phone notes count.
- Automate alerts for expirations and option windows; assign ownership.
- Measure conversion and the single primary reason for failed LOIs.
FAQ
How do I pick the right repo for LOIs?
Pick what your team will use. If your finance team needs detailed obligations, add a lease-management tool. If brokers are mobile-first, pick a transaction platform with a mobile app or set strict folder rules. The tool should allow attachments, status updates, and date-based alerts.
Can I keep using email if I have a repo?
Yes, but treat email as raw input only. Every LOI that arrives by email must be uploaded and logged in the repo within one business day. If you can't enforce that, assign a delegate whose job is to capture inbound LOIs — avoid manual task tracking that creates pipeline blind spots by design (how manual task tracking creates pipeline blind spots).
What if the other side refuses to sign an LOI version in the repo?
Capture the highest-fidelity evidence you can: email, screenshot of chat, or a signed PDF. Attach those artifacts to the repo record and note the status as Negotiating. The point is to preserve the negotiation trail regardless of the other side's tooling preferences.
How granular should my "kill reasons" be?
Don't overdo it. Pick a short list (pricing, timing, financing, title, tenant use) and force one choice per dead LOI. The value is in consistent data; too many options mean nobody uses the field.
Before You Track This, Check This:
- Do you have one place everyone agrees to use? If not, pick it today.
- Does your repo show LOI status and critical dates on the asset card?
- Can you attach emails and phone notes to the LOI record?
- Is there a named owner for LOI capture and expiry tasks?
- Are you logging a single primary kill reason when deals die?
Tracking LOIs is not glamorous. But discipline here saves negotiation time, prevents missed deadline-driven defaults, and keeps your pipeline honest. Make the repo the habit and the rest becomes operational muscle.