HR & RecruitingDecision Doc & RFC#HR#decision#ATS

HR / Hiring Decision 1-Pager · ATS Switch / Process Change

Common HR 1-pagers: ATS switch / interview process change / 90-day plan revamp — capture the judgment so leadership decides async.

Pain addressed · HR decisions get stuck in 'all-hands proposal + endless meetings' loops. A structured 1-pager pushes them through in 3 days.

HR / Hiring Decision 1-Pager · ATS Switch / Process Change

Prompt·Advanced
Also available in 中文 →
You're my HR decision-doc partner. I have an org or hiring-process decision to push. Help me 1-page it for async leadership sign-off.

# Context
- Decision type: {decision_type} (ATS switch / interview-process change / onboarding revamp / comp band update / etc.)
- Decision title (≤ 15 words): {decision_title}
- Options + preferred: {options}
- Supporting HR data (time-to-hire / cost-per-hire / candidate NPS / employee churn): {hr_data}
- Approvers (usually People lead + CFO or CEO): {approvers}
- Cost of no decision: {no_decision_cost}

# 1-pager (≤ 450 words)

## 1. TL;DR (40 words)
"I recommend X · impact on time-to-hire / cost-per-hire / employee experience metric Y · need yes/no by [date]."

## 2. Status + trigger (60 words)
Why change now. 1-2 HR metrics (time-to-hire up 20% / candidate NPS down 15 points / etc.).

## 3. Options table (100 words)
| Option | Cost (annual) | Implementation effort | Metric impact | Change risk | My take |
- Change risk = internal pushback / candidate experience shift / data migration cost
- Cost includes license + implementation + internal training time

## 4. Recommendation + 1 trade-off (80 words)
"I recommend X because [2 reasons] but I acknowledge [1 trade-off, e.g. 6-month ATS migration temporarily drops hiring throughput 15%]."

## 5. Stakeholder impact map (60 words)
- Candidates: experience shift
- Hiring managers: operational change
- HR team: workload change
Name the most likely pushback per group.

## 6. Decision action + cost of no decision (60 words)
- ✅ → kick-off + first milestone date
- ❌ → 30-second core objection
- No decision → specific date + consequence

# Boundaries
- HR metrics must be from real internal data, not "industry roughly".
- Change risk must be specific (who pushes back + why).
- Total ≤ 450 words.
Saves ~50 min per use

Open directly on your favourite AI

One click copies the prompt and opens the platform in a new tab — just paste (⌘/Ctrl + V).

Workflow · 5 steps

  1. 1

    Pull your real ATS data, candidate NPS, time-to-hire. If you don't have a system, dump the last 2 weeks manually.

  2. 2

    Run in Claude or Kimi. Fill all 6 placeholders.

  3. 3

    Section 5 stakeholder map is where HR decisions usually fail — name who specifically will push back and why.

  4. 4

    Section 4 trade-off must be honest. e.g. ATS swap = 6 months of degraded hiring throughput.

  5. 5

    Send to leadership with a 72h default-yes rule. Schedule a parallel FYI broadcast to affected stakeholders.

Verify before you ship

AI's "almost right" is the #1 pain. Tick these off so reviewers can't find the obvious holes. (Checkbox state stays local — we don't track it.)

Done 0 / 5 checks

Why this prompt works

This prompt isn't a generic “write me a Decision Doc & RFC”. It folds in the concrete context a HR & Recruiting actually faces (target reader, info density, deliverable format). LLMs deliver an order-of-magnitude better answer when they get role × scenario × constraints together — they can make the right tradeoffs about what to spotlight and what to cut.

When to use

Best moment: you know roughly that you need to do a Decision Doc & RFC, but you're stuck on “how do I even ask the AI?” Muscle memory has no template. Copy this card, tweak 2-3 fields per the workflow, and get a first revisable draft in 30 seconds.

Common pitfalls

  • Send without tweaking placeholders · the draft reads as default-GPT and your reviewer spots it in 3 seconds.
  • Skip the verify checklist · “almost right” failures usually hide in a thing you assumed the model handled but it didn't.
  • Stop after the first answer · a single follow-up like “make section X tighter / more formal” usually pushes a 70 → 90.

Variants & extensions

Want to use this card more aggressively? Three extensions:

  • Swap languages: both EN/ZH prompts ship in the card — use the EN version when shipping to a Western audience.
  • Swap platforms: the same prompt has slightly different taste on ChatGPT / Claude / Kimi. The recommended-platform pill marks the best fit.
  • Stack the checklist: paste the verify checklist back into the chat and ask the AI to self-audit — error rate drops sharply.
PromptDeck Pro Bundle

Want 25 more prompts like this one?

Get the full 50-card Pro deck — multi-step chains, vertical variants, lifetime updates.

  • 50 prompts · 25 free + 25 advanced multi-step chains
  • PDF printable + Notion template
  • Lifetime updates · ~5 new prompts a month, auto-synced
  • Dual-language · EN/CN + 5 China-exclusive scenarios
Get Pro · $9 lifetime14-day refund · no questions · powered by Lemon Squeezy

Related cards