These prompts are for HR managers who need a compensation benchmarking report, pay equity brief, or salary adjustment memo drafted today — not next week. Paste one into ChatGPT or Claude, swap the variables, and you have a finished document ready to review and send.
These prompts pair well with Jasper AI for HR Managers-specific tone control, or Copy.ai for fast iteration.
Writing the Core Benchmarking Report
You are an HR compensation analyst writing an internal compensation benchmarking report for leadership review.
Job family being benchmarked: {job_family} Number of roles included: {role_count} Market data sources used: {data_sources — e.g. Radford, Mercer, internal salary survey} Geographic scope: {geography — e.g. US national, metro New York, EMEA} Benchmark percentile target: {target_percentile — e.g. 50th, 75th} Current average internal pay vs. market midpoint: {internal_vs_market — e.g. 8% below market} Audience: {audience — e.g. CHRO and CFO}
Write a 500 to 600 word compensation benchmarking report. Open with a one-paragraph executive summary that states the key finding in plain numbers. Follow with a section on methodology that names the data sources and explains the percentile target. Add a section on findings that compares internal pay to market by level (entry, mid, senior). Close with a recommendations section that proposes specific pay range adjustments and an implementation timeline. Use formal, data-forward prose throughout.
When to use it: First working draft before your quarterly comp review meeting — when leadership wants numbers and context before they’ll approve a budget conversation.
Pro tip: If your {data_sources} mix multiple survey vintages, note the survey date in the methodology section or the CFO will ask. Add a one-line caveat about data currency before you paste in the output.
You are an HR manager writing a compensation benchmarking summary for a single critical role that is hard to fill.
Role title: {role_title} Department: {department} Current salary range for this role: {current_range — e.g. $95,000–$115,000} Market rate at 50th percentile: {market_p50} Market rate at 75th percentile: {market_p75} Data source: {data_source} Business case context: {business_context — e.g. two failed searches in 12 months, 3 open reqs}
Write a 300 to 350 word internal briefing document. Lead with the gap between the current range and the market 75th percentile, expressed as a dollar figure and a percentage. Explain why the 75th percentile is the right target given the business context. Close with a single, specific salary range recommendation the hiring manager can take to finance for approval. No jargon. Write as if the reader has 90 seconds.
When to use it: When a role has missed two or more hire cycles and you need a one-pager that gets a budget exception approved fast.
Pro tip: Anchoring to the 75th rather than the 50th needs justification — your {business_context} variable is the load-bearing argument. Be specific: “two failed searches” is stronger than “competitive market.”
You are a senior HR analyst writing the findings section of an annual compensation benchmarking report covering an entire department.
Department name: {department_name} Number of employees in scope: {headcount} Roles benchmarked: {role_list — comma separated} Market data source: {data_source} Overall department pay position vs. market median: {overall_position — e.g. 5% below} Roles most at risk: {at_risk_roles} Company pay philosophy: {pay_philosophy — e.g. pay at 50th percentile for base, 75th for total cash}
Write a 400 to 500 word findings section. Organise it as three clearly labelled subsections: (1) Overall Pay Position, (2) Roles with the Largest Market Gaps, and (3) Alignment with Pay Philosophy. Use precise numbers throughout. Do not include recommendations — this section is findings only. Write for a compensation committee that will use this to decide on merit budget.
When to use it: When you’re splitting a large report into sections and need the findings section complete before the recommendations meeting the next morning.
Pro tip: Keep recommendations out of this section even if you have them. Mixing findings and recommendations in the same block gives committee members an easy reason to debate the methodology instead of the numbers.
You are an HR compensation manager writing the executive summary of a company-wide compensation benchmarking report.
Company size: {company_size — e.g. 800 employees} Benchmark year: {benchmark_year} Total roles benchmarked: {total_roles} Overall pay position vs. market: {overall_pay_position — e.g. 6% below median} Number of employees below market midpoint: {below_midpoint_count} Estimated cost to bring all below-midpoint employees to midpoint: {remediation_cost} Board-level audience: {yes_or_no}
Write a 200 to 250 word executive summary. Open with the single most important finding. State the scope in one sentence. Present the below-midpoint headcount and remediation cost as the core business risk. Close with one sentence on the recommended next step. Use plain language. No bullet points. No sub-headers. This should read as a single confident statement of the situation.
When to use it: When you need to attach a cover summary to a full report going to the board or a CEO who will not read past page one.
Pro tip: The remediation cost figure is the number that makes executives pay attention. If you don’t have a precise figure, use a range — but never omit it. A blank where the cost should be reads as unprepared.
You are an HR manager writing a methodology section for a compensation benchmarking report being shared with employees as part of a pay transparency initiative.
Data sources used: {data_sources} Survey participation: {survey_participation — e.g. Radford Q1 2026, 1,200 companies} Job matching approach: {job_matching — e.g. matched to survey job codes by scope and output, not title} Benchmark percentile: {benchmark_percentile} How often data is refreshed: {refresh_cycle — e.g. annually each Q1} Employee audience: {audience_description — e.g. individual contributors across all departments}
Write a 250 to 300 word methodology section written for employees, not HR professionals. Avoid survey jargon. Explain what benchmarking is in one sentence. Explain how jobs are matched to market data. Explain what the percentile target means in practical terms. Close by stating how often the data is updated. The tone should be transparent and direct, not defensive.
When to use it: When your company has committed to pay transparency and employees are asking how their ranges are set — before someone posts a confused question on Slack.
Pro tip: The job matching explanation is where employees lose trust. If your methodology uses scope and output rather than job titles, say that clearly. “We matched by what you do, not what your title says” lands better than “we applied a survey-code alignment process.”
Pay Equity Analysis Briefs
You are an HR compensation analyst writing an internal pay equity analysis brief for the CHRO.
Analysis scope: {scope — e.g. all US employees at Manager level and above} Protected characteristics analysed: {characteristics — e.g. gender, race/ethnicity} Methodology: {methodology — e.g. regression-adjusted mean comparison controlling for level, tenure, and performance rating} Key finding — gender gap: {gender_gap — e.g. women earn 3.2% less than men after controls} Key finding — race/ethnicity gap: {race_ethnicity_gap} Number of employees flagged for adjustment: {flagged_count} Estimated cost to remediate: {remediation_cost}
Write a 400 to 450 word pay equity analysis brief. Open with the methodology in two sentences so the CHRO can defend it if asked. Present gender and race/ethnicity findings in separate paragraphs with precise figures. State the number of employees flagged and the remediation cost. Close with a recommended approval step and timeline. Tone is factual and measured. Do not editorialize or use language that implies legal liability.
When to use it: After running your annual pay equity regression — before you brief the CHRO verbally, so she has something to read beforehand and the meeting covers decisions, not explanations.
Pro tip: “Do not editorialize” is doing real work in this prompt. AI models tend to add phrases like “this represents a significant disparity” — edit those out before sharing. Let the number speak.
You are an HR manager writing a one-page pay equity summary for department heads ahead of their annual merit cycle.
Department: {department_name} Department head name: {dept_head_name} Number of employees in the department: {headcount} Number flagged with a pay equity gap: {flagged_count} Average gap for flagged employees: {average_gap — e.g. 4.1% below peers at same level} Budget allocated for equity adjustments: {equity_budget} Deadline to submit adjustments: {deadline}
Write a 300 to 350 word document addressed to the department head by name. Explain what the flagged gap means without using statistical jargon. Tell them exactly how many of their reports are affected. State the budget available and the deadline. Give them one concrete instruction for what to do next. Tone is direct but not alarming — this is information they need to act on, not a warning.
When to use it: When you’re distributing pre-populated merit worksheets and need an accompanying note that gets managers to actually use the equity budget line instead of ignoring it.
Pro tip: Name the department head in the prompt and in the output. A memo that starts “Dear Sarah” gets read. “Dear Department Head” gets skimmed and filed.
You are a compensation manager writing an email to a department head explaining that one of their direct reports has been identified for a pay equity adjustment outside the merit cycle.
Department head name: {dept_head_name} Employee role (not name): {role_title} Reason for off-cycle adjustment: {reason — e.g. regression analysis identified a statistically significant gap vs. peers at the same level} Adjustment amount or percentage: {adjustment} Effective date: {effective_date} Action required from the manager: {manager_action — e.g. no action needed / please confirm you’ve briefed the employee}
Write a 200 to 250 word email. Subject line included. Open by stating the purpose in the first sentence. Explain the basis for the adjustment in plain language without legal hedging. State the amount and effective date. State what the manager needs to do. Close by offering to answer questions. Do not use the employee’s name in the email.
When to use it: When equity adjustments are being processed in payroll and the manager needs a heads-up before the employee sees a change in their pay stub.
Pro tip: Omitting the employee name is intentional — this email often gets forwarded or printed. Keep the name in the payroll system, not in the email chain. Adjust the {manager_action} variable carefully: if the manager shouldn’t discuss this yet, say so explicitly.
You are a senior HR analyst drafting the pay equity section of an annual report to be shared publicly on the company’s careers page.
Company name: {company_name} Analysis year: {analysis_year} Scope of analysis: {scope — e.g. all full-time employees globally} Unadjusted gender pay gap: {unadjusted_gap — e.g. 18% median pay gap} Adjusted gender pay gap (controlled for role and level): {adjusted_gap — e.g. 1.4%} Actions taken this year: {actions_taken — e.g. equity adjustment pool of $1.2M, updated job architecture} Next commitment: {next_commitment}
Write a 350 to 400 word pay equity statement. Lead with the adjusted figure and explain why the unadjusted and adjusted numbers differ — do not bury the unadjusted figure. Present the actions taken this year with specifics. Close with the next commitment and its timeline. Tone is transparent, confident, and precise. Avoid corporate language like “fostering an inclusive culture” — stick to what was actually done and what the numbers show.
When to use it: During annual report season when the communications team asks for the pay equity section and you need a draft that’s accurate before legal reviews it.
Pro tip: The explanation of adjusted vs. unadjusted is the section most likely to get rewritten by comms into something vague. Lock it down with specific numbers in your draft — it’s harder to water down a sentence with three figures in it.
You are an HR compensation manager writing a talking-points document for an HR business partner who needs to explain the company’s pay equity methodology to a skeptical employee.
Employee’s question or concern: {employee_concern — e.g. “I looked up my role on Glassdoor and I’m underpaid compared to colleagues”} HRBP name: {hrbp_name} Company’s pay equity process: {equity_process — e.g. annual regression analysis controlling for level, tenure, function} Most recent analysis date: {analysis_date} Whether the employee has been flagged: {flagged — yes / no / cannot_confirm} Tone needed: {tone — e.g. empathetic and direct / formal and careful}
Write a 300 to 350 word talking-points document — not a script. Organise it as four numbered points the HRBP can reference in the meeting. Each point should be one to three sentences covering: (1) acknowledging the concern, (2) explaining how the analysis works, (3) what the analysis found or cannot confirm, (4) what the next step is. Underneath each point, add one “if pushed” response in italics for a follow-up question.
When to use it: Before an HRBP walks into a difficult one-on-one where an employee has done their own market research and believes they are underpaid.
Pro tip: The “if pushed” rows are the most valuable part of this output. HRBPs often prepare for the opening question but not the follow-up. Review those rows carefully — if {flagged} is “cannot confirm,” the “if pushed” response needs to hold firm without sounding evasive.
Salary Range Design and Adjustment Memos
You are a compensation manager writing an internal memo proposing a salary range adjustment for a specific job level.
Job level affected: {job_level — e.g. Senior Engineer, Level 4} Current salary range: {current_range — e.g. $130,000–$160,000} Proposed new range: {proposed_range} Market data source: {data_source} Percentile target: {percentile_target} Number of employees whose pay falls below the new range minimum: {below_minimum_count} Cost to bring those employees to the new minimum: {remediation_cost} Approver: {approver — e.g. CFO, Compensation Committee}
Write a 350 to 400 word approval memo. Address it to the approver. Open with the proposed change and its rationale in two sentences. Present the market data in the second paragraph. Quantify the employee impact and cost in the third paragraph. Close with a request for approval and a proposed effective date. Formal tone. No bullet points. Write as if this will be filed with board materials.
When to use it: When you need finance or the comp committee to approve a range update before the next merit cycle loads into the HRIS.
**