Performance Management

Performance Management defines structured employee reviews and stores a record for each cycle. It recommends building the review form around goals and behaviours already tracked elsewhere, referring to KPI and OKR records instead of entering the same information again. The proposed cycle moves through self input, manager review, discussion, and a retained record with actions. It fits the Manage layer and Growth stage. This approach addresses review forms that cannot be found later and reviews that duplicate existing tracking.

The default deliverable is a short recommendation. An explicit setup, build or conversion request produces artifacts after essential missing facts are resolved. Advice receives a direct answer, while a review works from the material provided. This keeps the size of the proposed setup tied to the requested outcome.

Use it for performance reviews, appraisal templates, review-cycle design and an employee-review tracker. It does not make promotion or pay decisions and has no legal standing by itself. It does not compute payroll, tax, leave balances or KPIs.

This is an empty-template workflow, not processing of real employee or customer records. Automation, reminders and synchronization require the separate integration layer. Sensitive decisions and adjustments require qualified human review before anything is acted on.

Intake establishes review frequency, probation reviews and reviewer relationships. It distinguishes ratings from scores and confirms goals, feedback and development-plan content. It asks who signs off, whether reviews are shared with the person, how appeals work, where current forms are stored and whether the result should be forms, records or reporting. Questions are asked one at a time, excluding anything already answered in earlier messages. Unknown facts stay unknown. Intent, confirmed facts, open questions and requested formats remain internal unless the user asks to inspect them; no missing answer is invented.

The field model includes Review Title (text); Areas for Improvement (text); Behaviour Score (number); Department (text); Development Plan (text); Due Date (date); Employee Name (text); Increment Recommended (checkbox); KPI Score (number); Notes (long_text); OKR Score (number); Overall Rating (select); PIP Required (checkbox); Promotion Eligible (checkbox); Rating Label (text); Review Date (date); Review ID (id); Review Period (text); Review Type (select); Reviewer (text); Status (select); Strengths (text).

Overall Rating starts with 1 - Needs Improvement, 2 - Developing, 3 - Meets Expectations, 4 - Exceeds Expectations, 5 - Outstanding. Review Type starts with Probation, Quarterly, Half Yearly, Annual, Mid Term. Status starts with Not Started, Self Review, Manager Review, Calibration, Finalised.

Requested CSV, SQL DDL, JSON Schema and Notion mappings derive from one field list. Display names remain identical across CSV and JSON, and normalized SQL identifiers are documented. Relation fields keep their relational meaning, dates remain dates and money remains currency. Machine-readable data is separated from explanation, with validation failures and limitations reported separately.

One supplied SQL example is:

CREATE INDEX idx_performance_management_status ON performance_management (status);

Excel-compatible CSV uses UTF-8 with a byte order mark. Because CSV has no column types, numeric, date and currency formatting is identified after the data. A CSV is not an .xlsx workbook; the latter is generated only when requested. Example rows require an explicit request and must be clearly synthetic. Sensitive identifiers are not unnecessarily repeated in a review, and generated templates remain empty.

Notion output goes to notion-manual-import for the CSV, property mapping, import steps and verification checklist. Manual mappings require no connection. Requested workspace changes require verified tool access, the actual target and authorization; a claimed connection is insufficient evidence. Notion relation columns resolve only after both databases have been imported. Select options are an initial vocabulary that can be renamed to match the business. people-directory supplies the related employee master record; notification-reminder-hub is the separate due-date reminder module. Personal identifiers and sensitive financial details stay out of generated templates.