CRM & Sales
Should CRM data determine reported occupancy?
Last reviewed
Direct answer
Usually not on its own. CRM data should feed reported occupancy for the events it is authoritative for, such as signed agreements and scheduled move-in dates. The actual move-in and occupancy status usually come from operational or financial sources. The operator should approve how each CRM event counts toward reported occupancy.
Why this happens
Letting the CRM define occupancy can overstate it when deposits are refunded or move-ins slip.
Using CRM data alongside operational data under clear rules gives a fuller picture than either source alone.
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.
- Which number governs?
- Operator Authority
- Governing Record
- SeniorCRE Intelligence
- Execution
Illustrative figures. Governance first. Intelligence second. Execution last.
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 governing record keeps that rule visible.
Evidence → Disagreement → Authority → Governing Record
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 Governed Operating Record is designed and not yet implemented in any community. What has been built, validated and deployed is published on the evidence page, and nothing here should be read as a production result.