📁 HR

Employee Onboarding 30-60-90 Plan from Role Description and Team Setup

Turn a role description and team setup notes into a dated 30-60-90 onboarding plan with owners, check-ins, and no invented tools or milestones.

0.0
0Reviews
P
October 17, 2026

Prompt

Act as an onboarding coordinator who builds a 30-60-90 day plan from a pasted role description and team setup notes. You write dated goals, owners, and check-in questions. You do not invent tools, systems, policies, salary bands, or milestones that are not in Inputs.

You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Role description and team setup notes, pasted in full: [Notes]
- Start date and working pattern: [Start]
- Manager and buddy named in Notes: [People]
- Tools and systems listed in Notes only: [Tools]
- What success looks like at 30, 60, 90 days, if stated: [Success]
- Language: [Lang]
- Output format: [Format]

Generate:
1. Onboarding ledger: start date, manager, buddy, tools quoted from Notes. Forbidden: invented tools, invented policies, invented training courses.
2. Week 1 checklist: first five working days, one task per line, each traced to a line in Notes or marked NOT IN NOTES.
3. 30-day block: goals, first deliverable, first check-in question. Facts only from Notes; anything unstated is NOT IN NOTES.
4. 60-day block: goals, deliverable, and any dependency stated in Notes (for example a document that must be shared first).
5. 90-day block: goals from Success only; if Success is empty, write NOT IN NOTES instead of inventing targets.
6. Owners: every task assigned to a person named in People; otherwise OWNER NOT IN NOTES.
7. Missing scan: what a hiring manager must still supply (system access, policies, accounts) as a list with NOT IN NOTES labels.
8. Risk note: one line stating what cannot be planned until the gaps are filled.

Constraints:
- Every tool, person, and milestone traces to a quoted line in Notes. Quote or drop.
- No invented KPIs, no invented training courses, no employment-law advice.
- Mark NOT IN NOTES wherever Inputs are silent. End with a gaps list of five bullets the user still owes you.

Instructions

Paste the role description and team setup notes exactly as written, plus start date and named people. Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Examples

Example Input

Notes:
Role: Junior Customer Success Manager, mid-market SaaS. Reports to Dana Whitfield (CS Manager). Buddy: Priya Raman (CSM II).
Start date: Monday 03 November, 4 days/week (Mon-Thu).
Tools listed in the role description: Zendesk, HubSpot, Notion, Loom. Access requests go through the IT ticket queue.
Team: 6 CSMs, weekly pipeline standup Thursdays 10:00. Renewal process doc lives in Notion (not yet shared with the hire).
First 90 days success (from JD): "own a 25-account book by day 90, run first QBR by day 75."
Not stated: onboarding training schedule, commission plan, PTO policy.
Start: 2026-11-03, Mon-Thu
People: Dana Whitfield (manager), Priya Raman (buddy)
Tools: Zendesk, HubSpot, Notion, Loom
Success: own 25-account book by day 90; first QBR by day 75
Lang: English
Format: ledger + week 1 + 30/60/90 + owners + missing + risk

Example Output

1. Onboarding ledger.
Start: Monday 03 November 2026, Mon-Thu. Manager: Dana Whitfield (CS Manager). Buddy: Priya Raman (CSM II). Team: 6 CSMs, standup Thursdays 10:00. Tools quoted from Notes: Zendesk, HubSpot, Notion, Loom. Access via IT ticket queue. Success quoted: "own a 25-account book by day 90, run first QBR by day 75." Forbidden: invented tools - none used; invented policies - none used; invented training courses - none used.

2. Week 1 checklist.
Day 1 (Mon 03 Nov): file IT tickets for Zendesk, HubSpot, Notion, Loom access (Notes: access requests go through the IT ticket queue). Meet Dana Whitfield for a goals conversation (People). Request the renewal process doc (Notes: lives in Notion, not yet shared with the hire).
Day 2 (Tue): shadow Priya Raman on two Zendesk tickets (People + Tools). In HubSpot, read the mid-market account list.
Day 3 (Wed): read the renewal process doc if access arrived; otherwise chase the IT ticket (NOT IN NOTES: no training sessions listed for Wednesday).
Day 4 (Thu): attend the pipeline standup at 10:00 (Notes: Thursdays 10:00). Agree the first QBR shadow date with Priya (People).
NOT IN NOTES for week 1: training schedule, product certification, PTO briefing, commission briefing.

3. 30-day block (by 02 December).
Goals: Zendesk and HubSpot fluency on the shared queues; renewal process doc read; two shadowed QBRs. First deliverable: written shadow notes from one QBR, owner Priya Raman. First check-in question for Dana: "Which three accounts in the book I inherit carry the most risk, and why?" Day-30 success criterion NOT IN NOTES (the JD states day-75 and day-90 only).

4. 60-day block (by 02 January).
Goals: co-manage accounts alongside Priya; take first inbound Zendesk threads end to end. Dependency stated in Notes: the renewal process doc must be shared first (Notes: not yet shared with the hire). Deliverable: list of accounts with open renewals pulled from HubSpot only. Day-60 success criterion NOT IN NOTES.

5. 90-day block (by 02 February).
Goals quoted from Success: own a 25-account book by day 90; run first QBR by day 75 (around 17 January counting from 03 November). No other targets invented.

6. Owners.
Manager-owned tasks: Dana Whitfield (goals conversation, doc access). Buddy-owned tasks: Priya Raman (shadows, QBR prep). Hire-owned: IT tickets. OWNER NOT IN NOTES: training schedule assignment, commission plan briefing.

7. Missing scan (NOT IN NOTES).
- Onboarding training schedule - hire asks Dana.
- PTO and sick policy - hire asks HR.
- Commission plan details - hire asks Dana.
- Escalation and ticket-routing rules - hire asks Priya.
- Renewal process doc access - request from Dana on day 1.

8. Risk note.
Start date, manager, and buddy are present, so the plan is datable; until the training schedule and renewal doc arrive, week 1 days 3-4 stay placeholder tasks.

Gaps the user still owes you: training schedule, renewal doc access confirmation, escalation rules, commission plan timing, check-in cadence after day 30.

Reviews (0)

Please login to leave a review.
Loading reviews...