What to Include in a 30-60-90 Day PIP (With Examples)

One of the first decisions a manager faces when issuing a Performance Improvement Plan is how long it should be. The three most common formats are 30, 60, and 90 days. Each suits different situations — and choosing the wrong one can either rush the employee unfairly or drag out a process that should have concluded sooner.

This guide covers how to choose the right PIP duration, what to include in each format, and examples of each to help you structure your plan.

How to Choose the Right PIP Duration

30-day PIP

Best for situations where:

• The performance issues are relatively contained and well-defined
• The employee’s role produces results quickly (sales, customer service, high-frequency output roles)
• Prior warnings and coaching have already been extensive
• The gap between current performance and the standard is serious and the organization needs a resolution soon

A 30-day PIP moves fast. The employee has less time to demonstrate improvement, and check-ins need to be frequent — ideally weekly. This format is appropriate when the situation is urgent, not when the manager simply wants it over with.

60-day PIP

Best for:

• Most standard performance situations
• Roles where results take more than a week to measure meaningfully
• Situations where the employee has some genuine improvement trajectory but needs structure and accountability to sustain it
• First-time formal performance processes where the employee deserves adequate time

The 60-day format is the most common because it balances urgency with fairness. It allows for a 30-day check-in to assess early progress, mid-period coaching, and a final evaluation.

90-day PIP

Best for:

• Complex performance issues spanning multiple areas
• Roles with longer output cycles (project management, engineering, strategy roles)
• Situations where meaningful improvement requires skill development that takes time
• Organizations where the process requires this minimum period (some company policies or employment contracts specify 90 days)

A 90-day PIP is not appropriate when the issues are clear and the standard has been communicated for months. A longer timeline in those situations prolongs uncertainty for everyone and can signal to the employee that the consequences are not real.

The 30-Day PIP: Structure and Example

Structure

• Milestones: One formal mid-point check-in at day 15, final evaluation at day 30
• Check-ins: Weekly
• Goal type: Immediately measurable, daily or weekly output

Section breakdown

Performance issues: [Specific and documented — e.g., “Closed revenue over the past 60 days has averaged $14,000 against a monthly target of $28,000.”]

Goals:

1. Achieve a minimum of $22,000 in closed revenue in the 30-day PIP period (measured via CRM on the last business day of the month).
2. Complete a minimum of 15 documented outbound calls per day (logged in CRM by 5pm each day).

Timeline:

• Week 1–2: Daily activity tracking reviewed in weekly check-in. Manager provides coaching on call conversion.
• Day 15: Formal mid-point check-in — review CRM activity data and pipeline status.
• Day 30: Final evaluation — measure closed revenue and review call logs.

Support:

• Weekly 30-minute coaching sessions with the sales manager
• Access to two customer objection-handling training modules by Day 5
• Dedicated manager review of three live calls in Week 1

Consequences: If the revenue goal and daily activity targets are not met by Day 30, further disciplinary action, up to and including termination, will follow.

The 60-Day PIP: Structure and Example

Structure

• Milestones: Day 30 formal check-in, Day 60 final evaluation
• Check-ins: Bi-weekly
• Goal type: Monthly or period-based metrics; behavioral goals with observable outcomes

Section breakdown

Performance issues: [“Over the past three months, Emily’s customer satisfaction (CSAT) score has averaged 3.0 out of 5.0, against a team target of 4.0. Four formal client escalations have been attributed to Emily’s cases. These issues were discussed in one-on-ones on [date] and [date] with no sustained improvement.”]

Goals:

1. Achieve a CSAT score of 3.8 or above in the monthly report for each of the two calendar months in the PIP period.
2. Receive no more than one formal client escalation in each of the two months.
3. Submit all client follow-up communications within the 4-hour SLA on at least 95% of cases, as measured in the ticketing system.

Timeline:

• Weeks 1–4: Bi-weekly check-ins. Manager reviews CSAT data and open cases each week.
• Day 30: Formal mid-point review — assess Month 1 CSAT score and escalation count. Adjust support plan if needed.
• Day 60: Final evaluation — review Month 2 CSAT score, escalation count, and response time data.

Support:

• Access to the Customer Communication Excellence course by Day 7
• Weekly case review with team lead for the first four weeks
• Manager will review and provide written feedback on three complex client cases per week during Weeks 1–4

Consequences: If any of the three goals are not met by Day 60, a further disciplinary process will follow, which may include termination.

The 90-Day PIP: Structure and Example

Structure

• Milestones: Day 30 check-in, Day 60 check-in, Day 90 final evaluation
• Check-ins: Bi-weekly
• Goal type: Longer-cycle outcomes; project-based or multi-dimensional performance

Section breakdown

Performance issues: [“Over the past four months, three of Daniel’s five active software projects have experienced delivery delays of more than two weeks. Two projects missed scope requirements at handoff, requiring rework. In a team survey, three colleagues flagged insufficient communication during the planning phase. These issues were discussed in one-on-ones on [dates].”]

Goals:

1. Deliver all assigned projects within the agreed timeline, with no more than one delay exceeding three business days across the 90-day PIP period.
2. Achieve a technical quality score of 90% or above on code review assessments (measured by the team lead’s review checklist) for all pull requests submitted during the PIP period.
3. Send a project status update to all relevant stakeholders at the agreed cadence (weekly, by Friday at 4pm) for the full 90-day period, with no more than one missed update.

Timeline:

• Weeks 1–4: Bi-weekly check-ins. Manager reviews active project timelines and code review scores.
• Day 30: Formal check-in — review delivery record, quality scores, and stakeholder communication log.
• Day 60: Second formal check-in — assess trajectory. Consider whether any adjustment to goals or support is warranted.
• Day 90: Final evaluation — full review against all three goals.

Support:

• Enrollment in a project management fundamentals course by Day 10
• Bi-weekly one-on-one with a senior engineer for technical code review coaching
• Manager will work with Daniel in Week 1 to set up a project tracking system and stakeholder communication template

Consequences: If the performance goals are not met by Day 90, further disciplinary action, up to and including termination, will follow.

Common Mistakes in PIP Timeline Setting

Making it too short to be fair. A 30-day PIP for a project management role where project cycles run six weeks is not achievable. Match the timeline to how long it realistically takes to demonstrate the improvement.

Making it too long to be credible. A 120-day PIP signals to the employee (and to any future reviewer) that the organization lacks the resolve to address the situation. Standard timelines exist for good reason.

Failing to build in formal check-in milestones. A PIP without mid-period reviews runs on autopilot. The employee may not realize they are off track until it is too late to correct.

Extending repeatedly without cause. If a 60-day PIP expires, the manager must make a decision. Extending indefinitely because the conversation is uncomfortable is not a neutral action — it creates its own problems.

Get the Structure Right From the Start

Getting the timeline and milestone structure right is easier with a consistent framework. Templates Hub’s PIP Builder lets managers select their PIP duration and automatically structures the check-in schedule, goal timeline, and evaluation criteria to match — producing a complete, formatted plan without the guesswork.

Summary

The right PIP timeline is determined by the complexity of the performance issues, the measurement cycle of the role, and the organization’s policy. Thirty days suits urgent, high-frequency roles. Sixty days is the standard for most situations. Ninety days is appropriate for complex, long-cycle roles. Whatever the timeline, build in formal milestones, structure the check-ins, and make the goals measurable at each stage.

Related reading:

• How to Write a PIP That Actually Helps Employees Improve
• SMART Goals in a PIP
• How to Have a Performance Improvement Conversation
• Common PIP Writing Mistakes Managers Make
• Performance Improvement Plan Examples by Role
• How to Set a Realistic PIP Timeline
• How to Run a PIP Check-in Meeting
• The Best PIP Templates for Managers in 2025