BEST HR TOOLS | AI PROMPTS FOR HR
Editorial templates, September 21, 2026. Not benchmarked model outputs.
https://besthrtools.com/us/ai/hr-prompts/
Use fictional or approved material in an organization-approved workspace. Replace personal details with roles.

1. Approved role brief to job advertisement draft
Inputs: Approved role brief with a source ID, approved careers boilerplate with its own source ID, role title, organization type, location or work pattern, target word count.
Expected output: Headline, three sentence role summary, responsibilities list, essential and desirable requirements, closing application step, source ID beside each bullet, an Open questions list, and a human review label.

Goal: draft a job advertisement for internal review. Context: you are supporting a hiring team at [ORGANIZATION TYPE] recruiting for [ROLE TITLE] in [LOCATION OR WORK PATTERN]. Source: use only the approved role brief pasted below, labeled [SOURCE ID], plus the approved careers boilerplate labeled [BOILERPLATE SOURCE ID]. Do not add responsibilities, salary figures, benefits, or employer claims that are absent from those sources. Expectations: produce a draft of about [WORD COUNT] words with a headline, a three sentence role summary, a bulleted list of responsibilities, a bulleted list of requirements split into essential and desirable, and a closing application step. Cite the source ID beside each bullet. List every missing fact under a heading called Open questions rather than filling the gap. Label the output Human review required: unverified draft.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Read the draft beside the role brief and strike any responsibility, pay figure, or benefit that does not appear in the brief, then confirm the application step matches your live posting route.

2. Role criteria to interview question set
Inputs: Approved role criteria with a source ID, role title, team name, planned interview length, number of questions wanted, number of follow up probes wanted.
Expected output: A four column table of criterion, source ID, question, and what a complete answer would cover, plus a separate list of follow up probes and a human review label.

Goal: draft interview questions for a review panel. Context: the panel is hiring for [ROLE TITLE] in [TEAM NAME] and will run a [INTERVIEW LENGTH] conversation. Source: use only the approved role criteria pasted below, labeled [SOURCE ID]. Do not use candidate resumes, applications, notes, or any personal information, and do not create scoring rubrics, rankings, or hiring recommendations. Expectations: return a table with four columns: criterion, source ID, question, and what a complete answer would cover. Write [NUMBER] questions in total, at least one per criterion, in plain US English and open format. Add [NUMBER] follow up probes as a separate list. Where a criterion is vague or undefined, write Needs clarification in the question column instead of inventing a standard. Label the draft Human review required before panel use.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Check each question against the criterion it cites, remove anything that asks about health, family, or other personal circumstances, and confirm no scoring language crept into the table.

3. Interview logistics confirmation email
Inputs: Confirmed logistics with a source ID, approved accessibility contact line with a source ID, role title, date, start and end time, time zone, format, panel names and titles, subject character limit, body word limit.
Expected output: One subject line within the character limit and a body within the word limit covering time, format, duration, panel, what to bring, and adjustment requests, with a list of [TO CONFIRM] items and a human review label.

Goal: draft a logistics email confirming an interview time. Context: the recipient is a candidate for [ROLE TITLE] and the interview is [DATE], [START TIME] to [END TIME] in [TIME ZONE], held [FORMAT: video, phone, or onsite]. Source: use only the confirmed logistics details pasted below, labeled [SOURCE ID], and the approved accessibility contact line labeled [ACCESS SOURCE ID]. Expectations: write a subject line under [CHARACTER COUNT] characters and a body under [WORD COUNT] words, in a warm and plain tone, covering date and time with time zone, format and joining or arrival instructions, expected duration, panel first names and job titles, what to bring, and how to request an adjustment. Mark any detail not supplied as [TO CONFIRM] and list those items at the end. Label the draft Human review required before sending.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Verify the date, start time, time zone, joining link or address, and panel names against the calendar invite before sending, and resolve every [TO CONFIRM] marker yourself.

4. First week onboarding plan draft
Inputs: Approved onboarding outline with a source ID, approved team introduction list with a source ID, team name, role title, start date, work pattern, maximum activities per day.
Expected output: A day one to day five plan with a focus line, capped activities, a named owner and a source ID per activity, plus a Gaps section and a human review label.

Goal: draft a first week plan for a new team member. Context: the new starter joins [TEAM NAME] as [ROLE TITLE] on [START DATE], working [WORK PATTERN]. Source: use only the approved onboarding outline pasted below, labeled [SOURCE ID], and the approved team introduction list labeled [TEAM SOURCE ID]. Do not add system access steps, training modules, or meetings that are not named in those sources. Expectations: return a day by day plan for days one to five. For each day give a focus line, up to [NUMBER] activities, the owner for each activity, and the source ID it came from. Keep each activity to one sentence. Add a short section called Gaps listing anything the outline leaves undefined, such as an unnamed owner or an undated session. Label the draft Human review required.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Confirm each owner has agreed to the proposed session and every activity exists in the outline. Flag access-dependent activities for confirmation before finalizing the schedule.

5. Standard operating procedure to working checklist
Inputs: Full SOP text with a source ID, SOP version number and date, process name, the role or team that will use the checklist.
Expected output: A numbered checklist in SOP order with action, owner, trigger or timing, and mapped SOP section number per step, an Unclear in source flag where wording is ambiguous, a closing version line, and a human review label.

Goal: convert an approved standard operating procedure into a working checklist. Context: the checklist will be used by [ROLE OR TEAM] when performing [PROCESS NAME]. Source: use only the SOP text pasted below, labeled [SOURCE ID], including its version number and date. Do not add steps, tools, timings, or approvals that the SOP does not state. Expectations: return a numbered checklist that follows the SOP order. For each step give the action in the imperative, the named owner, the trigger or timing if the SOP states one, and the SOP section number it maps to. Mark any step where the SOP is ambiguous with Unclear in source and quote the phrase in question. End with a version line naming the SOP ID and date. Label the output Human review required: unverified draft.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Walk the checklist against the SOP section by section, confirm the version number and date on the footer, and resolve every Unclear in source flag with the process owner before anyone uses it.

6. Standard operating procedure to knowledge check
Inputs: Full SOP text with a source ID, process name, role or team taking the check, number of multiple choice questions, number of short answer questions.
Expected output: Multiple choice items with four options and one correct answer, short answer items, a correct answer with a one sentence explanation and SOP section number for each, a standing recall only note, and a human review label.

Goal: draft a short knowledge check based on an approved procedure. Context: the audience is [ROLE OR TEAM] who have read [PROCESS NAME]. Source: use only the SOP text pasted below, labeled [SOURCE ID]. Every question and every answer must be traceable to a sentence in that text. Expectations: write [NUMBER] multiple choice questions with four options each and one correct answer, plus [NUMBER] short answer questions. For each item give the correct answer, a one sentence explanation, and the SOP section number it comes from. Avoid trick wording and avoid scenarios the SOP does not cover. Add a standing note that the check covers recall of the written procedure only and is not evidence of competence or sign off. Label the draft Human review required.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Answer the quiz yourself against the SOP, confirm each correct answer maps to the cited section, and rewrite any option that is true in practice but not stated in the written text.

7. Approved change brief to employee announcement
Inputs: Approved change brief with a source ID, audience description, organization type, effective date, named contact from the brief, target word count.
Expected output: A subject line and a four part body covering what is changing, when it starts, what people must do and by when, and where to ask questions, with bracketed [TO CONFIRM] markers listed beneath and a human review label.

Goal: draft an internal announcement about an approved change. Context: the audience is [AUDIENCE, for example all staff or one department] at [ORGANIZATION TYPE], and the change takes effect on [EFFECTIVE DATE]. Source: use only the approved change brief pasted below, labeled [SOURCE ID]. Do not add reasons, timelines, impacts, or reassurance that the brief does not state. Expectations: write a subject line and a body of about [WORD COUNT] words with four parts: what is changing, when it starts, what people need to do and by when, and where to ask questions using the contact named in the brief. Use plain US English and short paragraphs. Put any point the brief leaves open in a bracketed [TO CONFIRM] marker and list them beneath the draft. Label the output Human review required before distribution.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Confirm the effective date, the required action, and the named contact against the change brief, and go back to the approver before any bracketed item is filled in.

8. Approved policy excerpt to employee FAQ draft
Inputs: Approved policy excerpt with a source ID, version and date, policy topic, audience description, number of question and answer pairs, answer word limit, named contact or team for referrals.
Expected output: Question and answer pairs phrased as employees ask them, each answer within the word limit and citing a clause number, referral lines where the excerpt is silent, an Unanswered by source list, and a human review label.

Goal: draft plain language FAQs from an approved policy excerpt. Context: the readers are [AUDIENCE] and the topic is [POLICY TOPIC]. Source: use only the policy excerpt pasted below, labeled [SOURCE ID], with its version and date. Do not interpret entitlement, decide eligibility, give legal advice, or answer a question the excerpt does not address. Expectations: write [NUMBER] question and answer pairs. Phrase each question the way an employee would ask it. Keep each answer under [WORD COUNT] words, use only what the excerpt says, and cite the clause number. Where the excerpt is silent or conditional, answer with a referral line pointing to [NAMED CONTACT OR TEAM] and add the question to a list called Unanswered by source. Label the draft Human review required before publication.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Check each answer against the clause it cites, delete any sentence that decides who qualifies for something, and route the Unanswered by source list to the policy owner before publishing.

9. Recurring manager meeting agenda
Inputs: Standing agenda template with a source ID, approved topic list for this cycle with a source ID, meeting name, duration, day and time, number of managers, team or function.
Expected output: A table of topic, one line purpose, owner, minutes allocated and source ID with minutes totaling the duration, plus a pre read line, a decisions to capture line, Needs input flags, and a human review label.

Goal: draft an agenda for a recurring manager meeting. Context: the meeting is [MEETING NAME], runs [DURATION] on [DAY AND TIME], and is attended by [NUMBER] managers from [TEAM OR FUNCTION]. Source: use only the standing agenda template labeled [SOURCE ID] and the approved topic list for this cycle labeled [TOPIC SOURCE ID]. Do not include any assessment of an individual, performance commentary, or named personnel matters, and do not add topics that are absent from the list. Expectations: return a table with topic, purpose in one line, owner, minutes allocated, and source ID, with the minutes totaling the stated duration. Add a pre read line and a decisions to capture line. Flag any topic without an owner or a stated purpose as Needs input. Label the draft Human review required.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Confirm the minutes add up to the meeting length, remove any line that names or evaluates an individual, and get each owner to accept their slot before the invite goes out.

10. Payroll handoff checklist from an approved procedure
Inputs: Approved handoff procedure with a source ID, sending team, receiving team, pay frequency, cutoff day. No employee data of any kind.
Expected output: A checklist grouped into before cutoff, at cutoff and after submission, with action, owner role, stated deadline and procedure section number per item, a blank confirmations column, Missing in source flags, and a human review label.

Goal: draft a payroll handoff checklist for internal review. Context: the handoff runs between [SENDING TEAM] and [RECEIVING TEAM] for a [PAY FREQUENCY] cycle with a cutoff on [CUTOFF DAY]. Source: use only the approved handoff procedure pasted below, labeled [SOURCE ID]. Do not include employee names, identifiers, pay data, or any personal records, and do not calculate, estimate, or reconcile any figure. Expectations: return a checklist grouped into before cutoff, at cutoff, and after submission. For each item give the action, the owner role rather than a person, the deadline stated in the procedure, and the procedure section number. Add a confirmations column left blank for the reviewer. Mark any step whose owner or deadline is not stated as Missing in source. Label the output Human review required.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Compare the checklist to the procedure, confirm no employee data or figure appears anywhere in it, and have the payroll owner confirm each stated deadline against the current cycle calendar.

11. Vendor demo brief from your requirements
Inputs: Approved requirements list with a source ID, internal scenario description with a source ID, team name, category described in your own words, session duration.
Expected output: A numbered agenda with requirement, source ID, scenario to walk through, question to ask and what you want to see on screen, plus a To define before the call section and a human review label.

Goal: draft a demo brief for a software evaluation meeting. Context: the team is [TEAM NAME], the evaluation covers [CATEGORY IN YOUR OWN WORDS], and the session lasts [DURATION]. Source: use only the approved requirements list pasted below, labeled [SOURCE ID], and the internal scenario description labeled [SCENARIO SOURCE ID]. Do not describe, assume, or assert anything about the vendor, its features, its pricing, or its performance. Frame vendor-facing items as questions or requests to demonstrate the requirement. Expectations: return a numbered agenda with the requirement, the source ID, the scenario to walk through, the question to ask, and what you want to see on screen. Add a short section listing requirements the source leaves undefined, under the heading To define before the call. Label the draft Human review required.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Remove any line that states something about the vendor rather than asking it, confirm each question ties back to a listed requirement, and agree the scenario with the team before the call.

12. Approved meeting notes to action list
Inputs: Approved meeting notes with a source ID, meeting name, meeting date, distribution list. For practice runs, fictional notes containing no real people and no real employee details.
Expected output: Two tables, one of actions with verb phrase, owner, due date and source line, one of decisions with source line, plus a Needs confirmation list quoting the ambiguous wording and a human review label.

Goal: turn approved meeting notes into a clear action list. Context: the notes come from [MEETING NAME] held on [DATE] and the output goes to [DISTRIBUTION LIST]. Source: use only the notes pasted below, labeled [SOURCE ID]. For practice runs, use fictional notes that contain no real people and no real employee details. Do not add actions, owners, or dates that the notes do not contain, and do not summarize opinions about individuals. Expectations: return two tables. The first lists actions with the action written as a verb phrase, the owner, the due date, and the line of the notes it came from. The second lists decisions with the decision and its source line. Put anything ambiguous under Needs confirmation with the exact quoted wording. Label the output Human review required.

If a fact is missing or sources conflict, flag it for human confirmation rather than supplying an answer. Use roles or fictional placeholders instead of personal details.

Approved source pack (label each document with its ID, version and date):
[PASTE APPROVED SOURCE TEXT HERE]

Human check: Confirm every action, owner, and date appears in the notes, remove any line that characterizes a person, and send the Needs confirmation list to the meeting chair before circulating.