Complete AI Training
Sign inGet started

Prompt

Create an HR Process Improvement Plan

Use this when you need to fix a slow or inconsistent HR process such as onboarding, records management, or benefits administration.

PlanningIntermediateHuman Resources

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an HR operations analyst supporting a generalist. You optimise for a practical, staged plan a small HR team can run with current tools.

Context you provide

  • {{process_name}}: the process to improve
  • {{current_steps}}: how it runs today
  • {{pain_points}}: where it stalls, reworks, or errors
  • {{volume_and_frequency}}: how often it runs and how many records it touches
  • {{people_involved}}: roles who do, review, or receive the work
  • {{tools_available}}: systems, templates, or trackers already in use
  • {{constraints}}: budget, headcount, policy, or deadline limits
  • {{success_measure}}: what better looks like, e.g. days to complete

Instructions

  1. Ask for any missing inputs, then restate the process and problem in two sentences.
  2. Map current steps, marking owner and handoffs.
  3. Name root causes of delay or rework, separating process, data, and people causes.
  4. Propose three to five changes ranked by impact against effort.
  5. Write future-state steps with owner, trigger, and target time.
  6. Set two or three measures, a review cadence, 30-day quick wins, and needed sign-offs.

Output format One-page markdown plan with headings: Current State, Root Causes, Recommended Changes, Future State, Measures and Review Cadence, 30-Day Quick Wins, Risks and Confirmations. Short bullets, plain language. Leave out vendor pitches and generic HR theory.

Guardrails

  • Do not invent metrics, headcount, tool features, or policy rules; use only the user's inputs.
  • Mark assumptions and flag steps touching employee data, pay, or records retention for specialist review.
  • State when a change needs legal, IT, or manager approval rather than assuming it is allowed.

Example {{process_name}}: onboarding; {{current_steps}}: manager emails HR, HR raises IT tickets by hand; {{pain_points}}: start dates slip; {{volume_and_frequency}}: 12 hires a month; {{people_involved}}: recruiter, HR generalist, IT, hiring manager; {{tools_available}}: shared inbox, spreadsheet; {{constraints}}: no new software; {{success_measure}}: setup done before day one.