Skip to content

Operator-controlled operating infrastructure for senior housing & care

Your systems disagree. Who decides which number goes to your owner?

SeniorCRE is designed to help senior housing & care operators reconcile conflicting information, establish operator-controlled authority, and create a defensible operating record across existing systems.

Bring us one occupancy number your systems disagree on. We’ll show who should decide which one governs, and the evidence behind it.

Explore a Founding Operator ValidationSee How SeniorCRE Works

Prefer a general conversation first? Request an Executive Briefing

Designed, not yet implemented in any community.

Start From Your Seat

Board reporting, financial close and community operations each need a number the organization can defend.

  • For the CEO

    Can you trust the operating picture you report to your board?

    Open the CEO guide

  • For the CFO

    Can you defend every number at month-end close?

    Open the CFO guide

  • For the COO

    How do you scale operating consistency across communities?

    Open the COO guide

Illustrative demo

When four systems disagree, who decides?

Pick a month, see four systems disagree, apply the rules one at a time, then check the evidence yourself.

Synthetic data for a 120-unit community. Not an operator result.

1. Pick a month

2. Four systems, four occupied-unit counts at month-end

  • Clinical census (EHR)

    101

    Who is physically in residence

  • Billing ledger

    103

    Who is being charged rent

  • Sales CRM

    102

    Who has signed or is still active

  • Bed board

    100

    Which units show as taken

4 systems report 4 different counts, from 100 to 103.

3. Apply the operator's rules

Read the four rules
  • R1 Definition: An occupied unit has a resident physically residing at 11:59 pm on the last day of the month. Respite stays count. Approved leaves with a held unit count.
  • R2 Authority: For physical residence, the clinical census governs. Billing, CRM and bed board corroborate; they do not decide.
  • R3 Hold limit: A leave longer than 30 days releases the unit. It is no longer counted as occupied.
  • R4 Transfers: A resident who moves units is counted once, at the destination.
    Connected data is not governed truth. Three systems report 118, 121 and 120 residents. The SeniorCRE sequence: preserve the source facts, keep conflicting answers visible, the operator defines who decides, the Operator-Controlled Operating Record, intelligence only from governed information, execution only with authorized action. Coherence before Intelligence. Designed architecture; illustrative data.
    The same disagreement, as one frame: three systems, three answers, and the sequence that resolves who decides. Counts are illustrative, not validated customer results.

    The governing sequence

    Three systems can report different numbers. None becomes authoritative merely because it is connected. The operator determines the governing definitions, evidence, decision authority, and permitted use.

    1. Evidence

      Preserve source facts, definitions, timestamps, and provenance.

    2. Disagreement

      Identify material differences without silently overwriting conflicting information.

    3. Authority

      Apply operator-defined policies and authorized decision rights.

    4. Operator-Controlled Operating Record

      Establish the accountable operating representation of governed facts and unresolved exceptions.

    5. Intelligence

      Apply intelligence within explicit evidence and authority boundaries.

    6. Execution

      Permit actions only through appropriate authorization and controls.

    A model confidence score never creates organizational authority.

    Illustrative demonstration. Real-world operator validation is the objective of the Founding Operator Program.

    Validate This in Your Operating Environment

    When systems disagree, the operator governs.

    What the architecture is designed to give the executive team

    • Defensible operating information

      Understand why operating systems disagree and retain the evidence behind authorized numbers.

    • Operator-controlled authority

      Establish who can approve definitions, resolve disagreements, and authorize decisions.

    • Governed intelligence

      Enable SeniorCRE Intelligence to operate within defined information and action boundaries.

    Intended capabilities and validation objectives — not measured operator outcomes.

    The first engagement

    Prove the operating record against a real disagreement.

    Explore a scoped validation using historical operating information to examine conflicting definitions, source evidence, operator authorization, and decision lineage. Participation follows only after scope, data handling, responsibilities and acceptance criteria are agreed in writing.

    What your organization brings

    • An executive sponsor and an accountable owner for the disputed occupancy number.
    • Agreement on the occupancy definition, purpose, reporting period and source authority.
    • Authorized source access and data-handling arrangements before any real operator data is used.
    • Written scope, acceptance criteria and participation terms before commitment.

    No confidential resident information is needed for the initial conversation. Do not send source files before authorized data handling is agreed.

    What the paid phase is intended to deliver

    • One governed occupancy figure

      A defined occupancy field with preserved source assertions, visible disagreement, an operator-defined authority rule and reconciliation. Not a portfolio-wide deployment.

    • Real-file operator proof

      Phase 1 proves the governed occupancy figure on the operator’s own authorized historical files, with the operator’s written acceptance of the result. Acceptance is a contractual requirement, not a completed acceptance; recurring close acceptance is Phase 2.

    • Independently traceable evidence

      A board-reviewable artifact whose governed figure can be walked back to its source rows by a reviewer outside the build team. The review is an acceptance requirement, not a completed review.

    30 minutes. One number your systems disagree on. No resident data needed.

    Explore a Founding Operator Validation

    Prefer a general conversation first? Request an Executive Briefing

    Two roads. One operating architecture.

    Operators do not have to rip and replace their technology stack to begin.

    Your communities today

    Road 1

    Govern your existing systems

    Keep the systems you already use.

    Start with one disputed census or labor figure from operator-supplied exports. Preserve the source records, agree the definition, name the authority and record the determination with its lineage.

    What's included, what's not

    Systems that stay in place

    • EHR / eMAR
    • Workforce
    • Accounting
    • CRM

    Not required to start

    • Rip-and-replace
    • System replacement

    Existing clinical, workforce, accounting and CRM systems remain in place. Named third-party connectors remain roadmap, not live; proof in an operator workflow is still required.

    Govern first. Replace only by choice.

    Explore the Operator-Controlled Operating Record

    Road 2

    Run on SeniorCRE

    Use SeniorCRE as the system of record for selected operating domains.

    For a community moving off paper, begin with resident and operating information entered directly into SeniorCRE, tablet charting and recorded incident notices. Agree scope, success criteria and exit terms; retain the paper record alongside and introduce functions in stages.

    What's included, what's not

    Starting scope

    • Resident & operating info
    • Tablet charting
    • Recorded incident notices

    Excluded from starting scope

    • Medication / eMAR
    • Billing
    • Payments
    • Payroll

    Starting scope excludes medication/eMAR, billing, payments and payroll. Medication administration and eMAR are roadmap, not built; clinical domains require build and clinical sign-off. No operator workflow validation or production deployment is claimed.

    The operator chooses the road.

    Explore Run on SeniorCRE

    Both roads end at an operator-controlled record.

    What sits above the record

    What sits above the record

    SeniorCRE Intelligence Layer

    Both roads produce the record. The Intelligence Layer is the band designed to reason from it — downstream of operator authority, never above it.

    Designed · not yet implemented in any community

    • Operator-authorized context
    • Role-aware scope
    • Permission boundaries
    • Traceable answers
    • SeniorCRE Intelligence (proposed)

    SeniorCRE Intelligence is the proposed layer above the operator-controlled record. Its 20 specialized intelligence roles and four separately described foundational systems are part of the product architecture, not validated customer deployments.

    SeniorCRE Superintelligence is the proposed governed orchestration and evaluation architecture. Over time, permissioned feedback could improve agent recommendations and coordination through measured outcomes, independent evaluation and human-approved releases. Intelligence may improve; authority remains with the operator.

    Design intent. No deployed or independently verified agents are claimed.

    How the Intelligence Layer is designed

    Designed for Institutional Accountability.

    SeniorCRE is being developed to establish operator-controlled authority over fragmented operating information while preserving existing systems and organizational decision rights.

    Designed · Not yet implemented in any community.

    The approach is being developed and operator validation is pending. The Operator-Controlled Operating Record is designed and not yet implemented in any community. No production deployments or measured operator outcomes are claimed.

    Explore the ArchitectureReview the Trust CenterUnderstand Operator Authority

    Real operator reconciliation

    The first proof we are working toward

    One operator’s reconciled month-end close — census, payroll and general ledger agreeing under the operator’s own rules — that the operator’s CFO is willing to stand behind.

    Status: Not yet achieved

    No operator has completed this close on SeniorCRE. When one does, this section will show the dated result and what it does and does not prove.

    Reproducible findings

    What senior housing & care leaders say they need

    68%
    of senior housing & care technology leaders named data integration the top use case for AI in 2026. Ziegler CTO Hotline, as reported by Senior Housing News, August 12, 2026
    76%
    cited fragmentation among technology platforms as an issue their organizations face. Ziegler CTO Hotline, as reported by Senior Housing News, August 12, 2026
    77%
    said operational efficiency was the top priority for new technology initiatives in 2026. Ziegler CTO Hotline, as reported by Senior Housing News, August 12, 2026
    77%+
    of surveyed executives ranked interoperability a top-three barrier to technology implementation. Argentum, The State of Technology Adoption in Senior Living, July 23, 2025

    Survey respondents describe their own priorities. These figures show the problem buyers name; they are not evidence that SeniorCRE solves it. Coherence before Intelligence.

    Go deeper

    Pick a topic. It opens right here on the page.

    All other topics on this page

    Before two numbers can be compared, they must mean the same thing.

    A hypothetical example: Community A reports 91% occupancy. Community B reports 91% occupancy. One denominator includes temporarily unavailable units; the other excludes them. The two figures are not yet like-for-like.

    Like-for-Like Check · hypothetical

    Metric definition
    Reported occupancy — occupied units ÷ available units
    Numerator
    Occupied units at period end
    Denominator
    Community A includes temporarily unavailable units; Community B excludes them
    Reporting period
    Same calendar month
    Source
    Community A: census export · Community B: billing system
    Comparability status
    Not yet comparable
    Unresolved difference
    Whether temporarily unavailable units belong in the denominator

    Decision Evidence Passport · proposed pattern

    Source evidence
    Both system exports, retained with lineage
    Metric definition
    Reported occupancy, as each system computes it
    Unresolved disagreement
    Denominator treatment of temporarily unavailable units
    Responsible decision-maker
    The operator’s designated authority for this metric
    Authorization status
    Pending operator review

    Illustrative proposed workflow — not an operator-validated result. The executive-facing insight stays separated from its supporting evidence and authorization: people decide; the record shows why.

    Why SeniorCRE

    Watch: Why SeniorCRE (2:09)

    Why SeniorCRE · Transcript

    Discover what your organization knows—but hasn’t been able to see.

    See. Understand. Investigate. Decide.

    One operator question, followed from signal to a human decision. This is a scripted future-state example, not open-ended AI.

    Concept illustration — fictional data; not a deployed or operator-validated capability.

    1. See

      Portfolio signal: nursing overtime at Facility A is up over the last 12 weeks. Data refreshed from the payroll extract dated Monday.

    2. Understand

      The measure: overtime hours ÷ worked nursing hours, nursing roles only, definition version 3 approved by the operator.

    3. Investigate

      Authorized sources: payroll (reconciled), schedule (partial), acuity (unavailable). Second question: “Is this the same pattern at Facility B?” — not comparable yet; see the Like-for-Like Check.

    4. Decide

      Options for the nurse leader and finance: approve a review, defer until acuity data arrives, or escalate. The operator can always answer “I cannot verify this.”

    Experience above; evidence beneath

    The Trust Line is a way of picturing the platform, not a new layer. Trust is checked throughout an investigation; it is never a one-time conversion of raw data into universal truth.

    Concept illustration — fictional data; not a deployed or operator-validated capability.

    Above the line · the experience operators want

    SeeUnderstandInvestigateDecide

    The Trust Line · checked continuously

    Source applicability · Evidence status · Permissions · Definition · Uncertainty · Authorized review

    Below the line · the foundation that makes it inspectable

    Source systemsOperator-Controlled Operating RecordGoverned context and lineageTruth and action policies

    Text version: above the line, operators see, understand, investigate and decide. At the line, each step is checked for source applicability, evidence status, permissions, definition, uncertainty and authorized review. Below the line sit source systems, the Operator-Controlled Operating Record, governed context and lineage, and truth and action policies. Nothing moves upward automatically.
    See the full architecture The operating record AI Governance

    Why This Matters to Institutional Operators

    Coherence before Intelligence.

    You want a single source of truth. The operator decides which number governs. Occupancy, staffing, care, and finance systems may provide conflicting answers. Dashboards display information; they do not determine which source has authority. SeniorCRE is designed to help operators establish governing records through evidence-based reconciliation and traceable human approval.

    • Data integration tells you what the systems say.
    • Data standardization helps you understand what the systems mean.
    • Operator-authorized governance establishes which information controls a particular business decision.

    Every disagreement costs executive time, weakens confidence in what gets reported, and can complicate lender and board relationships.

    Institutional pressures and illustrative financial exposure
    Institutional capital
    Institutional ownership and investment place greater emphasis on consistent, reviewable portfolio reporting.
    Portfolio expansion
    Growth and acquisitions can multiply systems, operating models and definitions that must be reconciled.
    Fragmented information
    Clinical, finance, workforce, census and CRM systems can each be correct for a different purpose.
    Executive accountability
    Leadership needs to establish the meaning, authority and provenance of information used in defensible decisions.

    The Exposure of Operating Without a Shared, Authorized Record: possible exposures to investigate, not verified losses or promised savings.

    Illustrative assumptions · October 31, 2026

    Revenue exposure starts at zero. Include only revenue exposure that excludes the reconciliation labor modeled below.

    Illustrative inputs, not measured results

    Annual reconciliation labor cost
    $72,000
    Annual revenue exposure · assumed
    $0
    Combined modeled exposure / year
    $72,000

    800 portfolio units · $7,200 per community / year · $90 per unit / year. Alternate views of the same total.

    Reporting/operational inefficiency: $18,000 within the labor cost above—not added again.

    Illustrative financial exposure based on user-adjustable assumptions. Not a measured SeniorCRE customer outcome.

    Method, assumptions and exclusions

    Illustrative teaching assumptions. The community count, monthly hours and loaded hourly cost reuse the October 16 synthetic example above. Units and inefficiency share are invented context; revenue exposure starts at zero and must be supplied by the visitor. No industry benchmark or customer measurement is used.

    Annual labor cost = communities × monthly reconciliation hours per community × 12 × loaded hourly cost. Revenue exposure = communities × annual assumed revenue exposure per community. Combined exposure = labor + non-overlapping revenue exposure. Inefficiency share is a subset of labor, not an additional cost. Per-community and per-unit values normalize the same total.

    Revenue exposure must exclude reconciliation labor already modeled here. Clinical, acquisition and staffing risks are not separately monetized. Labor may already be budgeted and is not necessarily avoidable cash expenditure. Exposure is not verified loss, recoverable savings, ROI or a SeniorCRE forecast. Uniform assumptions across communities; units are a capacity basis, not occupied units. Inputs are calculated locally and are not saved or submitted.

    Help Establish the Next Standard for Operating Information.

    SeniorCRE is seeking its first Founding Operator to validate a fundamental proposition: when operating systems disagree, the operator—not the software vendor or AI model—must determine which information governs.

    Working within the operator’s existing technology environment, the engagement will focus on demonstrating an authorized, traceable reconciliation of conflicting operating information.

    • Keep your existing systems

      Evaluate the governing layer without requiring wholesale replacement of established operating platforms.

    • Retain operator authority

      Define which sources and rules govern operating determinations.

    • Establish traceable evidence

      Evaluate whether disagreements, governing decisions, approvals and resulting records can be documented and reviewed.

    Evaluation objectives, not validated operator outcomes. The paid first phase remains bounded by the written participant agreement.

    One operating problem, one defined validation: stages and proposed acceptance criteria

    1. Define

      Identify a material occupancy or census disagreement involving existing operating systems.

    2. Establish authority

      Document the operator’s governing definitions, source priorities, exception handling and authorized decision makers.

    3. Demonstrate

      Test the proposed reconciliation workflow using appropriately authorized operating information.

    4. Validate

      Evaluate whether the resulting operating record preserves the governing determination and its supporting evidence.

    Proposed acceptance criteria

    • Source evidence is identifiable.
    • Conflicting values are preserved.
    • Operator-defined authority is documented.
    • The authorized determination is traceable.
    • Decision lineage can be reviewed.
    • The operator formally accepts or rejects the demonstrated result.

    Authorized data access, implementation scope, security requirements, participation commitments and acceptance criteria must be agreed during qualification and documented before work begins. No completion date, savings or operational outcome is guaranteed.

    Existing systems remain in place for this initial validation. Named third-party connections are roadmap, not live; operator-supplied exports require appropriate authorization.

    Watch The Architecture of Coherence (3:45)
    Open the full film and transcript
    Become a Founding OperatorReview program scope and commercial terms

    Proof hierarchy

    How we show our work

    Four kinds of evidence, strongest first. The first is the one we have not earned yet, so it is stated first with its status rather than buried at the end.

    1. Real operator reconciliation

      One operator's reconciled month-end close — census, payroll and general ledger agreeing under the operator's own rules, with the operator's CFO willing to stand behind it.

      Not yet achieved

      Read the first-proof gate

    2. Reproducible findings

      Published buyer research with named sources and dates. Open the original and check the figure yourself — nothing here asks for your trust.

      Published, dated and sourced

      See the findings

    3. Illustrative demo

      A conceptual occupancy dispute you can run in the browser: four readings disagree, the rules apply one at a time, the evidence stays visible. Invented figures that show the method, not a result.

      Conceptual, not operator data

      Run the demo

    4. Architecture and doctrine

      The layered design, the Operator-Controlled Operating Record and the authority rules behind the method — published design intent, open to inspection.

      Published design intent

      Open the architecture

    Architecture and doctrine

    The governing layer for your senior housing & care stack

    Coherence before intelligence. The operator governs the record, and everything above it runs on governed truth.

    Click any layer to explore

    Five reading bands. The canonical technical architecture remains seven layers — Source systems, Evidence & provenance, Disagreement detection, Operator Authority Chain™, Operator-Controlled Operating Record, SeniorCRE Intelligence, Controlled execution. This view groups them for reading; it does not rename or replace them.

    Designed, not yet implemented in any community. Illustrative architecture: layers describe design intent, not deployed production status. Source types shown do not imply a current integration, certification, or partnership.

    Why these five layers, and what each one governs

    One Operator-Controlled Operating Record. Authority Stays With You.

    • Source authority

      You decide which system, role or policy has the final word for each figure, and for which purpose.

    • Evidence-based reconciliation

      When systems disagree, the original values stay on file side by side, so the difference is visible instead of quietly overwritten.

    • Traceable human approval

      A named person approves which value governs, and the record keeps who decided, when and why. Software never makes that call for you.

    Coherence Makes Intelligence More Reliable

    SeniorCRE Intelligence is designed to reason from operator-authorized evidence, definitions and permissions. These intended applications are not commercially validated capabilities or measured performance gains.

    Intended intelligence applications · design intent
    Portfolio occupancy intelligence
    Interpret census and move-in differences under the definition authorized for each report.
    Revenue integrity
    Examine differences between resident status, service records and finance definitions before drawing revenue conclusions.
    Labor and staffing intelligence
    Interpret scheduled hours, agency use and overtime under agreed definitions.
    Clinical and acuity intelligence
    Explore resident-information differences within separately approved clinical scope and reliance gates.
    Acquisition integration intelligence
    Compare inherited operating definitions and source authority before combining portfolio reports.
    Executive and board reporting
    Explain operating figures with the source evidence and operator-approved rationale behind them.

    Operating record: what the organization authorizes for the purpose. Intelligence: what it may learn from that information. Execution: what people or systems are separately permitted to do.

    Explore SeniorCRE Intelligence

    First Founding Operator · inquiry

    Explore Becoming SeniorCRE’s First Founding Operator

    Begin a discussion about one material occupancy or census disagreement, your organization’s authority and the evidence required to accept or reject a proposed validation.

    Start with the inquiry — it tells us which number to prepare for.

    Do not include resident-identifying information or confidential operating records.

    Rather look at the calendar first?

    The inquiry is the usual path. If you would rather pick a time now, book the 30-minute assessment directly — no waiting for an email back.

    Book a 30-Minute Assessment
    What the assessment discussion can cover
    1. Portfolio information fragmentation
    2. Cross-system reporting disagreements
    3. Operator-defined authority requirements
    4. Potential economic exposure
    5. A proposed 90-day validation approach

    A proposed validation approach is a discussion topic, not a delivery commitment.