For Compensation and Benefits Analysts ·
What you'll accomplish
Use Claude to translate your pay equity regression output into a clear, legally neutral executive summary. Instead of spending 2–3 hours writing language that walks the line between transparency and legal risk, you'll produce a polished first draft in 20 minutes that your legal team can review.
What you'll need
Before opening Claude, compile the key numbers from your analysis. You'll need:
Write these in a plain text list. You'll paste them directly into your Claude prompt.
Go to {{tool:Claude.url}}. Click New Chat. Pay equity narratives contain sensitive data. Use your corporate Claude account if your organization has one, and confirm your data handling policy first.
Start with a short framing message explaining what you need:
I'm a compensation analyst writing a pay equity analysis summary for HR leadership review before it goes to legal.
I need you to help me write a clear, factual, legally neutral executive summary of our findings.
Use precise statistical language but also explain what the numbers mean in plain terms.
Avoid any language that could be read as an admission of liability.
The audience is the CHRO and HR leadership team.
In your next message, paste your findings:
Here are our pay equity analysis results:
Scope: [N] employees analyzed across [company description]
Model: OLS regression
Control variables: [list your variables]
R² = [value]
Unadjusted gaps (before controls):
- Gender: Women earn [X]% less than men
- Race: [Group] earns [X]% less than white employees
Adjusted gaps (after controls):
- Gender: [X]% gap (p=[value])
- Race: [X]% gap (p=[value])
Statistically significant gaps: [yes/no by group]
[Any other findings]
Based on these findings, please draft:
1. A 3-paragraph executive summary (250–350 words) suitable for CHRO review
2. A bullet-point recommendations section (3–5 bullets)
3. A one-sentence "bottom line" finding
Use objective language throughout. Do not speculate about causes of any gaps.
For statistically insignificant gaps, note that they are within statistical noise.
What you should see: A structured draft with an introduction, findings, and recommendations, ready for your edits and legal review.
Review the draft for accuracy. Check that every number matches your actual output. Adjust any language that feels too strong or too weak for your company's situation. Then send to your legal team before distributing to HR leadership.
Troubleshooting: If Claude's language feels too definitive about cause (e.g., "this demonstrates pay discrimination"), add: "Rewrite to remove any language suggesting cause. Note only that the gap exists and remains unexplained by the model's control variables."
For a finding with a significant gap: "Rewrite the gender pay gap finding to present the [X]% adjusted gap factually, note its statistical significance (p=[value]), and indicate it warrants further investigation without implying it is necessarily the result of intentional discrimination."
For a finding with no significant gap: "Write a 2-sentence finding for a pay group where the adjusted gap is [X]% with p=[value]. The gap is not statistically significant. Explain what this means in plain language for a non-statistician executive."
For the recommendations section: "Based on an adjusted gender pay gap of [X]% (statistically significant), write 3–4 recommendations for the CHRO. Focus on process improvements (job evaluation consistency, manager training, offer approval processes) rather than specific remediation amounts."