CRM & Sales
What happens when sales and operations disagree about available units?
Last reviewed
Direct answer
Units get promised that are not ready, or ready units sit unmarketed. The disagreement usually comes from different definitions: sales excludes reserved units, operations counts physically empty units, and maintenance excludes units in turnover. The operator should define "available" in writing and govern which source has authority for each condition.
Why this happens
Availability depends on several facts at once, and each lives in a different system.
A governed availability status prevents double-booking and lost revenue from units nobody is marketing.
Hypothetical example: unit availability on a monday
CRM
6 units available
Deposit-held units are marked reserved.
Operations
8 units available
Two units are physically empty and ready, regardless of deposits.
Maintenance
5 units available
Three units are still in turnover.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
Availability is a decision, not a fact recorded in one place. It depends on which events the operator counts.
The governance question
Sales data should inform occupancy, not quietly define it. The operator decides how deposits, pending move-ins and turnover affect reported occupancy and availability, and the operator-controlled operating record keeps that rule visible.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Approved definitions for available, reserved and occupied.
- Event matching between CRM move-ins and operating move-ins.
- Visible treatment of deposits and pending move-ins.
- Reconciliation of pipeline against actual census.
- Consistent definitions across sales dashboards and executive reports.
SeniorCRE perspective
In SeniorCRE’s architecture the CRM remains authoritative for pipeline while the operator’s rules decide how pipeline events affect occupancy and availability. Differences between sales and operations are surfaced as disagreements to resolve, not hidden by a merged view. Status: the Operator-Controlled Operating Record is designed and not yet implemented in any community. Current capability states and production-entry gates are published in the Evidence Record at the Trust Center; nothing here should be read as a production result.
