SteadyFile
Back to blog
performancepipworkplace

Performance management records to keep before a PIP meeting

What to save when you are put on a performance improvement plan: the plan, past reviews, metrics, support asked for, and a factual note after each check-in.

Updated 9 min read

Quick answer

Before a performance improvement plan (PIP) meeting, save a personal copy of the plan itself, your previous performance reviews, the goals you were given, and any reports showing how your work is measured. Add a list of support you asked for and what you received, such as training, tools or clarified priorities.

During the plan, write a short factual note after every check-in: date, who attended, what was reviewed, what you were told, and what was agreed. Go into each meeting with questions that clarify what success looks like, rather than arguments about the past.

The plan document is the centre of the file

PIPs vary a lot between employers, but most set out the concerns, the goals you are expected to meet, a time period, a schedule of check-ins and sometimes what may happen if the goals are not met. Whatever its format, the plan is the document every later conversation refers back to, so keep your own copy from the day you receive it.

Note the date you received it, how it was delivered (in a meeting, by email, through an HR system) and who gave it to you. If it was presented on screen in a meeting and not sent to you, ask for a copy and note when you asked. If a revised version appears later, keep both and record what changed. Plans sometimes shift mid-way, and a reviewer will want to see the version you were actually working toward at each point.

Records worth gathering now

Gather documents that are yours to keep, such as reviews, letters and messages addressed to you. Where something exists only in an employer system, note what it is and where it lives rather than exporting company data.

  • The PIP and any cover letter or email that came with it.
  • Your last two or three performance reviews, including any ratings and written comments.
  • The goals or objectives set for you at the start of the year or the start of the role.
  • Your job description or posting, to compare with what the plan now expects.
  • Messages praising your work, thanking you, or approving work the plan now criticizes.
  • Records of workload changes: new accounts, added responsibilities, a colleague leaving without replacement, system changes.
  • Your requests for training, tools, clearer priorities or accommodation, and the replies.
  • Any written feedback between reviews, such as one-on-one notes your manager shared with you.

Understanding how the targets are measured

Many plans rely on numbers: tickets closed, calls handled, sales, error rates, turnaround time. A number only means something once you know how it is counted. Before the first check-in, write down what you understand about each metric and mark anything that is unclear.

  • What exactly is counted, and what is excluded, such as escalated cases or work done for another team.
  • Who produces the report and how often.
  • What the target is and whether it is the same target others in the role have.
  • What your numbers were before the plan, as a baseline.
  • Whether anything outside your control affects the number, such as system outages or reassigned accounts.
  • Whether the target or the way it is measured changes during the plan, and the date of any change.

If you can see your own figures in a dashboard, note them weekly in your personal file in your own words, for example 'week of June 8: 41 tickets closed per dashboard, target 50.' That gives you a running record without copying company reports.

Support you asked for, and support you got

Plans often promise support: coaching, training, regular feedback, shadowing a colleague. Keep a simple two-column log: what you asked for or were promised, with the date, and what actually happened, with the date. 'Asked for training on the new billing system, June 2, by email. One 45-minute session held June 19.' The log is useful whether the support was generous or thin.

If a health condition, disability, family situation or religious practice affects your work, the discussion may involve accommodation. In Canada this is usually discussed as the duty to accommodate under human rights law, and in the United States the EEOC describes an interactive process under the Americans with Disabilities Act. The EEOC's guidance says a request does not have to be in writing, but keeping your own dated record of when and how you raised it, and what followed, makes the conversation easier to follow later. Rules differ by jurisdiction, so a qualified reviewer can tell you how they apply to you.

A factual note after every check-in

Check-ins are where a PIP is actually decided, and they are often not minuted. Your own note, written the same day, may be the only record of what was said. Keep it short and consistent:

  1. Date, start and end time, and format (in person, video, phone).
  2. Who attended, by role, such as your manager and an HR partner.
  3. Which goals or metrics were discussed and what figures were mentioned.
  4. What you were told about your progress, in their words where you are sure of them.
  5. What you said, including questions you asked and the answers.
  6. Anything agreed or promised, with any deadline.
  7. Documents shown or sent, and whether you received a copy.

An invented example: 'Week 3 check-in, Thursday, June 25, 2:00 to 2:30 p.m., video. Present: my manager, HR partner. Reviewed turnaround time: manager said I averaged 2.4 days against a 2-day target. I asked whether tickets waiting on another team count toward my time. Manager said they do for now and would confirm with the reporting team. Agreed: manager to send the confirmation by June 30. No document shared.'

Some people also send a brief, polite email after a check-in summarizing what they understood was agreed. If you do, keep it to facts and next steps, and save your own copy of what you sent.

Questions that clarify instead of argue

It is natural to want to correct the record in the first meeting. A calmer approach, and usually a more useful one, is to make sure you understand exactly what is expected. Clear answers also make your later notes far more meaningful. Questions you might prepare:

  • What would meeting each goal look like in practice, week by week?
  • Which of these goals matters most if I cannot move on all of them at once?
  • How will progress be measured, and can I see the same report you will use?
  • What support will be available, and who should I go to for it?
  • How often will we meet, and will I receive written feedback after each check-in?
  • If my workload or the metric definitions change during the plan, how will that be handled?

If you disagree with parts of the plan, note your specific points in your file with the documents that support them. Whether and how to raise disagreement formally is a decision you can make with better information, possibly after speaking with a union representative or lawyer.

Habits that make a PIP file weaker

  • Rewriting check-in notes days later to sound stronger. If you add something, date the addition.
  • Forwarding client files, reports or internal data to a personal account to prove your numbers.
  • Arguing point by point in long emails that you may later regret.
  • Posting about the plan on social media, even without naming anyone.
  • Recording meetings without first checking whether that is lawful where you are and allowed by workplace policy.
  • Keeping your only notes in a work notebook or on a work laptop.

Common questions

Do I have to sign the PIP? Many plans ask for a signature that acknowledges receipt, but what a signature means depends on the wording. If you are unsure, ask what the signature represents and note the answer. A lawyer or union representative can explain what it may mean for you.

Can I add my own comments to the plan? Some employers allow written comments on reviews or plans. If yours does, keep them factual and brief, and keep a copy. If not, your own dated notes still preserve your view.

What if the plan came soon after I raised a concern or asked for accommodation? Write down both dates and what happened in between, without drawing a conclusion. The US Equal Employment Opportunity Commission lists a lower performance evaluation and increased scrutiny among its examples when it explains retaliation, but whether that applies to any situation is a question for a qualified reviewer.

What happens if the plan ends in termination? Outcomes and rights after a job ends depend on your contract, any collective agreement and the laws where you work. Official sources such as the Government of Canada's federal labour standards pages and the US Department of Labor's termination page give general starting points.

Keeping a PIP file in SteadyFile

A PIP produces exactly the kind of material SteadyFile is designed to hold: one plan, a series of dated check-ins, metrics that change week to week and a growing set of emails. In a free workplace file at app.steadyfile.com, each check-in becomes a dated entry with who attended by role and what was said, and the plan, reviews and support requests get IDs in a records index you can link from each entry. Unclear metric definitions go to the gaps and questions list so they are ready for the next meeting. With an account, entry times and edit history stay visible. The exported packet lays the plan period out in order for a lawyer, union representative or advisor, and your employer never has access to it.

Sources and further reading

These links informed the topic framing. They are provided for general information; SteadyFile does not endorse or control third-party sites.

Prepare the file, then get qualified advice

When a situation is sensitive, organize the facts and questions first. Then bring the packet to the person who can help: a lawyer, a legal clinic, a union rep, HR or another advisor.

Translations are provided to make SteadyFile easier to use. Legal terms may vary by location. SteadyFile does not provide legal advice.