People Directory

People Directory defines the root employee record used by other people processes. It recommends one person record per human, with sensitive fields separated out and other modules linking to the record instead of duplicating it. The proposed lifecycle runs from joiner to person record, links with other modules, subsequent changes and an exit record. It fits the Onboard layer and Starter stage. A single agreed directory addresses employee lists spread across inconsistent spreadsheets and supports the linked leave, assets, payroll and review records.

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 to define an employee directory, people-directory template, staff database or employee master record. It references payroll, tax and banking information rather than owning those operational records. It does not compute payroll, taxes, leave balances 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.

Intake covers company size, full-time and part-time staff, contractors and remote work. It asks which salary or emergency-contact fields are needed and sensitive, then examines reporting lines, grades, bands and locations. It checks the existing HR system or spreadsheet, how stale it is, and whether the goal is a directory, master record or reporting. 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 Full Name (text); Annual CTC (currency); Currency (text); Date of Birth (date); Department (text); Email (email); Accounts (text); Emergency Contact (text); Emergency Phone (text); Employee ID (id); Employment Type (select); End Date (date); Grade Level (select); KPIs (text); Job Title (text); Access Role (text); LinkedIn (url); Manager (text); Nationality (text); Notes (long_text); Phone (text); Probation Status (select); Profile Photo URL (url); Skills (text); Start Date (date); Status (select); Time Zone (text); Work Location (text).

Employment Type starts with Full Time, Part Time, Contract, Intern, Consultant. Grade Level starts with L1, L2, L3, L4, L5, M1, M2. Probation Status starts with Not Started, In Progress, Passed, Failed, Extended. Status starts with Active, On Leave, Notice Period, Exited.

End Date can be absent until the relevant lifecycle stage or when no verified value exists; a missing date must not be invented to satisfy the schema. Email maps to a Notion Email property, and LinkedIn and Profile Photo URL map to URL properties. Imported Employee ID values stay Text, with a separate Unique ID property optional.

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_people_directory_status ON people_directory (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.