---
name: people-report
description: "Prepare headcount, turnover and organization-health report. Use for this workflow with supplied business information."
---

# People report

## Inputs and purpose

Use this workflow to prepare: Headcount, turnover and organization-health report.

Start with: Employee roster and dated workforce events.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Define reporting dates, employee populations and counting rules. Keep employees, contractors and vacant roles distinct.

2. Reconcile opening headcount, additions, exits and closing headcount. Use the agreed average population for turnover calculations.

3. Summarize relevant workforce changes without exposing unnecessary individual details or drawing conclusions from very small groups.

4. Return a workforce report and data-quality notes. State denominator, period and inclusion rules for every rate.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Clarify hiring, onboarding and employee processes.

Possible success measures: Time to hire, time to independence, HR admin hours. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).