# First-week onboarding plan — fictional Cedar Services example

Status: DRAFT; manager, People Operations, and IT review required.
Role: Customer operations coordinator.
Start date: 2026-10-19. Manager owner: Operations manager.
First-week outcome: Complete one supervised practice customer handoff using an approved sanitized packet.
Scope: Orientation, role learning, and practice. Not probation assessment, employee ranking, or live account provisioning.

## Approved-source register — fictional documents
| Source | Version | Effective date | Owner | Relevant section |
|---|---|---|---|---|
| Handbook | v3 | 2026-09-01 | People Operations | Role orientation; no remote-work rule supplied |
| Security Guide | v2 | 2026-09-15 | IT security owner | Section 4: customer data only in approved storage |
| Support Handoff SOP | v5 | 2026-10-01 | Operations manager | Sections 2–5: prerequisites and acceptance |
| Access Matrix | v4 | 2026-10-05 | IT access owner | Coordinator role: read-only CRM after approval |
Replace with real approved links and applicable policy versions before use.

## First-week milestones
| Day | Work | Owner | Prerequisites | Evidence | Initial state |
|---|---|---|---|---|---|
| Mon Oct 19 | Welcome, team map, and first-week goals | Manager | Approved role brief | Reviewed goals and named help contacts | Planned |
| Tue Oct 20 | Security walkthrough and read-only CRM request | IT; manager approves scope | Security Guide v2; Access Matrix v4 | Training record and request reference | Planned; access unconfirmed |
| Wed Oct 21 | Observe escalation with sanitized data | Buddy | Approved practice packet | Walkthrough notes and open questions | Planned; no live CRM dependency |
| Thu Oct 22 | Draft practice handoff | New teammate with buddy | SOP v5 and practice packet | Sample handoff with required fields | Planned |
| Fri Oct 23 | Review practice and next-week support | Manager | Practice draft | Accepted handoff or specific revision list | Planned |

## Access and dependency ledger
| Resource | Scope requested | Authority | Current state | Next action | Safe alternative |
|---|---|---|---|---|---|
| CRM | Read-only coordinator | Manager approval; IT grants | Not requested | Submit approved request through existing IT process | Sanitized demonstration |
| Policy library | Role-appropriate reading | Document owner; IT | Unconfirmed | Confirm approved access and successful login | Manager-led walkthrough of approved materials |
Do not record passwords. Request, approval, provisioning, successful login, and task completion are separate states.

## Source-backed FAQ examples
| Question | Draft answer | Source | Escalation |
|---|---|---|---|
| Can I store customer files on my personal drive? | No under the supplied fictional Security Guide; use approved storage | Security Guide v2, section 4, effective 2026-09-15 | IT security owner |
| How many remote days may I take? | Not found in supplied approved sources; confirm before relying on a schedule | No supporting passage supplied | People Operations |
| Can I edit live CRM customer records? | The supplied coordinator matrix specifies read-only access after approval; editing is not authorized by this plan | Access Matrix v4, effective 2026-10-05 | Manager and IT access owner |

## Review correction example
Rejected draft: New hires may work remotely three days each week.
Reason: No supporting policy was supplied.
Corrected answer: Working-arrangement rule not found in supplied policies; ask People Operations.
Action: Keep the plan usable while the policy owner answers; do not invent the rule.

## Completion and acceptance
- [ ] Manager confirms role priorities and achievable workload.
- [ ] Policy owner checks FAQ passages and effective dates.
- [ ] IT confirms requested scope, approval, and access state.
- [ ] Practice handoff includes required fields and a named reviewer.
- [ ] Every completed milestone has evidence; blocked work has an owner and next check.
- [ ] No unnecessary identity, payroll, medical, or private performance information is included.
- [ ] No employee ranking, hiring inference, or unsupported provisioning claim appears.
Reviewer: [name]. Approval date: [date]. Unresolved items: [list].

## Pilot measurement example — illustrative, not a promised outcome
| Measure | Example entry | Interpretation |
|---|---|---|
| Milestones completed / due | 4 / 5 = 80% | Only due milestones enter this denominator |
| Outstanding access blockers | 1 | IT owns the blocker; do not attribute it to employee performance |
| Unsupported FAQ answers caught in review | 1 | Remote-work claim removed before use |
| Preparation and review time | Record actual minutes separately | Compare with the documented prior process |
| New teammate feedback | Ask whether priorities and help contacts are clear | Improve instructions; do not score the person |

## Maintenance
Owner: Operations manager. Review after role, policy, or access-matrix changes.
Keep the approved version in the authorized location and archive superseded drafts under existing retention rules.