DocsUse CasesHR & People

HR & People

Use Cases by Department · Beginner Friendly

Automate the Entire Onboarding Journey

hronboarding

The Problem: HR teams spend 15-20 hours per new hire creating personalized documents and training plans.

1

Create Master Prompt

Select 'HR' category in Prompt Architect → Persona: 'Senior Onboarding Specialist'.

2

Define Variables

Use {{employee_name}}, {{role}}, and {{start_date}} for customization.

3

Batch Process

Run for 10+ hires in the Lab to generate welcome letters and 90-day plans instantly.

Best Practices

Start automate the entire onboarding journey with a small live pilot and one owner per review lane.

Track manual rewrite rate and cycle time per case from day one.

Bake this control into your checklist: jurisdiction and policy effective date are explicitly referenced

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: publishing drafts without naming accountable reviewer.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Automate the Entire Onboarding Journey Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Use manager-facing language in a separate section from legal-facing rationale.

Draft & Update Company Policies

hrpolicy

The Problem: Keeping policies aligned with changing regulations is slow and error-prone.

1

Upload Standards

Store the latest labor laws in the Vault.

2

Gap Analysis

AI compares your current policy against Vault documents and suggests updates.

Best Practices

Start draft & update company policies with a small live pilot and one owner per review lane.

Track manager clarity score and policy adherence rate from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: publishing drafts without naming accountable reviewer.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Draft & Update Company Policies Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Use manager-facing language in a separate section from legal-facing rationale.

Build Role-Specific Training Programs

hrtraining

The Problem: L&D teams struggle to personalize training for dozens of different departments.

1

Competency Mapping

AI generates a skill matrix for a specific role.

2

Content Generation

Generate micro-learning modules and quizzes based on that matrix.

Best Practices

Start build role-specific training programs with a small live pilot and one owner per review lane.

Track manager clarity score and policy adherence rate from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: overwriting prior decisions with no changelog.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Build Role-Specific Training Programs Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Store one approved ‘golden’ output per workflow and compare every new draft against it.

AI-Assisted Feedback Generation

hrperformance

The Problem: Managers write vague, inconsistent reviews that lack actionable steps.

1

Brain Dump

Manager inputs raw observations about an employee.

2

Bias Check

AI scans for gendered language or attribution bias before formatting the final review.

Best Practices

Start ai-assisted feedback generation with a small live pilot and one owner per review lane.

Track manual rewrite rate and policy adherence rate from day one.

Bake this control into your checklist: jurisdiction and policy effective date are explicitly referenced

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: generic templates that ignore role or location context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: AI-Assisted Feedback Generation Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Use manager-facing language in a separate section from legal-facing rationale.

Analyze Pulse Surveys & Engagement

hrsentiment

Problem: HR teams can't manually process thousands of open-ended survey comments monthly.

1

Export Comments

Upload raw survey text from your engagement platform.

2

Theme Tagging

AI categorizes comments (e.g., 'Work-Life Balance', 'Remote Tools').

3

Action Extraction

Extract the #1 suggested improvement for each department.

Best Practices

Start analyze pulse surveys & engagement with a small live pilot and one owner per review lane.

Track cycle time per case and manager clarity score from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: overwriting prior decisions with no changelog.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Analyze Pulse Surveys & Engagement Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Treat every first month rollout as calibration, not final process design.

Identify Future Leaders

hrtalent

Problem: Succession planning is often reactive and misses high-potential 'quiet' contributors.

1

Growth Scan

AI analyzes 2 years of performance data to detect high skill-acquisition velocity.

2

9-Box Mapping

Automatically populate a 9-box grid to pinpoint 'Ready Now' candidates for VP roles.

Best Practices

Start identify future leaders with a small live pilot and one owner per review lane.

Track policy adherence rate and manager clarity score from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: publishing drafts without naming accountable reviewer.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Identify Future Leaders Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Use manager-facing language in a separate section from legal-facing rationale.

FMLA & Regional Leave Compliance

hrleave

Problem: HR spends hours checking overlapping state and federal leave eligibility laws.

1

Policy Sync

Upload FMLA and regional leave law documents to the Vault.

2

Calculated Eligibility

AI determines exact weeks of protected leave based on employee tenure and local law.

Best Practices

Start fmla & regional leave compliance with a small live pilot and one owner per review lane.

Track manual rewrite rate and policy adherence rate from day one.

Bake this control into your checklist: jurisdiction and policy effective date are explicitly referenced

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: overwriting prior decisions with no changelog.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: FMLA & Regional Leave Compliance Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Store one approved ‘golden’ output per workflow and compare every new draft against it.

Audit Job Postings & Promotions for Bias

hrdei

Problem: Hidden bias in job descriptions and promotion criteria prevents team diversity.

1

Coded Language Scan

AI analyzes job posts for gendered or culturally alienating language.

2

Promotion Review

Scan promotion justification text to ensure consistent criteria across different demographics.

Best Practices

Start audit job postings & promotions for bias with a small live pilot and one owner per review lane.

Track manager clarity score and cycle time per case from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: generic templates that ignore role or location context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Audit Job Postings & Promotions for Bias Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Treat every first month rollout as calibration, not final process design.

Automate Market Salary Analysis

hrcompensation

Problem: HR teams manually compare internal data against 5+ survey providers, taking weeks.

1

Normalize Titles

AI maps internal 'Senior Dev' to Radfords/Mercer standard job codes.

2

Market Gap analysis

Identify employees currently +/- 15% from the market median for immediate review.

Best Practices

Start automate market salary analysis with a small live pilot and one owner per review lane.

Track manual rewrite rate and policy adherence rate from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: publishing drafts without naming accountable reviewer.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Automate Market Salary Analysis Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Use manager-facing language in a separate section from legal-facing rationale.

Mitigate Legal Risk in Separations

hrlegalrisk

Problem: Rushed terminations without proper documentation leading to high litigation costs.

1

Compliance Scan

AI audits termination reasons against state-specific 'At-Will' and 'Protected Class' laws.

2

Documentation Audit

Ensure all PIPs and performance warnings are present in the Vault before final approval.

Best Practices

Start mitigate legal risk in separations with a small live pilot and one owner per review lane.

Track manager clarity score and cycle time per case from day one.

Bake this control into your checklist: approval path to HRBP or legal is visible for escalations

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: publishing drafts without naming accountable reviewer.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Mitigate Legal Risk in Separations Owner: People Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Store one approved ‘golden’ output per workflow and compare every new draft against it.

Academy v4.0 · Interactive Documentation · Beginner Mode