5 Workday Analytics Every HR Leader Should Be Reviewing

Most HR reporting gets built to be shown. Somebody asks for a headcount number ahead of a leadership meeting, a report gets built to produce it, and it goes into a deck. The report answers the question it was built for and nothing else.

A dashboard worth reviewing on a cadence works differently. It has to be capable of telling you something you didn't want to hear. If there's no version of the output that would change a decision or embarrass somebody, the review is ceremonial and it will quietly stop happening within two quarters.

These are five I've built and put in front of HR teams. None of them ship configured out of the box in a way that answers these questions, and each one is worth the build because each one can contradict a belief the organization holds about itself.

1. Time Off Trends

Is leave clustering somewhere that should have prompted a conversation months ago?

Most managers track time off one request at a time. Approved, denied, balance remaining. That view can't show you a pattern, because a pattern only exists in aggregate.

Look at leave by team, by manager, and by quarter. Seasonal clustering is normal and tells you nothing. What matters is the exception: a sudden concentration of sick time on one team, a rise in unpaid leave in a single department, or a group of people who haven't taken a vacation day in eight months.

That last one is the most useful and the least tracked. Someone with a large untaken balance is either indispensable, which is a key person risk, or unable to step away, which is a workload problem. Either way it's a signal that arrives well before a resignation does.

2. Performance Distribution and Trend

Does your distribution actually support the pay decisions you say you're making, and can you explain which direction it's moving?

Every organization runs a review cycle. Most look at the completion rate and stop there.

Break the distribution down by department and by management level. Rating inflation is the common finding, and it's expensive. When one division rates eighty percent of its people above expectations, that isn't a statement about the talent. It's a statement about how that division's managers handle evaluation conversations.

The consequence is specific. If almost everyone lands in the same band, your merit budget can't differentiate, and the top performers receive something close to what everyone else receives. You end up with a pay-for-performance policy on paper and an across-the-board increase in practice.

Then run the same view across several cycles. If the share rated above expectations has climbed for three cycles running, there are two explanations. Your development investment is working, or your managers have gotten more generous. Those require completely different responses, and organizations tend to assume the first without testing it.

The useful cut is by manager. A leader whose team shows steady upward movement while a peer's stays flat may be developing people well, or may be avoiding hard conversations. The trend raises the question. Answering it requires knowing the teams.

3. Pay for Performance

Did your highest-rated people actually receive your highest increases?

This is the one that changes the room when it goes up on a screen, because most leadership teams assume the answer is yes.

Cross-reference performance ratings against merit outcomes at the individual level. What surfaces is rarely a policy failure. It's the accumulation of small local decisions: a manager who spread the budget evenly to avoid a difficult conversation, a compression adjustment that consumed a team's allocation, a high performer who happened to sit in a band with less room.

None of those decisions were wrong on their own. Together they produce a pattern where a top performer in one function received less than an average performer in another, and nobody intended it. That shows up later in exit interviews, and by then it's expensive to explain.

4. Overtime Spend

Is a team working more hours without any corresponding increase in output or headcount?

Overtime usually gets reviewed as a finance line item, which frames it as a cost to control rather than a signal to read.

Track it by team over time. The finding worth acting on is a department running significantly more overtime than the prior year with no increase in volume, revenue, or people. That's a process problem or a staffing problem, and it's producing the same output at a higher cost while burning down the team producing it.

Sustained overtime concentrated in one team is also the most reliable leading indicator of turnover I've seen in a workforce report. It shows up months before anyone resigns, and it's visible to anyone who looks.

5. Span of Control and Org Layers

Do your spans and layers match the complexity of the work you're asking the organization to do?

Most organizations can't answer that without pulling the data, which is why this one gets built the least.

Two cuts. How many direct reports each manager carries, and how many layers sit between an individual contributor and the top.

Neither number is good or bad on its own. Specialized work, regulated supervision, shift coverage, and geographic spread all produce small spans for legitimate reasons. The number starts a question rather than answering one.

What accumulates quietly is structure nobody revisits. A promotion brings a report along. A team splits to resolve a personality problem. Each was reasonable on the day it happened, and nothing since has prompted a second look.

The combination is the finding. A VP with seven layers beneath them and ten people in the entire organization is telling you something, and it isn't about span size. It's depth relative to size, and the explanation is often that titles were the only recognition mechanism available.

Once the structure is visible, the conversation is about what the work actually requires today.

Why These Don't Get Built

The obstacle is rarely capability. Workday can produce all of this, and the configuration effort is smaller than most organizations assume.

What stops it is that nobody owns the question. Reporting gets built in response to requests, and requests come from people who need a specific number for a specific meeting. Nobody submits a ticket asking for a report that might reveal their own division's rating inflation.

So the reports that exist are the ones somebody asked for, and the ones that could change a decision go unbuilt. That gap is the actual reason a mature Workday tenant can produce a hundred reports and still leave leadership making workforce decisions on instinct.

Where CRG Starts

We build these with HR teams and then hand them over, along with the review cadence and the person accountable for looking at them. A dashboard nobody reviews on a schedule is a configuration exercise rather than an analytics capability.

If your tenant is live and your reporting isn't telling you anything you didn't already believe, that's a fixable gap and usually a shorter engagement than organizations expect.

Talk to CRG about the reporting your leadership team is missing.