People & HR · For CHRO
Better performance reviews in half the time
- Claude
- Teams
- Word
- Workday
The short answer
Claude gathers each employee's goals, feedback and recorded achievements from the tools your teams already use, then drafts a balanced review summary for the manager. It flags vague or potentially biased language and points to evidence. The manager edits and approves every review, so people stay in charge and reviews take a fraction of the usual time.
Key takeaways
- Managers spend many hours each cycle hunting for evidence and writing from a blank page.
- Claude gathers goals, feedback and achievements the employee is already permitted to see, then drafts a balanced summary.
- A built-in bias check flags loaded or uneven wording before a manager finalises it.
- Managers keep full control: Claude drafts and checks, and the named manager approves every review.
Executive summary
Performance reviews matter to every leader, yet they often eat up managers' time and produce inconsistent results. Good feedback depends on remembering what happened over twelve months, and many managers simply do not have the time to dig it out. The result is rushed, generic reviews that frustrate employees and weaken pay and promotion decisions. This automation lets Claude do the gathering and first drafting, working inside Microsoft Teams, Word and your existing Workday records. It also checks the draft's language for bias and imbalance. Managers spend their time on judgement and conversation rather than admin. The organisation gains reviews that are more consistent, better evidenced and more defensible, delivered in a fraction of the usual time.
What is the real cost of slow, generic performance reviews?
Most performance cycles ask managers to write a thoughtful assessment of each team member, often for a dozen or more people at once. Few managers have a clear record of the year. Achievements are scattered across Teams chats, shared documents, project emails and half-remembered conversations. So they either spend days searching for evidence or fall back on general phrases that could describe almost anyone.
The hidden cost is significant. Time is lost that could go to coaching and development. Reviews arrive late, which weakens the link to pay and progression decisions. Employees who receive vague feedback are less likely to understand what good looks like, and high performers may leave because their work was not recognised in specific terms.
- Managers often spend long periods searching for evidence before writing a single sentence.
- Generic wording makes it hard to justify ratings and promotion decisions.
- Late reviews delay pay and development conversations that employees are waiting for.
What changes for the organisation with Claude?
With this automation in place, the review cycle starts with evidence already gathered. Claude collects each employee's agreed goals, the feedback they have received and the achievements recorded during the period. It organises this into a clear picture of the year, grouped by goal and theme. The manager receives a first-draft summary they can read in minutes instead of hours.
Consistency also improves. Every review is built from the same structure and the same kinds of evidence, which makes it easier for leaders to compare outcomes across teams and locations. HR can focus on calibration and quality rather than chasing late forms.
- Each review begins from a structured summary of goals, feedback and achievements.
- Reviews follow a common structure, improving comparison across teams.
- HR shifts effort from chasing forms to calibrating outcomes.
How does Claude connect to Teams, Word and Workday?
Claude for Microsoft 365 works with the tools your people already use. It can read the Teams conversations and shared files a manager is allowed to access, and pull goal and review information from Workday, the HR system of record. The draft is produced as a Word document, in your organisation's house style, ready for the manager to edit.
Company know-how is packaged using Claude Skills, so the review template, rating definitions and the wording your leaders expect are followed every time. Claude Skills are company know-how packaged so Claude follows it consistently. Learn more about Claude Skills and how Claude for Microsoft 365 brings these tools together. For the wider picture of how this fits across the whole organisation, see how Claude and Microsoft 365 together lift productivity. A closely related automation is Hire faster with fair, consistent candidate screening.
- Goals and review records are read from Workday with the same permissions the manager already has.
- Feedback and achievements are gathered from Teams and documents the manager can already see.
- The draft is written in Word, using your template and rating definitions via Claude Skills.
What does a day in the life look like before and after?
Before automation, a people manager preparing reviews for a team of eight might block out several full days. They open old emails, scroll through Teams threads, and try to recall what each person delivered. They then write each review from scratch, often late in the evening, and worry that the language is uneven between men and women or between newer and longer-serving staff.
After automation, the same manager opens a prepared draft for each team member. The summary already lists goals, feedback and achievements with sources. The manager reads, adds their own judgement, corrects anything Claude has missed, and reviews the bias check flags. The work that remains is the part only a manager can do: deciding, coaching and having the conversation.
- Before: days spent searching for evidence and writing from a blank page.
- After: a prepared draft per person, with sources, ready for judgement and edits.
- Before: uneven wording that is hard to defend. After: a bias check flags issues for the manager to resolve.
How are governance, security and fairness protected?
Claude only sees what each user is already permitted to see. A manager can draft reviews only for their own direct reports, and an employee's records are not exposed to colleagues outside that reporting line. Every draft is clearly marked as a draft, and the named manager must approve and edit it before anything is shared with the employee or entered into Workday.
The bias check is a support, not a verdict. It highlights wording that may be gendered, uneven in length between peers, or dependent on personal characteristics, and it asks the manager to justify or change it. Access logs and version history allow HR to see who produced and approved each review. Employment decisions remain with people, and your legal and HR advisers should set the policy for how reviews are used.
- Managers see only the reviews for their own direct reports.
- Drafts are marked clearly and cannot be finalised without the manager's approval.
- The bias check prompts a manager to reconsider uneven or loaded language.
- Access and version records show who prepared and approved each review.
How do you measure whether it is working?
Measure the change in manager time, the timeliness of review completion and the quality of the feedback itself. Ask managers and employees whether the reviews feel specific and fair. Track how often bias flags are resolved and whether ratings show a more even pattern across groups over successive cycles. Use these measures to refine your templates and training, not to rank individual managers.
Typical results reported by organisations running structured review drafting include managers spending noticeably less time on the admin of each review and reviews being completed earlier in the cycle. Results depend on your starting point, the quality of goal-setting and the discipline of your review calendar.
- Track manager hours per review before and after the change.
- Measure on-time completion across the review cycle.
- Ask employees whether feedback feels specific, balanced and actionable.
- Review bias flags and resolution rates each cycle to refine templates.
How should an organisation start?
Start with a free automation audit. We look at how goals are set, where review records live, which Teams and document sources managers rely on, and how your current template is written. We identify the simplest pilot, usually one department completing one review cycle, and agree who approves drafts and how the bias check is reviewed. We then build the workflow, test it against real but anonymised examples, and expand once managers and HR are confident in the output.
Throughout, your people remain responsible for every decision. The automation exists to return time to managers and to make the evidence behind each review easier to see and easier to trust.
- Run a free automation audit to map goals, records and review templates.
- Pilot with one department and one review cycle.
- Agree approval roles, bias-check review and access rules before go-live.
How it works
Gather
Claude collects each employee's goals, feedback and recorded achievements from Workday, Teams and shared documents the manager can already see.
Organise
The evidence is grouped by goal and theme, with sources noted, so the manager sees the whole year at a glance.
Draft
Claude writes a balanced first-draft review in Word, using your template and rating definitions.
Check
A bias check flags loaded, uneven or personal wording and suggests a neutral alternative for the manager to consider.
Approve
The manager edits, adds their judgement and approves the final review before it is shared or entered into Workday.
Before and after
Gathering evidence for each review
BeforeHours of searching emails, chats and files from memory.
AfterStructured summary of goals, feedback and achievements prepared in advance.
Writing the review
BeforeWriting from a blank page, often late in the evening.
AfterBalanced first draft in Word, ready for the manager to refine.
Checking fairness of language
BeforeRelying on the manager to spot uneven wording unaided.
AfterBias check flags issues for the manager to resolve before approval.
Completing the cycle
BeforeReviews trickle in late and chase-ups consume HR time.
AfterDrafts ready early, so HR focuses on calibration and quality.
What leaders typically see
- 30–50%Typical reduction in manager time spent preparing each review
- EarlierTypical improvement in on-time review completion across the cycle
- More evenTypical consistency in the specificity and balance of review wording
Typical ranges. Your free audit sets a baseline for your own organisation.
What it means for each leader
- CHRO
- Consistent, well-evidenced reviews that support fair pay and progression decisions, delivered on time.
- CFO
- Less management time spent on admin, freeing capacity for work that drives performance and cost discipline.
- COO
- Managers spend more time coaching their teams and less time on paperwork, supporting steadier delivery.
- CIO
- Reviews sit inside the Microsoft 365 and Workday environment already in use, with clear access controls and logs.
- General Counsel
- A documented, human-approved review trail and a bias check that supports fair treatment and defensible decisions.
United States, United Kingdom, India and the Middle East
United States
Performance records and employment decisions may fall under federal and state employment law, including anti-discrimination rules, and state privacy laws such as California's CCPA/CPRA. US hosting is available for the deployment, and your legal team should set the policy on how reviews are used.
United Kingdom
Employee data is governed by UK GDPR and the Data Protection Act 2018, and equality law shapes how reviews are written and used. UK hosting is available, and the design lets you keep humans accountable for every decision about pay and progression.
India
Employee records are covered by the Digital Personal Data Protection Act, 2023, alongside employment and equal-opportunity rules. India hosting is available, and the review workflow keeps managers responsible for approving every assessment.
Middle East
Employee data falls under the UAE Personal Data Protection Law, Saudi Arabia's Personal Data Protection Law overseen by SDAIA, Qatar's data protection law and free-zone rules such as DIFC and ADGM where relevant. Arabic-language needs are considered in the audit, and data-residency requirements are assessed so the deployment region is chosen to meet them.
Safeguards built in
- Claude only accesses the goal, feedback and achievement records each user is already allowed to see.
- Managers see reviews only for their own direct reports.
- Every draft is marked as a draft and needs the manager's approval before it is final.
- The bias check prompts review of loaded or uneven wording without making decisions for the manager.
- Access logs and version history show who prepared and approved each review.
- Your HR and legal advisers set the policy on how reviews are used in pay and promotion decisions.
From audit to rollout
Audit and design Weeks 1–2
Map goal-setting, review records, templates and the Teams and document sources managers rely on.
Pilot Weeks 3–8
Run one department through one review cycle with anonymised test data, refining the template, Skills and bias check.
Controlled rollout Weeks 9–14
Extend to further departments with manager training, clear approval roles and monitoring of bias flags.
Scale and refine Week 15 onward
Use cycle results to improve templates, calibration and training across the organisation.
The Claude products behind it
Claude working with Outlook, Word, Excel, Teams and SharePoint.
Company know-how packaged so Claude follows it every time.
Frequently asked questions
What does doing nothing cost us?
Managers continue to spend many hours each cycle searching for evidence, and reviews tend to arrive late and vague. This weakens pay and promotion decisions and can frustrate high performers. The cost is measured in manager time, delayed decisions and reduced confidence in the process, all of which add up across a year.
Is employee data secure?
Claude only sees the records each user is already permitted to access, and access is logged. Drafts stay within your Microsoft 365 and Workday environment and are not finalised without a named manager's approval. We design the workflow around your existing security controls.
Where is our data stored?
Deployment can be hosted in India, the United States, the United Kingdom or the European Union, depending on your requirements. The free audit confirms where your employee data must reside and selects the deployment region accordingly.
Will the AI decide who gets a promotion or a pay rise?
No. Claude drafts and checks the review. Managers form the judgement, edit the wording and approve the outcome. Decisions about pay and progression remain with accountable people under your own policies.
How do we know the drafts are accurate?
Every draft shows the sources of its evidence, so managers can check each point against the underlying record. Anything that cannot be sourced is flagged rather than presented as fact. Managers are trained to read drafts critically before approving them.
Will this change how my staff feel about reviews?
Employees usually respond well when feedback is more specific and better evidenced. We recommend telling staff clearly how drafts are prepared, that managers approve every review, and how the bias check works, so trust is built from the start.
Which Microsoft 365 licences or tools do we need?
You need the Microsoft 365 tools your teams already use, including Teams and Word, and access to your Workday review records. The audit confirms which licences and connections apply in your environment before any build begins.
Can this work in our offices outside the US and UK?
Yes. We support organisations in India and the Middle East as well. Local employment and data protection rules, and Arabic-language needs where relevant, are assessed during the audit so the design fits each location.