Time Tracking

Time Tracking defines hour logging by project, linking it to billing only where the business charges by the hour. Keep entries minimal when no billing use exists. The process captures an entry, obtains approval, locks the period and supplies an invoice or cost view. Lock an invoiced period to preserve its billing trail; the template describes that rule rather than enforcing a software lock. The register can retain employee, department, client, project, task description, supplied hours, rates, amounts, approval and invoice reference. Currency and billing values remain confirmed inputs.

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 timesheet templates, project-hour registers and billable-hours tracking where an agreed approval and billing trail is needed. It does not send invoices, pay people, calculate payroll or continuously monitor anyone.

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.

Establish billable versus internal purpose, client billing or productivity use; daily versus weekly and project versus task granularity; approvers, lock periods and correction rules; current logging tool and completeness; and whether the result is a log, invoicing input or payroll input. 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 Time Entry (text); Approver (text); Billable (relation); Billable Rate (per hour) (currency); Currency (text); Billable Amount (currency); Invoice (text); Date (date); Department (text); Employee Name (text); Hours Logged (number); Month (text); Notes (long_text); Project (text); Client (text); Status (select); Task Description (long_text); Time ID (id); Type (select); Week Number (number).

Status starts with Draft, Submitted, Approved, Rejected, Invoiced. Type starts with Billable, Internal, Training, Leave, Admin.

The supplied model defines Billable as a relation field; Type supplies the Billable, Internal, Training, Leave and Admin categories. Invoice remains text rather than an automatic billing-system connection.

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_time_tracking_status ON time_tracking (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.