Performance and Reviews Official

Turns a manager's raw notes into a short summary, the actions with owners, and any risk worth watching.

1. 011:1 between {{manager}} and {{employee}} on {{date}} (mood: {{mood}}). Notes: {{notes}} Write "Summary:" then three lines. Then "Actions:" one per line as "<owner>: <action> (by <date or next 1:1>)". Then "Watch:" one line, or "Nothing to watch". Plain text, under 120 words. Output: The summary, the actions and the watch line, plain text.

Reads the person's goals, their 1:1 summaries and their self-review, and drafts the manager review with examples and a suggested rating.

1. 01Manager review of {{employee}} for cycle "{{cycle}}" by {{reviewer}}. Read the Goals table for this employee and cycle (title, status, progress, last update), the 1:1 Notes table for this employee (summaries, dated), and the Reviews table for their Self review in this cycle. Search the Performance Review Guide for the rating scale. List the evidence: goals with outcomes, three moments from the 1:1s, and what the self-review claims. Output: The evidence list as plain text lines.
2. 02Write the draft. "Highlights:" three points, each with a named example. "Areas to grow:" two points, each with an example and one concrete next step. "Development:" one line on the development goals. "Suggested rating:" the scale word and one sentence of why, naming the evidence. If evidence is thin, add "Manager, please add:" with what is missing. Second person, plain text, under 300 words. Output: The draft review as plain text, under 300 words.

Decides whether a review is due soon or late and drafts the nudge for the reviewer.

1. 01{{review_type}} review of {{employee}} for "{{cycle}}" by {{reviewer}}, status {{status}}, due {{due}}. Today is the run date. If the due date is more than five working days away, output exactly: Not yet due. Otherwise say whether it is due soon or overdue and by how many days. Output: Not yet due, or due soon / overdue with the days, as plain text.
2. 02If task 1 said Not yet due, repeat it and stop. Otherwise draft the reminder to {{reviewer}}: two sentences naming {{employee}}, the cycle, the due date, and "Write it on the reviews portal". If overdue, add one line for the reviewer's manager. Plain text. Output: The reminder text, or Not yet due, as plain text.

Compares the proposed rating with the self-review, the goals and the review's examples, and flags what the meeting should discuss.

1. 01Calibration of {{employee}} for "{{cycle}}": proposed {{proposed_rating}}. Rationale: {{rationale}} Read the Reviews table for this employee and cycle (self and manager ratings, highlights, areas to grow) and the Goals table (status and progress). Search the guide for the calibration checks. Output: The self rating, the manager rating, the number of examples, and the goals outcome, as plain text.
2. 02Output "Flag:" then exactly one of None, Outlier, Missing evidence, Inconsistent. Then "Because:" two lines with the facts. Then "Discuss:" one question for the meeting, or "Nothing to discuss". Plain text, under 100 words. Never propose a rating. Output: The flag, the reason and the discussion question, plain text.

Counts reviews by status per department, lists overdue reviewers, calibration flags and goals at risk, and sends it to the People lead.

1. 01Find the cycle with Status Open in Review Cycles. Count its reviews by Status and by the employee's Department (join through Employees). List reviewers with a review Not started past its due date. List calibration rows with a Flag other than None or Unchecked. List goals with Status At risk. Output: The counts and the lists, as plain text.
2. 02Write the report: the numbers as short lines, then "Overdue:" by name, "Calibration flags:" by name with the flag, "Goals at risk:" by name. Then "Decisions this week:" at most three. Under 250 words, plain text. Send it with Turtle Notify to the People lead and confirm. Output: The report text and a confirmation that it was sent, plain text.