Sequence access, relationships, learning, supervised practice, and evidence of readiness without assuming instant productivity
9 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Build a realistic onboarding plan using only confirmed role, employee, and organizational information.
Start date, duties, decision rights, systems, data, stakeholders, readiness evidence, and prohibited independent work:
[role]
Prior knowledge, location, timezone, pattern, language, accommodations, equipment, and consented preferences:
[person]
Manager, buddy, trainers, access owners, policies, training, meetings, reviews, dependencies, compliance, and capacity:
[organization]
Start with prerequisites that must be complete before day one and flag owners or dates that are missing. Sequence orientation, relationships, system and data access, policy and security learning, role knowledge, observation, guided practice, feedback, increasingly independent work, and milestone review. For each dated activity state outcome, owner, learner action, prerequisite, artifact or observable evidence, expected effort, and contingency. Grant least privilege and never invent access, completion, policy, training requirement, manager, meeting, deadline, or employee need. Separate exposure, practice, demonstrated competence, and authorization; attendance alone is not readiness. Protect focus time and avoid overloading the first days with passive meetings. Provide 1-week, 30/60/90-day milestones only where the role warrants them, with mutual feedback and adjustment questions. Include absence, delayed equipment/access, remote, accommodation, and failed-readiness paths without penalizing the employee for organizational delay.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Role and readiness outcomes
Operations Coordinator starts Sep 7 2026. Duties: triage requests, confirm owner and acceptance criteria, maintain Linear, prepare twice-weekly reviews, document process changes. May not change product priority, approve spend, manage staff, or access production credentials. First-week evidence: correctly classify five fictional requests and identify missing owners. Day-30: run one supervised review. Day-60: manage routine queue with sampled checks. Day-90: propose one evidence-backed process improvement; manager retains approval.
New employee context
UK remote, UTC+1 in September, core overlap 13:00-17:00 UTC. Confirmed strong spreadsheet experience, no Linear experience. Company laptop shipping confirmed but delivery date not provided. English working language. No accommodation information supplied; manager should provide private request route rather than infer needs.
Organizational resources
Manager Sam, buddy Lina, IT owns accounts, Security runs required data-handling module, Support Lead explains request taxonomy, Product Ops owns Linear training. Manager has 45 minutes/day in week one; buddy 30 minutes/day. Access policy: email and HR portal before day one; Linear read-only first, edit after supervised practice; no production access. Reviews with manager end of days 3 and 5, then weekly. Exact account provisioning dates and laptop delivery unknown.
Example output
Before Sep 7 — organizational prerequisites
IT: confirm laptop delivery and email/HR-portal provisioning dates; both are currently missing. Manager Sam: send first-week schedule, role boundaries, core-hour expectation, and private accommodation-request route. Product Ops: prepare read-only Linear account but do not enable edit access. If equipment is late, the employee is not marked behind; Sam provides accessible, non-sensitive orientation material and reschedules system practice.
Day 1 — purpose and safe access
Sam covers role outcomes, prohibited decisions, escalation, and how success will be evidenced, not a full calendar of meetings. IT verifies approved access; no production credentials. Security assigns the confirmed data-handling module. Evidence: employee can identify what data and decisions are outside scope. Lina runs a 30-minute team-and-help-path orientation. Preserve at least two focus blocks.
Day 2 — request taxonomy and observation
Support Lead models three fictional requests. Employee classifies two with explanation. Product Ops demonstrates Linear read-only. Evidence is reasoning, not attendance. If access is missing, use exported fictional screens; do not use live customer data.
Day 3 — guided practice and review
Employee classifies all five fictional requests, identifies missing owners/acceptance criteria, and drafts questions without changing priority. Product Ops observes. Sam's end-day review compares evidence to the week-one criterion and asks what remains unclear.
Days 4-5 — supervised workflow
Employee shadows one handoff review, then prepares a fictional review packet. Edit access is considered only after the supervised task is accurate and the authorized owner confirms; it is not automatic. Day-5 review records ready, needs more practice, and organizational blockers separately.
Day 30: lead one real review with Sam present; evidence includes accurate owners, unknowns, and escalation. Day 60: manage routine queue with a predeclared sample review; no priority decisions. Day 90: present one process hypothesis with baseline evidence, risk, and test; Sam decides approval. Weekly two-way check asks what support, scope, access, or plan should change.
Why this works
1
Readiness evidence prevents calendar attendance from being mistaken for competence or authorization.
2
Dependency ownership exposes organizational blockers before they become employee performance problems.
Check the result
Does every activity have an outcome, owner, prerequisite, evidence, and contingency?
Are access, competence, and authorization separate under least privilege?
Are organizational delays prevented from counting against the employee?
ChatGPT