These 25 prompts are for HR managers who need a finished weekly report draft, not another blank template. Fill in the variables, paste the prompt into ChatGPT or Claude, and use what comes back with light edits.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
Weekly Headcount and Hiring Status Reports
You are an HR manager writing a weekly hiring status update for senior leadership.
Reporting week: {week_ending_date} Open roles: {number_of_open_roles} Roles with active candidates: {roles_with_candidates_list_in_bullets} Offers extended this week: {number_of_offers_extended} Offers accepted: {number_accepted} Hiring blockers or delays: {blocker_description_or_none} Tone: {concise and factual / executive-facing / operational}
Write a 200 to 250 word hiring status update. Open with a one-sentence headline on overall hiring health. Use a brief narrative paragraph followed by a bullet list of role-by-role status. Close with one sentence flagging the top action item for next week. No HR jargon. Write like a business update, not a staffing report.
When to use it: Friday afternoon before you send the weekly leadership pack and your hiring pipeline has moved in at least two roles.
Pro tip: If you have zero offers accepted this week, change the tone variable to “operational” — it signals the update is factual and prompts less anxiety than an executive-facing tone on a slow week.
You are an HR manager writing a weekly headcount summary for the CFO.
Reporting week: {week_ending_date} Total headcount at week close: {total_headcount} Net change from prior week: {net_change_as_plus_or_minus_number} Departments with headcount movement: {department_and_change_in_bullets} Approved headcount budget for this quarter: {approved_budget_number} Variance to budget: {variance_as_plus_or_minus_number} Known upcoming changes: {upcoming_hires_or_departures_or_none}
Write a 150 to 200 word headcount summary memo. Lead with the current total and net change. Show the budget variance in plain terms (over, under, on track). List department movements in a tight bullet table format. Close with one sentence on the next material headcount event and its expected week.
When to use it: When the CFO has asked for weekly headcount visibility and you want a consistent format they will actually read rather than forward unread.
Pro tip: If your variance to budget is zero, say “on track” not “zero variance” — CFOs read fast and “on track” reads as confident rather than overly technical.
You are an HR manager writing a weekly time-to-fill tracking note for the recruiting team lead and hiring managers.
Reporting week: {week_ending_date} Roles tracked this week: {role_list_in_bullets_with_days_open} Company target time-to-fill: {target_days} Roles exceeding target: {over_target_roles_and_by_how_many_days} Root cause for delays where known: {delay_reasons_or_none} Next interview slots confirmed: {yes_or_no_with_detail}
Write a 180 to 220 word internal tracking note. Use a data-first opening sentence. Present the role-by-role status in a simple table (role | days open | status vs target). Flag roles over target in bold. Write one sentence per delayed role naming the reason. Close with a two-sentence action summary for the week ahead.
When to use it: Monday morning before your stand-up with hiring managers, so the conversation starts with shared data rather than competing recall.
Pro tip: Rename “exceeding target” to “at risk” in the output — hiring managers respond faster to risk language than to metrics language when you need their calendar cleared for interviews.
You are an HR manager writing a weekly attrition alert for the CHRO.
Reporting week: {week_ending_date} Departures confirmed this week: {number_of_departures} Departure details: {name_or_role_and_department_and_voluntary_or_involuntary} Rolling 90-day attrition rate: {rate_as_percentage} Departments with elevated attrition: {department_names_or_none} Exit interview themes collected this week: {one_to_three_themes_or_pending}
Write a 150 to 200 word attrition alert. Open with the 90-day rate compared to the prior period in one sentence. Summarise this week’s departures without using names if involuntary. Note elevated departments. If exit themes are available, write a short paragraph naming them. Close with a recommended action or monitoring note for the CHRO. Tone: direct, no alarm language unless the rate has crossed a threshold of 15% rolling.
When to use it: Any week with two or more confirmed departures, or when a department’s rolling rate has shifted by more than two percentage points.
Pro tip: If exit interview data is still pending, write “pending” in that variable rather than leaving it blank — the prompt will correctly flag it as a gap the CHRO should expect to see filled next week.
You are an HR manager writing the new hire onboarding completion summary for the weekly ops review.
Reporting week: {week_ending_date} New hires in their first 30 days: {number_of_new_hires} Onboarding tasks completion rate: {completion_rate_as_percentage} Incomplete items and owners: {item_and_owner_in_bullets_or_none} New hire feedback received: {sentiment_summary_or_none} Escalations or issues this week: {issue_description_or_none}
Write a 160 to 200 word onboarding summary. Open with the completion rate and whether it is above, at, or below the 90% benchmark. List incomplete items as a short action table (item | owner | due date). If feedback was received, summarise it in two sentences using the sentiment provided. Close with one sentence on what HR will monitor in the coming week. Tone: operational and brief.
When to use it: Wednesday or Thursday, when you want the ops review to land with visibility on any onboarding gaps before the end of the week.
Pro tip: If completion rate is below 85%, add “escalation risk” as a tag in the subject line of the email you attach this to — it gets the right people moving without you having to chase separately.
Weekly Employee Relations and Compliance Updates
You are an HR manager writing a weekly ER case status summary for the HR director.
Reporting week: {week_ending_date} Active ER cases this week: {number_of_active_cases} Case categories: {categories_list_e.g._conduct_grievance_performance_in_bullets} Cases opened this week: {number_opened} Cases closed this week: {number_closed} Cases requiring director escalation: {yes_with_brief_reason_or_none} Confidentiality level: {standard_internal_or_restricted}
Write a 200 to 250 word ER case summary. Do not include names or identifying details. Use case reference numbers if available, otherwise use “Case A, Case B” etc. Open with an overall case load sentence. Summarise movement (opened, closed, pending). Flag any escalation in a clearly labelled section at the end. Tone: clinical, factual, written for a director who reads this in two minutes.
When to use it: End of week before the HR director’s Friday review, when your ER log has had any movement at all during the week.
Pro tip: If a case involves a protected characteristic, add that it is “legally sensitive” in the escalation section but do not specify the characteristic in this summary — your director needs to know to read the case file before acting, not to act on the summary.
You are an HR manager writing a weekly compliance training completion report for the legal and compliance team.
Reporting week: {week_ending_date} Training module name: {training_module_name} Completion deadline: {deadline_date} Current completion rate company-wide: {completion_rate_as_percentage} Departments below 80% completion: {department_names_or_none} Employees with zero progress past the midpoint reminder: {number_or_none} Next automated reminder date: {next_reminder_date}
Write a 180 to 220 word compliance training status report. Open with the completion rate and days remaining to deadline. List below-threshold departments as a bullet with their individual rates. Flag non-starters in one sentence with the count only, no names. Close with the reminder schedule and one sentence on what HR will do if the rate falls below 70% by the deadline. Tone: formal, factual, suitable for forwarding to legal.
When to use it: Midway through a mandatory training window, when legal has asked for a status update before the deadline hits.
Pro tip: If you are five or fewer days from the deadline and below 80%, change the closing sentence to request authority to send a manager-directed nudge from the CHRO — compliance teams respond faster when the ask is specific and comes with a clear escalation path.
You are an HR manager writing a weekly grievance and complaint intake log summary for the VP of HR.
Reporting week: {week_ending_date} New complaints received: {number} Complaint categories this week: {categories_in_bullets_e.g._harassment_pay_dispute_management_conduct} Complaints acknowledged within SLA (48 hours): {yes_all_or_number_out_of_total} Investigation status on prior open complaints: {brief_status_per_case_using_case_letters} Pattern or trend flagged: {yes_with_description_or_none}
Write a 200 to 240 word intake log summary. Open with the week’s intake count and whether acknowledgement SLA was met. Summarise category distribution in two to three sentences without naming individuals. Update prior cases with one-line status per case using case letters. If a trend is flagged, write a standalone short paragraph on it and recommend one action. Tone: measured, professional, suitable for VP-level review.
When to use it: Any week where two or more complaints arrive in the same category — that repetition is the signal a pattern summary will be useful.
Pro tip: If all complaints this week fall into one category, the VP will ask why immediately. Pre-empt this by adding a one-sentence hypothesis in the trend section even if you mark it as unconfirmed — it shows you are watching the data, not just logging it.
You are an HR manager writing a weekly policy exception and deviation report for the HR operations lead.
Reporting week: {week_ending_date} Policy exceptions requested: {number} Exception types: {types_in_bullets_e.g._remote_work_policy_leave_cap_notice_period_waiver} Exceptions approved: {number_approved} Exceptions denied: {number_denied} Exceptions pending review: {number_pending} Approving authority for each approved exception: {role_not_name_per_exception}
Write a 160 to 200 word policy exception log narrative. Open with the week’s exception count versus the prior four-week average if you have it, or just the count. Summarise the types briefly. List approved and denied counts with the authority level that signed off. Flag any pending exceptions that are older than five days. Close with one sentence on whether exception frequency is trending up, stable, or reducing. Tone: operational, concise.
When to use it: Before your weekly HR ops meeting when you want a written record of exception decisions that can be filed and referenced in audits.
Pro tip: If the same policy type appears in exceptions three weeks running, that variable is your prompt to add “recurring exception type — recommend policy review” in the closing sentence. It flags a systemic gap without you having to call a separate meeting.
You are an HR manager writing a weekly safety and incident report for the operations and HR leadership team.
Reporting week: {week_ending_date} Incidents reported: {number_or_none} Incident types: {types_e.g._near_miss_first_aid_recordable_in_bullets} Recordable incidents this week: {number} Year-to-date recordable count: {ytd_count} Root cause identified: {yes_with_summary_or_under_investigation} Corrective actions taken or in progress: {action_list_or_none}
Write a 180 to 220 word safety incident summary. Open with the week’s incident count and whether any are recordable under OSHA standards. Summarise each incident type in one sentence. State the YTD count in context (same period last year or against the annual target if known). Present corrective actions as a numbered list. If root cause is still under investigation, say so clearly and note the expected date for findings. Tone: factual, no minimising language.
When to use it: Every week, even on zero-incident weeks — a “zero incidents this week” report takes 30 seconds to produce and protects you if a question about a prior week’s reporting gap ever arises.
Pro tip: On zero-incident weeks, keep the corrective actions field populated with any ongoing actions from prior weeks. A report that shows active follow-through is more useful to operations leadership than a blank-field report.
Weekly Payroll, Compensation, and Benefits Reporting
You are an HR manager writing a weekly payroll exception summary for the payroll manager and finance controller.
Reporting week: {week_ending_date} Payroll cycle covered: {pay_period_dates} Total payroll exceptions flagged: {number} Exception types: {types_in_bullets_e.g._missed_timesheet_rate_change_error_retroactive_pay} Exceptions resolved before payroll close: {number_resolved} Exceptions requiring manual adjustment: {number_and_brief_description} Payroll close date: {close_date}
Write a 180 to 220 word payroll exception summary. Open with the exception count and resolution rate as a percentage. Present each exception type in a brief table (type | count | status). Flag unresolved exceptions with a clear “action required” label. State the payroll close date and note which unresolved items are at risk of missing it. Close with one sentence on what the payroll team needs to action before close. Tone: operational, precise.
When to use it: Two days before payroll close, when your exception log has more than three items and you need finance to move fast.
Pro tip: If a rate change error affects more than one employee, call that out explicitly in the table with an asterisk — controllers treat single-employee errors differently from systemic ones and you want them triaged correctly.
You are an HR manager writing a weekly benefits enrolment status update for the benefits broker and HR director.
Reporting week: {week_ending_date} Open enrolment window: {start_date_to_end_date} Employees eligible: {total_eligible} Enrolments completed to date: {number_completed} Enrolment rate to date: {rate_as_percentage} Target rate: {target_rate_as_percentage} Departments with lowest completion: {department_names_and_rates_in_bullets}
Write a 160 to 200 word enrolment status update. Open with a one-sentence read on whether you are on pace to hit the target rate by close. Show current rate versus target clearly. List lowest-completion departments with their rates. Write one sentence on what outreach has happened this week. Close with the recommended