Evidence-Based Probation Performance Review

Write probation review feedback grounded in observed facts, not impressions.

Prompt · 3 variables

You are an HR manager who has reviewed and returned numerous {{job position role}} probation review forms. You know that generic summaries without concrete evidence explain nothing in the long run.

I need to write a probation performance review for a {{job position role}} who has worked with us for {{probation period}}. Below are my rough notes capturing various incidents, including both positive accomplishments and areas for improvement.

Categorize the recorded incidents into four categories: Task Execution, Work Attitude, Collaboration, and Growth Pace. For each category, attach one or two specific supporting observations and write a single-sentence takeaway of what was demonstrated. If a category has no supporting notes, leave it blank and write "No observations recorded."

Format the output using a table followed by paragraphs. First, present a table with columns: Category | Observed Incident (including timeframe) | Verified Capability | Areas Needing Improvement. Below the table, provide an overall summary of around eight sentences. Conclude with 2–3 specific questions or items I should verify before making a final conversion decision.

Do not fabricate any events not present in the notes. Do not force filler content into categories that lack evidence. Avoid character-judging adjectives like "diligent" or "highly responsible"; describe strictly what happened and when. Do not include legal conclusions or formal contract statements. In the overall summary, summarize the evidence neutrally without declaring a final pass/fail verdict.

Observation Notes: """ {{observation case}} """

Copy, then paste here · ChatGPT and Claude open with the prompt filled in Open in ChatGPT ↗Open in Claude ↗Open in Gemini ↗ Edit in builder Download classroom card

Some variables here may contain personal data. Replace real names, numbers and company names with placeholders.

Why it is written this way

Role
You are an HR manager who has reviewed and returned numerous {{job position role}} probation review forms. You know that generic summaries without concrete evidence explain nothing in the long run.
Context
I need to write a probation performance review for a {{job position role}} who has worked with us for {{probation period}}. Below are my rough notes capturing various incidents, including both positive accomplishments and areas for improvement.
Task
Categorize the recorded incidents into four categories: Task Execution, Work Attitude, Collaboration, and Growth Pace. For each category, attach one or two specific supporting observations and write a single-sentence takeaway of what was demonstrated. If a category has no supporting notes, leave it blank and write "No observations recorded."
Format
Format the output using a table followed by paragraphs. First, present a table with columns: Category | Observed Incident (including timeframe) | Verified Capability | Areas Needing Improvement. Below the table, provide an overall summary of around eight sentences. Conclude with 2–3 specific questions or items I should verify before making a final conversion decision.
Constraints
Do not fabricate any events not present in the notes. Do not force filler content into categories that lack evidence. Avoid character-judging adjectives like "diligent" or "highly responsible"; describe strictly what happened and when. Do not include legal conclusions or formal contract statements. In the overall summary, summarize the evidence neutrally without declaring a final pass/fail verdict.
Input
Observation Notes: """ {{observation case}} """

When probation reviews are rushed the day before the deadline, they often end up with vague statements like "Showed good work ethic and adapted well." Such generic phrasing can be used to justify both passing and failing an employee, offering zero actionable explanation to the individual. Months later, when asked why a decision was made, nothing remains but faded memories.

Task demands specific scenes rather than vague impressions. Grouping observations into four defined categories and requiring evidence for each immediately exposes gaps in observation. Explicitly permitting "No observations recorded" is crucial—without this, the AI will fabricate plausible fluff, which then gets documented as fact.

Format separates the content into a structured table and a summary paragraph to serve different readers. HR checks the table to verify concrete evidence, while management reads the narrative summary. Blending both into a single text block often dilutes the factual basis. Setting the Role as an HR manager who rejects weak reviews prompts the AI to critically scrutinize whether every statement is backed by proof.

Constraints forbid making a definitive hiring verdict because employment decisions belong strictly to human managers; if the model declares "Conversion recommended," reviewers tend to rely on it uncritically. Wrapping the raw notes in """ prevents random fragments from being misinterpreted as instructions. Prompting for "Items to verify further" ensures managers address remaining blind spots before rushing to a premature conclusion.

Unfamiliar terms? See Aha AI: hallucination, output-format

Compared with a bad example

Common bad example

Write a probation review for an employee who worked for 3 months and did fine.

This produces empty filler like "Diligently performed assigned tasks and adapted well to the team." Such generic lines cannot be used for meaningful 1:1 feedback or submitted to HR as valid documentation. Real incidents—like missed deadlines or rework—disappear, while non-existent achievements may be fabricated.

Variations

Delivering Constructive Feedback to the Employee

Delivering Constructive Feedback to the Employee

From the {{probation period}} observation notes below, select only the areas needing improvement and rewrite them into talking points for a direct 1:1 feedback session. For each point, structure it within three sentences: The specific incident · The resulting impact · The expected standard for the next 3 months. Avoid judgmental personality labels, and include one sentence per point detailing how I will support their growth.

""" {{observation case}} """

Written evaluation language differs from spoken feedback. This shifts the conversation from a one-sided verdict into an alignment on future performance standards.

Mid-Probation Check-In Template

Mid-Probation Check-In Template

We have reached the midpoint of the {{probation period}} for our {{job position role}}. Based on the observations below, generate a mid-probation check-in table. Organize it into three columns: Capabilities Verified So Far · Items Not Yet Verified · Tasks to Assign for the Remaining Period. Describe specific behaviors to observe in the remaining time to make an informed final decision. Do not make a final pass/fail conclusion.

""" {{observation case}} """

Discovering a lack of evidence at the end of probation is too late. Conducting a mid-term review clarifies exactly what behaviors need to be monitored during the remainder of the period.

Model notes

The final employment decision is not for the AI to make. Use the AI strictly to organize the evidence, and determine the evaluation verdict yourself.

Related prompts

Last updated 2026-09-02 · Found a mistake? Let us know