Write the monthly people report: headcount, starters and leavers, overtime and leave
At the start of the month Claude reads last month's staff, overtime and leave records and writes the people report for the owner: headcount, who joined and who left, overtime and leave by department, against last month.
FullHRWhen you need it
Set it up5 steps
Open the Claude desktop app and sign in with the Claude account you use for work. On a personal Free, Pro or Max plan, chats can be used for training unless you switch off SettingsPrivacyHelp improve Claude.
No account yet? Ask your manager.
Where things are in Claude
- CustomizeConnectors In Claude's left sidebar: connect your email and files.
- /schedule Type it in a new Cowork task to run a prompt on a schedule.
- Scheduled In Claude's left sidebar: what runs, to pause or change it.
- On the first working day of the month, put last month's staff list, overtime and leave records, as your payroll program or your accountant gives them, into a Monthly folder inside your HR folder. Leave pay out of them.
- Keep a one-page "Hours rules" file in your HR folder with your normal hours, overtime limit and leave rules, as your handbook or your accountant gives them. Claude uses no limit of its own.
- Connect Google Drive under CustomizeConnectors. Keep this workflow's files in one Drive folder called HR.
- Open Cowork, paste the prompt and name the month. The first time, also put your last report in the Monthly folder, so Claude follows its layout.
- Check every number against your records before the report goes to anyone. Claude marks what it could not find.
Set this up on your computer: the Claude desktop app runs it.
The prompt
- Write the people report for the month I name, from the files in the Monthly folder inside my HR folder, the "Hours rules" file in my HR folder, and last month's report in the Monthly folder inside my HR folder.
- 1. Headcount at the start and the end of the month, by department, and against the same month last year where the data has it.
- 2. Starters and leavers by department, with the leaving reasons as recorded (resigned, dismissed, end of contract, retired, other). Count separately the leavers who had been with us less than 6 months.
- 3. Overtime hours by department, against last month. List the people above the overtime limit in the "Hours rules" file. If the file gives no limit, write [TO FILL: our overtime limit] and do not use one of your own.
- 4. Leave days taken by type (annual, sick, unpaid, other) and by department, against last month.
- 5. Three lines on what needs attention, such as a department whose overtime or sick leave rose by a third or more, or several leavers from one team.
- Write it as a Google Doc in the Monthly folder. Use only the figures in the files, and write [MISSING] where one is not there. Describe teams, not people: never guess why someone left or was off, never comment on anyone's health, and name a person only in the overtime list.
If your company keeps employee records out of AISafe version
Counts only. Claude reads numbers by department with no names, ID numbers or pay, and a department of fewer than 5 people is counted with another, so no number points to one person.
What you get
A two-page people report with the month's numbers by department, the changes against last month, and three lines on what needs attention.
Get this workflow for your team
Two minutes each: everyone gets a plan of ready workflows like this one, inside your company's rules.
Your manager sees progress and hours. Never what Claude reads or writes.
FirstPrompt's workflow library adapts parts of Anthropic's knowledge-work-plugins (Apache-2.0), rewritten by FirstPrompt. Source and licence