Build or buy · The governance architecture
Someone has to design and maintain the governance architecture.
The question is whether it has to be you.
Every operator already has governance. Definitions, source authority, resolution habits and decision history exist whether or not anyone wrote them down. What differs is whether that apparatus is designed and maintained on purpose, or reconstructed each time a figure is questioned.
SeniorCRE gives senior housing & care operators a purpose-built operating authority infrastructure without requiring them to design and maintain the entire governance architecture themselves. Existing systems remain in place, while operators establish which facts govern decisions, preserve supporting evidence and control downstream intelligence.
Designed, not yet implemented in any community. No production deployment, measured portfolio rollout or validated operator outcome is claimed here.
01 · The choice you already have
Three ways the apparatus gets established.
These are not products. They are the three postures available to any operator, and each one is a legitimate answer for somebody. The differences are what they require and what they leave unsettled.
01
Let it emerge
What it requires: No up-front work. Definitions, authority and resolution exist informally and are re-derived when someone asks.
What it does not settle: Nothing is written down, so each disagreement is argued again and the answer depends on who is asking.
02
Design and maintain it yourself
What it requires: A standing owner for the whole apparatus, plus the capacity to author definitions, declare authority, write reconciliation rules, keep lineage, manage permissions and retention, and re-open all of it when the business changes.
What it does not settle: It does not remove the decisions. It moves the standing work of keeping the structure current onto your team, indefinitely.
03
Adopt a purpose-built operating record
What it requires: The operator still declares definitions, source authority, reconciliation rules and permissions. The structure that records them, preserves the evidence and enforces the limits is supplied rather than engineered.
What it does not settle: It does not decide for you. Authority over what the business accepts stays with the operator, and the gates that would demonstrate it still have to be met.
The rest of this page is about the second posture only — what keeping the structure yourself actually contains — so the choice can be made on the work rather than on the slogan.
02 · What "yourself" contains
Eight obligations that do not finish.
Governance is not a project with an end date. Each item below is standing work: it has to be authored once, kept current, and be producible when someone outside the building asks. If any of them has no named owner today, that is the gap — regardless of which posture you choose.
01
Definitions
Author and version the definitions of occupancy, census, labor hours, care level and reporting period — separately for each purpose they serve.
02
Source authority
Declare which system, role or policy has the final word for each field, and for which purpose. A different source may stay valid elsewhere.
03
Reconciliation rules
Decide in advance how a disagreement between valid readings is detected, reviewed and resolved — including who may grant an exception.
04
Decision lineage
Keep who approved a governing value, when, on what evidence and for what purpose — retrievable long after the person who approved it has moved on.
05
Access and action permissions
Establish who may read, who may act, who may escalate, with which limits and what human oversight each action requires.
06
Change control
Define what happens to the record when a system is replaced, a definition changes, a reporting period is restated or a community is acquired.
07
Evidence retention
Set how long original source readings, approvals and reasoning are kept, in what form, and how they are produced on request.
08
Regulatory and payer change watch
Track the changes that alter what must be recorded or reported, and re-open the definitions and rules they touch.
What each obligation has to leave behind
Definitions
A definition register with purpose, owner and effective date.
Source authority
A source-authority matrix keyed by field and purpose.
Reconciliation rules
Written resolution rules with an exception path.
Decision lineage
An approval trail tied to the value, not to a mailbox.
Access and action permissions
A permission model separating reading from acting.
Change control
A change procedure that survives the change.
Evidence retention
A retention schedule with a retrieval route.
Regulatory and payer change watch
A review trigger tied to external change, not to memory.
The test for any of these is the same: an owner, lender or surveyor asks a question about a figure from two years ago. Can the answer be produced from the record, rather than reconstructed from memory and a spreadsheet?
03 · Who holds this work today
The pieces usually exist. The standing ownership usually does not.
In most senior housing & care operators this work is already being done — split across finance, information technology, compliance, clinical leadership and operations. Finance holds reporting periods and definitions. IT holds systems and access. Compliance holds retention and survey readiness. Clinical leadership holds scope and reliance. Operations holds census and staffing reality.
What is usually missing is not intelligence or effort. It is a single standing owner for the whole apparatus, and one place where definition, authority, reconciliation and lineage are recorded together instead of in four systems and two habits. Some operators do have a data-governance function; the question worth asking is whether it reaches operating decisions or stops at reporting.
04 · When building it yourself is right
There are operators for whom this is the correct answer.
Building the structure in-house is not the naive option. For some portfolios it is the strongest one. It is the right answer when:
- You have a standing data and engineering function, and intend to keep it funded.
- Your operating processes are genuinely bespoke and you do not want them standardized.
- You treat this apparatus as core intellectual property and want no external dependency for it.
- You can name the person accountable for the record five years from now, and the one after them.
What comes with it is the maintenance, not the design. A horizontal platform does not know what an eMAR, a care level or a state survey is until your team teaches it, and the teaching does not end: every regulatory change, payer-model change and new joint-venture structure becomes an engineering project. That is a defensible cost allocation. It is not a free one.
05 · Before you commit
Eight questions that work either way.
Ask these before choosing a posture, and ask them of any vendor as well. If you can answer all eight from a written record today, the build-yourself path is well grounded. If you cannot, the gap is the same one either way — only the owner differs.
- 01
Who signs the definition of occupancy for a lender report versus a staffing review — and are those two allowed to differ?
- 02
Where is the source-authority policy written down, and can it be produced on request?
- 03
When two authoritative systems disagree, is the resolution recorded, or re-derived each time?
- 04
Could you show who approved a governing figure eighteen months ago, and the evidence they saw?
- 05
What happens to the record when you acquire a community running different systems?
- 06
Who owns this apparatus when the person who built it leaves?
- 07
What would an owner, lender or surveyor need to see today to consider the question answered?
- 08
What does keeping the structure current cost each year, and who authorizes that cost?
06 · Where SeniorCRE fits
The operator decides. The structure is supplied.
SeniorCRE is the operator-controlled operating infrastructure for senior housing & care. The design intent is that the operator keeps every authority decision — which definition applies, which source governs, which reading is accepted, who may act on it — while the record preserves the evidence and the path to approval.
Deployment remains the operator's choice. Keep the systems you run today and have the operating record govern what they produce, or deploy SeniorCRE itself as the system of record for defined functions. Neither path is presented as the only one, and neither is presented as available today without its gates.
No operator-production deployment, live named connector, measured portfolio rollout or standard go-live duration is claimed. Replacement of a fixed number of systems within hours is not an available offer or a measured result. Medication administration/eMAR and third-party write-back are excluded from starting scope. Synthetic examples, architecture documents and controlled tests are not operator acceptance.
Bring the eight questions to a working session.
The briefing is a working review of your own definitions, source authority and disagreement history — not a product demonstration. Scope, prerequisites and acceptance gates are stated before anything is proposed.