30-60-90 day plan for people operations managers

A 30-60-90 day plan for a new people operations manager should spend the first month making the HRIS and payroll agree, listing every state where employees work and what the company has registered there, and mapping the employee lifecycle from offer to offboarding; the second month fixing the gaps and automating the steps that keep breaking; and the third month delivering people data leaders trust and a calendar of the rules the company will trigger as it grows. As of November 2026, a new hire must be reported to the state where they work within 20 days, Form I-9 Section 2 is due within 3 business days of the first day of work, and federal laws switch on at 15, 20, 50 and 100 employees.

This plan is for the founder, COO or head of people hiring a people operations manager at a company of roughly 50 to 500 employees, often remote or hybrid and spread across many states. Where the job is mostly employee relations and policy, use the 30-60-90 day plan for HR managers; where it is mostly transactions, the HR coordinator plan; and where benefits are a separate seat, the benefits manager plan.

What does a people operations manager own that an HR manager does not?

The test of the role is whether the company can hire, move and offboard someone correctly without the people operations manager doing it by hand. A growing company adds states, managers and thresholds faster than anyone updates the process.

What does the 30-60-90 day plan look like?

30-60-90 day plan — [Name], People Operations Manager, [company]
Reports to: [COO / head of people / founder]   Start date: [date]
Employees: [N] in [N] states and [N] countries   Contractors: [N]
Model: [own payroll / PEO / employer of record for some countries]
Systems: [HRIS], [payroll], [ATS], [IT provisioning], [survey tool]

DAYS 1-30 — One record, one map, one lifecycle
Goals:
- Compare HRIS and payroll for every employee: legal name, title,
  manager, work location, pay, status; pick the source of truth
  for each field
- State register: every state or country where someone works, with
  withholding, unemployment and new hire reporting status
- Walk the lifecycle with each owner: offer, preboarding, day one,
  changes, leave, offboarding; note system, owner, deadline
- Check onboarding deadlines are met: Form I-9 Section 2, new hire
  reports, state notices
- List the federal headcount thresholds crossed and coming
Deliverables by day 30:
- Data mismatch list with owners
- State register and lifecycle map agreed with leadership
Check-in: day 30

DAYS 31-60 — Fix and automate
Goals:
- Close the mismatches; one change process for title, manager, pay
  and location that updates payroll before cutoff
- A relocation checklist: nobody changes work state without it
- Automate the three steps that fail most (example: IT access on
  day one, access removed on the last day, I-9 reminders)
- Handbook: state addenda for every state on the register
Deliverables by day 60:
- HRIS and payroll match at month end
- Relocation and offboarding checklists in use
Check-in: day 60

DAYS 61-90 — Data and the growth calendar
Goals:
- Monthly people report: headcount, hires, exits, attrition by team,
  open roles, time to first productive week
- Growth calendar: rules that start at the next thresholds, with
  dates and owners
- Run or fix one program cycle (performance review or survey)
Deliverables by day 90:
- People report leaders use without asking for a recount
- Growth calendar for the next 12 months
Check-in: day 90 — full review

Which federal rules switch on as headcount grows?

From the agencies' own pages and regulations as of November 2026. Each law counts employees its own way, and state laws often start lower. This is not legal advice.

What goes in a state-by-state register for remote employees?

The register is only as good as the trigger that updates it. Most companies find a missing state when an employee mentions a move months later; a relocation checklist, signed off before the move, closes that gap. For a country where the company has no entity, see what an employer of record is.

How should the employee lifecycle be mapped?

For the first weeks of a remote hire, the onboarding plan for remote employees and the new hire onboarding checklist cover the employee's side.

Which numbers should a new people operations manager baseline?

The standards are examples only; set targets once the baseline is clean.

How should the hiring manager use the plan in the final interview?

Give finalists the headcount by state, the systems list and one broken process, and ask for a short plan. Score it with how to evaluate a 30-60-90 day plan in an interview. A strong plan fixes the data before the dashboards, builds the state register early and turns one-off fixes into a process. Scenario questions:

• "An engineer mentions she moved to another state last month. What happens on Monday?"
• "The HRIS and payroll disagree on 30 employees' managers. Which is right, and how do you stop it happening again?"
• "We will pass 50 employees next quarter. What changes, and what do you do now?"
• "A manager wants an exit meeting today with someone in another state. What do you check first?"

For the manager side of the loop, the interview guide for people managers covers the leaders this role supports.

What should each check-in cover?

A filled example

What does the founder or COO owe the new people operations manager?

• Authority over the HRIS and the processes around it, including saying no to tools that create a second record.
• A payroll partner and access to payroll reports from day one.
• A rule that work location changes need approval, announced by leadership, not people ops alone.
• Counsel for state questions, so the register records answers, not guesses.

Common mistakes

• Buying a tool before fixing the data. A new system imports the old mismatches.
• Learning about moves from payroll. By then the company is late in a new state.
• Treating offboarding as a farewell. Final pay and access removal have deadlines.
• One handbook for every state. State addenda carry the rules that differ.
• Passing a threshold by surprise. FMLA, ACA, EEO-1 and WARN duties start on counts the company can see coming.

How do you adapt the plan?

• Through a PEO: the PEO runs payroll registrations; the register still needs every state, and the company keeps hiring and workplace rules.
• International employees: add each country's employer of record contract and local notices; see what an employer of record is.
• First people hire at a startup: do the state register and onboarding deadlines first; programs wait until day 61.
• Larger company with an HR team: the role narrows to systems and data; pair with the HR generalist plan for the people who use them.
• Staffing firm: temp payroll across states belongs to the staffing manager plan; people ops covers the firm's own staff.