Census dipped. Is it leads, tours, move-outs or price?
Join the CRM with move-ins, move-outs and the rent roll. See which part of the path from inquiry to resident changed at the community whose census fell.
Open QuerriWhat you'll need
Querri (Free trial) to see what changed behind a census dip
Welcome Home and Yardi: Step 1 says what each adds
Your move-in and move-out rules: so a transfer is never counted as a move-out
Free resources
Start your free trial here →Sample data sets
Synthetic data for Tallowmere Senior Living, a made-up operator with four communities. Residents appear as codes only. Not real resident, family, staff or financial data.
Need help?
If you have any questions, you can request a demo or email our team.
Before we begin
When census dips, the first question in the census meeting is whether we need more leads. Answering it means reading the CRM funnel report, the census report and the rent roll side by side, and they rarely agree on what a move-in is. Leads and tours live in the CRM; move-ins, move-outs and rate live in the resident system.
This playbook finds the community whose census moved, then compares leads, tours, move-ins, move-outs and rate quarter against quarter.
How it works:
- • Upload Welcome Home and Yardi
- • Find the community whose census moved
- • Compare inquiries, tours and move-ins by quarter
- • Look at move-outs by reason, and rate
- • Build the census review
Follow the steps
Upload Welcome Home and Yardi
Two sources, one project:
- •
Welcome Home (or your CRM): inquiries, tours, deposits and move-ins by source.
- •
Yardi (or your resident system): occupancy by day, move-outs with their reasons, and the rent roll.
Both come in as exports; next week's files rebuild every view.
Tip: Bring three quarters, so a dip can be compared with more than one quarter before it.
-
Welcome Home leads
-
Yardi occupancy, moves and rent roll
Find the community whose census moved
Start with occupancy by community, not the portfolio:
"Show occupancy by community for the last three quarters. Whose census moved?"
Portfolio occupancy held at 93.0%, which hid one fall: Harrowby House dropped 3.6 points from Q2 to Q3.
| Community | Q2 2026 | Q3 2026 |
|---|---|---|
| Harrowby House | 92.0% | 88.4% |
| Kestrel Grove | 89.8% | 93.3% |
| Ashby Commons | 93.9% | 94.6% |
| Linden Hill | 95.0% | 95.6% |
| All communities | 92.9% | 93.0% |
Occupancy, occupied units over units in service.
Compare inquiries, tours and move-ins by quarter
Then check the top of the funnel at the community that dipped:
"For Harrowby House, compare inquiries, tours, deposits, move-ins and move-outs by quarter."
At Harrowby House, inquiries rose from 82 to 85 and move-ins from 8 to 9. Move-outs rose from 11 to 15.
| Measure | Q2 2026 | Q3 2026 |
|---|---|---|
| Inquiries | 82 | 85 |
| Tours | 39 | 44 |
| Move-ins | 8 | 9 |
| Move-outs | 11 | 15 |
Harrowby House, Q2 and Q3 2026. Transfers between care settings are not counted as move-ins or move-outs.
Look at move-outs by reason, and rate
Move-outs have reasons, and rate tells the rest:
"At Harrowby House, why did residents move out, quarter by quarter? Was memory care full? Were new residents moving in below street rate?"
Nine of Harrowby House's 26 move-outs since April were for a higher level of care, while its memory care was full. New residents also moved in further below street rate in Q3.
| Reason | Q2 2026 | Q3 2026 |
|---|---|---|
| Higher level of care | 4 | 5 |
| Death | 5 | 3 |
| Financial | 0 | 3 |
| Moved closer to family | 2 | 2 |
| Other | 0 | 2 |
Harrowby House move-outs by recorded reason.
Build the census review
Four numbers for the census meeting, and the drivers that moved.
The narrative Querri writes:
At Harrowby House, leads held in Q3 and move-outs rose; across Q2 and Q3, 9 of 26 move-outs were for a higher level of care while memory care was full.
What you can create or export:
- The table, to Excel, CSV or Google Sheets
- A live dashboard that refreshes when new exports land
- A presentation for the meeting, to PDF or PowerPoint
| Driver | Change | What it suggests |
|---|---|---|
| Inquiries and tours | Up | Leads held |
| Move-ins | Up 1 | Sales held |
| Move-outs | Up 4 | Look here first |
| Rate on new move-ins | Lower | Watch rate |
Harrowby House, Q3 2026 against Q2.
Bring the census meeting the driver that moved, not a request for more leads.
Try it on your own dataTips for a census review people trust
Look by community before the portfolio
Communities moving in opposite directions cancel out in the total. A flat portfolio can hide the one community that needs a plan.
Never count a transfer as a move-out
A move to memory care in the same community keeps the resident. Counting it twice makes move-outs and move-ins both look higher.
Teach Querri your rules once. Every answer after that follows them.
What a move-in and a move-out are, how occupancy is counted, how move-out reasons are grouped, how rate against street is measured: say each rule once and Querri applies it to every question on that data.
Show me how
Say it in chat
Settle a rule in conversation and the Librarian records it as a fact under Facts & Rules, attached to the table it governs. Every later question on that data applies it, whoever asks, and every view built afterwards carries it.
"A transfer between care settings is never a move-in or a move-out. Save that as a rule for the Yardi resident directory."
Or bring the document that already says it
Upload your census reporting guide like any other file. Querri files a From a document card in the Inbox with the statements it found, each with its page and exact words; tick the ones to keep and they become facts. The rules this playbook depends on:
- Occupancy: occupied units over units in service, daily
- Move-in: a new resident, counted on the move-in date
- Move-out: a resident leaving the community, counted on the move-out date
- A transfer between care settings is neither
- Inquiries, tours and deposits are counted on their own dates
- Rate against street: actual rent against market rent
"Read our census reporting guide and propose the rules it states about move-ins and move-outs. I'll review them in the Inbox."
Where the rules reach
A rule is attached to the data, not to one person's chat, so it follows the data everywhere:
- • Every question asked in chat, by anyone on the sales and marketing team
- • Every view the Librarian builds on that data
- • Every step of a project, including the code it writes
- • Dashboards and scheduled runs, each time they refresh
- • Claude and ChatGPT, when they ask Querri
You stay in control
Every rule is listed under Facts & Rules next to the data it governs, where you can edit or remove it. Rules from a document wait for your tick in the Inbox, and a Worth remembering card is how Querri offers one it noticed itself. Workspaces and roles decide who can change what. Company-wide rules go in Settings → Customize; the Library is where the rest lives.
The payoff in the census meeting
The meeting starts with the driver that moved. Changing how a move-out is counted is a sentence.
Frequently asked questions
Why didn't the portfolio show the dip?
Does this show why residents left?
Would more leads have helped?
Why exclude transfers?
How is rate against street measured?
Can I see this every week?
Do I need a connector for Welcome Home or Yardi?
How often should this run?
Other popular resources
Playbook
Spend where rooms are about to open
Where are rooms about to open, and which sources fill them?
Playbook
Incentives against rate
Are incentives filling rooms or giving away rate?
Demo
Request a walkthrough
See Querri in action with your own data.
Pricing
Compare plans
Find the right plan for individuals, teams, or enterprise.