Project-Based Performance

Project-Based Performance defines per-project reviews for a business at Scale stage in the Operate layer. It recommends scoring completed projects against three or four fixed measures and recording a close reason so comparisons use a consistent denominator. The sequence is delivery, scoring, close-reason recording and review across projects. A scorecard captures the project, the person and role involved, review ownership, dates, scores and feedback, with a link to a performance review where needed.

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 when project overruns and feedback are captured inconsistently or completed projects need comparable reviews. It does not assess individuals or report company-wide performance; it defines a register rather than calculating scores 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.

Identify live project count, duration and delivery owner; agreed on-time, budget or effort and client-satisfaction measures; review cadence, reviewers and team versus individual scope; the existing capture method and whether the desired outcome is a scorecard or a status tracker. 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 Project Review Title (text); Employee Name (text); Project (text); Project Manager (text); Role on Project (text); Review Date (date); Delivery Score (number); Quality Score (number); Collaboration Score (number); Overall Score (number); Feedback (long_text); Linked Performance Review (relation); Status (select); Project Review ID (id).

Status starts with Not Started, In Progress, Submitted, Assessed, Closed.

Keep a close reason alongside the agreed measures, even when adapting the starter field model. The JSON example requires Review Date, Delivery Score, Quality Score, Collaboration Score, Overall Score and Status.

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_project_based_performance_status ON project_based_performance (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.