Inquiry triage, pre-admission clinical review, PASRR, contract execution, move-in handoff, NOMNC/ABN, waitlist, discharge with revenue close-out — the conversion from lead to resident on one record.
When systems disagree, the operator governs.
9 of 66 documented workflows — Admissions domain.·See all domains·Last updated:
Most senior housing & care software is sold as a feature list. This is a workflow library. Each section below is one admissions job-to-be-done — the problem operators actually describe, the way the platform runs the work, and what the outcome looks like when the work is run on one record instead of stitched across vendors.
Filter by decision maker
Every workflow in this library. Each section is one job-to-be-done — the problem, the way the platform runs the work, and the governing definition, source authority, reconciliation, and lineage behind it.
Outcomes at a glance
Every outcome is labeled by evidence class — industry benchmark (cites MGMA, HFMA, LeadingAge, CMS), internal estimate (modeled by SeniorCRE engineering), or expected outcome(modeled from workflow design + benchmarks; no customer communities measured yet — figures are targets, not validated results). See Industry Findings for methodology.
Inbound inquiries arrive on the website, the phone, and from referral partners. In most communities they get logged in three different systems and worked in inverse priority — whoever is loudest wins.
How the platform runs it
Every inquiry enters a single pipeline scored on payer-mix fit, acuity match, urgency, and source. SLAs route the highest-fit leads to senior sales counselors and the rest into structured nurture sequences. Every touchpoint — call, email, tour, follow-up — logs against the lead record. A daily standup runs from one funnel, not three.
What the outcome looks like
Expected outcome: inquiry-to-tour rates rise 10–20% and the average move-in time from first inquiry compresses by 5–8 days.
How does the platform run tours that convert without turning every counselor into a heroic salesperson?
Tours are run from memory. Some counselors do a structured discovery; others wing it. Conversion rates vary widely by counselor with no visibility into why.
How the platform runs it
Each tour has a discovery framework — clinical needs, financial picture, family dynamics, timeline — captured on the lead record. The system surfaces objections, suggests next-step content (move-in packets, financial-aid info, clinical capability docs), and schedules follow-ups automatically. Tour-to-deposit conversion is reported per counselor with the underlying discovery quality visible.
What the outcome looks like
Tour-to-deposit conversion lifts 15–25% across the team because the playbook is enforced instead of optional. New counselors ramp roughly 2× faster.
How does SeniorCRE run pre-admission clinical review so the community accepts the right residents?
Communities accept residents whose clinical needs exceed their capability and pay the price for months — falls, ER trips, family escalations. The clinical review at admission is often a checkbox by someone who never met the prospect.
How the platform runs it
Pre-admission clinical assessments capture diagnoses, current medications, ADL needs, behavior history, equipment requirements, and the hospital DRG / discharge summary when available. The DON reviews against community capability with a structured decision — accept, accept with conditions, decline. Decisions and clinical context flow into the care plan on day one.
What the outcome looks like
Inappropriate admissions decline. Move-in to first-incident interval extends. The DON spends less time managing residents who never should have been admitted.
How does SeniorCRE run PASRR Level I and coordinate Level II evaluations without delaying the admission?
Every Medicaid-funded NF admission requires a PASRR Level I; positives for serious mental illness or intellectual disability trigger a Level II evaluation that has to complete before admission. On a fragmented stack, the Level I is faxed, the Level II coordination is a phone tree, and the admission either delays or proceeds out of compliance.
How the platform runs it
PASRR Level I generates from the pre-admission record with the disqualifying conditions clearly screened. Positives auto-route to the state’s Level II contact with the supporting documentation packet. The admission file shows PASRR status — Level I complete, Level II pending, Level II complete — so the admissions team can sequence move-in against the regulatory clock instead of around it.
What the outcome looks like
PASRR-related admission delays drop. State-flagged PASRR non-compliance — a survey citation category — disappears as a finding because the workflow can prove the Level I was done and the Level II was coordinated.
How does the platform execute the admission contract without three days of back-and-forth?
Admission contracts are PDFs emailed for signature. Rate sheets get out of sync with the contract. Deposits and security amounts are tracked on a separate spreadsheet that the controller reconciles at month-end.
How the platform runs it
Contracts generate from the lead record with current rates, applicable care levels, and resident-specific terms. E-signature flows happen in one session with the family. Deposits and prepays post to the ledger automatically. Move-in is unblocked when every contractual prerequisite is complete.
What the outcome looks like
Time from "yes" to move-in compresses from a week to 48 hours, and the AR opens clean instead of needing month-end cleanup.
How does SeniorCRE turn move-in day into a clean handoff to clinical operations?
On move-in day the resident shows up, the family unpacks, and the floor finds out about a medication, an allergy, or a behavior history at 9 p.m. The first 72 hours set the trajectory and they often go badly.
How the platform runs it
A move-in checklist drives the day: room readiness, welcome packet, medication reconciliation, initial assessments, family orientation, dietary intake, and unit-level introductions. The clinical handoff includes everything captured during pre-admission. A 72-hour reassessment is scheduled automatically.
What the outcome looks like
Avoidable 30-day discharges drop. Family satisfaction in the first month rises. Clinical staff stop discovering critical information on the night shift.
How does the platform deliver NOMNC and ABN notices on time so Medicare appeal exposure stays inside the rules?
Medicare requires a Notice of Medicare Non-Coverage at least two calendar days before the end of covered services, and an ABN when the operator believes Medicare will not cover a service. Late or missing notice converts into liability the operator absorbs. On a fragmented stack the notice is a paper form the social worker hopes the family signed.
How the platform runs it
The platform schedules NOMNC and ABN delivery against the projected end-of-coverage date the moment the discharge plan is set. The form generates from the resident record, captures the signature on device, and posts proof of delivery to the audit log. A missed window escalates before the day-of, not after.
What the outcome looks like
Late-NOMNC liability events go to zero. Medicare appeals that previously fell to the operator for procedural reasons are now defensible because the delivery proof exists.
How does the platform run a waitlist that respects clinical fit and revenue priority?
Waitlists in most communities are a notebook at the front desk. When a unit comes available, the call goes to whoever the front desk remembers first, not to the best clinical and financial fit.
How the platform runs it
The waitlist tracks each prospect with desired unit type, payer, clinical needs, target date, and deposit status. When a unit opens, the system surfaces the matched prospects ranked by fit. Routine waitlist contact is automated. Deposit refunds and policy-driven removals are logged.
What the outcome looks like
Vacancy turnover time decreases 3–5 days, and the financial mix of incoming residents stays closer to the underwritten plan.
How does SeniorCRE manage discharge — planned and unplanned — through to financial close?
Discharges are the messiest event in the resident lifecycle. Personal belongings, medication returns, family communication, final billing, refund of unused prepay, and notification of payers and physicians often happen in five different systems and with one person trying to coordinate them all.
How the platform runs it
A discharge workflow handles the full sequence: clinical handoff to the receiving setting (hospital, home, hospice), medication reconciliation, belongings inventory, family notifications, room turnover scheduling, final invoicing, and prepay reconciliation. Each step has an owner and a deadline.
What the outcome looks like
Final invoices land within five business days instead of thirty. Family complaints about the discharge process drop sharply. Room turnover to next move-in compresses.
What One Operational Record Eliminates in Admissions
Triage inbound inquiries so the right lead gets the right response
Run tours that convert without turning every counselor into a heroic salesperson
Run pre-admission clinical review so the community accepts the right residents
Run PASRR Level I and coordinate Level II evaluations without delaying the admission
Execute the admission contract without three days of back-and-forth
Turn move-in day into a clean handoff to clinical operations
Deliver NOMNC and ABN notices on time so Medicare appeal exposure stays inside the rules
Run a waitlist that respects clinical fit and revenue priority
Claim status: what is proven, what is designed
Status as of September 29, 2026 (last modified 2026-09-29)
SeniorCRE claim evidence step and proof class by claim, as of September 29, 2026
Claim
Evidence step
What is true today
Proof to inspect
Operator and portfolio workspace foundation built (roles, hierarchy, entity tree).
Validated
Provisioning controls have been exercised repeatedly in controlled SeniorCRE conditions, including the operator onboarding wizard. Not yet performed for an operator in production; no standard duration is published.
Control test record; synthetic or de-identified data; no operator PHI.
Single-community acceptance boundary.
Architecture designed
A gate sequence derived from the migration and acceptance model. No community has gone live for an operator, so no observed duration exists.
Written deployment plan and acceptance-gate model. No execution record exists.
Portfolio-wide rollout acceptance across multi-community scope.
Architecture designed
A wave-cadence model from the deployment plan. Sequencing depends on community count, system count, data condition, source access, and operator authority decisions. Not a completed rollout.
Written deployment plan and acceptance-gate model. No execution record exists.
Connectors to PointClickCare®, MatrixCare®, Yardi®, and QuickBooks®.
Validated
Ingestion and normalization exercised against synthetic and de-identified extracts in controlled SeniorCRE conditions. No third-party integration is live in operator production.
Control test record; synthetic or de-identified data; no operator PHI.
The Operator-Controlled Operating Record is designed and not yet implemented in any community. Authority rules, reconciliation, and field-level lineage are design intent; synthetic examples do not establish working governance.
Written deployment plan and acceptance-gate model. No execution record exists.
Clinical configuration: SeniorCRE as clinical system of record, or alongside an incumbent eMAR read one direction only.
Validated
Both configurations are built and exercised in controlled SeniorCRE conditions, with one authoritative MAR at all times. No PHI workload runs in operator production.
Control test record; synthetic or de-identified data; no operator PHI.
Barcode-verified administration with an automated five-rights check at the point of medication pass.
Architecture designed
Not built. Corrected September 7, 2026: earlier pages, operator training guides, and generated answers described this control as running, which was false. Implementation boundary: four of the five medication scan surfaces open a camera preview with no decoder and match only a manually typed NDC; one mobile surface decodes frames through the browser-native BarcodeDetector API where the browser supports it (Chromium/Android; not iOS Safari, not most desktops) and compares the NDC alone. No decoding library is bundled, no surface verifies resident, dose, route, or time, and no scan result blocks an administration. The five rights are verified by the administering clinician, not by SeniorCRE.
Build-queue entry with scope and dependencies. No implementation exists.
Live write-back into operator payroll and scheduling systems.
Architecture designed
Specified and in the build queue. Read-side ingestion only today.
Build-queue entry with scope and dependencies. No implementation exists.
Implementation effort required from the operator.
Architecture designed
Deployment is staged, not effortless: platform access, source access, authority rules, reconciliation, security review, and any history migration are scoped work with operator-side effort. Any claim of zero implementation would be false.
Written deployment plan and acceptance-gate model. No execution record exists.
Validated
Controls can be shown in controlled SeniorCRE conditions using synthetic or de-identified data only.
Architecture designed
Specified and sequenced by readiness and acceptance gates — but not yet executed with an operator. Not a duration claim.
Architecture designed
Specified and in the build queue. No built capability exists to demonstrate.
Status and evidence class as of September 29, 2026. SeniorCRE has no operator-production deployment. Public timing is gate-based and operator-specific; no standard go-live duration is published. Maintained and reviewed by John Hauber, Founder, SeniorCRE, LLC. A medication-safety control was described on earlier pages as running when it was not; that correction is published in full at /medication-safety-claim.
Admissions Work, Two Architectures
Inquiry → tour
On SeniorCRE
Auto-routed by acuity + payer
On Fragmented Stack
CRM round-robin
Operator Impact
Wrong fit, lost tour
Pre-admission review
On SeniorCRE
Clinical + financial in one record
On Fragmented Stack
PDF emailed to DON
Operator Impact
Inappropriate admissions
PASRR Level I/II
On SeniorCRE
Generated; Level II routed in-app
On Fragmented Stack
Fax + phone tree
Operator Impact
Admission delays + survey citations
Contract execution
On SeniorCRE
E-sign + ledger on same record
On Fragmented Stack
DocuSign + manual GL entry
Operator Impact
Yes → move-in takes a week
Move-in handoff
On SeniorCRE
Care plan live before arrival
On Fragmented Stack
Verbal handoff at front desk
Operator Impact
Avoidable 30-day discharges
NOMNC / ABN delivery
On SeniorCRE
Scheduled + proof on device
On Fragmented Stack
Paper form, hope-it-was-signed
Operator Impact
Operator absorbs Medicare liability
Waitlist priority
On SeniorCRE
Acuity + payer + LOS scored
On Fragmented Stack
First-call-first-served
Operator Impact
Mispriced bed days
Discharge billing
On SeniorCRE
Final invoice in 5 days
On Fragmented Stack
Final invoice in 30+ days
Operator Impact
AR aging stays high
Capability
On SeniorCRE
On Fragmented Stack
Operator Impact
Inquiry → tour
Auto-routed by acuity + payer
CRM round-robin
Wrong fit, lost tour
Pre-admission review
Clinical + financial in one record
PDF emailed to DON
Inappropriate admissions
PASRR Level I/II
Generated; Level II routed in-app
Fax + phone tree
Admission delays + survey citations
Contract execution
E-sign + ledger on same record
DocuSign + manual GL entry
Yes → move-in takes a week
Move-in handoff
Care plan live before arrival
Verbal handoff at front desk
Avoidable 30-day discharges
NOMNC / ABN delivery
Scheduled + proof on device
Paper form, hope-it-was-signed
Operator absorbs Medicare liability
Waitlist priority
Acuity + payer + LOS scored
First-call-first-served
Mispriced bed days
Discharge billing
Final invoice in 5 days
Final invoice in 30+ days
AR aging stays high
How Every Workflow Preserves Authority
1
Resident authority
Clinical, financial, family-scoped views, and incidents preserve their source authority and decision context.
2
Ledger authority
Charges, payroll, AP, and AR preserve the operator-approved ledger authority and reconciliation state.
3
Evidence lineage
Every entry, edit, and access timestamped and attributed — evidence-ready.
4
Governed operating view
Census, labor, AR, incidents, and compliance surface accepted definitions with preserved alternatives.
5
Authority reconciliation
Reconciliation records which trusted definition governs the decision and preserves alternate readings for later review.
Related Institutional Resources
All workflow libraries
Platform overview
One Operator-Controlled Operating Record
Operating Infrastructure Spec
Bring institutional discipline to your senior housing portfolio.
SeniorCRE is the operating, compliance, and asset-management layer for REITs, family offices, and institutional capital allocators in senior housing & care.
no SeniorCRE SOC 2 report claimed Multi-Entity Hierarchy Audit-Ready