Somewhere in the last few years, the question operators ask software vendors changed.
It used to be about clinical records. Can you handle assessments, care plans, medication administration, compliance? Those are still table stakes. But the operators evaluating platforms right now are asking something bigger: can this run the whole community? Resident management, billing, occupancy, dining, work orders, scheduling, the family portal, the point of sale at the bistro, and the reporting that ties it together.
That is a different kind of purchase. And it exposes a problem with how most software evaluations are run.
Every Vendor Checks Every Box
Send out a feature checklist and you will get it back fully checked by every vendor on your list. Resident management, yes. Billing, yes. Dining, yes. POS, yes. Reporting, yes.
The checklist cannot tell you the thing you actually need to know, which is whether those capabilities are one system or several systems wearing the same logo. A platform can legitimately claim dining management because it has a module for it, and still require a nightly file transfer before a cafe charge reaches a resident's statement. Both answers are "yes" on the form. They are very different Tuesdays for your business office.
This is why so many implementations disappoint. Nothing was misrepresented. The evaluation just measured the wrong thing.
Test Workflows, Not Features
The fix is straightforward. Stop asking what a platform has and start asking it to show you a complete task from beginning to end, without stopping.
A workflow test follows one real event across every system it touches. Not a module tour. One continuous demonstration, in a single session, where the vendor cannot say "and then that syncs overnight" without you noticing.
Here are five worth running with every vendor you evaluate.
-
A resident buys a coffee and a sandwich at the bistro on a Tuesday afternoon. Ask the vendor to ring it up, charge it to that resident's account, and then show you the charge appearing on their statement. Then show it in the general ledger.
Watch for how many screens, systems, or logins that takes. Watch especially for the words "and then this posts later."
Guest dining with a credit card
The resident's daughter joins for dinner and pays by card. Two people at one table, two completely different payment paths. One goes to a resident account, one to a card processor.
This is a common scenario that quietly breaks a lot of setups. Ask to see the server handle it on one check.
Salon and gift shop purchases
Same test, different revenue center. A haircut on Wednesday, a birthday card on Friday, both charged to the resident's account, both landing on the same monthly statement as the cafe purchases and the meal plan overage.
Communities running these through separate systems or paper logs are usually the ones discovering unbilled revenue at month end.
Month-end close
Ask them to walk you through closing a month. How much of that process is automatic and how much is a person reconciling two reports side by side?
This is the single most revealing question in an evaluation, because it exposes every seam between systems. The number of manual touchpoints in a month-end close is a direct measure of how integrated a platform really is.
A cross-department report
Ask for a single report that combines dining revenue, care level changes, and occupancy for one month. If that requires exporting from three places into a spreadsheet, you have your answer about whether the data actually lives together.
The Integration Question Behind the Integration Question
Nearly every platform in this space advertises integrations. Standards for exchanging data between systems exist because integration is more than a checkbox, yet the word still covers an enormous range.
Ask three specific things about any integration that matters to you:
- What direction does data flow? One-way and two-way are very different. A dining system that receives resident data from your clinical platform but cannot send charges back is only half connected.
- How often does it sync? Real time, hourly, and nightly are three different operational realities. A care level that changed this morning but does not reach billing until tomorrow is a billing error waiting to happen.
- What happens when it fails? Every integration breaks sometimes. Ask who gets notified, how you find out, and how long it typically takes to resolve. Vendors who answer that question comfortably have thought about it. Vendors who look surprised have not.
What "Purpose-Built" Should Actually Mean
Purpose-built for senior living is a phrase in every deck in this category. It is worth pressing on.
A platform genuinely built for this industry handles things that make no sense anywhere else. Meal plans with monthly allowances that carry overages and forfeitures. Residents ordering from bed because they cannot get to the dining room. A daughter in another state who needs visibility into her mother's charges. A single resident with a dietary restriction, a care level, a meal plan, a salon appointment, and a guest coming Sunday, all of which need to be true in every department at once.
Software adapted from hospitality, healthcare, or property management can be made to do these things. The question worth asking is whether it does them natively or through configuration, because configuration is where implementations get long and expensive.
A useful test: ask the vendor to explain meal plan forfeitures without stumbling. Vendors who live in senior living answer immediately.
Why This Matters More at High Occupancy
There is a timing element to all of this. Senior housing occupancy averaged 89.9% in the second quarter of 2026, the twentieth consecutive quarter of growth, according to NIC MAP data. Most communities are close to full.
When you have empty units, growth comes from filling them. When you are near capacity, growth has to come from operating better, which means capturing revenue you already earn, spending labor where it actually matters, and finding problems in weeks rather than quarters. All of that depends on the systems underneath.
The gap between a platform that mostly works and one that genuinely connects used to be an annoyance. At 90% occupancy it is a margin decision.
Before You Sign
Three things worth doing regardless of which direction you go:
- Talk to a reference community that runs the same combination of modules you plan to use, not just the same vendor. A platform can be excellent at clinical records and mediocre at dining, and a reference using only half the system will not tell you that.
- Ask what the implementation actually looked like, in weeks and in staff hours. Then ask the reference the same question and compare the answers.
- Run your five workflow tests with every finalist on the same day if you can. Fresh comparison is far more revealing than notes taken three weeks apart.
The right platform for your community is the one that can show you a resident's Tuesday from the coffee they bought to the statement they receive, without changing screens or explaining what happens overnight.
If you want to see how the Genesis Platform handles those workflows, from a cafe charge through to the month-end close, take a look.
Experience Genesis Platform Now
Or if you would rather have our team run your own workflow tests against your community's real scenarios, request a discovery call and we will walk through them with you.
Sources: LeadingAge CAST technology planning and vendor selection guidance; HL7 FHIR data exchange standards; NIC MAP second-quarter 2026 senior housing occupancy data.