Pre-boarding

Pre-boarding defines day-one preparation through a dated checklist that runs backwards from the joining date. It recommends marking each item complete instead of relying on a generic task list. The proposed process adds the joiner, generates the checklist, schedules items by due date and prepares the day-one handover. Unfinished items near the start date indicate where preparation may slip, such as a laptop that has not yet arrived. The skill defines the tracking structure rather than performing those preparation actions.

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 a pre-boarding checklist, before-day-one preparation or new-joiner readiness plan. It does not order equipment, provision accounts or send messages on the user behalf. It does not compute payroll, tax, 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 confirms the joining role and date, which documents or equipment must be ready and who prepares them. It examines when paperwork is sent and signed, who tracks it, the current checklist or email process, what gets missed and whether the requested outcome is a checklist, schedule 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 Pre-boarding Task (text); Employee Name (text); Department (text); Owner (text); Category (select); Joining Date (date); Due Date (date); Documents Received (checkbox); Laptop Ready (checkbox); Email Created (checkbox); Account Record (text); Status (select); Notes (long_text); Pre-board ID (id).

Category starts with Equipment, Accounts, Access, Paperwork, Orientation. Status starts with Not Started, In Progress, Ready, Complete.

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_pre_boarding_status ON pre_boarding (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.