<!-- LLM INSTRUCTIONS: Fill in the [ Add details... ] placeholders based on project context.

Context and Definition:
A team onboarding checklist is the set of things that must be true before
somebody can be useful on a team, written down so that they happen. Most of
them are invisible to the person who joins, which is the reason they are
routinely missed: the access grant, the introduction to the tooling, the
person to ask when something is unclear. A team that assumes a new member
will work these out spends the first month discovering what it should have
arranged in the first week.

The checklist is per person rather than per project, and the dates are
relative to the joining date for that reason. A new member's first week is
the same set of steps in the same order whatever else is happening on the
project, and a checklist with fixed calendar dates has to be redone every
time the joining date moves.

It can receive information from:
*   Project onboarding plan
*   Team composition and roles
*   Information security policy

It provides information to:
*   Team performance assessment
*   Lessons learned register
*   Project status report, when a team is not yet at full strength

Tailoring Tips:
*   Write what done looks like, not what to do. A task nobody can mark as
    complete is a task nobody will complete.
*   Name the one-off. Most of these are somebody's single action, and the
    step that gets missed is almost always the one that belongs to a person
    outside the team.
*   Close the checklist. The last entry is the one that says the onboarding
    is finished, and without it the list has no end.

Alignment:
The team onboarding checklist should be aligned and consistent with:
*   Team roles and responsibilities
*   Information security policy, because access is the largest block of it
*   Project onboarding plan, where the project has one

Section Instructions:
*   Onboarding Tasks: for each thing that must be true before the new member
    can be useful, give the task written so its completion is checkable, who
    does it, when it should be done relative to joining, and whether it is
    done or still pending.
-->

<h3 dir="ltr" align="right">{{Company_Name}}</h3>
<h2 dir="ltr" align="right">{{Project_Name}} - {{Project_ID}}</h2>
<h1 dir="ltr" align="center">TEAM ONBOARDING CHECKLIST</h1>

| **Date Prepared:** {{Current_Date}} | **Project Manager:** {{Project_Manager_Name}} | **Prepared By:** {{Prepared_By}} |
| :--- | :--- | :--- |

---

## Onboarding Tasks

| Task | Assigned To | Due Date | Status |
| :--- | :--- | :---: | :---: |
| [ Add details... ] | [ Add details... ] | [ .... - .... - .... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ .... - .... - .... ] | [ Add details... ] |
| [ Add details... ] | [ Add details... ] | [ .... - .... - .... ] | [ Add details... ] |

---

### Sign-off and Approvals

| Role | Name | Signature | Date |
| :--- | :--- | :---: | :---: |
| **HR / Onboarding Coordinator** | {{HR_Coordinator_Name}} | _______________________ | [ .... - .... - .... ] |
| **Team Lead** | {{Team_Lead_Name}} | _______________________ | [ .... - .... - .... ] |
| **Project Manager** | {{Project_Manager_Name}} | _______________________ | [ .... - .... - .... ] |
---

<div dir="ltr" align="right" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>Electronic Audit Trail: Hash SHA256: {{Audit_Trail_SHA256_Hash}}</span> <br>
  <strong>Template:</strong> TEAM ONBOARDING CHECKLIST | <strong>Ref:</strong> PMO-05.12 <br>
  <i>Generated on: {{Current_Timestamp}}, by <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">Tasleemat</a></i>
</div>

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-05.12.schema.json",
  "title": "Completed Team Onboarding Checklist Data Contract",
  "description": "Additive structural schema validating completed Team Onboarding Checklist artifact data payloads (PMO-05.12).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-05.12"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "onboarding_tasks": {
      "type": "object",
      "properties": {
        "task": {
          "type": "string",
          "minLength": 1,
          "description": "The activity, written so that a person who does not know the project can tell whether it is done. \"Get set up\" is not a task; \"reviewed the onboarding document\" is."
        },
        "assigned_to": {
          "type": "string",
          "minLength": 1,
          "description": "Who does it, which is not the same as who is waiting for it. Most onboarding tasks are somebody's one-off action, and naming the one-off is what stops the new member chasing something nobody owns."
        },
        "due_date": {
          "type": "string",
          "minLength": 1,
          "description": "When it should be complete, relative to the joining date rather than to a calendar day, because the joining date moves and a checklist full of fixed dates has to be redone when it does."
        },
        "status": {
          "type": "string",
          "minLength": 1,
          "description": "Done or pending, and the date it was done. A checklist nobody updates is one that has quietly stopped being true, and the entry is what shows it has."
        }
      },
      "required": [
        "task",
        "assigned_to",
        "due_date",
        "status"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "onboarding_tasks"
  ]
}

{
  "form_name": "Team Onboarding Checklist",
  "document_reference": "PMO-05.12",
  "_llm_instructions": "Populate the fields of 'Team Onboarding Checklist' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-05.12.",
  "fields": {
    "f01_Task": {
      "section": "Onboarding Tasks",
      "label": "Task",
      "guidance": "The activity, written so that a person who does not know the project can tell whether it is done. \"Get set up\" is not a task; \"reviewed the onboarding document\" is.",
      "value": ""
    },
    "f02_Assigned_To": {
      "section": "Onboarding Tasks",
      "label": "Assigned To",
      "guidance": "Who does it, which is not the same as who is waiting for it. Most onboarding tasks are somebody's one-off action, and naming the one-off is what stops the new member chasing something nobody owns.",
      "value": ""
    },
    "f03_Due_Date": {
      "section": "Onboarding Tasks",
      "label": "Due Date",
      "guidance": "When it should be complete, relative to the joining date rather than to a calendar day, because the joining date moves and a checklist full of fixed dates has to be redone when it does.",
      "value": ""
    },
    "f04_Status": {
      "section": "Onboarding Tasks",
      "label": "Status",
      "guidance": "Done or pending, and the date it was done. A checklist nobody updates is one that has quietly stopped being true, and the entry is what shows it has.",
      "value": ""
    }
  }
}