Monthly operations reviews are a fixture in multi-facility organizations. Done poorly, they become a recitation of numbers that everyone already saw, followed by a defensive discussion. Done well, they become the place where administrators get help, leaders learn what is working, and the organization improves a little each month.
The difference is rarely the data itself. It is how the data is prepared, how the conversation is structured, and what happens afterward.
Before the meeting: share the numbers first
Send each administrator their dashboard a few days before the review. If the first time they see their results is in the meeting, the time goes to reaction instead of discussion. With advance access, they can arrive with context: what happened, what they are doing, and what they need.
Ask each administrator to add short notes for any measure that moved significantly. This prepares the ground for a more useful conversation.
Keep the structure consistent
A consistent agenda helps everyone prepare and compare. A simple structure for each building might be:
- Headline: two or three things going well
- Concerns: the measures that moved the wrong way, with the administrator's explanation
- Plan: what is being done and what support is needed
- Follow-up: commitments for next month
Limit each building's time. If you have many buildings, consider a focused review for those with the largest changes and a brief written update for the rest.
Focus on the right measures
Choose a short list that spans resident care, people, and finances. For example:
- Census, admissions, and referral response
- Staffing, overtime, and agency use
- Call and communication response
- Quality indicators and assessment timeliness
- Revenue cycle health, including days in A/R and aging
The list should be consistent, so trends are visible across months. Add or remove measures deliberately, not on a whim.
Ask better questions
The tone of the meeting depends on the leader's questions. Compare these.
- "Why is your overtime up?" invites a defense.
- "What do you think is driving overtime on evenings, and what would help?" invites problem solving.
Good questions are specific, curious, and tied to a decision. They signal that the purpose is support, not blame.
Useful prompts
- What changed since last month?
- What have you already tried?
- What does your team say is causing this?
- What would you need from us to fix it?
- What should we learn from this for other buildings?
Share what works
One of the biggest benefits of a multi-building view is learning across sites. If one administrator found a way to shorten referral response time or reduce evening overtime, others can benefit. Reserve a few minutes for a building to share a practice. Over time, this builds a culture where improvement spreads.
Compare fairly
Buildings differ in size, resident mix, market, and staffing environment. Comparisons are most useful when they account for those differences, for example by looking at each building's own trend alongside shared targets. Avoid ranking tables that treat very different buildings as equals.
Close the loop
Meetings matter only if actions follow. Capture commitments in a simple shared log, with owner and date, and begin the next meeting by reviewing it. When administrators see that commitments are tracked on both sides, including support from the regional team, trust grows.
A hypothetical example
Imagine a hypothetical regional review where an administrator reports that agency use rose after two resignations. Instead of questioning the numbers, the regional director asks what would help, and the group agrees to share recruiting resources and review the building's posted wages against the local market. The next month's review checks whether open shifts have declined. The data led to support, not scolding.
Mistakes to avoid
- Reading numbers aloud. Everyone can read them in advance.
- Surprising people. Share data before the meeting.
- Changing measures constantly. Consistency builds understanding.
- Letting meetings run long. Focus keeps energy up.
- Forgetting to recognize success. Improvement deserves acknowledgment.
Make preparation painless
Assembling consistent dashboards for every building by hand takes time and invites errors. When the data refreshes automatically, leaders can spend their energy on the conversation.
CarePulse Analytics builds shared dashboards for multi-facility groups, drawing on the systems each building already uses. If you would like to see how a monthly review packet could look for your group, a short demo is a good way to start.