Probation Tracker

Probation Tracker defines a new-hire evaluation record for each person. It recommends keeping the start date, review dates, confirmation decision and evaluation criteria together. The proposed workflow moves from enrolment through first, middle and final reviews, then records confirmation or an extension. The purpose is to make the next review date visible so that ownership of the date is not lost. The field model includes checkpoints at 30, 60 and 90 days, while the intake establishes the actual probation length and review points.

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 a probation tracker, new-hire probation review, 30/60/90-day evaluation or confirmation record. It does not decide employment outcomes or provide legal guidance. Payroll, tax, leave-balance and KPI calculations remain outside the template workflow.

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 confirms how many people are on probation, their roles and existing extensions, the period length, confirmation criteria and review schedule. It establishes who reviews, who confirms employment and where feedback is recorded, then distinguishes a tracker from a review form or a need for both. 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 Probation Record (text); 30-Day Review Date (date); 30-Day Score (number); 60-Day Review Date (date); 60-Day Score (number); 90-Day Review Date (date); 90-Day Score (number); Confirmation Letter Issued (checkbox); Department (text); Employee Name (text); End Date (date); Manager (text); Mentor / Buddy (relation); Milestones Met (checkbox); Notes (long_text); Overall Score (number); Probation ID (id); Start Date (date); Status (select).

Status starts with Not Started, In Progress, Passed, Failed, Extended.

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_probation_tracker_status ON probation_tracker (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.