Frontrow Technology
← All insights & guides
Guide

Copilot — HR

Microsoft 365 Copilot for HR: 10 prompts that compress recruiting and people work in AU 2026

Ten Microsoft 365 Copilot prompts for Australian HR teams — JDs, candidate screening, interview prep, onboarding, policy drafting, performance reviews. Aligned to Fair Work Act and AU Privacy Act considerations.

Daniel Brown · Last reviewed 23 May 2026 · 7 min read

HR is one of the highest-leverage Microsoft 365 Copilot adoption surfaces in Australian mid-market. Recruiting workflows, onboarding documentation, policy drafting and performance management are all writing-heavy, repeating, and benefit materially from a draft-then-edit pattern. There are also genuine Privacy Act and Fair Work considerations that need flagging — Copilot can help, but it isn't licensed to make employment decisions. The ten prompts below are tested across AU HR teams of 50 to 5,000 staff.

The Frontrow HR prompt library — 10 prompts

Recruitment

  1. 1"Draft a job description for [role title] in [department]. The role reports to [title]. Key responsibilities: [list]. Required experience: [list]. Salary band: [range]. Tone: warm but professional. Australian English. Include a non-discrimination statement aligned with Fair Work Act." Job description first draft.
  2. 2"Compare these three candidate CVs against the JD attached. For each candidate, identify: 1) the experience that matches the JD strongest, 2) the weakest area, 3) two questions I should ask in an interview to dig into the gap." Candidate shortlisting support. Note: this is a structured review aid, not a hiring decision.
  3. 3"Based on the role and the candidate's CV, draft a structured behavioural interview pack with five competency-based questions, each with the STAR format expected answer outline." Interview prep.

Onboarding

  1. 1"Draft a 30-60-90 day onboarding plan for a new [role] starting on [date]. The role's manager is [name]. Standard team milestones for AU mid-market: company induction week 1, role-specific training weeks 2-4, first major deliverable week 8-12." 30-60-90 plan.
  2. 2"Draft a welcome email from the manager to the new starter, mentioning the start date, who'll meet them on day one, where to be and at what time, what to bring, and a friendly note about looking forward to working together." New starter welcome email.

Policy and procedure

  1. 1"Update this leave policy to reflect the changes in the Fair Work Act from [date]. Maintain the original structure. Flag anywhere the language no longer aligns with current legislation for legal review." Policy maintenance. Legal review still required.
  2. 2"Draft a workplace flexibility policy for AU mid-market, covering work-from-home, hybrid arrangements, and core hours. Reference the Fair Work right to request flexible working arrangements. Tone: practical, not legalistic. Australian English." Policy first draft.

Performance and people

  1. 1"Summarise the feedback in this 360 review into: 1) consistent strengths, 2) consistent development areas, 3) any feedback that's unique to one reviewer (potential outlier). Do not name reviewers." 360 feedback synthesis.
  2. 2"Draft a development plan for [employee role] based on these development areas: [list]. Include suggested training (Microsoft Learn paths where applicable), stretch assignments, and mentor candidates." Development plan draft.

HR comms

  1. 1"Draft a company-wide email announcing [HR change] effective [date]. Tone: clear, supportive, anticipates the most likely questions. End with the named contact for follow-up questions." Internal HR announcement.

Privacy Act and Fair Work considerations

Three lines AU HR teams should not cross with Copilot. First, Copilot must not be used to make adverse-action decisions (discipline, performance management, termination). It's a drafting aid, not a decision-maker. Adverse-action protections under the Fair Work Act require documented human decision-makers. Second, candidate data fed to Copilot is personal information under the Privacy Act 1988. Sensitivity labels should be applied to CVs and the Copilot interactions should stay inside the tenant boundary (which they do for Microsoft 365 Copilot, by design). Third, performance review summarisation must not introduce bias the original 360 reviewers didn't introduce — the prompt above asks for synthesis without naming reviewers, but the human reading the summary still needs to validate the picture against the originals.

Try it

Score your Copilot rollout discipline

HR adoption is a leading indicator of wider rollout success. The Copilot Adoption & Waste Detector scores the whole-tenant rollout.

Want us to run this with your team?

30 minutes. No deck. We'll walk through your tenant, your priorities, and the next sensible move.