Projects & Work Management

Projects & Work Management defines a register for work delivery. Keep tasks in the project tool people already update and use this register for project ownership, dates and health. The workflow creates a project, assigns its owner and dates, tracks tasks in the existing tool, reviews status and closes the project. The model can record costs, budgets, milestones, deliverables, progress and client satisfaction, with relationships to invoices and client accounts. It avoids maintaining competing task systems whose information diverges at their boundary.

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 status is repeatedly requested in chat or a project register is missing alongside an existing task board. It does not schedule people, replace a project tool or manage dependencies automatically. Scores, progress and financial amounts are recorded rather than calculated.

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.

Ask about active project count, duration and owners; tasks versus milestones, dependencies and estimates; people per project, percentage allocation and turnover; the present board or spreadsheet and its gaps; and whether a project register, task view or both are wanted. 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 Name (text); Actual Cost (currency); Budget (currency); Currency (text); Invoices (relation); Client / Stakeholder (text); Client Account (relation); Client Satisfaction Score (number); Deliverables (text); Department (text); End Date (date); Milestones (text); Notes (long_text); Priority (select); Progress % (number); Project ID (id); Project Manager (text); Project Type (select); Sprint (text); Start Date (date); Status (select); Team Members (text).

Priority starts with Low, Medium, High, Urgent. Project Type starts with Fixed Price, Time and Material, Retainer, Internal. Status starts with Planning, Active, On Hold, Completed, Cancelled.

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_projects_work_management_status ON projects_work_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.