Performance Milestone & Coaching Review

Template Overview

Managing underperformance requires compassion, radical clarity, and rigorous documentation. When an employee struggles to meet role expectations, ambiguous feedback only increases anxiety and leads to misunderstandings.

A formal Performance Milestone and Coaching Review establishes a structured framework: explicit gaps between current output and expected standards, specific measurable milestones, scheduled check-in checkpoints, and commitments for manager assistance.

This template provides a fair, legally sound layout designed to give the employee every possible opportunity to succeed while maintaining clear institutional accountability.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Performance Coaching Review: [Employee Name]"
date: [YYYY-MM-DD]
employee: "[[Employee Name]]"
manager: "[[Manager Name]]"
hr_partner: "[[HR Business Partner Name]]"
plan_duration: "30 Days (Ending [YYYY-MM-DD])"
plan_status: [Active Coaching | Milestones Met | Plan Extended | Escalated]
confidentiality: strictly-confidential-hr
tags: [performance, coaching, management, hr, milestones]
---

# Performance Coaching Review: [Employee Name] — [YYYY-MM-DD]

## 1. Purpose & Performance Standards
- **Intent Statement:** The purpose of this coaching plan is to clarify role expectations, address specific performance gaps, and support [[Employee Name]] in meeting standard job requirements.
- **Role Baseline:** Senior Software Engineer expected to deliver sprint commitments predictably, participate in architectural design reviews, and communicate blocking issues proactively.

## 2. Identified Performance Gaps & Required Standards
| Performance Domain | Current Observed Performance | Required Standard Expectation | Evidence / Examples |
| :--- | :--- | :--- | :--- |
| Delivery Predictability | Missed 4 of last 5 sprint deadlines without notice | Complete assigned sprint commitments or flag blockers 48h in advance | Sprints 24, 25, 26 deliverable logs |
| Code Quality & Testing | Submitted PRs lacking unit test coverage, causing build failures | All PRs must maintain >80% test coverage and pass CI/CD pipeline | PR #389, PR #402 broken builds |
| Proactive Communication | Did not attend 3 core team standups without advance notice | Attend all core agile ceremonies or notify team beforehand | September attendance logs |

## 3. Measurable 30-Day Milestones
- **Milestone 1 (Week 1-2):** Deliver the audio buffering refactor PR with 85% test coverage and zero regression failures by [Date].
- **Milestone 2 (Week 3-4):** Provide written daily async standup updates prior to 10:00 AM local time each working day.

## 4. Manager Support & Coaching Resources
- Manager will conduct two 30-minute coaching check-ins each week (Tuesday and Thursday).
- Senior mentor [[Mentor Name]] assigned for 3 hours/week of dedicated code pairing.

## 5. Progress Evaluation & Check-In Log
> [!IMPORTANT] Confidential Evaluation
> Weekly assessment of milestone progress:
> - **Week 1 Review:** PR delivered on time with full test coverage. Strong improvement noted.
> - **Week 2 Review:** Communication consistent; zero missed standup updates.

- [ ] [[Manager Name]] File signed coaching review with HR Business Partner.
- [ ] [[Employee Name]] Complete pairing session with mentor on Thursday.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Performance Review: Check-In Week 2"
date: 2026-09-25
employee: "[[Candidate A]]"
manager: "[[Elena Rostova]]"
plan_status: Active Coaching
tags: [performance, coaching, hr]
---

# Performance Review: Check-In Week 2 — September 25, 2026

## 1. Progress Review
Elena reviewed Candidate A's code output over the past two weeks. Both assigned PRs were delivered on schedule and passed all automated test suites.

## 2. Manager Coaching Notes
Candidate A acknowledged that pairing with Marcus Vance significantly clarified test architecture. Recommended continuing pairing for one more sprint.

## 3. Checkpoint Verdict
Performance is tracking positively toward full resolution at Day 30.

When to Use and When to Avoid

When to Use

• Use when addressing documented employee underperformance requiring structured remediation.
• Use to establish objective, measurable milestones and prevent subjective evaluation bias.
• Use when maintaining legally auditable personnel records in coordination with HR.

When to Avoid

• Avoid using as a first step before providing direct informal feedback in weekly 1-on-1s.
• Avoid using for routine project deadline renegotiations or technical architectural disagreements.

On-Device AI Integration

Process performance coaching sessions locally in Oyma:

Analyze the coaching review audio transcript:
1. Summarize the role expectations, observed gaps, and specific examples discussed.
2. Formulate the agreed measurable milestones, completion criteria, and timeline.
3. Document manager commitments for pairing, coaching, and resource allocation.
4. Record the scheduled evaluation cadence and agreed progress checkpoints.
Format in professional, legally sound CommonMark.

Sensitive personnel records remain encrypted on your Mac with zero cloud exposure.