For leaders of multiple buildings, the monthly operations review is one of the few moments when administrators, clinical leaders and regional staff are all looking at the same picture. Done well, it surfaces problems early, spreads good ideas and creates accountability that feels supportive. Done poorly, it becomes a recitation of numbers that everyone has already seen, followed by a list of tasks that nobody tracks.
Here is a practical structure for a monthly review that supports action.
Before the meeting
Send the data in advance
The most valuable time in the meeting is discussion, not data presentation. Send the dashboard or one-page summaries at least a day ahead. Ask administrators to come prepared to explain trends, not to read numbers aloud.
Agree on a consistent set of measures
Choose a core set, perhaps eight to twelve, that covers staffing, call and response performance, census and admissions, quality, and revenue cycle. Keep definitions stable so month-to-month comparisons are meaningful.
Ask for two notes per building
Before the meeting, ask each administrator to add a brief note: one thing going well, and one thing they need help with. This shifts the tone toward support from the start.
A sample agenda
- Opening (5 minutes): wins and recognition. Begin with something positive and specific.
- Portfolio view (10 minutes): a quick look at the overall picture and any outliers.
- Building spotlights (30 to 40 minutes): each building gets a few minutes, focusing on changes since last month and requests for help.
- Cross-building themes (10 minutes): patterns that appear in several buildings, such as agency use or slow referral response.
- Commitments (5 to 10 minutes): each action named, with owner and date.
Timing varies with portfolio size, but the shape is useful: celebrate, orient, discuss, find patterns, commit.
How to run the discussion
Ask about change, not level
"What changed since last month, and why do you think so?" invites analysis. "Why is this number low?" invites defense. Starting with change also gives credit to buildings that are improving from a hard place.
Use data as a starting point
Numbers show where to look, not what is true about the cause. Encourage administrators to share what they know on the ground. Often the most useful insight is the explanation behind a spike.
Distinguish problems of process from problems of resources
Some issues need a better routine; others need help from the regional team, such as recruitment support, a policy decision or budget flexibility. Naming which is which prevents blame.
Share good practices
When a building improves something, ask what they did. Then ask whether others could try it. Cross-learning is a major benefit of a portfolio and often the cheapest source of improvement.
After the meeting
Record commitments and follow up
A short written summary, with each action, owner and date, makes the next meeting more productive. Begin the next review by checking last month's commitments. If they are never revisited, people learn that they do not matter.
Track a small number of repeating items
If the same issue appears several months in a row, escalate it from a topic to a project with a named sponsor.
A hypothetical example
Imagine a hypothetical group of five buildings. The cross-building theme segment reveals that three of them have slow weekend referral response. Each administrator had assumed it was a local quirk. With the pattern visible, the group decides to pilot a shared weekend triage approach in one building and to compare results next month. The pilot might succeed or fail, but the group would not have run it without the review.
Making it sustainable
- Keep it to a predictable length
- Rotate a "deep dive" topic each month so the meeting does not become repetitive
- Invite clinical leaders as appropriate
- Respect time zones and schedules
- Use the same dashboard each time so people learn where to look
Pitfalls
- Too many measures. A long list diffuses attention.
- Surprises. Avoid raising a problem in public that you have not discussed privately first.
- Data disputes. If numbers are debated each month, fix the data pipeline.
- Meetings without decisions. Every session should end with at least a few concrete commitments.
Closing thought
A well-run monthly review is the rhythm that keeps a group learning together. If you would like to see how data from phone, call-light, email and EHR systems can arrive ready for that meeting, CarePulse can walk you through a demo.