Help me start the right HR and Recruiters workflow.
Task to use: Write Job Descriptions: use the public role post where vague wording context.
Paste current work: 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..
Audience and constraints: HR teams and recruiters writing role, interview, onboarding, and employee communication copy..
Who checks it: The final reviewer should know job description quality, role outcomes and required skills, and fairness and policy fit well enough to reject a fluent answer that cannot be traced back to role outcomes, responsibilities, requirements, compensation range, and hiring process..
Before writing, ask for anything missing that would change the write job descriptions: use the public role post where vague wording context output.
Return: The final pass should leave a job description ready for a candidate, employee, hiring panel, or HR reviewer, with the uncertain parts marked instead of smoothed over.
Stop if: Hold the answer if it blurs what is known, what is assumed, and what still needs evidence.
After the first answer
Save what came back, what needs fixing, and the next prompt change before moving to another task.
0No role notes yet
Run the prompt once, check the answer, then save the problem and next try here.
Nothing saved yet
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 choices.
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 work to finish, 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 named human check.
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 choice a person is trying to make, not by a generic prompt collection. 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 the work in front of you
Write job descriptions
Use when the next useful output is a job description and the answer needs copy options grouped by angle, audience, supporting detail, and revision note.
Write job descriptions needs role outcomes, responsibilities, requirements, compensation range, and hiring process; the check focuses on 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 useful output is interview questions and the answer needs interview questions with the usable answer first, then gaps and follow-up checks.
Prepare interview questions needs role scorecard, competencies, level, format, and fairness constraints; the check focuses on 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 useful output is a product scorecard and the answer needs a scoring table with levels, observable evidence, and reviewer notes.
Build interview scorecards needs role criteria, rating levels, evidence examples, and interviewer notes; the check focuses on product scorecard quality, rating anchors and evidence examples, and fairness and policy fit, not a generic writing pass.
Plan onboarding
Use when the next useful output is an onboarding plan and the answer needs a sequenced plan with stages, owners, timing, and choice checkpoints.
Plan onboarding needs new hire role, first-week goals, tools, meetings, and success signals; the check focuses on 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 useful output is an employee survey and the answer needs an employee survey with a source-backed outline, choice notes, and a closing check.
Write employee surveys needs research goal, audience, sensitive topics, scale, and anonymity limits; the check focuses on 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 useful output is performance review prompts and the answer needs performance review prompts with field labels, short bullets, and a use-or-revise note.
Write performance review prompts needs role expectations, examples, growth areas, goals, and HR policy; the check focuses on 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 useful output is policy language and the answer needs policy language organized by context, output, caveats, and the next human action.
Write policy language needs policy goal, audience, legal review notes, examples, and escalation path; the check focuses on 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 useful output is a rejection email and the answer needs a ready-to-edit message with subject line, body, tone notes, and review checklist.
Write rejection emails needs candidate stage, tone, relationship, feedback policy, and next opportunity; the check focuses on rejection email quality, candidate stage and respectful tone, and recipient-safe next step, not a generic writing pass.
Use this job description page when the job is a job description, not broad advice. It gives source prep, examples, prompts, and a short review path for job description quality, role outcomes and required skills.
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.
Move from a rough interview questions request to interview questions with the usable answer first, then gaps with runnable prompts and revision rules. The page shows when to reject the answer and what to save for reuse.
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. The first human check for interview questions work has to compare the answer with the supplied note. The response should keep the actual request visible through the edit. Start the interview questions from the rough request before shaping interview questions. A usable starting note for interview questions work 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.
HR and Recruiters get product scorecard prompts that carry source context, example inputs, answer checks, and safe-use notes. The page keeps scorecard row with evidence examples as the thing to inspect.
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 the rough request 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.
Use this workflow when the onboarding plan job starts with new hire role, first-week goals, tools, meetings, and success signals and needs a clear output shape. The result can be checked before it reaches a candidate, employee, hiring panel, or HR reviewer.
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 onboarding plan work, 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 source note into an onboarding plan. For onboarding plan work, paste the source as bullets, constraints, and audience notes so the model has enough shape for a sequenced plan with stages, owners, timing, and choice checkpoints.
Reject if
Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
Start the employee survey run with the working case, then copy prompts that preserve question neutrality, anonymity, scale wording, and actionability. The review pass checks notes from the user, example fit, constraints, and reviewer before anything gets reused.
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 employee survey work, 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 source note into an employee survey. For employee survey work, paste the source as bullets, constraints, and audience notes so the model has enough shape for an employee survey with a source-backed outline, choice notes, and a closing check.
Reject if
Restart the prompt if it adds citations, policies, credentials, or outcomes outside the source notes.
The performance review prompts workbench starts with the notes you already have, then shapes them into performance review prompts with field labels, short bullets, and a. It is built for hr and recruiters who need review note with example and growth rows, clear limits, and a reusable second pass.
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 performance review prompts work 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 performance review prompts work, the supplied note becomes the base for performance review prompts. A usable starting note for performance review prompts work 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.
The policy language page helps hr and recruiters turn rough notes into policy language. It pairs the prompt with a concrete example, stop rules, and a next workflow when the task does not fit.
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 the rough request 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.
Use this rejection email workflow when hr and recruiters need to move from source notes to a shareable answer without losing the original limits. It keeps rejection email quality, candidate stage and respectful tone visible before reuse.
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 provided context, examples, hard constraints, and the final human check or treats uncertainty as fact.