Remote Work Tracker

Remote Work Tracker defines a location-management roster and agreement record. Capture the person, agreed location and working window, equipment issuance and review. Its recommendation is to retain agreements rather than monitor daily presence. The supplied fields can record employee and department, work location, week start, HQ and remote days, core-hours confirmation, manager approval and notes. Equipment and working-window details should be adapted to the actual agreement rather than treated as facts already known about an employee.

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 remote or hybrid arrangements are scattered across conversations and the team needs an agreed roster and review record. It does not monitor activity, track location automatically or set business policy. It does not calculate leave balances or other employment measures.

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 remote headcount, fully remote versus hybrid arrangements and location changes; core hours, required overlap and communication; equipment, approval owner and company cost; existing records and gaps; and whether a roster, policy record 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 Remote Work Entry (text); Employee Name (text); Department (text); Work Location (text); Week Start (date); HQ Days (number); Remote Days (number); Core Hours Met (checkbox); Manager (text); Approved (checkbox); Notes (long_text); Remote ID (id).

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 TABLE remote_work_tracker (
  remote_work_entry VARCHAR(255),
  employee_name VARCHAR(255),
  department VARCHAR(255),
  work_location VARCHAR(255),
  week_start DATE NOT NULL,
  hq_days NUMERIC NOT NULL,
  remote_days NUMERIC NOT NULL,
  core_hours_met BOOLEAN NOT NULL,
  manager VARCHAR(255),
  approved BOOLEAN NOT NULL,
  notes TEXT,
  remote_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

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.