Quick Answer: A new hire survey is a structured questionnaire sent to recently hired employees at set points in their first weeks or months, designed to measure how well onboarding is working and how connected new starters feel. It typically covers pre-boarding logistics, day-one experience, manager support, role clarity, and training quality. Companies use the results to fix onboarding gaps early, before they turn into early attrition.
New hire surveys sit at the front end of the employee listening cycle. Unlike an annual engagement survey, which asks a whole workforce how it feels about the company, a new hire survey asks a specific cohort about a specific window of time: the onboarding period, when impressions form fastest and are cheapest to correct.
The timing matters more than the question count. A survey sent at day 7 tells you whether the laptop arrived and whether the manager showed up. A survey sent at day 90 tells you whether the role matches the job description. Ask the day-90 question at day 7 and you get noise. Ask the day-7 question at day 90 and you get a shrug.
Most new hire survey programs run across three or four checkpoints and measure a mix of operational and emotional signals.
Common checkpoint schedule:
- Pre-start or week 1: Was the offer-to-start communication clear? Did equipment, access, and paperwork arrive on time? Did someone greet you on day one?
- Day 30: Do you understand what success looks like in this role? Have you met the people you need to know? Is training useful?
- Day 60 or 90: Does the job match what was described in hiring? Do you feel supported by your manager? Would you recommend this company as a place to work?
- Day 180 (optional): Are you productive? Do you see a path forward here?
Typical question types:
- Likert-scale ratings on onboarding clarity, manager support, and belonging
- A new hire NPS or eNPS question to produce a trackable score
- Open-text prompts such as "What is one thing we should have done differently in your first week?"
- Binary operational checks on equipment, systems access, and payroll setup
The operational questions are the ones most teams underweight and most new hires care about. Broken access on day one is a recurring theme in onboarding feedback, and it is also the easiest problem on the list to solve.
Early attrition is expensive and predictable. Onboarding sets the tone for tenure, and the signals that predict a six-month exit usually show up in the first thirty days: unclear expectations, an absent manager, a role that does not resemble the interview.
A new hire survey turns those signals into data a People team can act on. Three practical uses:
Diagnosing which part of onboarding is broken. Aggregate scores are less useful than segmented ones. If day-30 role clarity scores 4.6 in engineering and 2.9 in field operations, you have a manager enablement problem in one function, not a company-wide onboarding problem.
Holding the process accountable. Onboarding involves recruiting, IT, payroll, facilities, and the hiring manager. Measure each handoff and ownership becomes clear.
Building the business case. Onboarding investment competes for budget against everything else. A survey that shows a 20-point gap in day-90 confidence between cohorts with a structured buddy program and those without makes the case for expanding it.
The catch is that surveys only create value if the loop closes. New hires who answer honestly and see nothing change learn that feedback is decorative, and response rates drop with every subsequent cycle.
Trigger it off the HRIS, not a calendar reminder. Start dates vary, so surveys should fire relative to each individual's day one. Manual sending breaks at scale and produces inconsistent data.
Keep it short. Five to eight questions per checkpoint. A twenty-question survey at day 7 competes with orientation, systems setup, and a first team meeting, and it loses.
Reach people where they already are. Email works for desk-based hires. For frontline, shift-based, and deskless workers, SMS or in-app delivery through Slack or Teams gets far higher completion than an email account they check once a week. ChangeEngine reports a 7x increase in survey participation when listening moves into the channels employees already use rather than a separate portal they have to remember.
Say what happens next. A single line explaining who reads the responses and how results are used lifts both response rate and answer quality.
Decide on anonymity deliberately. Anonymous responses tend to be more candid. Identified responses let you follow up with an individual who flags a real problem. Many teams run identified operational questions and anonymous sentiment questions in the same survey.
A survey is one instrument in a sequence, not the sequence itself. It works best when it sits inside a designed onboarding journey: a welcome message before day one, a first-week orientation, manager check-in prompts, training milestones, and a 90-day review. The survey measures whether that journey landed.
ChangeEngine handles this by building surveys into automated onboarding journeys triggered off the HRIS, so the day-7, day-30, and day-90 check-ins fire alongside the branded comms, and the results feed the same analytics view as the messages themselves. Teams using this pattern report saving around 20 hours of admin per new hire, largely because the survey and the follow-up comms stop being separate manual tasks.
The most useful thing a new hire survey produces is not a score. It is a short list of specific fixes, sized to the next hiring cohort, that you can implement before the next batch of start dates lands.
