How to Do a Performance Improvement Plan (With Timeline)

A performance improvement plan runs on a clock. You spend about two weeks preparing before anyone is told. Then you hold a first meeting on Day 1 and check in weekly. You review the numbers at the midpoint and decide when the plan ends at Day 30, 60 or 90.
Many guides answer the search "how to do performance improvement plan" with a list of steps for writing the document. This guide spends its time on what comes after the paperwork, because that is where plans succeed or quietly fail.
You will get a day-by-day timeline, pre-start checks, a Day 1 meeting structure, a midpoint decision table and a close-out process. You will also see how the same plan changes for shift-based and frontline employees, who may work different shifts from the manager running the plan.
Key Takeaways
- A PIP is a dated sequence, not a document. Table 2 maps the full clock from two weeks before Day 1 to a 30-day follow-up after the close.
- Run a pre-flight check before you write anything: evidence, an even standard, prior feedback, protected activity, and a root-cause look at the job itself.
- Write each target with a metric, a baseline, a goal date and a data source. "Be more accurate" is not a target.
- The midpoint review is the decision point to protect. Use it to continue, adjust the support, or involve HR on next steps while there is still time.
- Plans for rotating-shift and multi-location teams need check-ins fixed to a shift overlap and measures that exist on every shift.
- HR Cloud's Performance Management pages describe goals, check-ins and review cycles. They do not describe a dedicated PIP form, so the plan document itself stays with your HR team.
What Is a Performance Improvement Plan, and Who Does What?
A performance improvement plan (PIP) is a written, time-limited plan. It names a performance gap, sets measurable targets, lists the employee's support and schedules reviews to a decision date. HR Cloud's PIP definition page covers the basics, and our performance improvement plan template guide gives you the fill-in version. This guide covers the sequence around the template.
A PIP involves three parties, and plans stall when the roles blur. The manager runs the plan day to day. HR reviews it for consistency and risk, and keeps the record. The employee does the work and tells you what is getting in the way.
| Role | Owns | Does not own |
|---|---|---|
| Manager | Evidence, targets, weekly check-ins, delivering the promised support, check-in notes | The decision to end employment, legal interpretation |
| HR | Plan review, consistency with how similar cases were handled, records, escalation to counsel | Daily coaching |
| Employee | Meeting the targets, raising blockers early, asking for the support listed in the plan | Writing the targets alone |
Table 1. Who owns what in a PIP
Why this matters for managers: The manager column carries the heaviest weekly workload. Gallup's 2026 State of the Global Workplace report found that global manager engagement fell from 27% to 22% between 2024 and 2025. A stretched manager may skip the weekly check-ins that make a PIP fair. Block that time on your own calendar first.
How Long Should a Performance Improvement Plan Last?
Plans commonly run 30, 60 or 90 days. Published manager guides from Paycor and Sage both describe a 30 to 90 day range. Paycor ties the length to how severe the issue is, and Sage says it can vary by company or team. Neither guide presents the length as a legal requirement. Check your union agreement, handbook and state rules with HR, then choose the length from the work itself.
Pick the length by asking how long it takes for the measure to show a real trend. An accuracy rate recorded every shift shows direction within a few weeks. A skill like running a team huddle or closing a complex account may need 90 days to show up more than once.
Scale the checkpoints to the length you choose. The midpoint review sits at half the plan: Day 15, 30 or 45 for plans of 30, 60 or 90 days.
Table 2 shows the clock for a 60-day plan. Writing the plan is the second row. The rows around it decide whether the plan is fair and whether it works.
| When | What happens | Manager | HR | Document produced |
|---|---|---|---|---|
| Days -14 to -4 | Pre-flight check | Gathers evidence, compares to peers, checks prior feedback | Reviews the file and flags risk | Evidence summary |
| Days -3 to -1 | Write the plan | Drafts gap, targets, support, schedule | Reviews for consistency | Draft PIP |
| Day 1 | Kickoff meeting | Delivers the plan, listens | Attends, takes notes | Signed acknowledgment |
| Days 2 to 29 | Weekly check-ins | Reviews numbers, delivers support | Spot-checks the record | Written check-in notes |
| Around Day 30 | Midpoint review | Presents progress, proposes a decision | Joins the decision | Midpoint summary |
| Days 31 to 59 | Weekly check-ins continue | Same as above, with any adjustments | Same | Check-in notes |
| Day 60 | Close-out meeting | Reports results against each target | Reviews outcome and next step | Closing summary |
| Days 61 to 90 | Follow-up | Monitors, tells the employee how it is going | Files the record | Follow-up note |
Table 2. The PIP clock for a 60-day plan
Why the clock matters: Each row after Day 1 repeats a promise you made on Day 1. If the plan promises weekly check-ins and you hold three of eight, the employee can argue the plan was not a real chance to improve. Put each date on the calendar before the Day 1 meeting.
What Should You Check Before Starting a Performance Improvement Plan?
Spend the two weeks before Day 1 on a pre-flight check. A plan built on thin evidence or an uneven standard is hard to repair with good check-ins later, so the problems worth catching start here. Work through these six questions in order, and stop if one of them changes your answer.
- Can you describe the gap in observable terms? Write what happened, on which dates, against which written standard. "Poor attitude" fails this test. "Missed the shift-start handoff in six of the last ten shifts" passes it.
- Is the standard applied evenly? Compare the employee against peers in the same role, same shift and same period. If four others miss the same target, you have a team problem rather than a PIP.
- Has the employee heard this before? A PIP should not be the first time someone learns the standard is not being met. If the only prior feedback was verbal, write down when it happened and what was said. If there was none, start with a documented coaching conversation and give it a short window. Some employers call this an informal PIP. It gives the employee a fair first signal before anything formal begins.
- Is there protected activity or leave in the picture? Check whether the employee recently raised a complaint, asked for an accommodation or requested leave. The next section covers the guidance.
- Is the job itself part of the problem? Look at unclear expectations, missing training, broken tools, schedule changes and workload. If the gap traces to the system, fix the system first.
- Has HR reviewed it? Walk through the file with HR before writing the plan. Ask whether a union agreement, handbook promise or state rule changes the process.
What Do the Legal Checks Look For?
This is general information, not legal advice. Employment counsel should review any plan that touches the situations below, and state and local rules vary.
Retaliation risk. The EEOC's enforcement guidance on retaliation says an action is materially adverse if it might well deter a reasonable person from engaging in protected activity. The guidance lists warnings, lowered evaluations and scrutinizing someone's work or attendance more closely than others' without justification among the possible examples. It also notes that higher appraisals before the protected activity, with no new performance problems, can support an inference of retaliation. If your employee complained last month and the first documented gap appears this month, ask HR to review the timeline before you proceed.
Accommodation requests. EEOC's guidance on reasonable accommodation says an employee need not use the phrase "reasonable accommodation", and that a request starts an informal, interactive process. The same guidance says employers are not required to lower production standards that apply to everyone. It adds that an accommodation may be needed so the employee can meet the standard. If the performance gap may connect to a medical condition the employee has mentioned, talk to HR before the PIP, not after it.
Family and medical leave. The Department of Labor's FMLA page says covered private employers have 50 or more employees in 20 or more workweeks. Employees are eligible with 12 months at the employer, 1,250 hours in the prior 12 months, and a worksite with at least 50 employees within 75 miles. Federal regulations at 29 CFR 825.220 say FMLA leave may not be held against an employee in discipline or counted under no-fault attendance policies. If any of the gap period overlaps with leave, ask HR whether and how to exclude it from your evidence.
Unionized workplaces. The NLRB says the right to request a representative arises during an investigatory interview, and that under current Board law only union-represented employees have it. The NLRB General Counsel has asked the Board to restore a broader rule, so check current law. Check your agreement and ask HR whether any step of your process counts as an investigatory interview.
At-will employment. Under the at-will model, as HR Cloud's glossary explains, either side can end the relationship at any time for any lawful reason, though exceptions and state rules apply. A handbook, contract or past practice that promises a PIP may change that, so ask HR.
Hypothetical example: A distribution center team lead notices that an order picker's accuracy has dropped. The standard is 98% pick accuracy. The picker's eight-week average is 91%, while the other eleven pickers on the same shift average 98% or higher, and none average below 97%. The lead checks the six items on the list. The standard is applied evenly, there is no leave or accommodation flag, and HR sees nothing unusual in the file. But the only prior feedback was a hallway comment. So the lead schedules a documented coaching conversation first, writes up what was said, and sets a two-week window. Only if accuracy stays flat does the lead move to a formal plan, now with a documented first conversation behind it.
A check before you move on: If you can't answer question 1 in writing, with dates and a standard, don't write the plan yet. Fix that first.

How Do You Write the Plan Itself?
Write the plan in the three days before Day 1. It has six parts, and each one answers a question the employee will ask in the meeting.
- The gap: What is happening, on which dates, compared with which written standard?
- The targets: What exactly must change, by when, and how will it be measured?
- The support: What will you provide, and by what date?
- The schedule: When are the check-ins, the midpoint review and the close-out?
- The outcomes: What happens if the targets are met, and what happens if they are not?
- The acknowledgment: A line for the employee's signature that confirms receipt, not agreement.
How Do You Write a Target That Can Be Measured?
A usable target has four fields: the metric, the baseline, the goal with its date, and the data source. The baseline matters because it shows the employee where they start. The data source matters because it settles disagreements before they start.
| Weak target | Measurable version |
|---|---|
| Be more accurate | Reach 95% pick accuracy by Day 30 and 98% by Day 60, measured weekly from the pick report. Baseline: 91% over the prior eight weeks. |
| Communicate better | Post a shift-end handoff note covering open orders on 5 of 5 scheduled shifts each week, checked in the handoff log. |
| Be on time | Arrive by the scheduled shift start on 9 of 10 shifts in each two-week period, per the time records. |
| Improve customer service | Reach an average of 4.0 or higher on post-interaction survey scores by Day 45, reviewed weekly. |
Table 3. Weak targets and their measurable versions (illustrative examples)
Limit the plan to a small number of targets. Two or three are easier to track and easier for the employee to focus on than ten. If you can't choose, pick the targets that matter more to the business and defer the rest to the normal performance cycle.
How Do You Choose the Support?
Support is half of the plan, and it should match the gap. If the problem is skill, offer training, shadowing or a peer mentor. If the problem is clarity, give written expectations and examples of acceptable work. If the problem is workload or tools, name what you will change.
Each item needs an owner and a date, and the owner may be you.
Why the order holds: Drafting targets before support keeps you honest. If you can't name support that would plausibly help the employee reach the target, the target may not be realistic. Revisit it before Day 1, not after.
How Do You Run the Day 1 Meeting?
The Day 1 meeting sets the tone for the next 60 days, so give it a structure. Hold it in private with HR in the room. Schedule it so the employee isn't heading straight back onto a busy floor afterward. Bring two copies of the plan, one to hand over and one for the file.
Use this sequence:
- State the purpose in one sentence. Say the plan exists to close a specific gap and that you will help.
- Name the gap with evidence. Share the dates, the standard and the data. Keep it to facts you gathered in the pre-flight check.
- Walk through the targets. For each target, say the metric, the baseline, the goal date and the data source.
- Walk through the support, including your own commitments. Say what you will provide and by when.
- Give the schedule. State the check-in day and time, the midpoint review date and the close-out date.
- Explain the outcomes plainly. Say what happens if the targets are met and what the next step may be if they are not. Do not predict the result.
- Ask for the employee's response. Ask what is getting in the way. Write the answers down and treat them as inputs to the support list.
- Hand over the plan and ask for an acknowledgment signature. The signature confirms the employee received it.
Sample opening wording: "This plan is about closing a gap in pick accuracy. Here is the standard, here is where you are now, and here is what I will do to help you close it."
Avoid four things in the room. Skip commentary on personality or attitude, because the plan covers observable work. Skip comparisons to named colleagues. Skip promises you can't keep, such as "you'll be fine if you try harder." And skip reading the document aloud, which turns a conversation into a recitation.
Hypothetical example: The distribution center lead from earlier delivers a 60-day plan to the picker. The targets are 95% accuracy by Day 30 and 98% by Day 60, against a baseline of 91%. The lead commits to two shadow shifts with a senior picker in week one, a scanner check by Day 5 and a weekly accuracy report each Friday. Check-ins are set for Fridays after the report. The picker says the scanner has been misreading labels on one aisle. The lead writes that down and adds an equipment check on that aisle to the support list.
Manager tip: Give the employee time after the meeting. A short pause before the first check-in lets the plan sink in. It also gives you time to finish the week-one support you promised.
What Happens in the Weekly Check-Ins?
Weekly check-ins are where a PIP is won or lost. Hold them on the same day and time each week, and keep them short and consistent. If the employee works rotating shifts, fix the check-in to a shift overlap, and see the frontline section below.
Run each check-in with the same agenda:
- Numbers since last time. Compare the latest figures to the target and to the baseline.
- What helped and what got in the way. Ask the employee first.
- Support delivered and support owed. Check your own commitments as well as theirs.
- Focus for the coming week. Pick one or two things.
- Written summary. Send it to the employee and file it with HR.
Record the same fields in each note: the date, each measure against its target, the support delivered, the employee's comments, and the next step. Consistent notes make the record fair to the employee and clear to anyone who reads it later. They also keep you from relying on memory in week six.
Two rules keep the check-ins honest. First, no surprises: if the numbers are behind in week two, say so in week two, not at the midpoint. Second, recognize progress when it happens, and write it down. A plan that records only misses reads as a case file and feels like one to the employee.
If the employee raises a complaint, a health concern or a leave request during the plan, stop and call HR before the next step. That moment can change how the plan should be handled and how the record will be read later.
Where this goes wrong: One failure to watch for is a plan that starts with energy and then fades. Check-ins slip to every other week, notes get thin, and the support you promised doesn't arrive. By the midpoint, the employee has a stronger argument than you do.
How Do You Run the Midpoint Review?
The midpoint review is a decision point worth protecting. It happens at half the plan, around Day 30 for a 60-day plan. Prepare a one-page summary of each target, the figures to date and the support delivered. Then decide with HR which of the four situations in Table 4 you are in.
| Midpoint signal | What it suggests | Manager move |
|---|---|---|
| At or above the midpoint target | The plan is working | Say so plainly, keep the schedule, keep recognizing progress |
| Below target but moving in the right direction | The gap is closing more slowly than planned | Keep the targets, adjust the support, document why |
| Below target and flat | The support may not address the cause, the target may be unrealistic, or the role may not fit | Bring HR in, revisit the root cause, decide the next step before the plan runs out |
| The employee has raised blockers you haven't resolved | The plan's fairness is at risk | Fix your side first, document the fix, consider whether the dates still make sense |
Table 4. Midpoint signals and manager moves
Share the outcome of the review with the employee in writing the same day. If you adjust the support or any date, record the reason. Changing a target mid-plan is reasonable when the data shows it was unrealistic, but it needs a stated reason and HR's agreement.
Hypothetical example: At Day 30, the picker's accuracy is 94%. That is 3 percentage points above the 91% baseline and 1 point under the Day 30 target of 95%. The picker needs 7 points of improvement in total to reach 98%, so 3 of 7 is a visible start. The lead and HR agree the trend is positive and the scanner fix helped. They keep the targets, add two more shadow shifts with the senior picker, and note the reason in the midpoint summary.
What HR watches for: HR looks for consistency between the midpoint summary and what the check-in notes say. If the notes were upbeat for four weeks and the summary is suddenly negative, expect questions. Keep the tone of your written record steady with what actually happened.


How Do You Close a Performance Improvement Plan?
On the last day, hold a close-out meeting and report the result against each target. The data decides the conversation, not your overall impression. Prepare a closing summary that lists each target, the final figure, and the support delivered. Then walk through one of the three outcomes in Table 5.
| Outcome | Evidence | Next step | Document |
|---|---|---|---|
| Targets met | Final figures at or above each target | Close the plan, confirm in writing, return to the regular review cycle, schedule a follow-up | Closing summary, follow-up dates |
| Partly met | Some targets met, or clear progress short of the goal | Extend only with a stated reason and new dated targets, or adjust the support or the role | Reason for extension, new targets and dates |
| Not met | Targets missed despite the support listed in the plan | HR and counsel review the full record before any decision is made or communicated | Closing summary with each target's result |
Table 5. PIP outcomes and next steps
Treat an extension as a decision, not a drift. A reasonable extension names what changed (for example, a support item arrived late) and gives new dated targets. An open-ended extension tells the employee the goalposts can move.
If the targets were met, say so clearly and recognize the effort. Then keep the follow-up promise. In a 60-day plan, a follow-up window through Day 90 gives you room for a few light check-ins to confirm the gain holds. After that, the employee returns to the normal review cadence, and the PIP closes as a record rather than a label.
If the targets were not met, do not make the decision in the meeting alone. A decision to end employment should go through HR and legal review. It should rest on the complete record: the evidence, the support delivered, the check-in notes and the midpoint summary. The manager should not make or deliver that decision alone.
What to remember: The close-out meeting should contain no news the employee hasn't already seen in the weekly check-ins and the midpoint summary. If it does, the process failed at an earlier step.
How Does a PIP Change for Frontline and Shift-Based Teams?
A plan built for an office team on a shared schedule can fail for frontline staff, who may work different hours from their manager. HR Cloud's guide on who counts as a frontline worker covers the workforce in more detail. For the PIP, four adjustments matter.
- Fix the check-in to a shift overlap. Choose a recurring slot when both people are on site, and keep it inside the employee's scheduled hours. Ask HR how your pay rules apply if a meeting runs past the shift.
- Pick measures that exist on each shift the employee works. A target observed only on the manager's shift misses data from other shifts.
- Name one plan owner. If several supervisors cover different shifts, they send their observations to the owner, who writes the weekly note. The employee should hear one consistent message.
- Keep the plan reachable. HR Cloud's performance management page notes that employees can access their data through the HR Cloud mobile app, which helps away from a desk.
Hypothetical example: A home care agency's scheduling coordinator works two rotating shifts, and the branch manager is on site only during days. The plan target is to send visit confirmations to caregivers by 3 p.m. the day before on 9 of 10 working days. The system's sent log provides the data on both shifts. The check-in is fixed to the Tuesday overlap, and the evening supervisor sends the manager a short note each Thursday. The plan owner stays the same throughout.
Why frontline plans differ: The data source can decide whether the plan is fair. If the measure lives in a system that records each shift, the plan is fair across schedules. If it depends on one supervisor's recollection, the plan is open to challenge from the first week.
What Mistakes Undermine a Performance Improvement Plan?
Several avoidable patterns undermine a plan. Table 6 pairs each one with a fix.
| Mistake | Why it hurts | Fix |
|---|---|---|
| No prior feedback | The employee is surprised, and the plan reads as a verdict | Hold a documented coaching conversation first |
| Vague targets | No one can tell whether they were met | Use a metric, baseline, goal date and data source |
| Support listed but not delivered | The plan reads as paperwork | Give each support item an owner and a date, and track your own side |
| Check-ins that slip | The record thins and trust drops | Calendar all dates before Day 1 |
| An uneven standard | Raises fairness and discrimination questions | Compare peers and ask HR to review |
| A plan written only to document an exit | The employee may sense it, and the effort stops | Write each target as something you want them to reach |
| No HR involvement until the end | Risk surfaces too late to fix | Bring HR in during the pre-flight check |
Table 6. PIP mistakes and fixes
Pattern to notice: Each mistake in the table is a gap between what the plan says and what the manager does. The plan is only as credible as the follow-through, and the follow-through is visible to the employee each week.
Where Does Software Help With a Performance Improvement Plan?
Software can't write the plan or make the decision. It can keep dates, goals and progress in one place, so the record doesn't live in a manager's inbox. HR Cloud's Performance Management is built around goals, check-ins and review cycles, and its Goal Tracking page describes real-time progress tracking.
In HR Cloud's help center, a goal is created in the Perform app's Goals tab. The form takes a name, an optional description, a goal type, start and due dates, assignees and optional attachments. The assignee records progress with the Check-in button, entered as a percentage. Goals can also be attached to a review when Goal Tracking was enabled for that cycle during cycle setup.
What to expect: HR Cloud's product pages and the help center articles reviewed for this guide do not describe a PIP template or a PIP-specific workflow. Keep the plan document with HR and use goals and check-ins to track the targets. Record the actual figures in your weekly note, since the check-in field records percentage progress. Performance management is included in the Growth and Full Suite plans, and not in Onboard. Pricing is quoted by headcount, plan and add-ons, per the pricing page.
What Should You Do in the Next 48 Hours?
If you are working out how to do performance improvement plan prep this week, start with three steps you can finish in two days.
- Write the gap statement and run the six pre-flight questions. Put the dates, the standard and the evidence on one page. If question 1 or 3 fails, plan a coaching conversation instead.
- Draft two or three measurable targets. For each, fill in the metric, baseline, goal date and data source, then list your support.
- Book HR and put each date on the calendar. Schedule the HR review, Day 1, each weekly check-in, the midpoint review and the close-out.
Why 48 hours: The calendar work is the step that gets skipped. Once the dates exist, the plan has a shape, and the weekly rhythm is much harder to let slide.
Discover how our HR solutions streamline onboarding, boost employee engagement, and simplify HR management
Book a DemoFrequently Asked Questions
How long does a performance improvement plan last?
Plans commonly run 30, 60 or 90 days, and published manager guides describe a 30 to 90 day range. No single length fits all gaps. Choose the duration by how long the measure takes to show a trend. Set the midpoint review at half the plan, such as Day 30 for a 60-day plan.
How does a performance improvement plan work?
In short, how to do performance improvement plan work comes down to a dated sequence. Prepare the evidence, write measurable targets with support, meet on Day 1, check in weekly, review at the midpoint and decide at the end. Each step is documented so the employee knows where they stand.
When should a manager use a performance improvement plan?
Use one when there is a documented gap against a written standard, the employee has heard about it before, and support could plausibly close it. Hold off if the gap traces to unclear expectations or workload. Also pause if a complaint, accommodation request or leave is involved and HR hasn't reviewed it.
What does a performance improvement plan look like?
It is a short written document with six parts: the gap, the targets, the support, the schedule, the outcomes and an acknowledgment line. Each target lists a metric, a baseline, a goal date and a data source. Our performance improvement plan template guide has a fill-in version.
Can a performance improvement plan be extended?
Yes, if your policy allows it. Extend only with a stated reason, such as support that arrived late, and set new dated targets with HR's agreement. An extension without a reason or new dates tells the employee the goalposts can move, which weakens the whole plan.
Is there an informal performance improvement plan?
Some employers use the term for a documented coaching conversation with a short window and clear expectations, but without the formal plan structure. It gives the employee a fair first signal. It is a sensible step when the gap has not been raised in writing before.
How do you write a performance improvement plan for a sales employee?
Use targets the employee controls, such as activity and conversion measures, alongside revenue, and set each against a baseline and a goal date. Compare the employee to peers with similar territories or pipelines, and ask HR to review. Revenue alone can hide whether the gap is skill or territory.
Does HR Cloud include performance improvement plan software?
HR Cloud Performance Management covers goals, check-ins and review cycles, according to its product page and help center. Those pages do not describe a PIP template or workflow, so the plan document stays with HR while goals and check-ins track the targets. It is included in the Growth and Full Suite plans.
About the author

Like What You Hear?
We’d love to chat with you more about how HR Cloud® can support your business’s HR needs.
Book Your Free Demo

