# Role-to-Onboarding Checklist Prompt

> A reusable prompt that turns a role description and real tool list into a day-by-day onboarding checklist with owners, gaps and conflicts flagged.

## Install

Copy the content below into your project:

# Role-to-Onboarding Checklist Prompt

A reusable prompt that turns a role description and real tool list into a day-by-day onboarding checklist with owners, gaps and conflicts flagged.

## Start here

Paste two inputs into one ordinary AI chat that accepts text: your **role description** (title, department, seniority, responsibilities, reporting line) and your **tools actually used** list (each tool plus what it is used for). Optional context: time zone, remote or on-site, recurring meetings, required training.

Then paste the complete prompt (appended below this guide). Send it. The AI returns a draft checklist only: first-week essentials, a tool enablement table, days 1–5, weeks 2–4, and a gaps/conflicts/assumptions section.

Check the output before using it:
- Every table row traces to a sentence in your role description.
- Day 1 holds whatever blocks the listed responsibilities.
- Anything you did not supply appears as `[OWNER?]` or `UNVERIFIED: needs confirmation`, never as an invented name or deadline.
- Any tool you listed but never explained is marked `UNEXPLAINED TOOL`, not deleted.
- The result says it is a draft for human review.

If a required input is missing, the prompt asks you for it instead of guessing.

## The task this covers

New-hire onboarding is usually assembled from memory, so first-day blockers surface late. This prompt reconciles two things: what the role must do, and what tools the role actually uses. It keeps setup, orientation and social steps separate, sequences them, and names what still needs a human owner.

It is a planning aid. It does not grant access, contact anyone, or confirm licence, seat or approval status; unstated items stay unverified.

## What you get

| Section | Content |
|---|---|
| 1 | First-week essentials, each with its role-description basis |
| 2 | Tool table: used for, first-week step, likely owner, category, status |
| 3 | Days 1–5, numbered, with `[OWNER?]` placeholders |
| 4 | Weeks 2–4, grouped by week |
| 5 | Gaps, conflicts and assumptions, labelled |
| 6 | Self-check lines you can read quickly |

The prompt also includes a fictional worked example, clearly labelled as an example, so you can see the expected shape.

## FAQ

**Do I need any setup or account?** No. An ordinary text chat is enough; no terminal, API or installation is involved.

**Can I trust the owners and dates it suggests?** Treat them as drafts. Any owner or timeline you did not supply should be marked `[OWNER?]` or `UNVERIFIED`. Confirm with the people who actually grant access.

**What about private data?** Inputs may include internal tool names and reporting lines. Paste only what your workplace allows, and treat the output as an internal draft.

## Verification note

source reviewed; runtime not tested. This prompt is a text template: it produces a draft checklist for a human to check. No account creation, permission grant or scheduling was performed, and no runtime test was run.

## Source and thanks

Original TokRepo prompt, licensed CC BY 4.0. Reference context: [ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>) (reviewed 2026-10-04), cited as general workspace context only; the prompt does not depend on a specific announced feature.

## Complete reusable prompt

# Role-to-Onboarding Checklist (Draft Only)

You are helping me prepare a first-week and first-30-days onboarding checklist for a new hire. This is a **draft for human review**, not a task list I will execute, not a message to any system or person, and not a claim about what the new hire can access.

## My inputs (paste each one, labelled)

1. **Role description** — job title, department, seniority, listed responsibilities, skills, reporting line, and any stated start date.
2. **Tools actually used** — the real list of applications, platforms, shared drives, channels and physical equipment this role uses. For each, include what it is used for and, if known, who currently grants or approves access.
3. **Context notes (optional)** — team location/time zone, whether the role is remote or on-site, recurring meetings, and required training or compliance items.

## What to do

1. **Extract the minimum viable setup.** From the role description alone, list the concrete things a person in this role must be able to do in the first week. Keep them verb-based (e.g. 'review incoming requests', 'draft weekly report'), and cite which part of the role description implies each item.
2. **Map each tool to a first-week enabling step.** For every tool in my list, write one step: what the new hire needs (account, seat, permission, orientation, or a walkthrough) and who is likely responsible. If a tool appears in my list but has no clear purpose in the role description, mark it `UNEXPLAINED TOOL` — do not silently drop it or invent a purpose.
3. **Sequence into days.** Produce a day-by-day plan for days 1–5 and a week-by-week plan for weeks 2–4. Put anything blocking day-1 work earliest. Where ordering matters, say why in one short clause.
4. **Separate three categories**: (a) access/setup steps, (b) knowledge/orientation steps, (c) social/team steps. Do not merge them.
5. **Flag gaps and conflicts.** After the plan, list: (i) steps you could not assign an owner to because my inputs were silent, (ii) any tool mentioned but never explained, (iii) any responsibility in the role description that no tool or step supports, and (iv) any assumption you made, clearly labelled as an assumption.

## Output format

### 1. First-week essentials (from role description)
Bullet per item: capability — role-description basis.

### 2. Tool enablement table
Markdown table with columns: Tool | Used for | First-week step | Likely owner | Category (setup / orientation / social) | Status (clear / UNEXPLAINED TOOL).

### 3. Day-by-day (days 1–5)
For each day: numbered steps with owner placeholders `[OWNER?]` where I did not supply one.

### 4. Weeks 2–4
Grouped by week, same format.

### 5. Gaps, conflicts and assumptions
Four labelled sub-lists matching step 5 above.

### 6. Self-check before you finalise
Answer these in one line each:
- Did any step appear that is not traceable to my role description or tool list? If yes, name it.
- Did I invent an owner, a timeline, a plan level or an approval route? If yes, flag it.
- Is every tool listed in section 2 also addressed somewhere in sections 3–4, or explicitly marked UNEXPLAINED?
- Did I replicate any exact sentence from my inputs? If yes, quote it so I can decide whether to keep it.

## Boundaries

- Prepare the checklist only. Do not send, schedule, invite, request access, or contact anyone.
- Do not assume plan eligibility, seat availability, licence type, permission level or approval turnaround. If unstated, write `UNVERIFIED: needs confirmation`.
- Do not add legal, medical, financial or security advice. If a compliance item is required and unstated, list it as a gap rather than describing the rule.
- Keep steps concrete and checkable by a human. Avoid filler like 'get familiar with the team'.

## Uncertainty handling

If either required input is missing, stop and ask me for it. If a tool's purpose is unclear, mark it rather than guessing. If two inputs conflict (e.g. a tool in my list contradicts a stated responsibility), show both versions side by side and note the conflict.

---

## Fictional worked example (labelled as example only)

**Role description (excerpt, fictional):** 'Operations Assistant. Reports to the Ops Manager. Responsibilities: process incoming supplier invoices, maintain the monthly supplies tracker, book courier collections, and answer customer delivery queries.'

**Tools actually used (fictional):** 'Email platform — sending and receiving; Shared spreadsheet — supplies tracker; Courier portal — booking collections; Team chat — internal questions.'

**Output shape:**

| Tool | Used for | First-week step | Likely owner | Category | Status |
|---|---|---|---|---|---|
| Email platform | Sending/receiving | Confirm mailbox is active and review the shared inbox rules with the Ops Manager | [OWNER?] | Setup | Clear |
| Shared spreadsheet | Supplies tracker | Review the tracker structure and add one test row with the Ops Manager watching | [OWNER?] | Orientation | Clear |
| Courier portal | Bookings | Watch one booking, then place one supervised booking | [OWNER?] | Setup | Clear |
| Team chat | Internal questions | Join the team channel and introduce themselves | [OWNER?] | Social | Clear |

Day 1 would place email access and the shared spreadsheet walkthrough first, because both block the listed invoice and tracker responsibilities. Day 2 would add the supervised courier booking.

**Task-specific checks for this example:**
1. Pass if every row in the table maps to a sentence in the fictional role description. Fail if 'customer delivery queries' appears as a capability but no tool is assigned, and this is not listed in gaps.
2. Pass if the day order explains why the email step precedes the courier step. Fail if the order is unexplained or alphabetical.
3. Pass if the output says the plan is a draft needing confirmation. Fail if it claims the new hire will have any account, seat or permission.
4. Pass if the fictional example stays labelled as an example. Fail if pretending it came from a real company.
5. Pass if any owner I did not supply is rendered as `[OWNER?]` or `UNVERIFIED`. Fail if a specific person, team or turnaround time is invented.

## References and reuse

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

Original TokRepo prompt · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Reference documents retain their own rights.

---

<!-- ZH -->

# 岗位描述到入职清单提示词

一个可复用的提示词，把岗位描述与真实工具清单整理成可复核的逐日入职清单，并标出负责人、缺口与冲突。

## 开始使用

在任意一个能接受文本的普通 AI 对话里粘贴两项输入：你的**岗位描述**（岗位名称、部门、资历、职责、汇报关系）和**实际使用的工具清单**（每个工具及其用途）。可选补充：时区、远程或坐班、例会、必须参加的培训。

然后粘贴完整提示词（附在本指南之后）。发送后，AI 只返回一份草稿清单：首周要点、工具启用表格、第 1–5 天、第 2–4 周，以及缺口／冲突／假设部分。

使用前先检查输出：
- 表格每一行都能对应岗位描述里的某句话。
- 第 1 天包含会阻塞所列职责的事项。
- 你未提供的内容显示为 `[OWNER?]` 或 `UNVERIFIED: needs confirmation`，而不是被编造的人名或期限。
- 你列出但未说明用途的工具被标记为 `UNEXPLAINED TOOL`，而不是被删掉。
- 结果明确说明这是供人工复核的草稿。

如果缺少必需输入，提示词会向你追问，而不是猜测。

## 这个任务解决什么

入职安排常靠记忆拼凑，第一天的阻塞问题往往很晚才暴露。这个提示词把两件事对齐：岗位必须完成什么，以及岗位实际使用哪些工具。它把账号开通、熟悉了解和团队社交三类步骤分开、排序，并指出哪些还需要人工指定负责人。

它是规划辅助，不会开通权限、联系任何人，也不会确认许可、席位或审批状态；未说明的内容一律保持待验证。

## 你会得到什么

| 部分 | 内容 |
|---|---|
| 1 | 首周要点，每条附岗位描述依据 |
| 2 | 工具表：用途、首周步骤、可能负责人、类别、状态 |
| 3 | 第 1–5 天，编号步骤，含 `[OWNER?]` 占位符 |
| 4 | 第 2–4 周，按周分组 |
| 5 | 缺口、冲突与假设，带标签 |
| 6 | 可快速阅读的自检条目 |

提示词还包含一个明确标注为示例的虚构范例，方便你了解预期格式。

## 常见问题

**需要额外安装或账号吗？** 不需要。普通文本对话即可，不涉及终端、API 或安装。

**它建议的负责人和日期可信吗？** 当作草稿看待。你未提供的负责人或时间点应显示为 `[OWNER?]` 或 `UNVERIFIED`。请向真正负责开通权限的人确认。

**内部数据怎么办？** 输入可能包含内部工具名和汇报关系。只粘贴单位允许的内容，并把输出视为内部草稿。

## 验证说明

source reviewed; runtime not tested（已审阅来源；未做运行时测试）。该提示词是文本模板：产出供人工检查的草稿清单。未执行开通账号、授予权限或安排日程，也未进行任何运行时测试。

## 来源与致谢

TokRepo 原创提示词，采用 CC BY 4.0 许可。参考背景：[ChatGPT release notes](<https://help.openai.com/en/articles/6825453-chatgpt-release-notes>)（2026-10-04 查阅），仅作为通用工作区背景引用；本提示词不依赖任何特定新发布功能。

## 完整可复制提示词

# 岗位到入职清单（仅为草稿）

你正在帮我为新员工准备一份首周及前 30 天的入职清单。这是一份**供人工复核的草稿**，不是我会执行的任务清单，不是发给任何系统或任何人的消息，也不是关于新员工能访问什么的声明。

## 我的输入（逐项粘贴并加标签）

1. **岗位描述**——岗位名称、部门、资历、列出的职责、技能、汇报关系，以及任何已说明的入职日期。
2. **实际使用的工具**——该岗位真实使用的应用程序、平台、共享盘、频道和实体设备清单。每项都要包括用途，如果知道，还要包括目前由谁授予或审批访问权限。
3. **背景备注（可选）**——团队所在地／时区、该岗位是远程还是坐班、例会，以及必须参加的培训或合规事项。

## 要做什么

1. **提取最低限度可用配置。** 仅根据岗位描述，列出该岗位人员在第一周必须能够完成的具体事项。用动词表达（例如「审阅进来的请求」「起草周报」），并引用岗位描述中暗示每一事项的部分。
2. **把每个工具映射到首周启用步骤。** 对我清单中的每个工具，写一个步骤：新员工需要什么（账号、席位、权限、熟悉了解，或一次讲解演示），以及可能由谁负责。如果某个工具出现在我的清单里，但在岗位描述中没有明确用途，标记为 `UNEXPLAINED TOOL`——不要悄悄删掉它，也不要编造用途。
3. **按天排序。** 为第 1–5 天生成逐日计划，为第 2–4 周生成逐周计划。任何阻塞第 1 天工作的事项排在最前。如果顺序重要，用简短从句说明原因。
4. **分成三类**：(a) 权限／配置步骤，(b) 知识／熟悉了解步骤，(c) 社交／团队步骤。不要合并它们。
5. **标出缺口和冲突。** 计划之后，列出：(i) 因我的输入未说明而无法指定负责人的步骤，(ii) 提到但从未说明用途的工具，(iii) 岗位描述中没有任何工具或步骤支持的职责，(iv) 你做出的任何假设，并明确标注为假设。

## 输出格式

### 1. 首周要点（来自岗位描述）
每个事项一条：能力——岗位描述依据。

### 2. 工具启用表格
Markdown 表格，列：Tool | Used for | First-week step | Likely owner | Category (setup / orientation / social) | Status (clear / UNEXPLAINED TOOL)。

### 3. 逐日计划（第 1–5 天）
每一天：编号步骤，凡我未提供负责人的地方使用负责人占位符 `[OWNER?]`。

### 4. 第 2–4 周
按周分组，格式相同。

### 5. 缺口、冲突与假设
四个带标签的子列表，与上文第 5 步对应。

### 6. 定稿前的自检
每项用一行回答：
- 是否出现了无法追溯到我的岗位描述或工具清单的步骤？如果有，指出它。
- 我是否编造了负责人、时间线、计划层级或审批路径？如果有，标出来。
- 第 2 节列出的每个工具是否也在第 3–4 节的某处得到处理，或被明确标记为 UNEXPLAINED？
- 我是否复制了输入中的任何原句？如果有，引用它，以便我决定是否保留。

## 边界

- 只准备清单。不要发送、安排日程、邀请、请求访问或联系任何人。
- 不要假设套餐资格、席位可用性、许可类型、权限级别或审批周转时间。如果未说明，写 `UNVERIFIED: needs confirmation`。
- 不要添加法律、医疗、财务或安全建议。如果某项合规事项是必需的且未说明，将其列为缺口，而不是描述该规则。
- 步骤要具体，且可由人工核对。避免「熟悉团队」这类空话。

## 不确定性的处理

如果缺少任一必需输入，停下来向我追问。如果某个工具的用途不清楚，标记出来而不是猜测。如果两项输入相互冲突（例如我清单中的某个工具与某项已陈述的职责矛盾），把两个版本并排列出，并注明冲突。

---

## 虚构范例（明确标注，仅为示例）

**岗位描述（节选，虚构）：**“运营助理。向运营经理汇报。职责：处理收到的供应商发票、维护每月用品跟踪表、预约快递取件、回答客户配送查询。”

**实际使用的工具（虚构）：**“电子邮件平台——收发邮件；共享电子表格——用品跟踪表；快递门户——预约取件；团队聊天——内部提问。”

**输出格式：**

| 工具 | 用途 | 首周步骤 | 可能负责人 | 类别 | 状态 |
|---|---|---|---|---|---|
| 电子邮件平台 | 收发邮件 | 确认邮箱已启用，并与运营经理一起查看共享收件箱规则 | [OWNER?] | 账号开通 | 明确 |
| 共享电子表格 | 用品跟踪表 | 查看跟踪表结构，并在运营经理旁看下添加一行测试数据 | [OWNER?] | 熟悉了解 | 明确 |
| 快递门户 | 预约取件 | 旁观一次预约，然后在监督下完成一次预约 | [OWNER?] | 账号开通 | 明确 |
| 团队聊天 | 内部提问 | 加入团队频道并做自我介绍 | [OWNER?] | 团队社交 | 明确 |

第 1 天会先安排邮箱访问和共享电子表格讲解，因为二者都会阻塞所列的发票和跟踪表职责。第 2 天再加入监督下的快递预约。

**本示例的任务特定检查：**
1. 通过：表格每一行都能对应到虚构岗位描述中的某句话。不通过：“客户配送查询”作为一项能力出现，却没有分配任何工具，且未列入缺口。
2. 通过：每日顺序能解释为什么邮箱步骤排在快递步骤之前。不通过：顺序没有说明，或按字母顺序排列。
3. 通过：输出说明该计划是草稿，需要确认。不通过：声称新员工将拥有任何账号、席位或权限。
4. 通过：虚构示例始终标注为示例。不通过：假装它来自一家真实公司。
5. 通过：我未提供的任何负责人均呈现为 `[OWNER?]` 或 `UNVERIFIED`。不通过：编造出具体的人、团队或处理时限。

## 参考资料与复用

- [ChatGPT release notes](https://help.openai.com/en/articles/6825453-chatgpt-release-notes) · Reviewed 2026-10-04

TokRepo 原创提示词 · [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)。参考资料保留各自原有权利。

---
Source: https://tokrepo.com/en/workflows/role-onboarding-checklist-prompt-3ca072f5
Author: Prompt Lab