Choose by the output you need to make

ChatGPT Prompts for HR and Recruiters

HR teams and recruiters writing role, interview, onboarding, and employee communication copy.

Where ChatGPT helps this role

Turn rough notes into a reviewable asset for a candidate, employee, hiring panel, or HR reviewer.
Convert a recurring hr and recruiters workflow into a reusable prompt sequence.
Ask ChatGPT for clarifying questions before committing to tone, format, or evidence.
Create a quick version for routine work and a deeper version for high-stakes work.
Review an existing answer against privacy, accuracy, and role-specific constraints.
Rewrite output for a different audience without changing the underlying facts.
Build a checklist that makes the human review faster and less subjective.

Main Risks

Prompts must support fair review and human judgment, not automated employment decisions.
A broad prompt can hide missing source material, so hr and recruiters should name the exact evidence before asking for output.
Over-polished wording can make weak assumptions look finished; every page links the prompt to a review step.
Copying the same prompt across tasks weakens results because hr and recruiters need different inputs for planning, review, outreach, and explanation work.

Recommended Workflow

Pick the task page that matches the decision, not just the closest job title.
Prepare the source notes, audience, constraints, and forbidden assumptions before copying a prompt.
Run the prompt once for structure, then run a review prompt against facts, tone, and missing context.
Save the final prompt with the human review checklist so the workflow can be reused without becoming automatic.

Choose the first task by situation

Start with Write job descriptions when the user has source notes but does not yet know the right output structure, then move to Prepare interview questions or Build interview scorecards only after the audience and review owner are clear.

Choose by situation

Choose Write job descriptions when the main problem is shaping raw context into something a candidate, employee, hiring panel, or HR reviewer can inspect.
Choose Prepare interview questions when the user already has a first version and needs the next artifact in the same hr and recruiters loop.
Choose Build interview scorecards when the risk is quality control, review consistency, or a clearer handoff to another person.
Open the role guide when the user cannot name the task yet and needs to decide whether to create, revise, review, or sanitize context first.

Avoid starting with

Do not start from a broad role prompt when the user already knows the concrete task.
Do not start from a writing prompt when the missing piece is source material or reviewer approval.
Do not reuse a hr and recruiters prompt across unrelated tasks without changing inputs, constraints, and review checks.

HR and Recruiters pages are organized by the decision a person is trying to make, not by a long list of clever prompt phrases. The role page should help the user pick the first useful task, then the task page should carry the details: source material, variable fill, example, stronger prompt, and human review boundary.

Pick the workflow by decision

Write job descriptions

Use when the next decision is the shape, review path, or reuse rule for a job description.

Write job descriptions needs role outcomes, responsibilities, requirements, compensation range, and hiring process; its review lens is job description quality, role outcomes and required skills, and fairness and policy fit, not a generic writing pass.

Prepare interview questions

Use when the next decision is the shape, review path, or reuse rule for interview questions.

Prepare interview questions needs role scorecard, competencies, level, format, and fairness constraints; its review lens is interview questions quality, competency signal and behavior probe, and fairness and policy fit, not a generic writing pass.

Build interview scorecards

Use when the next decision is the shape, review path, or reuse rule for a product scorecard.

Build interview scorecards needs role criteria, rating levels, evidence examples, and interviewer notes; its review lens is product scorecard quality, rating anchors and evidence examples, and fairness and policy fit, not a generic writing pass.

Plan onboarding

Use when the next decision is the shape, review path, or reuse rule for an onboarding plan.

Plan onboarding needs new hire role, first-week goals, tools, meetings, and success signals; its review lens is onboarding plan quality, first-week milestones and tool access, and fairness and policy fit, not a generic writing pass.

Write employee surveys

Use when the next decision is the shape, review path, or reuse rule for an employee survey.

Write employee surveys needs research goal, audience, sensitive topics, scale, and anonymity limits; its review lens is employee survey quality, question neutrality and anonymity, and fairness and policy fit, not a generic writing pass.

Write performance review prompts

Use when the next decision is the shape, review path, or reuse rule for performance review prompts.

Write performance review prompts needs role expectations, examples, growth areas, goals, and HR policy; its review lens is performance review prompts quality, evidence examples and growth goal, and fairness and policy fit, not a generic writing pass.

Write policy language

Use when the next decision is the shape, review path, or reuse rule for policy language.

Write policy language needs policy goal, audience, legal review notes, examples, and escalation path; its review lens is policy language quality, plain-language rule and examples, and fairness and policy fit, not a generic writing pass.

Write rejection emails

Use when the next decision is the shape, review path, or reuse rule for a rejection email.

Write rejection emails needs candidate stage, tone, relationship, feedback policy, and next opportunity; its review lens is rejection email quality, candidate stage and respectful tone, and recipient-safe next step, not a generic writing pass.

Open a prompt workbench

Review-first run

Write Job Descriptions: avoid the wording fair, job-related, and reviewed

A job descriptions page for people who need a job description, not loose advice: source prep, examples, prompts, and review steps. job descriptions stays close to a public role post where vague wording can create screening risk, which keeps ChatGPT from drifting into generic advice.

Turn role outcomes, responsibilities, requirements, compensation range, and hiring process into a job description for a candidate, employee, hiring panel, or HR reviewer.

Bring first: Need responsibilities, outcomes, requirements, compensation range note, interview process, and inclusive wording check. job description section map with outcome language needs the source note, output shape, and review owner in the same pass. A keeper version should preserve the rough-note signal. a job description should use the note as its source. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.

Prepare interview questions Build interview scorecards Plan onboarding

Ready-to-run path

Prepare Interview Questions: use role scorecard and competencies

Move from a rough interview questions request to interview questions formatted as clear sections, bullets, and a review checklist, using runnable prompts plus reject-if and repair rules. interview questions catches the failure point where interview questions can lose job relevance or fairness boundaries, because that is where polished answers usually fail.

Turn role scorecard, competencies, level, format, and fairness constraints into interview questions for a candidate, employee, hiring panel, or HR reviewer.

Bring first: Need competency groups, behavioral questions, follow-ups, scoring notes, and questions to avoid. Keep job-related and fair. Reviewer approval for prepare interview questions has to compare the first answer with the supplied note. The response should keep the actual request visible through the edit. Start prepare interview questions from the rough request before shaping interview questions. A usable prepare interview questions input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if: Ask for a correction if it ignores the original notes and answers from general knowledge instead.

Write job descriptions Build interview scorecards Plan onboarding

Ready-to-run path

Build Interview Scorecards: turn notes into product scorecard

HR and Recruiters get prompts for interview scorecards that include source context, example inputs, answer grading, and a safe-use review lane. interview scorecards should only be saved after someone can replace polished filler with source-backed lines inside a product scorecard.

Turn role criteria, rating levels, evidence examples, and interviewer notes into a product scorecard for a candidate, employee, hiring panel, or HR reviewer.

Bring first: Need criteria, 1-5 levels, evidence examples, interviewer notes, red flags, and calibration guidance. a candidate, employee, hiring panel, or HR reviewer can be misled by polished wording, so the reviewer check needs to stay visible. The prompt should make the reviewer questions unavoidable. Treat build interview scorecards as first-pass evidence for a product scorecard. Build Interview Scorecards works better when the context is in named fields, because each variable can be checked before copying.
Reject if: Discard the answer if it cannot trace which details came from the source and which details were inferred.

Write job descriptions Prepare interview questions Plan onboarding

Review-first run

Plan Onboarding: work from people-operations workflow where consistency, fairness, and

Use this page when onboarding needs new hire role, first-week goals, tools, meetings, and success signals, a clear output shape, and a review pass before sharing with a candidate, employee, hiring panel, or HR reviewer. onboarding treats first-week plan with owner and success signal as the asset to check, not as decorative output.

Turn new hire role, first-week goals, tools, meetings, and success signals into an onboarding plan for a candidate, employee, hiring panel, or HR reviewer.

Bring first: Need 30-day plan, first week schedule, tools, buddy, manager checkpoints, learning goals, and success criteria. In plan onboarding, the rough note has to lead because role-level advice would flatten the situation. The answer should show which details still need checking. Carry the plan onboarding note into an onboarding plan. For plan onboarding, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and decision checkpoints.
Reject if: Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.

Write job descriptions Prepare interview questions Build interview scorecards

Ready-to-run path

Write Employee Surveys: work from people-operations workflow where consistency, fairness, and

Start the employee surveys run with the working case, then copy prompts that preserve question neutrality, anonymity, scale wording, and actionability and surface source notes, examples, constraints, and reviewer judgment. employee surveys treats survey version with anonymity and scale notes as the asset to check, not as decorative output.

Turn research goal, audience, sensitive topics, scale, and anonymity limits into an employee survey for a candidate, employee, hiring panel, or HR reviewer.

Bring first: Need 10 survey questions, mix scale and open text, anonymity note, sensitive wording review, and reporting caveats. In write employee surveys, the rough note has to lead because role-level advice would flatten the situation. The answer should make the user's constraint hard to miss. Carry the write employee surveys note into an employee survey. For write employee surveys, paste the source as bullets, constraints, and audience notes so the model has enough shape for an employee survey formatted as clear sections, bullets, and a review checklist.
Reject if: Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.

Write job descriptions Prepare interview questions Build interview scorecards

Ready-to-run path

Write Performance Review Prompts: keep review note with example and growth rows sourced

Use this performance review page to turn role expectations, examples, growth areas, goals, and HR policy into performance review prompts with examples, rejection rules, and a human review pass. performance review review starts at the moment where performance reviews can slide from observable work into personality judgment.

Turn role expectations, examples, growth areas, goals, and HR policy into performance review prompts for a candidate, employee, hiring panel, or HR reviewer.

Bring first: Need review prompts for accomplishments, collaboration, growth areas, goals, and manager evidence. Avoid personality judgments. Examples for write performance review prompts help only when they keep the source note visible while shaping review note with example and growth rows. The first pass should name the source details it is using. In write performance review prompts, the supplied note becomes the base for performance review prompts. A usable write performance review prompts input includes what is known, what is uncertain, and what the reviewer must verify.
Reject if: Send it back for revision if it skips examples that sound plausible but cannot be tied back to the user's source.

Write job descriptions Prepare interview questions Build interview scorecards

Review-first run

Write Policy Language: turn notes into policy language

For hr and recruiters handling policy language, this page keeps the source notes, audience, output shape, and reviewer visible in one run. policy language should only be saved after someone can flag legal-review lines and simplify wording without changing the policy intent.

Turn policy goal, audience, legal review notes, examples, and escalation path into policy language for a candidate, employee, hiring panel, or HR reviewer.

Bring first: Need policy sections, employee responsibilities, manager approval, equipment, security, exceptions, and review notes. a candidate, employee, hiring panel, or HR reviewer can be misled by polished wording, so the reviewer check needs to stay visible. The model should not smooth away the missing context. Treat write policy language as first-pass evidence for policy language. Write Policy Language works better when the context is in named fields, because each variable can be checked before copying.
Reject if: Discard the answer if it cannot trace which details came from the source and which details were inferred.

Write job descriptions Prepare interview questions Build interview scorecards

Ready-to-run path

Write Rejection Emails: prep candidate, employee, hiring panel, or HR handoff

This rejection emails workflow helps hr and recruiters copy the right prompt, inspect the answer, and hand off only what the source supports. rejection emails examples stay close to a people-operations workflow where consistency, fairness, and review ownership matter, so the prompt has a real work setting.

Turn candidate stage, tone, relationship, feedback policy, and next opportunity into a rejection email for a candidate, employee, hiring panel, or HR reviewer.

Bring first: Need two rejection email versions, respectful tone, no legal risk, optional future interest line, and feedback-policy boundary. rejection note set with feedback boundary would be weak without the source details, so the evidence has to stay attached. The saved version should keep the one-time details editable. HR and Recruiters should use the note as the base for a rejection email. Before hr and recruiters run this, separate facts, preferences, and limits so the finished answer does not hide assumptions.
Reject if: Do not use the answer if it hides unsupported claims about source notes, examples, constraints, and reviewer judgment or treats uncertainty as fact.

Write job descriptions Prepare interview questions Build interview scorecards

Where to go next

Write job descriptionsWrite job descriptions fits when the next decision is the shape, review path, or reuse rule for a job description. Keep it separate because write job descriptions needs role outcomes, responsibilities, requirements, compensation range, and hiring process; its review lens is job description quality, role outcomes and required skills, and fairness and policy fit, not a generic writing pass.Prepare interview questionsPrepare interview questions fits when the next decision is the shape, review path, or reuse rule for interview questions. Keep it separate because prepare interview questions needs role scorecard, competencies, level, format, and fairness constraints; its review lens is interview questions quality, competency signal and behavior probe, and fairness and policy fit, not a generic writing pass.Build interview scorecardsBuild interview scorecards fits when the next decision is the shape, review path, or reuse rule for a product scorecard. Keep it separate because build interview scorecards needs role criteria, rating levels, evidence examples, and interviewer notes; its review lens is product scorecard quality, rating anchors and evidence examples, and fairness and policy fit, not a generic writing pass.Plan onboardingPlan onboarding fits when the next decision is the shape, review path, or reuse rule for an onboarding plan. Keep it separate because plan onboarding needs new hire role, first-week goals, tools, meetings, and success signals; its review lens is onboarding plan quality, first-week milestones and tool access, and fairness and policy fit, not a generic writing pass.Write employee surveysWrite employee surveys fits when the next decision is the shape, review path, or reuse rule for an employee survey. Keep it separate because write employee surveys needs research goal, audience, sensitive topics, scale, and anonymity limits; its review lens is employee survey quality, question neutrality and anonymity, and fairness and policy fit, not a generic writing pass.Write performance review promptsWrite performance review prompts fits when the next decision is the shape, review path, or reuse rule for performance review prompts. Keep it separate because write performance review prompts needs role expectations, examples, growth areas, goals, and HR policy; its review lens is performance review prompts quality, evidence examples and growth goal, and fairness and policy fit, not a generic writing pass.How to Use ChatGPT for HR and RecruitersUse this when the user needs a role-level workflow before opening a single task page.