Overview

You're in a board meeting. A board member asks: "How's our workforce? Are we retaining talent? Are we hitting our hiring targets? What are the risks?" HR wasn't invited to this meeting. So the CEO, who doesn't have detailed people data, makes up an answer based on impression and gut feel. "We're doing fine. Hiring is strong. People seem happy. We're well-positioned to grow." No data. No risks called out. No nuance. No evidence.

The board, without real information, makes a major decision: approve expanding headcount 40% over the next year. Then attrition spikes, hiring slows down because you're desperate for anyone who can start, customer onboarding suffers because you're training people who leave after three months, and growth plans derail. Six months later, people realize the expansion was poorly timed.

This is where executive reporting matters. HR has data, headcount, attrition, hiring, compensation, engagement, diversity, succession readiness. But if that data doesn't reach leadership in a form they can understand and act on, it doesn't matter. You might as well not have it.

Executive reporting is different from operational reporting. Operational reporting is "here's the raw data." Executive reporting is "here's what the data means for the business and what we should do about it." Exec reports are concise (busy people have seven other meetings today), answer the question directly, show trends not snapshots, highlight what needs action, and recommend decisions.

When HR reporting is excellent, the organization makes better people decisions. When HR doesn't report well, people decisions are made without data, based on gut feel, politics, or inertia. And they're usually wrong.

Pro Tip: Your job as HR leader isn't just to manage people. It's to give leadership the information they need to manage people strategically. If you can't communicate data clearly, you're invisible. Your data matters only if leaders see it, understand it, and use it.

Why Executive Reporting Matters More Than You Think

Most HR leaders underestimate how much impact good reporting has on business outcomes. You think your job is hiring, onboarding, and managing processes. That's the operational work. But the strategic work is translating what's happening with your people into insights that shape business decisions.

A VP of People at a 300-person SaaS company shared this: "For the first two years, I had no formal reporting structure. I'd give the CEO a gut sense: 'Hiring is going OK, people are mostly happy.' Six months in, the CEO approved a major product pivot that required 40% more engineers. I knew our attrition was high (12% annually) and our hiring was slow (35-day average), but I never quantified it for her. So when she made the decision to expand, she didn't know she was asking us to hire the same number of people we typically lose, all while we're ramping. It was a disaster. We hired 30 people, 12 left within six months, and we only netted 18. The company was in chaos.

Now I send a monthly flash report (one page) and a quarterly deep dive. It takes me 90 minutes to prepare. The CEO reads it the same day and uses it to inform decisions. When we talk about expanding headcount or entering a new market, she always asks, 'What does the people report say?' Data changed how she thinks about growth."

That's the difference. Good reporting doesn't just inform. It changes how decisions are made.

The Three Types of Executive Reports

Executive reports aren't all the same. Different audiences need different cadences and detail levels.

1. Monthly Flash Report (1 Page, 5-Minute Read)

Audience: CEO, CFO, sometimes executive team

Purpose: Is everything OK? Are there any urgent people issues leadership needs to know about this month?

Cadence: First Friday of each month

Format: One page (not more), with key metrics, highlights, concerns, and one decision needed

Why it works: Busy leaders need a quick pulse check. One page fits on a phone. Five-minute read happens between meetings. You're giving them the headline and the key data points, not the deep analysis.

2. Quarterly Business Review (3-4 Pages, 20-Minute Read)

Audience: Executive team, sometimes board members

Purpose: Comprehensive view of people function. Are we on track with our people strategy? What's working? What needs attention? What are the risks?

Cadence: End of each quarter (or beginning of next quarter)

Format: 3-4 pages with executive summary, detailed metrics by function, risks/opportunities, recommendations

Why it works: Leadership teams make bigger decisions quarterly (budget allocation, strategic direction, hiring plans). You need enough detail to inform real decisions.

3. Annual Board Report (5-8 Pages, 30-Minute Read)

Audience: Board of directors, executive team

Purpose: Full strategic view of people function. Did we achieve our people strategy? What did we learn? What's the plan for next year? What are the big risks?

Cadence: Once a year, before or at annual board meeting

Format: 5-8 pages with deep strategic analysis, year-over-year comparisons, business impact, and next-year recommendations

Why it works: Boards want to understand where the company is on people-critical issues: leadership pipeline, attrition, diversity, compensation competitiveness, organizational health. You're helping them understand risk.

The Monthly Flash Report: Getting a 5-Minute Executive Decision

One page. Five-minute read. Answers the question: Are we healthy? Do we have any urgent people issues?

Report structure (example):

MONTHLY PEOPLE FLASH REPORT | April 2026

HEADLINE: "On track overall. Engineering attrition spike requires immediate attention."

HEADCOUNT & HIRING
Current headcount: 487 (up from 483 last month, +10 YTD vs. plan of +12)
Hires this month: 6 people (plan was 8; 2 offers pending)
Open reqs: 12 (1 above normal; 2 backfills for departures, 1 expansion)

RETENTION & ATTRITION
Attrition this month: 1.2% (annualized: 14.4%, vs. target 12%)
Trend: UP from 0.9% last month (concerning, 3-month trend: ↑)
Root cause analysis: 2 engineers left citing lack of growth opportunity +
compensation below market. 1 sales rep relocated. 1 contractor ended.
By department: Engineering 2.0% monthly (4 people YTD), Sales 0.5%, Ops 0%

KEY METRICS
Time-to-fill: 28 days (target 25 days; increase due to volume)
Offer acceptance rate: 90% (good; target 85%)
New hire diversity: 40% women, 22% underrepresented minorities
(tracking well toward annual targets)

WHAT'S WORKING
✓ Hiring pipeline strong for Q2 (10 offers out, 9 pipeline)
✓ New hire quality good (Q1 cohort showing solid performance)
✓ Diversity hiring on track to hit annual targets (30% women, 25% URM)
✓ Manager engagement and retention stable

WHAT NEEDS ATTENTION
⚠ Engineering attrition spike: 2 departures = 1.5% of engineering in one month
If trend continues, annualized attrition in engineering will be 24% (target 12%)
⚠ PM role open 45 days (typical is 25; limited candidate pool)
⚠ Span of control: 2 managers now have 12+ reports (best practice 8-10)

WHAT WE'RE DOING ABOUT IT
• Engineering: Compensation benchmark review underway (due May 10).
If gap found, adjustment proposal to executive team by May 15.
• PM search: Expanded to use executive recruiter if not filled by May 31.
• Span of control: Recruiting for engineering team lead backfill; target start June 15.

FORECAST
- On track to hit Q2 hiring targets if PM role fills by May 31 ✓
- Attrition forecast: If engineering trend continues 1-2 more months, expect
16-18% annualized (above target). If stabilizes, expect 12-14%.
- Headcount forecast Q2 end: Plan 495. Most likely outcome 490 (3 departures offset
by 6 hires if we hit targets).

DECISION NEEDED THIS MONTH
1. Approve engineering compensation adjustment? (Budget impact $60-80k annually)
2. Approve executive recruiter for PM search? (Cost $25-30k, but faster results)

This one-pager does several critical things:
1. Headline tells the story immediately. Not "Here's the data." But "Here's what it means." The CEO reads the headline and already knows the answer: "on track overall, but engineering issue to watch."
2. Metrics show current state and trend. "Attrition is 1.2% this month" is a data point. "Attrition is 1.2% this month, up from 0.9% last month, trending up" shows pattern and direction. "...trending up, primarily in engineering" shows where the problem is.
3. Highlights and concerns focus on what matters. Not "1.2% of people left." But "Engineering is losing people due to compensation gaps. This costs us [X] and risks growth plan."
4. Recommendations tell leadership what to do. Not "We have a retention problem." But "We recommend raising engineering salaries by [X]% at cost of $[Y], or expanding recruiter budget to reduce hiring time, or both."

Leaders can skim in 5 minutes, understand the issues, and make decisions. No follow-up email needed. No "let me get back to you."

Important Warning: Most HR leaders write these reports wrong. They lead with metrics ("Attrition: 1.2%") instead of insights ("We're losing engineers to compensation gaps."). They bury the decision needed ("At the bottom: "Approve recruiter budget? Yes/No.") instead of front-loading it. Rewrite your report with the headline and decision first.

The Quarterly Business Review: Comprehensive Strategic View

3-4 pages. Designed to be read in 20 minutes. Comprehensive view of people function.

Page 1: Executive Summary (1 page)

• Opening paragraph: What happened this quarter? In one paragraph, what's the most important thing leadership should know?
  - Key metrics snapshot: Headcount change, attrition rate, hiring progress, biggest concern
  - On track against plan? Yes/yellow/no for each major goal
  - One main decision needed

Example:

QUARTERLY BUSINESS REVIEW | Q2 2026 | PEOPLE & CULTURE

EXECUTIVE SUMMARY

Q2 was a solid quarter for hiring but exposed retention risks in engineering.
We hired 18 people (plan: 17), bringing us to 495 headcount. However, we lost
6 people (attrition 1.2%), primarily in engineering (4 departures due to
compensation gaps). We're on track to hit annual headcount targets, but
attrition is trending 20% above target. Key risk: If engineering attrition
continues at current rate, we'll struggle to scale the engineering team for
product roadmap. Recommendation: Conduct immediate compensation review in
engineering and approve retention bonuses for key people.

GOALS THIS QUARTER
✓ Hire 17 people → 18 hired (on track; 106% of target)
⚠ Attrition 1.0% or lower → 1.2% actual (20% above target; watch trend)
✓ Hit diversity targets → 40% women, 22% URM (on track)
? Launch succession plan → 40% complete; on track for Q3 launch
⚠ Implement new perf review system → delayed to Q3 (resource constraints)

HEADCOUNT SNAPSHOT
Start Q2: 477. Hires: 18. Departures: 6. End Q2: 495
% of plan: 108% (ahead on count, but cost of attrition offsetting)

Page 2-3: Details (2 pages)

This is where you go deeper. Show what's working, what's not, where you need help.

Hiring (with trends)

HIRING PERFORMANCE

Hires this quarter: 18 (plan 17, on track)
- Engineering: 8 hired (plan 8) ✓
- Sales: 4 hired (plan 4) ✓
- Operations: 6 hired (plan 5) (over-hired; was vacancies)

Time-to-fill trend:
Q1: 32 days
Q2: 28 days (improving) ✓

Offer acceptance rate: 91% (steady)

By department time-to-fill:
Engineering: 35 days (target 25; candidate pool small)
Sales: 22 days (target 25; on track)
Operations: 20 days (target 25; over-filled vacancies)

Forecast Q3: Plan to hire 20 (expansion + backfills). Risk: If engineering
attrition continues, we'll be hiring to backfill rather than expand.

Retention (with root cause analysis)

RETENTION & ATTRITION

Attrition Q2: 1.2% (plan 1.0%, actual 20% above target)
Annualized attrition: 14.4% (target 12%)

Departures this quarter: 6 people
- 4 engineers (cited: compensation below market, limited growth, stress
from understaffing)
- 1 sales rep (relocation)
- 1 contractor (ended contract)

By tenure:
< 1 year: 2 departures (new hires not fitting)
1-2 years: 2 departures (compensation and growth issues)
2+ years: 2 departures (contractors and relocations)

Retention risks (people who might leave):
- 2 senior engineers expressed concerns about compensation to manager
- 1 product manager interviewed externally (per LinkedIn tracking)
- Engineering team morale declining due to understaffing

Root cause: Engineering compensation is 8-12% below market rates (based on
salary benchmarking). High workload due to 2 departures earlier in year
(staff gap not backfilled quickly enough).

Recommendation:
1. Conduct formal compensation review in engineering by July 15
2. If gaps found, approve retention bonuses for key people (budget $80-120k)
3. Accelerate backfill hiring (currently 2 reqs open; add urgency)
4. Assess workload/burnout in engineering (survey or focus groups)

Development & Succession

DEVELOPMENT & SUCCESSION READINESS

Promotions Q2: 2 (both successful, on track)

Succession readiness:
VP level (currently 3, plan for 2-3 more over next 2 years):
- Ready now: 1 (Director of Engineering, can move to VP Engineering)
- Ready in 12 months: 1 (VP Sales role, Director Sales is developing)
- Need development: 2 others have potential but 18+ months away

Manager pipeline:
- 8 people identified as "manager ready" (vs. plan of 10)
- 2 identified but not yet ready (need training/mentoring)

High-potential program: Launched 3 months ago, 5 people enrolled, progressing well

Recommendation: Close the 2-person gap in manager readiness by end of Q3
(training and assignment to stretch roles)

Risk: If attrition continues in engineering, our senior engineer pipeline
gets disrupted. Two of the "ready now" for promotion were the engineers
we just lost.

Compensation & Budget

COMPENSATION & MARKET POSITIONING

Salary spend: On budget ($2.8M YTD vs. $2.85M plan, 98%)
Variable comp spend: On budget (bonuses, commissions tracking)
Equity spend: On budget (RSU grant value $1.5M annual plan)

Market benchmarking (Q2 survey):
Engineering salaries: 8-12% below market (concerning)
Sales comp: On market (95-105% of market median)
Operations: On market (98-102% of market median)

Equity:
Senior engineers at lower quartile of equity (compared to Bay Area norms)
PM compensation in line with market

Budget impact of compensation adjustment:
- 8% increase in engineering base salaries: $150-200k annually
- Retention bonuses for 3 key engineers: $80-120k (one-time)
- Total: $230-320k for remainder of year

Recommendation: Approve engineering salary adjustment by July 1

Page 4: Risks & Opportunities (1 page)

RISKS & OPPORTUNITIES

IMMEDIATE RISKS (Next 30 days)
• Engineering attrition continues: Losing another 1-2 engineers would drop
team below minimum viable size for product roadmap. Mitigation: compensation
review + stay conversations with at-risk people
• PM hiring takes longer: If PM search extends beyond 60 days, impacts product
planning. Mitigation: bring in executive recruiter, lower experience bar if needed
• Manager span of control: 2 managers with 12+ reports burning out. Mitigation:
accelerate manager backfill

MEDIUM-TERM RISKS (Next 90 days)
• Cumulative attrition effect: If we lose 2-3 more people in engineering,
ramp-up becomes impossible and product delivery suffers
• New hires not integrating: Q1/Q2 cohort has 2 people struggling (at risk of
early departure). Mitigation: check-ins, mentoring, clear feedback
• Diversity gains fragile: If we continue losing diverse hires at higher rates,
we lose progress. Mitigation: track retention by demographic, address root causes

OPPORTUNITIES (Win column)
• Manager pipeline strong: 8 people identified as manager-ready. If we invest in
training, we have strong bench for growth
• Succession plan launch: 40% complete, launching Q3. This will clarify our
succession risks and create a plan
• Sales hiring on track: Sales team is happy and productive. Opportunity to
promote strong performers into team lead roles

WHAT WE NEED FROM LEADERSHIP
1. Approval for engineering compensation adjustment ($230-320k spend)
2. Decision on hiring speed trade-off: Hire fast (lower bar, higher cost) or
slow (higher quality, lower cost, risk of missing targets)?
3. Decision on manager development program: Invest in training vs. external hire
for future manager roles?

This quarterly view gives leadership everything they need to understand the people function and make strategic decisions. It's not fluff. It's not overwhelming. It's the right amount of detail for 20-minute review.

The Annual Board Report: Strategic Overview

5-8 pages. Presented to board of directors. Deep strategic view of people function.

Table of Contents:

• Executive Summary (1 page) - What happened this year? Did we achieve our people strategy? What's ahead?
  - People Strategy & Goals (1 page) - Our strategy. Goals. Did we hit them?
  - Hiring & Headcount (1-2 pages) - Where we are. Where we planned to be. Success metrics.
  - Retention & Culture (1-2 pages) - Attrition analysis. Trends. Root causes. Culture health.
  - Development & Succession (1 page) - Pipeline. Promotions. Succession readiness for key roles.
  - Compensation & Benefits (1 page) - Market positioning. Equity. Budget impact.
  - Diversity, Equity, Inclusion (1 page) - Progress. Gaps. Commitments for next year.
  - Risks & Outlook (1 page) - What could derail us. What's the opportunity. Next year plan.

Example Board Report excerpt:

ANNUAL PEOPLE STRATEGY REPORT | 2026

EXECUTIVE SUMMARY

2026 was a year of significant growth and learning. We hired 78 people (target 80)
and grew from 417 to 495 headcount (+18.7%). However, we lost 12 people to attrition
(target 8), revealing compensation and culture gaps we're now addressing. Our people
strategy of "selective growth + retention focus" was only partially achieved: growth ✓,
but retention challenge. Key wins: strong hiring in engineering and sales, successful
launch of manager development program, diversity hiring on track. Key learning:
engineering compensation is not competitive at the Bay Area market rate, causing
above-target attrition. Key action for 2027: compensation adjustment and retention
focus in engineering + launch succession plan for director-level roles.

PEOPLE STRATEGY 2026

Strategy: "Selective growth with retention focus"
• Grow headcount to 500 (target 500 by year-end)
• Hit 90% manager satisfaction
• Achieve 10% attrition rate (top quartile)
• 35% women, 30% underrepresented minorities

RESULTS 2026
✓ Headcount: 495 (99% of target; essentially hit target)
✓ Manager satisfaction: 88% (close to target, slight miss)
⚠ Attrition: 12.6% (above target of 10%; 26% miss)
✓ Diversity: 38% women, 28% URM (on track for next year)

KEY DECISIONS NEEDED FOR 2027
1. Approve engineering compensation adjustment ($230-320k annually)
2. Approve director-level succession plan (resource + budget TBD)
3. Commit to diversity investment (mentorship program, recruiting focus, etc.)

The board reads this and understands: growth is happening, but there's a retention risk we're addressing. Leadership is engaged. Strategy is clear. Decisions are needed.

Making Reports Board-Ready: Visualization and Translation

Board members don't care about HR metrics. They care about business impact. So translate.

Instead of: "Attrition is 2.5%, above our target of 2.0%"

Say: "We're losing 30 people annually, costing us $2M in replacement costs and onboarding time. Last quarter we lost 2 engineers and 1 PM to competitors, each costing $150k to replace. Root cause: compensation is below market. Recommendation: Raise engineering salaries 8-10% at cost of $250k annually."

Now the board understands: this is a business problem with a cost, a root cause, and a solution.

Use visuals, not tables.

Instead of:

Month | Attrition Rate
Jan | 1.1%
Feb | 1.3%
Mar | 1.2%
Apr | 1.5%
May | 2.0%
Jun | 1.8%

Show:

Attrition Rate (Monthly %)

2.5% | target 1.0%
2.0% | ___,--/
1.5% | ,--‾‾‾‾\___/
1.0% |__,--/ <- target
0.5% |
| Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec

The chart shows at a glance: attrition was low Jan-Mar, spiked Apr-May, coming down but still above target.

Translate metrics to business language:

• "Attrition 12.6% annually" → "Losing 1 person per month per 100-person team"
  - "Time-to-fill 35 days" → "6 weeks to fill an open role, delaying product launches"
  - "Manager span of control 11 reports" → "Managers stretched, less 1:1 time with reports, risk of manager burnout"
  - "Diversity: 38% women, 28% URM" → "Underrepresented vs. tech industry average (45% women, 35% URM), underrepresented vs. California population (52% women, 50% URM)"

Board members understand business impact. So frame HR metrics as business problems: cost, revenue impact, execution risk, culture risk.

Common Executive Report Mistakes (And How to Fix Them)

Mistake 1: Too much detail.
Your annual board report is 15 pages with every data point you can think of. Board members skim the first page and give up.

Fix: Ruthlessly cut detail. Annual board report: 5-8 pages max. Every page should answer a question ("Are we on track? What are the risks?"). If a page doesn't answer a question, delete it.

Mistake 2: No context.
"Attrition is 2.5%." OK, is that good or bad? Better or worse than before? Better than industry?

Fix: Always show context. "Attrition is 2.5% (target 2.0%, down from 3.0% last year, above industry average of 2.0%). Trend is improving but still above target."

Mistake 3: No recommendations.
"We have a hiring problem. Our time-to-fill is 40 days." OK, what should we do?

Fix: Always include recommendations. "Time-to-fill is 40 days (target 25). Options: (1) Hire recruiting team (cost $200k/yr, would reduce time-to-fill to 25 days); (2) Use recruiters for half of hires (cost $100k, would reduce time-to-fill to 32 days); (3) Lower hiring quality bar (faster, but risk of retention)."

Mistake 4: No visuals.
Your report is 8 pages of tables and prose. Exhausting to read.

Fix: Add charts. "Hiring vs. plan" as a trend chart. "Attrition by department" as a bar chart. "Headcount growth" as a stacked bar chart showing hires, departures, net change. Visuals are 10x easier to understand than tables.

Mistake 5: No business impact.
"Retention of senior engineers is 87%." So what?

Fix: Connect to business. "We're losing one senior engineer every 6 months. Each engineer takes 4 weeks to ramp up. So we lose 1 month of productivity per engineer lost. Over a year, that's 2 months of engineering productivity lost. At $300k average engineer cost, that's $50k in lost output annually, plus $150k in replacement costs. Total impact: $200k. Recommendation: Improve retention through compensation adjustment."

Mistake 6: Data is wrong or missing.
Your report says "Attrition is 2.0%" but your HRIS system shows 2.3%. Or you don't have data on retention by department.

Fix: First, get accurate data. Second, if data is incomplete, say so. "We have complete hire/attrition data. Engagement survey data is in progress (due Q3). Succession data is being documented now."

Practical Application. Build Your Reporting System

For the next month, implement a reporting system:

Step 1 (This week): Talk to your CEO/CFO.
"If you had one people report each month, what would be on it? What decisions do you make based on people data?"

Step 2 (Next week): Create templates.
- Monthly flash report (1 page template)
- Quarterly business review (4-page template)
- Annual board report (8-page template)

Step 3 (Week 3): Identify your metrics.
Monthly: headcount, attrition, hiring progress, 2-3 key concerns
Quarterly: above + department details + risks/opportunities + recommendations
Annual: strategic overview + year-over-year comparison + next-year plan

Step 4 (Week 4): Automate the data.
Set up a dashboard or spreadsheet that auto-pulls headcount, hiring, attrition, turnover cost, etc. You shouldn't be manually calculating every month.

Step 5 (Ongoing, Month 2+): Write the narrative.
Don't just present numbers. Provide context: "Attrition is 2.5% (above target), trending up, primarily in engineering, due to compensation gaps, costing us $200k annually. Recommendation: approve compensation review."

Step 6: Add visuals.
Chart attrition trends. Chart hiring vs. plan. Chart headcount growth. Visuals communicate faster than numbers.

Step 7: Send on schedule.
First Friday of month (flash report). End of each quarter (QBR). Once a year (board report). Consistency signals that this matters.

Step 8: Get feedback.
After each report: "Is this useful? What's missing? What should I change?"

Key Takeaways

• 
  Executive reports must be concise and actionable. One page for monthly (5-minute read). 3-4 pages for quarterly (20-minute read). 5-8 pages for annual (deep dive, 30-minute read).
• 
  Translate data to business impact. Don't say "attrition 2.5%." Say "losing 30 people annually, costing $2M in replacement and onboarding time."
• 
  Show trends, not snapshots. "Attrition is 2.5%" is a data point. "Attrition is 2.5%, up from 1.8% last quarter, trending up for 3 consecutive quarters" is a trend.
• 
  Use visuals. Charts show trends immediately. Line graphs for metrics over time. Bar charts for comparisons. Visuals are 10x faster to understand than tables.
• 
  Include recommendations. Problem statement without recommendation is incomplete. "Attrition is rising" is a problem. "Attrition is rising, due to compensation gaps, recommend approving $250k salary adjustment" is actionable.
• 
  Report consistently. Monthly, quarterly, annually. Leadership learns to expect it and builds it into decision-making cycles.
• 
  Know your audience. Monthly report is for CEO/CFO (busy, high-level). Quarterly is for exec team (more detail, strategic decisions). Annual is for board (strategic, full-year view).
• 
  AI can generate much of the report. Metrics auto-calculated. Formatting and charts auto-generated. But narrative and recommendations require human judgment. You write those.

FAQ

Q: How do I know what metrics leadership cares about?
A: Ask them. "If you had one people report each month, what would be on it?" You'll get the answer. Also look at what decisions they make: hiring approvals, compensation changes, headcount planning. The data behind those decisions should go in your report.

Q: Should I send the same report to the board as the CEO?
A: No. Board report is more strategic and less operational. CEO report might have "Hire 2 more salespeople" (operational). Board report would have "Sales hiring on track for growth targets, diversity improving." Same data, different focus.

Q: What if the data is bad?
A: Say so. "We don't have complete data on engineering departures by reason (HR surveys incomplete). We're working to improve data quality." Better to acknowledge a gap than to make up numbers or hide bad news.

Q: Can I automate report generation?
A: Mostly yes. Metrics auto-calculated from HRIS/ATS. Charts and formatting auto-generated. But narrative (context, recommendations) needs to be human-written. That's where judgment comes in.

Q: How do I handle bad news in a report?
A: Don't hide it. Lead with it. "We missed our attrition target this quarter (12.6% vs. 10% target). Root cause: engineering compensation gap. Recommendation: approve compensation review and retention bonuses." Leadership respects honesty. They'll lose respect if you hide problems.

Q: Should I include leading indicators (not just lagging)?
A: Yes. Attrition is a lagging indicator (people already left). Engagement survey scores, exit interview data, and employee sentiment are leading indicators (predicting future attrition). Include both.

Q: How many metrics is too many?
A: Monthly report: 3-5 key metrics. Quarterly: 8-12. Annual: 15-20. More than that and you're overwhelming the reader. Only include metrics that drive decisions.

What's Next

You've now covered how to report people data to leadership. The next chapter dives into advanced prompt techniques: how to use AI to solve complex HR problems that require reasoning, not just data processing. You'll learn chain-of-thought prompting, persona engineering, and multi-step workflows that let AI solve problems that require human-like reasoning.