What workforce monitoring data belongs in a QBR?

Aggregate, trend-level data only. Capacity utilization by function, productivity-trend direction quarter-over-quarter, tool-cost rationalization wins, and major operational risk signals. Individual employee data does not belong in a QBR — it's the wrong altitude for the audience and it creates legal exposure.

How many monitoring slides should a QBR include?

At most three to five. Workforce data competes for QBR attention with revenue, product, customer, and financial slides — and rightfully loses if there are too many. The discipline of cutting from twelve slides to five forces leaders to identify what actually matters.

What's the most common QBR misuse of monitoring data?

Naming individuals. The moment a QBR slide identifies specific employees by productivity score, the conversation goes off the rails legally and culturally. Trend, aggregate, and function-level views belong in QBRs. Individual-level data belongs in 1:1s.

Should QBRs include capacity forecasts?

Yes — capacity is where workforce monitoring earns its keep at the executive level. A capacity slide that shows demand outpacing supply by 15 percent next quarter is the single most actionable workforce slide in a QBR.

Executives presenting workforce data in a quarterly business review meeting

Leadership

By eMonitor Editorial Team

May 22, 2026 7 min read

Using Monitoring Data in Quarterly Business Reviews (QBRs)

Q: Who should own QBR workforce slides?

Operations or COO function, with input from HR and finance. HR-only ownership tends to bias toward engagement narratives without operational consequence. Operations ownership ties workforce data to decisions about hiring, redeployment, and tool investment.

Most QBR workforce slides are either skipped entirely or contain numbers nobody acts on. Monitoring data deserves a place in the QBR — but only at the right altitude, in the right slots, with the right interpretation. Here's the five-slide cut.

Using monitoring data in quarterly business reviews is the practice of distilling workforce activity, capacity, and productivity trends into the small number of slides that survive a QBR's brutal slide budget. The goal is decisions — hiring, redeployment, tool rationalization — not a recap of who clicked what.

Altitude Matters More Than Volume

The most common QBR workforce-data failure: too much detail at the wrong altitude. A QBR audience cares about function-level patterns and quarter-over-quarter trends, not employee-level scores. Individual data in a QBR is the wrong shape for the audience — and a legal exposure waiting to happen if it identifies people by name.

Three altitude rules:

Aggregate across teams, never individuals.
Trend across quarters, not snapshots.
Decision-linked: every chart maps to a decision being made this quarter.

The Five Slides That Survive

Slide 1 — Capacity vs. demand. Forecasted demand against measured productive supply for the next quarter, by function. Red where demand exceeds supply by more than the buffer. This is the slide that drives hiring and redeployment decisions. Capacity planning fundamentals support this slide.

Slide 2 — Productivity trend by function. Quarter-over-quarter productive utilization for each team. Direction matters more than the absolute number — a flat 65 percent is healthier than a falling 80 percent.

Slide 3 — Tool and license rationalization. SaaS spend reduced from app-usage data, license seats consolidated, vendor renewals informed by actual adoption. Easiest dollar number to put on a QBR slide.

Slide 4 — Operational risk signals. Burnout indicators trending up in named functions, after-hours activity climbing, access-anomaly events. Not naming individuals — naming functions and patterns.

Slide 5 — One forward-looking ask. What changes for next quarter — a hire, a tool retired, a policy adjusted. If the workforce slides don't end in an ask, they were a status report.

Misuses That Destroy QBR Credibility

Naming individuals. Even a single slide showing "lowest productive utilization: J. Smith 42 percent" turns a QBR into a workforce tribunal. It also exposes the company to disparate-impact litigation if the slide gets misinterpreted by an audience not trained to read it.

Vanity productivity scores. "Average productive time is up 4 percent" is a vanity metric — it doesn't drive a decision and it's usually within noise. Cut it.

Hours worked as the headline. Hours don't equal output. Senior leaders see this on the slide and reasonably ask "so what?"

Engagement narratives without operational consequence. "Engagement is up" presented in isolation reads as HR self-promotion. Engagement is interesting when it ties to attrition forecasting or capacity risk.

QBR Slide Flow

The workforce slides usually sit best between the operational/finance slides and the customer/product slides. The narrative arc:

Here's last quarter's revenue and finance picture
Here's the workforce capacity behind that picture
Here's where capacity is constraining product/customer outcomes
Here's our forward ask

This positioning makes workforce data a bridge between financial reality and product/customer ambition. It survives the slide cut because it explains the gap between the two.

Who Owns the Workforce QBR Slide

The most common ownership mistake: HR owns the slide solo. HR ownership tends to bias toward engagement narratives without operational consequence. The better model is operations or COO ownership with input from HR and finance — operations frames the workforce data in terms of decisions, HR adds the engagement/risk context, finance ties it to dollars.

For COO-level framing, see operations director workforce visibility.

What to Do Before Your Next QBR

Pull last quarter's workforce slides and apply the cut: keep only slides that drive a named decision in the next quarter. In most companies you'll go from 12 slides to 4 or 5. The cuts feel ruthless and produce a better QBR.