Course & Upskilling Requests

Course & Upskilling Requests helps define a training request process before producing its tracking artifacts. It starts by distinguishing setup, conversion, review and advice requests. A request for advice receives a short recommendation; a request to build produces the selected formats after essential missing facts are resolved. The recommended workflow runs from a request through manager approval and finance approval to enrolment, completion and a certificate.

Approval routing depends on cost and a named approver. Completion tracking is included when the completion affects a decision. The skill asks about budget per person, annual pools versus individual requests, currency, approval order and any fast track threshold. It also checks whether a service bond is needed, whether learning happens in an LMS or externally, and whether certificates should be tracked. Questions arrive individually and stop when further answers would not change the output.

Use it to create a training request form or upskilling request tracker, or to move requests out of email threads and spreadsheets. It fits a growth-stage business defining its learning approval process. A review request stays a review of the material supplied, rather than automatically becoming a full system build.

The deliverables are empty templates. The skill does not deliver courses, manage an LMS, calculate payroll or tax, or provide legal advice. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review remains necessary before these templates drive real decisions.

Inputs are the process details the user confirms: budget, approvers, post-approval requirements, the current request channel and the desired outcome. Unanswered items remain unknown instead of receiving invented values. Requested outputs can include CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook.

The field list records the request title, employee, department, course, provider and course link. It links a skill gap and stores the request reason, cost, currency, duration, start date and budget line. Separate manager, HR and finance approval fields accompany service bond duration, LMS enrolment, completion date, certificate receipt, status and request ID. Initial status choices cover requested, approved, scheduled, in progress, completed and rejected requests.

All formats derive from the same fields. Money uses currency types, dates use date types and cross-table pointers use relations. CSV and JSON retain matching display names while SQL uses normalized identifiers. One SQL example is:

CREATE INDEX idx_course_upskilling_requests_status ON course_upskilling_requests (status);

Excel-compatible CSV uses UTF-8 with a byte order mark; a workbook is created only when requested. CSV formatting guidance identifies number, date and currency columns because CSV itself carries no types. Example rows remain synthetic and appear only on request.

The Notion step routes to notion-manual-import for CSV, property mappings, import instructions and verification. Manual mappings need no connection. Live workspace changes require verified tool access and authorization for the target. Related employee records can use people-directory, and notification-reminder-hub can turn due dates into reminders. Notion relations resolve only after both databases have been imported.