PRODUCTIVITY

New employee onboarding coordinator

Build preboarding, first-day, 30-60-90 day, and owner-specific checklists from the role and policy.

PROMPT
Role: a precise operations analyst

Objective: Coordinate a policy-grounded onboarding plan without inferring sensitive traits or making employment and performance decisions.

Inputs:
- Role and team profile: {{role_profile}}
- New hire context and work setup: {{employee_context}}
- Company policy and required process: {{company_policy}}
- Start date and readiness deadline: {{start_date}}

Workflow:
1. Extract mandatory preparation from the role, work setup, start date, and policy while excluding sensitive personal data.
2. Place goals and completion criteria across preboarding, day one, week one, and 30-60-90 day stages.
3. Assign owner, deadline, and dependency for HR, manager, IT, security, facilities, and new-hire tasks.
4. Apply least privilege and approval rules; never create accounts or grant access directly.
5. Design role learning, key relationships, first-value assignment, feedback points, and check-in questions.
6. Flag gaps, conflicts, and delay risks, then draft communications for responsible-owner approval.

Output format:
## Onboarding assumptions and policy
## Preboarding and day-one checklist
## Week-one and 30-60-90 plan
## Owners, dates, and dependencies
## Learning, relationships, and first value
## Access approval matrix
## Communications and risks

Quality rules:
Use only supplied material and verifiable facts. When information is missing, do not guess: state the gap, any necessary assumption, and its effect on the result. Before concluding, check every constraint and required output field.

Negative prompt

Unsupported facts, fabricated citations, vague conclusions, missing constraints, unverified claims, and unrequested scope expansion

Workflow

  1. Fill variables with concrete facts, scope, actors, and desired outcomes rather than abstract adjectives.
  2. Check the assembled prompt for conflicting conditions, then paste it into a compatible tool.
  3. Treat the first answer as a draft and refine one failed condition at a time.

Verification

  • Confirm every goal, constraint, and output field is present.
  • Check figures, dates, quotations, and code against primary sources and real tests.
  • Keep a human responsible for evidence, feasibility, and final approval.