Scheduled People-Metrics Digest: Auto-Draft Your Business-Unit Leader's Report

What This Builds

A standing pipeline that turns your recurring HRIS export into a first-draft narrative report, ready for you to review before your business-unit leader ever sees it. You still own the send. The pipeline just kills the part where you rebuild the same slide from scratch every cycle because last quarter's version is buried in someone else's folder.

The report drafts itself between the moment the data lands and the moment you sit down to check it.

Prerequisites

• A standard export you already run from your HRIS (turnover, headcount, or engagement data) that lands as a file or a copy-paste into a spreadsheet
• A Zapier account on a plan that supports multi-step Zaps and a scheduled trigger
• A Google Workspace account for the Sheet and Doc this pipeline reads from and writes to
• A Claude account to draft the narrative summary
• Total ongoing cost if you do not already have these: $29.99/month for Zapier's Professional plan, plus $20/month for Claude. Google Workspace is typically already covered by your employer's business license.

The Concept

Think of this as a standing research assistant who reads your spreadsheet the moment you finish updating it and hands you a written summary before you ask for one. You are not automating the report. You are automating the first draft of the report, the part that never actually needed your judgment, so your time goes to deciding what the leader needs to hear instead of formatting a table.

Build It Step by Step

Part 1: Standardize where the data lands

Pick one Google Sheet as the fixed destination for your recurring export (turnover, headcount, or engagement, whichever cycle you are automating first). Keep the same tab name and column headers every cycle. Zapier needs a stable shape to read from, and a moved column or renamed tab is the most common reason this kind of pipeline quietly breaks.

Name the tab something exact, like Q_Export, and never rename it once the Zap is live.

Part 2: Build the scheduled trigger

1. In Zapier, click Create Zap
2. For the trigger, search Schedule by Zapier and choose the cadence that matches your reporting cycle (monthly or quarterly)
3. Set the day and time you want the draft to start assembling, ideally a day or two before you actually need to review it, so you have buffer if something needs a rerun

What you should see: A scheduled trigger that will fire automatically on your chosen cadence, with no manual step needed to start it.

Part 3: Pull the sheet data and generate the narrative

1. Add a step: Google Sheets → Lookup Row(s) or Get Many Spreadsheet Rows, pointed at your Q_Export tab
2. Add a step: Claude (Zapier's Claude/Anthropic integration) → Send Prompt
3. In the prompt field, paste the data from the previous step along with instructions like: "Summarize this turnover data by department. Call out any department where the rate moved more than 3 points from last quarter. Write two short paragraphs a business leader can read in under a minute. Do not name individual employees."
4. Test the step and check that the output reads like a paragraph, not a data dump

What you should see: A written summary, two or three paragraphs, with specific numbers pulled from your sheet rather than generic language.

Part 4: Route the draft to yourself, not to the leader

1. Add a step: Google Docs → Create Document from Text, using the Claude output as the body, saved to a folder only you and your manager can access
2. Add a final step: Email by Zapier or Gmail → Send Email, addressed to yourself, with a subject line like "DRAFT: [Business Unit] People Metrics, ready for your review"
3. Do not add the business-unit leader as a recipient anywhere in this Zap. That step happens outside the automation, by hand, after you have reviewed the draft.

What you should see: An email in your own inbox linking to a draft document, not a report the leader has already received.

Part 5: Turn it on and review your first cycle

Publish the Zap. On the next scheduled run, open the draft, check every number against the source sheet, edit the language to match how you would actually say it to this leader, then send or share it yourself. This review step is not optional. It is the whole reason the leader's name is not in the automation.

Real Example: Quarterly Attrition Digest for the Sales Org

Setup: A Zap runs on the first business day of each quarter, reading a Q_Export tab with department-level turnover numbers.

Input: The quarterly export shows attrition in the sales org rose from 8% to 13%, concentrated in employees with under 18 months of tenure.

Output: Claude drafts: "Attrition in the sales organization rose from 8% to 13% this quarter, with the increase concentrated among employees in their first 18 months. Three of the four departures cited compensation in exit conversations. Recommend reviewing entry-level sales compensation ahead of next quarter's planning cycle." You edit the last sentence, because you know the leader already has budget concerns, and send it from your own account.

Time saved: What used to take two to three hours (pulling the export, building a pivot, writing the narrative) now takes 15-20 minutes of review and editing.

What to Do When It Breaks

• No draft email arrives on schedule → This is the failure you will not notice unless you check for it. Open Zapier's Task History weekly for the first month and turn on Zapier's built-in "notify me on Zap error" setting so a failed run emails you instead of silently skipping.
• Claude's summary reads like a data dump instead of a narrative → Your prompt is too vague. Add an explicit instruction like "write in full sentences, no bullet points, under 150 words" and re-test.
• Numbers in the draft do not match the sheet → Check that the column headers did not shift. A renamed or reordered column is the most common cause; the Lookup Row step reads by header name, not position.
• The Sheet lookup pulls stale or duplicate data → Confirm your export process overwrites the Q_Export tab each cycle rather than appending new rows below old ones.

Variations

• Simpler version: Skip the Google Doc step and just have Claude's output land directly in your own draft email, if you are comfortable editing inline rather than in a document
• Extended version: Add a second Claude step that drafts three discussion questions based on the data, so the digest doubles as prep for your next 1:1 with the leader

What to Do Next

• This week: Build the Zap around whichever export you already run most often
• This month: Run it through one full cycle and tighten the prompt based on what you had to edit
• Advanced: Add a branch that routes a second, more detailed version to yourself for calibration prep, using the same underlying data pull

Advanced guide for HR Business Partner professionals. Automations move workforce data through a third-party platform on their own. Aggregate to department or business-unit level rather than naming individuals in the source sheet where possible, confirm with whoever owns your company's data policy that people-analytics exports are approved to flow through Zapier and Claude, keep any leave or medical-related fields out of the export entirely, and restrict access to the destination Sheet and Doc to the same people who could already see the underlying HRIS report.