PROMPT BRO
HR desk

Track probation reviews and draft letters

Probation ended last week. The review meeting is scheduled for next week.

Tested Claude Opus 5.5, medium effort · 15 Nov 2026 · on the practice files

By hand1–2 hrs
With AI15 min
Per month · estimate
Easier on your office computer.Send to my computer
I usePick yours. We'll show the right steps.

Make the probation tracker

Employee code, role, review due date, feedback status and approved decision if any. Use the sample first.

First time? Try it on fake data first:

Confirm letter format

Keep your approved confirmation or extension template in Word. HR decides outcomes, not AI.

Privacy Use employee codes and status only in an approved tool. Remove names, review narratives, personal details and salary figures; fill letters locally.

Fill the orange boxes
You send (the "prompt": the message you paste into your AI tool)
probation-tracker.xlsx

I'm attaching a probation tracker. As on [As on date], flag reviews due in the next [Upcoming window] calendar days including today. A. For every row show overdue (date before as-on), due soon (today through as-on plus window), or later. Show feedback pending and decision pending separately, even if review is later. B. List all overdue and due-soon reviews, plus rows with feedback or decision missing. Do not treat an overdue review as an employment decision. C. Draft one confirmation letter template and one extension letter template only for the approved decision types present. Use [Employee name], [Employee code], [Effective date], [Extension end date], [Approved reason], [Signatory] as needed. I'll fill in Word. Do not invent terms, duration or reasons. Ignore age, gender, religion, caste, marital status, photo, college name and hometown. Never mark down career breaks. A person makes all hiring or appraisal decisions. HR decides confirmation or extension and checks company policy. Do not repeat personal identifiers from the data (personal names, phone numbers, email or postal addresses, bank account numbers, UPI IDs, PAN, Aadhaar, GSTIN or other registration numbers) unless the output genuinely needs one; use the code, ref or row instead, and copy any needed identifier exactly. Keep masked values masked; never guess, complete or unmask them.

Which model? Use your tool's strongest model with thinking turned on.

In your AI tool: attach the files with the + button, paste, send.

What you'll get back (example, from the practice files)
2overdue
3due soon
1later
  • E302Overdue, feedback pending. Due 12 Nov; no decision recorded.
  • E305Due today. 14 Nov; feedback and decision pending.
  • E303Extension approved. Use [Extension end date] and [Approved reason] locally.
Before you trust it

Then send this: Recheck date boundaries and every pending field. Count overdue, due soon and later, and ensure letters use placeholders and approved decision types only.

If it goes wrong
It confirms overdue employees

Reply: "Dates are flags only; never decide an outcome."

It invents extension duration

Reply: "Use [Extension end date]."

Dates look wrong

Reply: "Use YYYY-MM-DD; today counts as due soon."

Sir ne bola urgent. Ab bolo: ho gaya.

Did it work?