Senior living operations reporting
Census and occupancy by care level, move-ins and move-outs, payer mix, agency labor cost per resident day, and NOI by community — in one model built on the systems you already run. A senior US-based engineer builds it and keeps it refreshing. Most builds in 3–5 business days.
Representative dashboard — sample data
The operator's view
Most operators can tell you today's census to the resident. Far fewer can say which community earned money last month, why, and how much of the answer was agency staffing. We build reporting that puts the operating picture and the financial picture in the same model — occupancy by care level, move-ins and move-outs, length of stay, payer mix, labor and dining cost per resident day, and net operating income per community.
The information already exists; it is just scattered. Census lives in the resident or clinical system, prospects live in the sales CRM, hours live in payroll and scheduling, and revenue and expense live in the general ledger — each on its own calendar, each with its own definition of a "unit." Joining them once, properly, is what turns four exports into a monthly operations review that starts with agreement instead of reconciliation.
What we build for operators
Buy a block of prepaid Flex hours and, if you're unhappy within the first 4 hours, we refund you in full — no questions asked. Hours are deducted only for work you've reviewed and approved, there's no project minimum, and your banked hours never expire.
Why operators call us
You send the request; a senior engineer models your resident, CRM, payroll, and ledger data around the way your communities actually run.
Independent living, assisted living, memory care, and skilled units carry different rates, different costs, and different demand. Held as one dimension, occupancy and revenue per occupied unit read correctly per level instead of blending into a single building number.
Net move-ins, move-out reason, and length of stay tracked together, so a flat census reads as what it actually is — strong sales offsetting attrition, or a quiet month in both directions.
Payroll and scheduling hours joined to daily census, so agency, overtime, and straight-time cost can be compared across communities on the same denominator rather than argued about from two different reports.
Private pay, Medicaid, Medicare, and VA revenue shown as a mix with trend, so a shift in who is paying shows up as a chart while there is still time to respond to it, not as a variance at close.
Revenue, controllable expense, and net operating income per community on one definition — so the regional conversation is about why a building differs, not about whose spreadsheet is right.
Occupancy, resident days, and cost per resident day written once as governed measures, so the executive director, the regional, and the CFO are all reading the same arithmetic.
Four levers decide it: how full the building is, what each occupied unit earns, what it costs to staff, and how long residents stay. Occupancy and rate set the revenue line; labor — especially agency and overtime hours — is the largest controllable expense; and length of stay quietly determines how much sales effort the community has to reproduce each month just to hold flat.
A model that carries only one or two of those levers will mislead. A community can look strong on occupancy and still trail on NOI because its mix has drifted toward lower-rate units, or because it is covering a vacant care role with agency staff at a premium. Those conclusions only appear when census, rate, payer mix, and labor sit in one model with consistent definitions — see Power BI dashboard development for how a build like this runs.
Care levels are not interchangeable, and reporting that averages across them hides most of what a regional needs to know. Here is what leadership typically watches at each level, and why the same metric behaves differently as acuity rises.
| Care level | Census & revenue metrics | Cost & mix metrics |
|---|---|---|
| Independent living | Occupied units, occupancy vs budget, average rate per occupied unit, net move-ins | Mostly fixed staffing; dining cost per resident day is the swing item |
| Assisted living | Occupancy, base rate plus level-of-care revenue, care assessment changes | Care hours per resident day, overtime share, agency reliance by shift |
| Memory care | Occupancy, rate per occupied unit, shorter and more variable length of stay | Highest staffing ratio; agency cost per resident day moves NOI fastest here |
| Skilled nursing | Daily census, admissions and discharges, revenue per patient day | Payer mix across Medicare, Medicaid, VA and private pay; nursing hours per resident day |
| Portfolio roll-up | Occupancy and net move-ins by community and region, with trend | NOI by community, controllable expense per occupied unit, labor as a share of revenue |
Census, unit and care-level detail, and move-in and move-out dates come from the resident or clinical platform your communities already run. Prospects, tours, deposits, and move-in dates come from the sales CRM. Hours, agency invoices, and overtime come from payroll and scheduling. Revenue, controllable expense, and NOI come from the general ledger. Anything still living in a spreadsheet — a rate sheet, a budget, a market-rate comparison — can join the model too.
Senior living platforms vary in what they expose: some offer a documented API, some a reportable database, and some realistically only scheduled exports. All three can produce dependable reporting, but the design differs, so we establish it in the scope estimate before any hours are used rather than discover it mid-build. Most skilled nursing and senior care operators we speak to are on PointClickCare, and getting operational data out of it is specific enough to have its own page — our PointClickCare Power BI dashboard page covers the extraction routes, what Advanced Insights does and does not do, and what a realistic refresh schedule looks like. Once connected, we configure scheduled refresh in the Power BI service — Microsoft's documentation on data refresh in Power BI (opens in new tab) covers the mechanics we set up — so the morning numbers are current without anyone exporting a thing.
| Source | What it contributes | Dashboard it feeds |
|---|---|---|
| Resident / clinical platform | Unit inventory, care level, daily census, move-in and move-out dates | Census & occupancy, length of stay |
| Sales CRM | Inquiries, tours, deposits, expected move-in dates, lost reasons | Sales funnel to move-in, forward census |
| Payroll & scheduling | Worked hours by department, overtime, agency invoices and rates | Labor cost per resident day, agency reliance |
| Billing / AR | Resident charges, level-of-care revenue, payer source, collections | Payer mix, revenue per occupied unit |
| General ledger | Revenue, controllable expense, budget by community and account | NOI by community, budget vs actual |
Agency and overtime hours are the fastest-moving controllable line in most communities, and they are also the hardest to see, because the hours sit in scheduling, the cost sits in invoices, and the denominator — resident days — sits in the census system. Until those three are joined, "we're using too much agency" is a feeling rather than a figure a regional can act on.
We model worked hours by department and shift against daily census, so agency, overtime, and straight-time cost per resident day are comparable across buildings and care levels, with the premium over in-house cost shown explicitly. If payroll reporting is the bigger problem across your whole organization, our Power BI payroll dashboard page covers that work directly.
You buy prepaid Flex hours that never expire, at published prices: Starter $2,500, Growth $4,600, or Power $8,000, with senior US-based work from $100/hour. A first census, labor, and NOI build typically fits inside one block, and most builds ship in 3–5 business days once you approve the scope estimate.
Compared with a traditional consultancy, there is no project minimum, no retainer you have to keep feeding, and no unused hours expiring at quarter end — hours deduct only for work you have reviewed and approved. See how prepaid Flex hours work, or our affordable Power BI consulting page for the full comparison.
Owners, operators, executive directors, regional directors of operations, and CFOs at senior living and seniors housing organizations without an in-house BI team — single campuses, small regional groups, and portfolios that have grown by acquisition and inherited a different reporting habit with each building.
Two neighbouring needs are covered elsewhere on this site, deliberately. If what you need is clinical and care-quality reporting — incidents, outcomes, regulatory measures, throughput across a provider organization — that is a different data set with different governance, and Power BI for healthcare is the right page. If your question is really about leases, work orders, and third-party managed real estate rather than resident operations, see Power BI for property management. And if the blocker is simply getting data out of the EHR rather than deciding what to measure, start with the PointClickCare Power BI dashboard page. Operators who also run a Medicare-certified home health arm need a separate model for it — care delivered in the home is paid in 30-day PDGM periods with LUPA thresholds and visit utilization rather than by occupied unit — which is covered on Power BI for home health agencies. If you already have senior living reports that nobody trusts, a Power BI health check is the fastest way to find out why. Contact is form-only — send your request and we'll reply with a scope estimate.
business days, typical
hours, never expire
own everything
A first census, labor, and NOI build usually fits inside one Flex block, and hours deduct only for work you approve. See Flex pricing →
How it works
Tell us which systems hold census, sales, payroll, and the ledger, how you define occupancy and resident days, and who should see which communities. We reply with a scope and hours estimate before any work begins.
A senior US-based engineer builds the model across your resident, CRM, payroll, and GL data, writes the DAX for occupancy, cost per resident day, and NOI, and reconciles totals to your systems — typically 3–5 business days.
We publish to your workspace, set overnight refresh so figures are current each morning, apply role-based access by community or region, and hand over the model and credentials. You own everything.
Representative perspective
We were reviewing occupancy at the building level and thought two communities were performing the same. Splitting it by care level showed one of them was carrying its number entirely on independent living while memory care sat half empty.Regional director of operations, multi-community operator
Representative perspective
Agency spend was the line everyone argued about and nobody could size. Putting it next to census as a cost per resident day ended the argument in about a minute.CFO, regional senior living group
Tell us where census, payroll, and the ledger live, and how your organization defines occupancy. We'll scope the task and tell you the hours before any work begins — drawn from prepaid Flex hours that never expire, with no project minimums and no obligation.
FAQ
Yes — that is usually the first thing we model. Independent living, assisted living, memory care and skilled units are held as their own dimension, so occupancy, revenue per occupied unit and net move-ins can be read per care level, per community, and rolled up to the portfolio without anyone re-keying a census sheet.
Any platform that offers an API, a reportable database, or a scheduled export. In this sector that usually means a clinical or resident system, a sales CRM, a payroll or scheduling system, and the general ledger. Because each vendor exposes data differently, we confirm the extraction method for your stack in the scope estimate first.
Yes. We join payroll and scheduling hours to census by day, so agency, overtime and straight-time cost can be expressed per resident day and compared across communities and care levels. That is the view that shows whether a community is expensive because of rate, mix, or reliance on agency staffing.
Our senior living work is deliberately operator- and P&L-facing: census, revenue, labor and NOI. Clinical and care-quality reporting — incidents, outcomes, regulatory measures — is a different data set with different governance, and we cover that work on our Power BI for healthcare page instead.
Yes. Communities are modeled as a dimension rather than as separate reports, so the same measures aggregate to region and portfolio and drill back down to a single building. That is what makes NOI by community comparable — one definition of occupancy, revenue and expense applied everywhere.
Book a free demo
Tell us the task. We scope it, you approve, and a senior consultant delivers — typically in 3–5 business days. Prepaid hours that never expire.
The fastest way to reach us is the form — tell us the task and we'll reply within one business day.