Free AI Training / 4 ChatGPT Prompts Every HR Manager Needs (RCTFC Framework)

4 ChatGPT Prompts Every HR Manager Needs (RCTFC Framework)

Two HR managers get handed the same impossible hiring request on a Monday morning. One's still staring at a blank job posting by lunch. The other already has it drafted, reviewed, and posted. This lesson hands you the exact framework — RCTFC — to turn ChatGPT from a generic-answer machine into a tool that writes job postings, builds interview guides, drafts performance reviews, and scripts the hard conversations.

Watch on YouTube →Book a Free Strategy Call →

Overview

HR work is full of writing that has to be right the first time: a job posting that attracts the right candidates, interview questions that make a panel consistent, a performance review that survives calibration, a difficult conversation that actually opens instead of making everyone more nervous. RCTFC — Role, Context, Task, Format, Constraints — turns ChatGPT into a tool that produces each of these specifically enough to send as-is. This guide walks through four real HR workflows built on that framework.

What You'll Learn

Understand the RCTFC prompting framework and why each of its five parts matters
Write a complete, publishable job posting from a hiring manager's rough notes
Build a structured behavioral interview guide that keeps a panel consistent
Draft a performance review narrative grounded in specific accomplishments, not vague praise
Script the opening of a difficult conversation without sounding harsh or hedging

Use Case 1: The Job Requisition

A hiring manager's three bullet points aren't a job posting yet, and turning them into one usually means writing around vague team notes on a deadline. This prompt sets the role as a recruiter who writes postings that attract the right candidates, feeds in the manager's actual notes — team size, must-have skills, salary band — and asks for a complete, publish-ready posting. The constraint against inflated jargon like "rockstar" and requiring the salary band stated plainly is what makes this read like an actual open role at an actual company, not a template. That's the posting that goes live the same day instead of getting rewritten twice first.

Real hiring manager notes — team size, specific must-have skills — keep the posting from reading generic
Banning inflated jargon like "rockstar" or "ninja" is a small constraint with an outsized effect
Stating the salary band plainly instead of "competitive" is what candidates actually want to see

Example Prompt

💡 Click "Copy Prompt" below to copy this prompt directly to your clipboard—no typing needed.

Role: You are a recruiter who writes job postings that attract the right candidates for the role. Context: Hiring manager's notes: team is Growth Marketing (6 people), must-have skills are B2B SaaS experience, paid social, and campaign reporting, salary band is $85,000-$105,000, role is hybrid (3 days in office). Task: Write a complete job posting ready to publish. Format: A short intro paragraph, then a Responsibilities section, then a Requirements section. Constraints: No inflated jargon like "rockstar" or "ninja." State the salary band plainly, not "competitive."

This reads like an actual open role at an actual company — that's what goes live today instead of sitting in drafts for a rewrite.

Use Case 2: The Interview Guide

When three people interview the same candidate and none of them ask the same things, the panel isn't actually evaluating consistently — everyone's just running their own favorite questions. This prompt builds a structured guide instead: five behavioral questions mapped to the role's actual top competencies, each with a note on what a strong answer sounds like. The constraint against yes/no questions and hypothetical brainteasers dressed up as behavioral is what keeps every question genuinely diagnostic. That's what makes the panel consistent — every interviewer scoring the same thing, instead of comparing notes on completely different conversations afterward.

Mapping questions to the role's actual top competencies keeps the panel evaluating the same things
A note on what a strong answer sounds like turns the guide into a real scoring tool
Banning yes/no and brainteaser-style questions keeps every question genuinely behavioral

Example Prompt

💡 Click "Copy Prompt" below to copy this prompt directly to your clipboard—no typing needed.

Role: You are an HR partner who builds structured interview guides for hiring panels. Context: Role is Growth Marketing Manager, top competencies are ownership of ambiguous problems and cross-functional communication, this is the second-round panel interview. Task: Write five behavioral interview questions mapped to those two competencies. Format: Each question followed by a one-line note on what a strong answer sounds like. Constraints: No yes/no questions. Nothing that's actually a hypothetical brainteaser dressed up as behavioral.

This is what makes the panel consistent — every interviewer scoring the same thing instead of running their own favorite question.

Use Case 3: The Performance Review

Twelve performance reviews due Friday, each one needing to hold up in a calibration meeting, is exactly the kind of task where "team player, great attitude" starts creeping in out of sheer time pressure. This prompt forces the alternative: a review narrative grounded in one specific accomplishment and number, with the growth area named just as concretely. The constraint that every claim must be backed by a specific project or number is what makes this review survive calibration — it's built on things that actually happened, not vague praise a manager could have written about anyone on the team.

One specific, numbers-backed accomplishment beats a paragraph of general praise
Naming the actual growth area concretely is as important as naming the win
Every claim tied to a project or number is what makes a review defensible in calibration

Example Prompt

💡 Click "Copy Prompt" below to copy this prompt directly to your clipboard—no typing needed.

Role: You are a manager writing a performance review grounded in specific accomplishments. Context: Employee is Maria, core competency is project ownership, she led the Q2 platform migration two weeks ahead of schedule and her growth area is delegating rather than doing everything herself. Task: Write a review narrative for the "project ownership" competency. Format: One paragraph of evidence, then one sentence of forward-looking feedback. Constraints: Every claim must be backed by a specific project or number. No vague praise like "team player" or "great attitude."

This is the review that survives the calibration meeting, because it's built on things that actually happened.

Use Case 4: The Difficult Conversation

A hard conversation on the calendar tends to get its opening line rewritten five times, because most managers know the difference between a conversation that lands and one that just makes everyone more nervous, but can't always find the words under pressure. This prompt writes only the opening — three or four sentences the manager could actually say out loud — grounded in the specific pattern, the business impact, and what's already been raised before. The constraint against corporate hedge words like "circle back," and naming the specific behavior rather than a character judgment, is what keeps this direct without being harsh. That's the version that actually opens the conversation instead of making everyone more nervous.

Writing only the opening — not the whole meeting — keeps the script usable and natural
Naming the specific behavior instead of a character judgment keeps the tone fair
Banning hedge words like "circle back" forces directness without becoming harsh

Example Prompt

💡 Click "Copy Prompt" below to copy this prompt directly to your clipboard—no typing needed.

Role: You are an HR partner coaching a manager through a difficult performance conversation. Context: Employee has missed three consecutive sprint deadlines, the business impact is the team's Q3 release is now at risk, and this was raised informally once already, two weeks ago. Task: Write an opening script for the conversation, not the whole meeting. Format: Three to four sentences the manager could actually say out loud. Constraints: Direct but not harsh. No corporate hedge words like "circle back." Name the specific behavior, not a character judgment.

This is the version that actually opens the conversation instead of making everyone more nervous — direct about the behavior, not a judgment about the person.

Summary

RCTFC doesn't replace the judgment calls only an HR manager can make — reading the room when someone's about to walk, knowing which battles to fight with leadership — it clears out everything sitting between the blank doc and the thing you'd actually send. The four prompts in this guide cover the highest-stakes writing in HR: the requisition, the interview guide, the review, and the difficult conversation. Each follows the same five-part structure, so it transfers directly from one task to the next.

Next Steps

Run the job requisition prompt on the next req that lands in your inbox, using your hiring manager's actual notes instead of the example above. As the hiring process moves forward, the interview guide, review, and difficult-conversation prompts carry the same structure straight through.