Key takeaways
- Treat the tiers as differences in scope and authority, not importance: unit (each shift), department (weekly), executive (rotating, at least monthly per unit).
- Write escalation criteria down at design time, such as an issue seen in three or more Tier 1 rounds goes to Tier 2.
- Use Tier 2 leaders as the link: they see unit-level detail and feed patterns up to executives.
- Add tiers one at a time, starting from the unit level.
What tiered rounding means
Tiered rounding is a structural model that organizes leadership rounding into three connected levels: unit-level (Tier 1), department or manager-level (Tier 2), and executive-level (Tier 3). Each tier has its own cadence, observation focus, and escalation path. The model is not a hierarchy of importance — it is a hierarchy of frequency, scope, and decision authority.
The point of the structure is connection. A unit-level shift huddle that surfaces a recurring equipment failure feeds the department manager's weekly rounds, where the pattern across multiple shifts becomes visible. The department manager who sees the same equipment issue across three units feeds the executive's monthly rounds, where the pattern across multiple departments becomes visible. Without the tiering structure, observations stay where they're made — and the systemic patterns the most senior leaders are best positioned to address never reach them.
Healthcare organizations that adopt tiered rounding typically already have something resembling Tier 1 in place — daily huddles, shift handoffs, charge nurse walks. The tiering work is making Tier 2 and Tier 3 deliberate, scheduled, and connected to the data flowing up from Tier 1.
There is no single published standard for tiered rounding. The tiers, cadences and durations below are one common pattern, modeled on the way tiered huddles connect unit, department and executive levels. Adjust them to your organization's size and span of control.
What each tier does
Tier 1 — Unit-level (daily or per-shift)
Tier 1 rounding is conducted by charge nurses, unit managers, or rotating clinical leaders within a single unit, typically every shift or every day. The cadence is high frequency; the scope is narrow — one unit, current shift, immediate operational state.
- Owner: charge nurse, unit manager, or designated shift leader
- Cadence: per-shift or daily
- Duration: 15–30 minutes
- Focus: immediate operational state — staffing, equipment, patient acuity, in-process safety concerns
- Output: shift huddle notes, immediate Tier 1 follow-ups, items escalated to Tier 2
Tier 2 — Department or manager-level (weekly)
Tier 2 rounding is conducted by department managers, directors, or rotating mid-level leaders across multiple units within their span of control, typically weekly. The cadence is moderate; the scope is broader — pattern visibility across units within a department, with focused observation on areas flagged by Tier 1 escalations.
- Owner: department manager, director, or service-line leader
- Cadence: weekly per unit (or weekly across a unit rotation)
- Duration: 45–60 minutes per unit
- Focus: cross-shift patterns, recurring Tier 1 escalations, unit-to-unit comparison, frontline engagement
- Output: department-level findings, follow-up assignments, items escalated to Tier 3
Tier 3 — Executive-level (monthly)
Tier 3 rounding is conducted by C-suite executives, VPs, and senior leaders across the organization. Each unit typically sees an executive about monthly, while the executive team as a whole rounds somewhere every week; IHI's WalkRounds model asks senior leaders to round at least weekly, rotating to share the load. The scope is broadest — system-level patterns, leadership visibility to frontline staff, signaling priority through presence.
- Owner: CEO, COO, CNO, CMO, VPs
- Cadence: monthly per unit (or monthly across a unit rotation)
- Duration: 60–90 minutes per unit
- Focus: organization-wide patterns, executive visibility, strategic alignment with frontline reality, recognition
- Output: executive observations, strategic-level decisions, board-reportable patterns
ImprovementFlow
Leadership Rounding
ImprovementFlow schedules who rounds where and when, including rotations across leaders and areas, and shows sponsors which rounds are on schedule and which follow-ups are aging.
How the tiers connect
Vertical escalation
Findings flow upward when they exceed the tier's scope. A Tier 1 observation that recurs across multiple shifts becomes a Tier 2 pattern. A Tier 2 finding that recurs across multiple units becomes a Tier 3 systemic issue. Each tier owns its scope; escalation criteria — explicit, documented — determine when a finding belongs at the next level.
Escalation criteria should be defined at program design, not invented during operation. Common patterns: "any safety event meeting threshold X escalates immediately," "any finding appearing in 3+ Tier 1 huddles escalates to Tier 2," "any Tier 2 pattern appearing in 3+ units escalates to Tier 3." Without explicit criteria, escalation depends on individual judgment, which produces inconsistent and politically influenced patterns.
Lateral aggregation
Tiers also produce aggregate data that flows laterally across the organization. A Tier 1 huddle on Unit A and a Tier 1 huddle on Unit B both produce findings that, in aggregate, reveal cross-unit patterns invisible at either unit. The Tier 2 manager covering both units sees the aggregate; the program-level dashboard surfaces it organizationally.
The structural insight is that no single tier, by itself, sees enough. Tier 1 sees high-resolution operational reality but only one unit. Tier 3 sees the full organization but only at low cadence. The connection between tiers is what produces the picture that is both detailed and comprehensive.
Common implementation patterns
- Sequential rollout. Start with Tier 1 if it isn't already running, formalize it for 60–90 days, then add Tier 2, then Tier 3. Launching all three at once spreads attention thin and often leaves all three half-done.
- Tier 2 as the integration layer. The department manager attends Tier 1 huddles on a rotating basis, reviews aggregate Tier 1 data weekly, and feeds patterns up to Tier 3. This role is the connective tissue of the system.
- Executive Rounding as Tier 3, not as a parallel program. Some organizations run executive rounding without connecting it to operational tiers. The result is executives walking units with no context — Tier 1 and Tier 2 data, in aggregate, give Tier 3 walks the focus they otherwise lack.
- Cross-tier calibration sessions. At program kickoff, all three tiers' leaders should observe at least one round at each tier together, to calibrate observation style and establish shared language for findings.
How ImprovementFlow supports this
- Schedule who rounds where and when, including rotations across leaders and areas, so each tier's coverage is planned rather than left to whichever units feel comfortable.
- Findings above a severity threshold you define reach the right leadership level, so a unit-level round connects to organization-wide visibility.
- Filter observations by category, unit or time window to see patterns across rounds, and sponsors see which rounds are on schedule and which follow-ups are aging.
Key terms
- Rounding: A scheduled walkthrough of a physical or functional area where a designated person observes conditions against a checklist.
- Round: A single discrete rounding event — one leader walking one area at one scheduled time. Multiple rounds across leaders and areas aggregate into cycle data.
- Rounding Cadence: The rhythm at which rounds occur for a given leader/area combination. Common patterns: weekly on the same unit, monthly across units, daily for executive unit tours.
- Observation: A single data point captured during a round — what was seen, who was observed, what category it fits.
- Round Follow-up: The action taken in response to a finding from a round. Core to closing the loop — unused findings undermine the entire practice.
