Performance Improvement Checkpoint

Template Overview

When an employee’s output diverges from expected standards, structured performance improvement checkpoints ensure absolute clarity regarding expectations, timelines, and required remedies. The Performance Improvement Checkpoint template provides an objective, empathetic, and legally defensible Markdown structure to track progress.

Markdown Template Structure

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

---
title: "Performance Checkpoint: [Employee Name] - Week [X]"
date: [YYYY-MM-DD]
employee: "[[Employee Name]]"
manager: "[[Manager Name]]"
hr_partner: "[[People Operations Partner]]"
plan_start_date: [YYYY-MM-DD]
plan_target_date: [YYYY-MM-DD]
overall_evaluation: "On Track / Off Track / Substantial Improvement"
tags: [performance, pip, management, hr, feedback]
---

# Performance Improvement Checkpoint — [Employee Name]

## 1. Plan Objectives & Milestone Expectations
- **Objective 1 (Delivery Velocity):** Complete and merge assigned sprint deliverables within estimated cycle times without requiring secondary developer intervention.
- **Objective 2 (Code Quality):** Maintain unit test code coverage >=80% and zero regression defects on shipped pull requests.
- **Objective 3 (Communication):** Proactively update ticket blocker status during morning standup by 09:30 AM daily.

## 2. Weekly Progress Evaluation
| Performance Objective | Observed Evidence This Week | Objective Assessment | Next Week Focus |
|---|---|---|---|
| Delivery Velocity | Merged PR #402 ahead of schedule | Satisfactory | Tackle multi-service integration task |
| Code Quality | Two minor linter warnings resolved | Satisfactory | Expand regression test suite coverage |
| Communication | Clear blocker escalation on Wednesday | Satisfactory | Maintain consistent daily cadence |

## 3. Manager Support & Coaching Resources
- [ ] Provide 45 minutes of weekly architectural pairing with the team lead.
- [ ] Supply curated documentation on testing methodologies and mock data frameworks.

## 4. Next Checkpoint & Formal Acknowledgment
Next formal evaluation session scheduled for **[Next Date]**. Both manager and employee acknowledge review of the performance notes above.

Filled Real-World Example

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

---
title: "Performance Checkpoint: Jordan Hayes - Week 3"
date: 2026-10-09
employee: "[[Jordan Hayes]]"
manager: "[[Sarah Sterling]]"
hr_partner: "[[Chloe Bennett]]"
plan_start_date: 2026-09-18
plan_target_date: 2026-10-30
overall_evaluation: "Substantial Improvement"
tags: [performance, pip, management, hr]
---

# Performance Improvement Checkpoint — Jordan Hayes

## 1. Progress Overview
Sarah Sterling reviewed Jordan's pull requests from Sprint 24. Jordan successfully delivered the database migration script with zero defect escapes and comprehensive unit tests.

## 2. Assessment
Jordan has met all three core performance objectives for the second consecutive week. Both parties agreed that sustained performance at this standard will lead to a successful plan closeout on October 30.

When to Use and When to Avoid

When to Use

• Use during formal performance improvement plan (PIP) checkpoints between managers and employees.
• Use to establish indisputable documentation of expectations, feedback, and observed progress.
• Use to ensure fairness, empathy, and objective clarity during challenging employment evaluations.

When to Avoid

• Avoid using as a surprise reprimand without prior informal feedback.
• Avoid using for casual, routine 1-on-1 mentorship catch-ups.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the performance checkpoint audio recording:
1. Extract specific performance objectives discussed alongside stated quantitative criteria.
2. Summarize manager observations of progress and employee explanations objectively.
3. Itemize agreed support resources, coaching pairing, and the date of the next formal checkpoint.
Output in clean, structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.