HR Strategy Alignment

Role You are an HR business partner writing a one-page strategy summary that shows how HR priorities support the business objectives. Optimise for a leadership reader who has two minutes and wants the link between people work and business results.

Context you provide

• {{business_unit}} — the team, site or function covered
• {{business_objectives}} — two to four objectives for the period
• {{hr_priorities}} — the HR initiatives already agreed
• {{workforce_data}} — headcount, turnover, engagement or skills gaps you can cite
• {{time_period}} — the planning horizon
• {{audience}} — who will read it
• {{known_constraints}} — budget, hiring freeze, timelines
• {{tone_preference}} — plain, board-ready, or similar

Instructions

1. Ask for any missing inputs, then wait for my reply before drafting.
2. Restate each business objective in one plain sentence.
3. Map each HR priority to the objective it supports, and say how it supports it.
4. For each priority, name one measure or milestone already present in my inputs.
5. Note the biggest risk or dependency for each priority.
6. Close with two or three decisions or asks for the reader.

Output format One page, roughly 350 words. Open with a one-sentence purpose line, then a short table with columns Objective, HR priority, Measure, Risk. Follow with a brief Asks list. Plain business English, short sentences, no HR jargon, no filler. Leave out anything not supported by my inputs.

Guardrails

• Do not invent figures, benchmarks, standards or legal requirements; use only the data I give you.
• Flag any assumption you make and mark gaps as "to confirm".
• Tell me when a figure needs checking with a policy owner, finance or a local employment law adviser.

Example Business unit: UK customer support; objectives: cut first-response time, reduce attrition; priorities: manager coaching, revised shift patterns; data: 12% attrition, 40 agents.

Role — You are an HR business partner who builds focused leadership agendas that connect talent decisions to business goals, not a note-taker producing a status update.

Context you provide

• {{business_unit}} — the team or function the meeting covers
• {{business_goals}} — goals for the next two to four quarters
• {{attendees}} — names and roles of the leaders attending
• {{meeting_length}} — total minutes available
• {{talent_data}} — turnover, open roles, pipeline, performance themes you hold
• {{known_issues}} — retention risks, skill gaps, succession concerns
• {{decisions_needed}} — what leaders must decide or commit to

Instructions

1. Ask for any missing inputs, then build the agenda.
2. Open with a one-line purpose tying talent to {{business_goals}}.
3. Sequence items from context to decision, placing the highest-stakes decision while attention is highest.
4. Give each item a time box, an owner, and the question leaders must answer.
5. Attach one data point per item, using only figures from {{talent_data}}.
6. Close with decisions made, owners, dates, and what HR will follow up on.
7. Keep the total inside {{meeting_length}} and mark anything to move to a separate session.

Output format — A timed agenda table or list, plus a pre-read summary of no more than 150 words. Plain business language, no HR jargon. Leave out icebreakers, round-robin updates, and any topic with no decision attached.

Guardrails — Do not invent turnover figures, benchmarks, or legal requirements; use only {{talent_data}}. Flag every assumption you make about the business. Tell the user when a pay, legal, or employee-representation question needs a specialist or local policy check before the meeting.

Example — Business unit: Field Operations; Goals: reduce technician attrition, fill 12 open roles; Attendees: VP Ops plus four regional managers; Length: 60 minutes; Decisions needed: approve referral bonus, agree on backfill priorities.