Module 1 Onboarding, pre-start through 90 days
Most tech onboarding fails between offer accept and day 1, not after. This module front-loads the work that has to happen before the new hire shows up, then keeps the cadence tight through 90 days. Everything is automatable in a modern HRIS plus IT provisioning stack.
Pre-start phase
Trigger: signed offer in ATS. Owner: HR Ops.Day -14
2 weeks before start- Send welcome packet: start date, manager, day 1 schedule, dress code, parking or remote info
- Kick off background check if not done at offer
- Collect I-9 docs, W-4, state tax forms, direct deposit, emergency contact
- Order equipment: laptop, monitor, peripherals, headset
- Hold calendar: day 1, week 1 1:1s, 30/60/90 reviews
- Manager drafts first-week plan and 30-day goals
Day -7
1 week before start- IT creates accounts: email, SSO, Slack, ticketing, project tools
- Add to HRIS, payroll, benefits enrollment, org chart
- Schedule day 1 orientation block (HR + IT + manager)
- Assign onboarding buddy (peer, not manager). Send buddy charter.
- Send "what to expect on day 1" email with logistics
- Manager sends personal welcome note
Day -1
Day before start- Equipment confirmed: at desk if office, delivered if remote
- Confirm calendar invites visible to new hire's email
- Slack channels and Google groups joined and verified
- HRIS profile complete and visible to team
- Manager posts intro in team channel for next-day welcome
Vertical callouts — pre-start
AI / ML Provision compute and data access early
- Open IT ticket day -7 for GPU cluster, internal eval frameworks, model registry, and notebook environments. Wait time is the biggest day 1 blocker.
- Confirm hardware spec is correct for the role: ML eng usually needs Mac Studio or Linux workstation, not the standard issue laptop.
- Pre-load reading list: model card library, eval rubrics, last 2 quarters of research notes.
- If touching frontier models, confirm RAI / safety training is scheduled before any model access.
Gaming NDAs, depots, and pre-launch sensitivity
- Send project-specific NDA addendum before any depot access. Track signature in HRIS.
- Provision Perforce or Plastic SCM accounts day -7 with depth limits scoped to the new hire's discipline.
- If hiring near a launch, restrict day 1 access to non-launch projects. Add launch project access only after IP/legal clears.
- Order role-specific gear: dev kits, headsets, capture cards, devkit network access for console teams.
Animation / VFX DCC licenses and pipeline access
- Reserve seats for DCC software the role uses: Maya, Houdini, Nuke, ZBrush, Substance, RV. Floating licenses can stall starts.
- Provision render farm access and asset management system (Shotgun, ftrack, Kitsu) day -7.
- Send pipeline overview deck and tools doc before day 1. Ramp time on a custom pipeline is real.
- If artist is union-eligible (TAG, IATSE), confirm union paperwork before payroll setup.
Software / SaaS Repo, oncall, and CI access
- Add to GitHub or GitLab org day -7. Provision SSH keys and signing keys procedures.
- Schedule oncall shadow rotation in week 2 or 3, not week 1. Primary oncall not before week 8.
- Prepare a small "first PR" task already scoped, ideally fixing a real bug. Day 1 shipping a one-line PR is the gold standard.
Fintech Regulatory checks and SOC 2 access matrix
- If role is registered (FINRA), confirm U4 filing and fingerprinting before start. Lead time is 2-4 weeks.
- Update SOC 2 access control matrix and least-privilege role mapping before account creation.
- Schedule mandatory compliance training (AML, sanctions, code of ethics) before any customer or transaction system access.
- Background check standard: 7-year criminal, credit, and employment for any role touching money movement.
Health tech HIPAA training and BAA verification
- HIPAA training must be completed and attested before any PHI access. Schedule day 1 morning for any role that will touch PHI.
- Verify BAAs are in place for every vendor the new hire will use that may transit PHI: Slack, Notion, Zendesk, Drive, etc.
- Document the new hire's PHI access scope in your access log; this is auditable.
- If clinical role, verify state licensure and DEA where applicable before day 1.
Day 1 and Week 1
Owner: Manager + Buddy. HR holds the schedule.Day 1 morning
9:00 to 12:00- 9:00 — Manager welcome (30 min). Mission, team, success metrics, what good looks like at 30 days.
- 9:30 — IT setup, credential verification, MDM enrollment
- 10:30 — Buddy connect and tour (in-person) or Slack walkthrough (remote)
- 11:00 — Round-robin team intros, 5 minutes per person
- 12:00 — Lunch with buddy (expensed)
Day 1 afternoon
1:00 to 5:00- 1:00 — HR orientation: handbook, benefits, timekeeping, expense, PTO
- 2:30 — Compliance training kickoff (security, privacy, anti-harassment)
- 3:00 — First 1:1 with manager: 30/60/90 plan, cadences, comms norms
- 4:30 — Day 1 wrap with buddy. What went well, what was confusing.
Week 1
Days 2 to 5- Daily 15-minute manager check-in. End of day, not start.
- Read core docs: team rituals, on-call rotation, runbooks, eng or design principles
- Shadow a peer for half a day on real work
- Complete required compliance training by EOW
- Ship "hello world" task by EOW: a small, real, mergeable piece of work
- Buddy weekly coffee chat scheduled
30 / 60 / 90 day plan
Owner: Manager. HR sends reminders 5 days before each gate.30 days
Ramp gate- Manager review of fit, ramp velocity, friction points
- New hire: feedback on onboarding, what was missing, what surprised them
- Set first deliverable scope. One project, scoped to 4-6 weeks.
- 30-day pulse survey: belonging, clarity, support
60 days
First independent ship- First independent project shipped (scope appropriate to level)
- Peer feedback round: 3 peers, 3 questions, 15 minutes each
- Manager: confirm we have the right person for the right role
90 days
Full ramp- Performance check against role expectations
- Confirm comp, equity vesting, refresh eligibility
- Retention conversation: what would keep you here for 2 more years
- If concerns: written improvement plan, 30-day check-in
Templates
Click any to expand. Copy button puts it on your clipboard.Welcome email — HR to new hire (Day -14)
Sent within 24 hours of signed offer.Subject: Welcome to {{COMPANY}} — first day prep
Hi {{FIRST_NAME}},
Congratulations again. We're excited to have you join us as {{ROLE}} on {{START_DATE}}.
Here's what you need from us before day 1:
1. Complete your I-9, W-4, and direct deposit forms in {{HRIS}} by {{DAY_MINUS_7}}.
2. Confirm your shipping address for equipment by {{DAY_MINUS_10}}.
3. Reply with your t-shirt size for your welcome kit.
Your first day at a glance:
- 9:00 AM — Welcome with {{MANAGER_NAME}}, your manager
- 10:30 AM — Coffee with {{BUDDY_NAME}}, your onboarding buddy
- 1:00 PM — HR orientation (benefits, handbook, tools)
- 3:00 PM — First 1:1 with {{MANAGER_NAME}}
- 4:30 PM — Wrap
If you're remote, your laptop will arrive by {{DAY_MINUS_2}}. If you're in office, head to the {{LOCATION}} reception at 8:45 AM.
Reach out anytime. Email me directly or text {{HR_PHONE}}.
{{HR_NAME}}
People Operations | {{COMPANY}}
Manager pre-start note (Day -3)
Personal, not corporate. Sent from manager's email, not HRIS.Subject: Looking forward to Monday
Hi {{FIRST_NAME}},
Quick note from me before you start. I'm really glad you said yes.
A few things I want you to know going in:
- Your first month, your job is to learn. Not to ship anything heroic. I'll tell you when that changes.
- Ask me anything, even if it sounds dumb. I'd rather answer 10 questions than have you guess wrong.
- If something feels off in your first 30 days, tell me. We'll fix it.
For Monday: come at 9:00, no prep needed. We'll get you set up and you'll meet the team. Plan on a normal-energy day, not a sprint.
See you Monday.
{{MANAGER_FIRST_NAME}}
Buddy charter
What the buddy commits to in the first 30 days.{{COMPANY}} onboarding buddy charter
The buddy is a peer (not manager) who answers the small questions
new hires don't want to bother their manager with.
Time commitment: 2 hours / week for 4 weeks, then ad hoc.
What you commit to:
- Day 1: lunch (in person if possible, video if not)
- Week 1: daily 10-minute Slack check-in: "What's confusing today?"
- Weeks 2-4: weekly 30-minute coffee or video call
- Always: be reachable on Slack for quick questions
What you do not commit to:
- Performance feedback (that is the manager's job)
- Career advice (above your pay grade unless you're senior)
- Covering for the new hire if they go silent
If concerns come up:
- Tell the manager directly within 48 hours
- Loop in HR if you suspect a mismatch with role or culture
You will be recognized for buddy work in your next review.
30 / 60 / 90 day plan template
Manager fills out by day 1.{{HIRE_NAME}} — 30 / 60 / 90 day plan
Role: {{ROLE}} | Manager: {{MANAGER}} | Start: {{START_DATE}}
By 30 days — LEARN
- Meet every member of the team in 1:1s
- Complete all required compliance training
- Read: {{TEAM_DOCS}}
- Shadow: {{SHADOW_PEERS}}
- Ship: one small, real, mergeable contribution
- Pulse check: what's working, what's confusing
By 60 days — CONTRIBUTE
- Own one project end to end (scope: {{PROJECT_SCOPE}})
- Establish working cadence with key cross-functional partners: {{XFN_PARTNERS}}
- First peer feedback round
- Demonstrate fluency with: {{TOOLS_OR_SYSTEMS}}
By 90 days — DRIVE
- Take ownership of {{ONGOING_AREA}}
- Set quarterly goals with manager
- Identify one process improvement to propose
- Confirm fit and trajectory
Manager check-in cadence: weekly 1:1, plus formal reviews at 30, 60, 90.
Recommended tool stack
What plugs into what.HRIS / payroll
Rippling, Gusto, BambooHR, Workday (mid-market and up)
ATS
Ashby, Greenhouse, Lever
Onboarding workflows
Sapling (Rippling), Enboarder, native HRIS workflows
Equipment
Hofy, Firstbase, Allwhere
Identity / SSO
Okta, Google Workspace, Microsoft Entra
Device management
Kandji, Jamf, Mosyle (Apple), Intune (Microsoft)
SaaS access provisioning
Rippling IT, BetterCloud, Zylo
Survey / pulse
Lattice, Culture Amp, native pulse in HRIS
Module 2 Performance reviews and comp cycles
Tech companies tend to either over-engineer reviews into theater or skip them entirely. This module is a tight semi-annual cycle that runs in 6 weeks, ties cleanly to comp and equity, and forces calibration before letters go out. The cadence: June and December, comp lands by January 1 and July 1.
Cycle phases
HR Ops owns the cadence and reminders.Cycle kickoff
Week -2- Manager training: 60-minute refresh on rubric, calibration, and bias
- Calibration logistics confirmed: who's in which room, by level and org
- Comp budgets locked by finance: merit pool, promotion pool, equity refresh pool
- Promotion candidate slates submitted by managers
Self-assessment
Weeks 0 to 1- All employees complete self-assessment in Lattice or equivalent
- Peer nominations submitted (3-5 per person, manager approves)
- Reminder cadence: 3 days before, 1 day before, day-of, overdue daily
Peer feedback
Weeks 1 to 2- Peer feedback collected via short structured form (3 questions)
- HR Ops monitors completion rates daily
- Anonymous to peers, attributed to manager
Manager review
Weeks 2 to 3- Manager writes review for each direct report
- Skip-level review for outliers (top 10%, bottom 10%, promotion candidates)
- Initial rating proposed using rubric
Calibration
Week 4- Calibration meetings by level and function (4-8 managers per room)
- Distribution discussion against target curve
- Promotion case defenses
- HR partner facilitates, takes notes, owns final ratings
Delivery + comp
Week 5- Comp letters generated (merit, promotion, equity refresh)
- Delivery 1:1s within 5 business days
- Goal-setting for next cycle
- Cycle retro: completion rates, score distribution, manager feedback
Target rating distribution (calibration anchor)
Soft guide, not a forced curve. Adjust by team size and tenure.| Rating | Label | Target % | Merit treatment | Equity |
|---|---|---|---|---|
| 5 | Exceptional | ~10% | Top of merit band + bonus multiplier 1.25-1.5x | Equity refresh, accelerated |
| 4 | Exceeds expectations | ~25% | Above midpoint of merit band, bonus 1.1x | Standard equity refresh |
| 3 | Meets expectations | ~55% | Midpoint of merit band, bonus 1.0x | Refresh per tenure schedule |
| 2 | Inconsistent | ~8% | Below midpoint, bonus 0.5-0.75x | No refresh |
| 1 | Below expectations | ~2% | No merit; PIP recommended | No refresh |
Vertical callouts — performance and comp
AI / ML Research vs eng tracks, publication credit
- Maintain separate ladders for research and engineering. Research progression weights publications, citations, eval contributions, novel results. Eng weights model deployment, latency, reliability.
- Publication and open-source contributions count as performance evidence. Make this explicit in the rubric or your top researchers will leave.
- Comp: ML eng salaries are running 1.4-1.8x equivalent software eng. Refresh aggressively. Consider double-trigger acceleration for senior researchers.
- Retention bonuses for senior research staff are now standard, not exotic.
Gaming Cycle timing around ship, not calendar
- Do not run reviews during crunch or in the 60 days before a major launch. Schedule cycles between milestones, ideally 30 days post-ship.
- Bonus structure tied to ship: critical reception (Metacritic, review averages), commercial performance (units, retention, ARPDAU), and team milestones.
- Recognize craft tracks separately. Senior animators, technical artists, level designers may not want to manage. Build comp progression for ICs that doesn't cap.
- Crunch hours, if they happened, must factor into the review conversation. Quietly burning out your team is the most expensive talent strategy.
Animation / VFX Project-based and union dynamics
- Project completion reviews supplement annual reviews. Each show wrap should generate a written reel-and-feedback artifact.
- Recognize craft mastery beyond leveling. Many senior artists don't want to manage; build IC tracks that pay accordingly.
- Union dynamics: TAG / IATSE rates may set comp floors. Confirm rate compliance before merit increases land.
- Reel rights and credit are real comp. Negotiate which shows artists can show in their reel as part of the offer and review process.
Software / SaaS Dual ladder and oncall load
- Maintain a true IC vs manager dual ladder. Senior IC compensation should match Director-level manager compensation at the same level.
- Oncall load and incident command count as performance evidence, not invisible work.
- Promotion criteria should require evidence of impact across multiple teams or quarters at L5+; don't promote on potential alone.
Fintech Risk-adjusted metrics, compliance currency
- Performance metrics must be risk-adjusted. Speed without risk discipline is a liability, not an achievement.
- Compliance training currency factored into eligibility for merit increases. Lapsed training = no merit.
- Bonuses for revenue-impacting roles are tied to net revenue, not gross, and clawed back on chargebacks or losses within a defined window.
- Document ratings carefully. Anything that ends in a U5 filing will be looked at by regulators.
Health tech Compliance KPIs and clinical inputs
- Audit findings, training currency, and access log cleanliness factor into ratings for any role touching PHI or clinical decisions.
- Clinical advisor inputs (e.g., from a clinical lead) for any clinician-facing or clinician-involving role.
- Bonus tied to outcomes the company is paid on: STAR ratings, HEDIS measures, patient outcomes for value-based care models.
- Document everything. FDA-regulated environments need an auditable performance trail.
Templates
Self-assessment, manager review, calibration agenda, comp letter.Self-assessment template
Keep it short. 5 questions, 30 minutes max.{{NAME}} — Self-assessment, {{CYCLE}}
1. Top three accomplishments this cycle
For each: what was the impact, and how do you know?
2. Top three things you'd do differently
Be specific. "I'd communicate more" doesn't count.
3. Goals for next cycle
Three. No more. Each one with a measurable outcome.
4. What support do you need from your manager?
Be direct. We can't fix what we don't hear.
5. Where do you want to grow next?
Pick one of: deeper expertise, broader scope, people leadership,
different domain, or none of the above.
Optional: anything else you want on the record before this cycle closes.
Manager review rubric
5 dimensions, 1-5 scale, behavioral anchors.{{NAME}} — Manager review, {{CYCLE}}
Level: {{LEVEL}} | Track: {{IC_OR_MGR}}
Rate 1-5 on each dimension. Provide one specific example per dimension.
1. Impact — Did the work move the business?
5: Outsized impact, scope larger than level
3: Solid impact appropriate to level
1: Output below level expectations
2. Craft — Quality, depth, technical or functional skill at level
5: Setting the bar for the team
3: Meets level expectations
1: Gaps that affect outcomes
3. Direction — Choosing the right work, not just doing it well
5: Identifies and prioritizes work others miss
3: Picks the right work with manager input
1: Frequently working on the wrong things
4. Collaboration — Effect on the team's ability to do their work
5: Multiplier on others. People want to work with this person.
3: Reliable partner
1: Net drag on the team
5. Growth — Trajectory and learning
5: Demonstrably better than 6 months ago, learning fast
3: Steady growth
1: Plateaued or regressing
Overall rating: ___
Promotion readiness: [ ] yes [ ] not yet [ ] not on this track
Comp recommendation: ___
Rationale (3 sentences max): ___
Peer feedback prompt
3 questions, 15 minutes per response.Peer feedback for {{NAME}}
1. What is {{FIRST_NAME}} doing that the team should keep doing?
One specific example.
2. What should {{FIRST_NAME}} stop or do less of?
One specific example. Be honest. Anonymous to {{FIRST_NAME}}.
3. If {{FIRST_NAME}} were promoted to the next level, what's the
one thing they'd need to do differently?
Optional: anything else their manager should know to give them
a fair review.
Calibration meeting agenda
90 minutes, 8 managers, 50-80 reviews.Calibration meeting — {{LEVEL}}, {{ORG}}
Facilitator: {{HR_PARTNER}} | 90 minutes | Camera on
Pre-read: ratings spreadsheet, distribution chart, promotion cases.
Send 48 hours before. Read it before the meeting.
Agenda:
0:00 HR partner: ground rules. No advocacy. Examples beat opinions.
Cite behaviors, not labels. Push back if you don't see the case.
0:05 Distribution review. Where is each manager landing vs target.
0:15 Top performers (5s). Brief defense. 2 minutes each.
0:35 Bottom performers (1s and 2s). Brief defense. 2 minutes each.
0:55 Promotion candidates. 5 minutes each, with one challenger named
in advance to push back.
1:20 Outliers and edge cases.
1:25 Final ratings locked. HR partner sends summary within 24 hours.
Ground rules:
- Manager owns the rating until calibration. Calibration owns it after.
- HR partner has final say on distribution if calibration is gridlocked.
- No litigation by Slack after the meeting.
Comp adjustment letter
Sent within 5 business days of review delivery.Subject: {{CYCLE}} compensation update
Hi {{FIRST_NAME}},
Following our review conversation, here is your updated compensation,
effective {{EFFECTIVE_DATE}}.
Base salary
- Current: {{CURRENT_BASE}}
- New: {{NEW_BASE}}
- Change: {{PCT_CHANGE}}
{{IF_PROMOTION}}
Promotion: from {{OLD_LEVEL}} to {{NEW_LEVEL}}
{{END_IF}}
{{IF_BONUS}}
Performance bonus: {{BONUS_AMOUNT}}, paid {{PAY_DATE}}
{{END_IF}}
{{IF_EQUITY_REFRESH}}
Equity refresh: {{SHARES}} shares of {{TYPE}}, vesting over
{{VEST_PERIOD}} starting {{VEST_START}}. Grant agreement to follow
under separate cover.
{{END_IF}}
This reflects your performance rating of {{RATING}} and the
calibration discussion across the {{ORG}}. We're glad you're here.
Questions: reply directly to me or {{HR_PARTNER}}.
{{MANAGER_NAME}}
Performance improvement plan (PIP) intro
Use sparingly. Document everything before it gets here.Performance Improvement Plan — {{NAME}}
Manager: {{MANAGER}} | HR partner: {{HR}} | Start: {{DATE}} | Duration: 60 days
Why we're here
Specific, behavioral. Cite examples from the last 90 days.
Reference prior conversations with dates.
What needs to change
Three to five outcomes. Each one observable. Each one
attached to a date by which it should be visible.
What I'll do to support you
Concrete: more 1:1 time, scoped projects, paired work,
a coach, training. Pick what's real.
How we'll measure progress
- Weekly 1:1 with written summary
- 30-day check-in with HR
- 60-day decision: meets expectations, extend, or separate
What happens if you don't meet expectations
Direct language. Termination is on the table. The point of the
plan is to either fix the situation or end it cleanly.
Signatures: employee, manager, HR
Note: signing acknowledges receipt, not agreement.
Recommended tool stack
Reviews, comp, equity.Reviews / 1:1s / goals
Lattice, 15Five, Culture Amp, native HRIS
Comp planning
Pave, CompTool, Carta Total Comp, Aeqium
Comp benchmarks
Pave, Radford (Aon), Levels.fyi, Option Impact
Equity admin
Carta, Pulley, Shareworks (Morgan Stanley)
Calibration
Lattice Compensation, Charthop, Pave Bands
Engagement / pulse
Culture Amp, Lattice, Officevibe
Module 3 Offboarding and access revocation
Offboarding is where most companies leak data, customer relationships, and goodwill. The trigger varies (resignation, performance, layoff), but the runbook is the same: acknowledge fast, plan transition, revoke access on a clear timeline, and audit. Done well, alumni become referral pipelines. Done poorly, you make tomorrow's regulatory headache.
Phases
Owner: HR Ops, with manager and IT in tight coordination.Within 1 hour
Trigger- Manager acknowledges in writing. Kind, brief, professional.
- Manager notifies HR and skip-level
- HR opens offboarding ticket and assigns owner
- IT alerted to plan access revocation timeline (do not revoke yet)
Within 24 hours
Plan- HR + manager align: last day, transition scope, communication plan
- Decide: standard departure, garden leave, or immediate access removal
- Manager drafts internal announcement (do not send yet)
- Identify knowledge transfer owner per project
Transition phase
Last 2 weeks (voluntary)- Knowledge transfer plan: KT doc, recorded walkthroughs, shadow sessions
- Project handoff matrix: who owns what after departure
- Exit interview scheduled with HR (not direct manager)
- Final paycheck calculation: salary, accrued PTO per state law, expenses
- Benefits termination notice prepared (COBRA in US)
- Equipment return logistics arranged
Last day
Departure- Exit interview with HR (30 minutes, structured)
- Equipment returned or shipped (return label provided for remote)
- Badge / physical access returned
- Email auto-reply set; signature replaced with team alias
- Internal and external announcements sent (with employee approval on wording)
- Access revocation begins on schedule
Post-departure
Day +1 to +90- Day +1: confirm all access revoked, document in audit log
- Day +7: exit survey sent
- Day +14: final paycheck verified, COBRA letter sent
- Day +30: email forward expires, 30-day departure survey
- Day +90: employee files archived per retention policy. Rehire eligibility flagged.
Access revocation timeline
Voluntary departure with 2-week notice. Adjust for involuntary.| System | Voluntary timeline | Involuntary timeline | Owner |
|---|---|---|---|
| SSO / IdP (Okta, Entra) | End of last day | During termination meeting | IT |
| Email account | Forward to manager 30 days, then disable | Disable immediately, forward to manager 30 days | IT |
| VPN, internal network | End of last day | During termination meeting | IT |
| Code repos (GitHub, GitLab) | End of last day. Revoke PATs and SSH keys. | Immediate | Eng Ops |
| SaaS tools (Slack, Notion, Figma, Jira) | End of last day. Transfer ownership of personal items first. | Immediate | IT / SaaS Ops |
| Customer / production systems | 3 business days before last day | Immediate | Eng / IT |
| Shared drives, ownership transfer | 2 business days before last day | Immediate | IT |
| Company credit card | Last day | Immediate, cancel | Finance |
| Physical badge, office keys | Last day, returned in person | Collected during termination meeting | Facilities |
| MDM / device wipe | Within 7 days of equipment receipt | Within 24 hours of return | IT |
Vertical callouts — offboarding
AI / ML Models, weights, training data, IP
- Audit personal cloud accounts (AWS, GCP, HuggingFace, W&B) for company artifacts: weights, eval scripts, training data. Reclaim or confirm deletion in writing.
- Restate IP assignment in exit paperwork. Be explicit that prompt libraries, fine-tunes, and eval rubrics are company IP.
- Non-compete enforceability varies by state (CA, MN essentially can't enforce; others can). Get legal review before relying on it.
- For senior researchers, consider a 30-90 day garden leave to manage publication and recruiting risk to competitors.
Gaming NDAs, leak prevention, depot access
- NDA reaffirmation is essential, especially within 6 months of a launch or major reveal. Have legal-drafted language ready.
- Revoke depot access (Perforce, Plastic SCM) first. Asset leaks are the most common breach vector.
- If departing employee had access to unannounced projects, scope of NDA reaffirmation should explicitly cover those projects.
- Watch for sudden departures in the 90 days before launch. They sometimes precede leaks.
Animation / VFX Reel rights and credit
- Pre-clear which shots, sequences, or projects the artist can include in their reel after departure. Put this in writing.
- Be generous when you can. Reel reputation is the artist's career, and tight policies hurt your alumni network.
- Confirm credit attribution on shipped projects.
- Asset access (Shotgun, ftrack) revoked first because of IP risk on unreleased shows.
Software / SaaS Oncall and shared service accounts
- Oncall handoff with named replacement. Make the handoff visible in PagerDuty before last day.
- Audit shared service accounts and bot tokens the departing employee created. Rotate before last day.
- Revoke commit signing keys; rotate any service account credentials they had personal access to.
- If they were a code reviewer, redistribute CODEOWNERS responsibility before they leave.
Fintech Regulatory disclosure and customer data
- If registered (FINRA), file U5 within 30 days of termination. Termination reason language matters; legal-review every U5.
- Garden leave is common for senior roles, especially trading, sales, and senior eng touching customer money movement.
- Customer notification: if departing employee owned customer relationships, plan transition communication carefully. Watch for solicitation.
- SOC 2 access removal must be documented. Auditors will ask for evidence.
- Check non-solicit and confidentiality language is current; reaffirm in exit packet.
Health tech PHI access logs and BAA cleanup
- Pull PHI access logs for the departing employee for the last 30 days. Confirm patterns are normal.
- Revoke PHI access first, before any other system. Document timing.
- If any PHI access lingered past the revocation deadline, evaluate breach notification obligations under HIPAA and state law.
- Confirm zero remaining BAA-covered system access before closing the ticket.
- If clinical role, notify state licensing board if departure affects active patient panels.
Templates
Acknowledgment, KT plan, exit interview, runbook.Resignation acknowledgment — manager to employee
Within 1 hour of receiving notice.Subject: Got your note
Hi {{FIRST_NAME}},
Thank you for telling me directly. I'm sorry to see you go, and I
appreciate the way you handled this.
A few quick logistics:
- Last day confirmed: {{LAST_DAY}}
- I'll loop in {{HR_PARTNER}} to help with paperwork and benefits
- Let's grab 30 minutes today or tomorrow to talk through transition
- We'll coordinate on the team announcement; you'll see it before
it goes out
I want this to be a clean, respectful exit. Tell me what would make
that easier on your end.
{{MANAGER_FIRST_NAME}}
Internal team announcement
Manager sends after employee approves wording.Team,
Sharing news: {{NAME}} has decided to move on from {{COMPANY}}.
Their last day will be {{LAST_DAY}}.
{{NAME}} has been here {{TENURE}} and contributed
{{2_TO_3_HIGHLIGHTS}}. We're going to miss them.
Between now and {{LAST_DAY}} we'll be working through transition.
Project handoffs:
- {{PROJECT_A}} → {{NEW_OWNER_A}}
- {{PROJECT_B}} → {{NEW_OWNER_B}}
Please direct questions on those to the new owner starting now,
not on {{LAST_DAY}}.
Join me in thanking {{FIRST_NAME}} for what they built here.
{{MANAGER_NAME}}
Knowledge transfer document structure
Departing employee fills out by halfway through notice period.{{NAME}} — Knowledge transfer doc
Last day: {{LAST_DAY}} | New owners listed inline
1. Active projects (one section per project)
- Goal and current status
- New owner: ___
- Key stakeholders and how to reach them
- Open decisions waiting on me
- Deadlines in next 90 days
- Where docs and code live
2. Recurring responsibilities
- Meetings I run or attend (and whether they should continue)
- Reports I produce (and whether they're still needed)
- Approvals I'm in the path of (and who should replace me)
3. Tribal knowledge
- 5 things I figured out the hard way that someone new should know
- 3 people in this org who know things that aren't written down
- 3 vendors or external contacts and what they're useful for
4. What's broken that I never got to fix
Be honest. This is your gift to whoever follows you.
5. What you should not do (and why)
The traps and dead ends I learned about.
Exit interview question set
HR conducts. 30-45 minutes. Recorded only with consent.Exit interview — {{NAME}}
HR: {{HR}} | Date: {{DATE}} | Tenure: {{TENURE}}
Opening (3 min)
Thank them. Confirm what's confidential vs reportable.
Why now (5 min)
1. What made you start looking?
2. What made you accept the new role?
3. Was there a moment you started checking out?
Day to day (10 min)
4. What did you love about the work here?
5. What got in the way of doing your best work?
6. How was your relationship with your manager? Specific.
7. How was the team dynamic?
Compensation and growth (5 min)
8. Was your comp competitive? Where did it fall short?
9. Did you see a path forward here? Why or why not?
Leadership (5 min)
10. What does leadership at {{COMPANY}} get right?
11. What do they miss?
Final (5 min)
12. What's one thing we could change that would have kept you?
13. Would you recommend {{COMPANY}} to a friend? Why or why not?
14. Anything else on the record before we close?
Close (2 min)
Thank them. Confirm rehire eligibility (or not, with reason).
Confirm next steps on benefits, equipment, final pay.
Access revocation runbook
IT executes. HR confirms in writing within 24 hours of last day.Access revocation runbook — {{NAME}}
Departure type: [ ] voluntary [ ] involuntary [ ] layoff
Last day: {{LAST_DAY}} | Effective time: {{TIME}}
Pre-revocation (T -3 days)
[ ] Identify owned shared docs, repos, dashboards
[ ] Transfer ownership to {{MANAGER}} or new owner
[ ] Identify shared service accounts; rotate credentials
[ ] Audit personal cloud usage if elevated access role
At T (last day, EOD)
[ ] Disable SSO / IdP account
[ ] Disable VPN
[ ] Disable email; set forward to {{FORWARD}} for 30 days
[ ] Revoke source control access; revoke PAT and SSH keys
[ ] Revoke production system access
[ ] Revoke customer system access
[ ] Remove from MDM enrollment (after device return)
[ ] Cancel company credit card
[ ] Revoke physical access (badge, office keys)
T +1
[ ] Send confirmation to HR: all access revoked, with timestamps
[ ] Audit log review
T +7
[ ] Wipe device after return, redeploy or archive
T +30
[ ] Disable email forward
[ ] Final access audit
T +90
[ ] Archive employee file per retention policy
[ ] Compliance report (if regulated environment)
Owner: {{IT_OWNER}} | Reviewer: {{SECURITY_OR_HR}}
Final paycheck and benefits letter
State law varies on PTO payout. Confirm before sending.Subject: Final pay and benefits — {{NAME}}
Hi {{FIRST_NAME}},
Following up on your departure {{LAST_DAY}}.
Final paycheck
- Base through last day: {{BASE}}
- PTO payout: {{PTO_HOURS}} hours at {{HOURLY}} = {{PTO_AMOUNT}}
({{STATE}} state law: {{PAYOUT_RULE}})
- Outstanding expenses: {{EXPENSES}}
- Total: {{TOTAL}}, paid {{PAY_DATE}} via direct deposit
Benefits
- Health coverage ends: {{COVERAGE_END}}
- COBRA election notice: arrives within 14 days from {{COBRA_ADMIN}}
- 401k: contact {{401K_ADMIN}}; you have {{ROLLOVER_WINDOW}}
- Equity: {{VESTED_SHARES}} vested. Exercise window: {{EXERCISE_WINDOW}}
Contact {{EQUITY_ADMIN}} for paperwork.
Tax forms
- Final W-2 will be mailed by January 31 to your address on file:
{{ADDRESS}}. Update if needed: reply here.
Wishing you the best.
{{HR_NAME}}
Recommended tool stack
Identity, MDM, SaaS access, equipment.Identity / SSO
Okta, Microsoft Entra, Google Workspace
Device management
Kandji, Jamf, Mosyle, Intune
SaaS access mgmt
Rippling IT, BetterCloud, Zylo, Productiv, Torii
Equipment return
Hofy, Firstbase, Allwhere
Audit / SOC 2
Vanta, Drata, Secureframe
Exit surveys
Lattice, Culture Amp, Typeform
Bonus How to use this with a client
Three angles you can lead with depending on what the client needs and where you sit in the engagement.
Discovery and gap audit
- Walk client through this toolkit in a 90-minute session.
- Ask which workflow they currently run and which they don't. Mark it red, yellow, green.
- Use the gaps to scope a 6-12 week engagement.
- Lead-out deliverable: a custom version of this toolkit, branded for the client.
Implementation engagement
- Pick one module at a time. Onboarding is the easiest first win.
- Map their current HRIS and IT stack to the recommended tool stack. Identify integration gaps.
- Build the workflows in their tools (Rippling, Lattice, Okta, etc.). Run one cycle live with you embedded.
- Hand off with a runbook and 30-day post-launch support.
Vertical specialization positioning
- Pick two of the six verticals where you have the deepest experience. Lead with that on your site.
- The vertical callouts in this toolkit are your starter content for blog posts, case studies, and outbound.
- "HR ops for fintech" or "People ops for AI labs" sells better than "HR consulting." Specificity wins deals.