E+E
E+E Consulting
HR strategy for technology companies

HR Automation Toolkit for Technology Companies

A working playbook for onboarding, performance and comp cycles, and offboarding. Workflows, copy-paste templates, and tool stacks, with vertical-specific callouts for AI, gaming, animation, software, fintech, and health tech.

3 modules. Onboarding, Performance + Comp, Offboarding. 27 templates. Email, scorecard, runbook, letter. 6 verticals. Filter content by your client's sector.
Vertical

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.

14 days
Pre-start runway target
100%
Day 1 access ready before 9am
5
Owners: HR, IT, Manager, Buddy, Hire
30 / 60 / 90
Manager review checkpoints
Offer acceptedTrigger
Day -14Welcome + paperwork
Day -7Accounts + buddy
Day -1Equipment + intro
Day 1Welcome + IT
Week 1Ramp + shadow
30 / 60 / 90Reviews

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.

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.

6 weeks
From kickoff to delivery
2x / year
Semi-annual cycle
5 inputs
Self, manager, peers, skip, calibration
100%
Comp letters within 5 days of delivery
Week -2Manager kickoff
Week 0Self + peer open
Week 1Self due
Week 2Peer due
Week 3Manager due
Week 4Calibration
Week 5Delivery + comp

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.
RatingLabelTarget %Merit treatmentEquity
5Exceptional~10%Top of merit band + bonus multiplier 1.25-1.5xEquity refresh, accelerated
4Exceeds expectations~25%Above midpoint of merit band, bonus 1.1xStandard equity refresh
3Meets expectations~55%Midpoint of merit band, bonus 1.0xRefresh per tenure schedule
2Inconsistent~8%Below midpoint, bonus 0.5-0.75xNo refresh
1Below expectations~2%No merit; PIP recommendedNo 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.

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.

1 hour
Resignation acknowledged
24 hours
Transition plan drafted
EOD last day
All access revoked
90 days
Final audit complete
TriggerResignation / decision
Hour 1Acknowledge
Day 1Plan
Last 2 weeksKT + handoff
Last dayExit + revoke
Day +30Survey + audit
Day +90Archive

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.
SystemVoluntary timelineInvoluntary timelineOwner
SSO / IdP (Okta, Entra)End of last dayDuring termination meetingIT
Email accountForward to manager 30 days, then disableDisable immediately, forward to manager 30 daysIT
VPN, internal networkEnd of last dayDuring termination meetingIT
Code repos (GitHub, GitLab)End of last day. Revoke PATs and SSH keys.ImmediateEng Ops
SaaS tools (Slack, Notion, Figma, Jira)End of last day. Transfer ownership of personal items first.ImmediateIT / SaaS Ops
Customer / production systems3 business days before last dayImmediateEng / IT
Shared drives, ownership transfer2 business days before last dayImmediateIT
Company credit cardLast dayImmediate, cancelFinance
Physical badge, office keysLast day, returned in personCollected during termination meetingFacilities
MDM / device wipeWithin 7 days of equipment receiptWithin 24 hours of returnIT

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.

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.