Senior Housing & Care Operating Questions
Your systems disagree. What happens next?
Clinical, financial, workforce, CRM and operating systems can each describe the same organization differently. Explore the questions senior housing & care leaders are asking about governance, reconciliation, authority, AI and what should happen when those systems disagree.
When systems disagree, who decides which number governs?
Three legitimate systems can report three different numbers for the same community on the same night. Integration can put them side by side. It cannot say which one has authority for a staffing, billing or board decision. That is an operator decision, and it should be made deliberately and recorded.
When systems disagree, the operator governs.
Clinical system
92
Accounting
90
CRM
91
- Which number governs?
- Operator Authority
- Governing Record
- SeniorCRE Intelligence
- Execution
Illustrative figures. Governance first. Intelligence second. Execution last.
Browse by topic
1. When Systems Disagree
Why legitimate systems produce different numbers, and who decides which one governs.
- Why do our senior living systems show different numbers?
- Which number should we trust when our systems disagree?
- What happens when two authoritative systems disagree?
- Who decides which number governs when senior living systems conflict?
- How do operators determine which operating number is correct?
- Can two different numbers both be technically correct?
- Why does integrating systems not eliminate conflicting data?
- What should happen when a dashboard disagrees with the underlying system?
- How should operators resolve conflicting operating information?
- How do we know where an operating number came from?
2. Census & Occupancy
Why census and occupancy differ across clinical, financial and sales systems.
- Why doesn't our EHR census match accounting?
- Why doesn't our occupancy report match our resident census?
- Why does CRM occupancy differ from financial occupancy?
- What is the correct definition of occupancy in senior living?
- Why do departments report different occupancy percentages?
- How should senior living operators reconcile census across systems?
- How can operators establish an authoritative daily census?
- How can census discrepancies be identified before month-end?
- How do census discrepancies affect financial reporting?
- Which system should govern occupancy reporting?
3. Data Governance
What data governance means for operators, and how it differs from integration and quality.
- What is data governance in senior living?
- Why does senior housing & care need data governance?
- Who should own data governance inside a senior living operator?
- How should a senior living operator establish data governance?
- What is the difference between data governance and data integration?
- What is the difference between data governance and data quality?
- What is the difference between data governance and master data management?
- Is a "single source of truth" enough for senior living?
- Can multiple systems remain authoritative under a governance model?
- What should a senior living data-governance framework include?
4. Source Authority
Which system is authoritative for what, who decides, and how overrides are recorded.
- What does source authority mean in senior living operations?
- Which system should be authoritative for resident census?
- Which system should be authoritative for financial data?
- Can authority depend on the specific operating question?
- Who determines source authority?
- How should source-of-truth rules be documented?
- What happens when the authoritative source is wrong?
- Can an operator override an authoritative system?
- How should overrides be documented?
- How do you preserve the original value after a governing determination?
5. EHR / EMR
How clinical records relate to finance, workforce and enterprise reporting.
- Should the EHR be the source of truth for senior living?
- What happens when EHR data conflicts with accounting?
- How should PointClickCare data be reconciled with financial systems?
- How should MatrixCare data be reconciled with other operating systems?
- How should Aline data be reconciled with accounting and workforce systems?
- Can an operator govern data without replacing its EHR?
- Does a senior living operator need one EHR across every community?
- What happens when communities use different clinical systems?
- How should EHR data be governed after an acquisition?
- Can a governing layer coexist with existing clinical systems?
6. Accounting & Finance
Why finance and operations disagree, and how finance can verify an operating number.
- Why does accounting disagree with operations?
- Why does month-end census differ from daily operating census?
- How should senior living operators reconcile revenue and census?
- Which occupancy number should the CFO use?
- How can finance verify the provenance of an operating number?
- How should adjustments to operating data be documented?
- How do conflicting numbers affect budgeting and forecasting?
- How can operators reduce spreadsheet-based reconciliation?
- How should financial systems interact with clinical systems?
- How can executives know whether a financial KPI is based on governed data?
7. CRM & Sales
How sales pipeline, deposits and move-ins relate to reported occupancy.
- Why does CRM occupancy differ from operational occupancy?
- Should CRM data determine reported occupancy?
- How should move-ins and move-outs flow between CRM and EHR systems?
- What happens when sales and operations disagree about available units?
- How should deposits and pending move-ins affect occupancy reporting?
- How can operators reconcile pipeline data with actual census?
- Which system should govern unit availability?
- How should CRM data be reconciled after a resident moves in?
- Why do sales dashboards sometimes disagree with executive reports?
- How can operators establish consistent sales and occupancy definitions?
8. Workforce & Labor
How staffing, labor and census data should be reconciled and governed.
- How should staffing data be reconciled with resident census?
- What happens when workforce and census systems disagree?
- How can senior living operators calculate labor per resident day accurately?
- Which census should be used for staffing calculations?
- How should UKG data be governed alongside clinical systems?
- Why do labor dashboards disagree with financial reports?
- How can operators connect staffing decisions to governed census?
- How should agency labor be incorporated into workforce reporting?
- How can executives trust labor KPIs across multiple communities?
- How should staffing data be governed during rapid census changes?
9. Multi-System Reconciliation
Why integration alone does not produce governed truth, and how reconciliation should work.
- How do we connect EHR, accounting, workforce and CRM data?
- Does integrating all our systems create a single source of truth?
- How do we prevent integrations from spreading incorrect data?
- What happens when integrated systems disagree?
- How should data conflicts be surfaced to operators?
- Should software automatically resolve conflicting values?
- When should a human make the governing determination?
- How should reconciliation decisions be recorded?
- How can reconciliation rules be standardized across an organization?
- What is decision lineage and why does it matter?
10. Multi-Community Operations
How multi-community operators standardize definitions without forcing one software stack.
- How do multi-community operators standardize operating definitions?
- How do operators compare communities using different software?
- How should data governance work across 10, 20 or 40 communities?
- How can regional operators establish one operating vocabulary?
- How should acquired communities be integrated into existing reporting?
- Can communities retain different systems under one governance architecture?
- How should regional leaders handle inconsistent community reporting?
- How can operators compare KPIs when underlying definitions differ?
- How should enterprise operating standards be enforced?
- How can an operator scale without forcing every community onto one software stack?
11. Executive Reporting
How CEOs, CFOs and boards can know whether a reported number is defensible.
- How does a CEO know whether a dashboard number is correct?
- How can CFOs verify the provenance of executive KPIs?
- Why do executive dashboards disagree with departmental reports?
- What should happen before a number reaches an executive dashboard?
- How should disputed numbers be displayed to executives?
- Should executives see the original values behind a governing number?
- How can boards trust senior living operating reports?
- What audit trail should exist behind executive KPIs?
- How can executives distinguish calculated data from governed data?
- What makes an operating record defensible?
12. AI & SeniorCRE Intelligence
Why AI must sit downstream of governance, and what that requires before deployment.
- Can AI determine which senior living operating number is correct?
- Should AI be allowed to override an operator's data?
- What happens when AI receives conflicting information from multiple systems?
- How can AI safely use senior living operating data?
- What data governance is required before deploying AI?
- How do operators prevent AI from acting on bad data?
- Can model confidence determine organizational authority?
- How can executives trust AI recommendations when underlying systems disagree?
- Should governance come before AI automation?
- What operating infrastructure does senior housing & care need before deploying AI at scale?
Where SeniorCRE fits
These answers are written to be useful whatever software you run. SeniorCRE is operator-controlled operating infrastructure for senior housing & care, built around a Governed Operating Record. It is designed and not yet implemented in any community, and we publish exactly what has and has not been proven.