8 Onboarding Survey Questions for Managers in 2026

You're preparing for an onboarding review. The manager says the role is clear, the tools are available, and the new hire is progressing. The new hire says priorities keep changing and they're still waiting for access. Both can be sincere. They're describing different parts of the same month.

Useful onboarding survey questions for managers make those differences actionable. Instead of asking whether someone is settling in, ask what you explained, what support you delivered, what work you reviewed, and what remains blocked. A positive impression isn't evidence that onboarding worked. A low rating isn't a verdict on the person.

The eight questions below give managers a repeatable checkpoint at 30, 60, and 90 days. They cover role clarity, resources, coaching, work evidence, support needs, cultural integration, confidence, and comparison with new-hire feedback. Keep the wording stable, but adjust the expected work to the checkpoint.

For HR leaders and recruitment agencies supporting placements, the decision is practical: does the next checkpoint need clearer expectations, better support, or a different work assignment? Keep the employee's perspective separate until both sides have answered.

If you use AI to summarize responses, apply governance for HR AI agents to access, review, and accountability. Don't let an automated summary turn a disputed observation into an employment recommendation.

1. Role clarity without prompting

Can this hire state their 90-day outcomes without prompting?

Ask the employee to explain their expected outcomes before you explain them again. Record the substance of their answer, then rate your agreement that they understand the outcomes and how success will be assessed.

Use a consistent 1–5 agreement scale, with a not-yet-observed option. Add a short follow-up asking what remains unclear. These are working response options, not a validated performance scale.

Gallup reported that employees were 2.5 times more likely to strongly agree their onboarding was exceptional when managers played an active role. That employee-reported association supports examining manager behavior, but it doesn't validate your manager rating or establish causation.

Decide what needs clarification

Say a new account manager lists internal training as the main outcome, while you expect an independently prepared account review. That discrepancy calls for a written outcome and acceptance criteria, not a conclusion that the employee lacks initiative.

• Write the outcome: Describe an observable result, not an activity such as learning the business.

• Check the priority: Ask what the employee would postpone if urgent work arrived.

• Update the plan: Use a 30-60-90-day plan template to keep agreed expectations visible.

Your rating measures your confidence in their understanding. Their explanation provides the evidence. If it's vague, inspect the documentation before treating the problem as performance.

2. Working access to essential resources

Does the hire have working access to what they need for their first deliverables?

An account marked provisioned isn't necessarily usable. Check whether the employee can complete the actual workflow, including opening documents, accessing the right environment, obtaining approvals, and contacting the person who holds missing information.

Answer yes, partly, no, or not yet tested. Name the blocked task rather than recording a general complaint about IT.

Test access against the work

For example, an analyst can sign into the reporting platform but can't open the production dataset. You might rate access positively because the account exists; the analyst reasonably rates it negatively because the assigned audit remains impossible.

Keep a shared request log with the resource, request date, named owner, and affected deliverable. An onboarding plan template gives you somewhere to connect those dependencies to the work they support.

Practical rule: Test whether the employee can do the task, not whether someone closed the access ticket.

Don't assume every delay requires broader permissions. Some restrictions are appropriate, especially for sensitive information. The action may be a supervised workflow, approved sample data, or a narrower assignment.

This question diagnoses working conditions. It doesn't measure technical competence, and managers shouldn't expect employees to compensate for missing permissions through personal accounts or unsafe workarounds.

3. Coaching time planned versus delivered

How much individual coaching was planned, and how much happened?

Record planned and delivered coaching separately. Include time spent clarifying expectations, reviewing actual work, explaining operating norms, or helping the employee make a decision. Don't count every status meeting as coaching.

The distinction matters because onboarding responsibility doesn't guarantee preparation. According to ATD's onboarding research, managers were involved in implementing onboarding strategies at 59% of organizations in 2023, while only 25% required managers to receive onboarding training. Those organization-level findings don't tell you whether a particular manager coaches well.

Record delivery and usefulness separately

A manager might have recurring sessions in the calendar but repeatedly replace them with brief deadline updates. Record that as reduced coaching delivery, even if manager and employee spoke frequently.

• Planned support: Record scheduled coaching time for the review period.

• Delivered support: Record what happened, excluding cancelled sessions.

• Content covered: Note whether you discussed expectations, work feedback, norms, or decisions.

• Employee perspective: Compare this with whether the new hire received useful feedback.

More coaching time isn't automatically better. An experienced hire may need targeted decisions rather than lengthy instruction, while a novice may need guided practice.

When delivery falls short, protect a recurring slot or delegate a defined coaching task to an appropriate colleague. Don't transfer managerial accountability to an onboarding buddy.

4. A completed piece of work with evidence

Can you point to a completed deliverable and the evidence used to review it?

Start with the artifact: a reviewed document, resolved ticket, completed analysis, approved design, or observed demonstration. Then record whether it met the agreed standard, partly met it, or needs further work.

A description of activity isn't the same as work evidence. Neither is attendance at training.

Agree on completion before reviewing it

Say an analyst submits a data-quality audit. The manager records the document location, the reviewer's acceptance note, and the remaining revision. That's more useful than describing the analyst as promising or slow.

• Name the artifact: Give a title or reference that an authorized reviewer can open.

• State the standard: Identify the acceptance criteria agreed before the assignment.

• Describe the gap: Separate quality concerns from missing inputs or delayed approvals.

No completed work is a reason to inspect task design and support before judging the employee.

At the early checkpoint, a bounded practice assignment may be appropriate. Later, look for increasing independence and work that reflects the role's actual responsibilities.

Evidence still has limits. A polished deliverable may include substantial assistance, while unfinished work may reflect an external dependency. Record the support provided and blocked decisions alongside the artifact so reviewers don't mistake output alone for independent capability.

5. An unresolved need with a named owner

What is the most important unresolved support need, who owns it, and when will it be reviewed?

Choose the need most likely to prevent the next agreed outcome. Other issues can remain in a supporting log, but the checkpoint should produce an action someone can own.

Enboarder's survey of 1,000 HR leaders in the United States, United Kingdom, and Australia found that only 36% considered the handoff among recruiting, HR, and hiring managers smooth and well coordinated. These are HR leaders' perceptions across those markets, not direct observations of every handoff or proof that your organization has the same problem.

Assign the next action, not just the issue

Suppose the employee doesn't know when to escalate a customer exception. Recording unclear escalation rules identifies the concern, but it doesn't resolve it.

Assign the manager to walk through a relevant scenario, document decision boundaries, and check understanding at the next review. Close the action when the employee can use the guidance, not merely when a document has been sent.

• Owner: Name a person rather than a department.

• Action: Specify what that person will do.

• Review date: Set a date appropriate to the blocked work.

• Closure evidence: Describe what will demonstrate resolution.

Support needs can be relational: an inaccessible stakeholder, contradictory feedback, or uncertainty about challenging a decision. A manager can't infer that everything is fine because the employee hasn't complained. Ask the matching question privately through the new-hire feedback process.

6. Observable team norms still being learned

Which team norms is the hire practicing, and which still need explanation?

Replace a general culture-fit rating with observable behavior. Useful examples include documenting decisions, raising risks early, inviting review, and following an agreed escalation route.

The competing values framework behind the Organizational Culture Assessment Instrument, or OCAI, distinguishes Clan, Adhocracy, Market, and Hierarchy orientations. Those labels describe organizational cultural patterns such as collaboration, experimentation, results, and control. They aren't personality categories or proof that a particular employee belongs.

Assess the environment as well as the employee

An organization-level culture assessment asks about shared working practices and expectations. An individual personality or values assessment asks different questions about a person. Neither should be substituted for evidence about how someone performs their work.

For example, a team may describe itself as collaborative but make important decisions in private conversations. A new hire who misses those decisions may need better access to the process, not a lesson in being more sociable.

• Name the norm: Describe the behavior expected in a specific situation.

• Check exposure: Establish whether anyone explained and demonstrated it.

• Invite challenge: Ask whether the norm helps the work or creates avoidable barriers.

Don't ask whether the employee resembles the team. Ask whether the team has made its working expectations understandable and usable.

Manager observations can miss discomfort or fear of speaking up. Provide a confidential route to HR, explain who can read responses, and don't promise anonymity when an individual checkpoint makes identification obvious. Never use a culture-profile score as a hiring veto or dismissal basis.

7. Manager confidence with a reason

How confident are you that the hire will meet the agreed 90-day outcomes, and why?

Use the same confidence scale at each checkpoint and require a reason tied to the other answers. Include an insufficient-evidence option rather than forcing certainty.

Confidence is a useful prompt for review, but it isn't performance. A manager may feel reassured by familiar communication habits or become concerned because an unfamiliar working style is harder to interpret.

Look underneath a changing rating

Suppose your confidence falls between checkpoints because there's no completed work to review. Before discussing a performance concern, inspect whether the assignment had clear acceptance criteria, usable access, and timely feedback.

You may need to narrow the deliverable so the employee can demonstrate capability. Alternatively, the evidence may show a specific skill gap that needs practice and coaching.

• Evidence reason: State what you observed, not a personality label.

• Support check: Identify what the organization has and hasn't provided.

• Next test: Specify the work or behavior that would increase or reduce your confidence.

Don't average this rating with access and coaching to create an overall employee score. Those measures describe different things, and combining them hides what needs fixing.

At the final checkpoint, compare confidence with actual outcomes rather than making another forecast about the same period. Discuss concerns with context and examples, not an unexplained number that the employee is left to interpret.

8. Calibration against new-hire feedback

Where does your view differ from the new hire's, and what evidence would change your mind?

Complete your answers before reading the employee's responses. Then compare matching subjects using the new-hire feedback questions: priorities, usable resources, useful feedback, support needs, and team norms.

Neither perspective is ground truth. The manager may see support offered but not whether it helped; the employee may understand their effort but not the acceptance standard. Ask what each answer refers to before resolving the difference.

Hypothetical worked example

A manager rates role clarity positively because a written plan exists. The new hire reports unclear priorities because urgent requests from another stakeholder repeatedly displace that plan.

They review the task queue and discover that nobody has defined which requests take precedence. The manager agrees to publish a priority order and handle conflicting stakeholder requests, then checks whether the employee can apply that rule.

The employee wasn't necessarily confused about the document. The manager wasn't necessarily withholding guidance. They were answering different versions of the question.

Response-to-action framework

• Both positive: Check a relevant artifact, then continue the plan.

• Manager positive, employee negative: Test whether support was usable and expectations were understood.

• Manager negative, employee positive: Clarify acceptance criteria and examine work together.

• Both negative: Assign ownership for the process, resource, or coaching failure.

Use the response-to-action table to record the selected action, owner, review date, and evidence needed. Agreement isn't proof of effectiveness, and disagreement isn't proof that someone is wrong.

How each manager checkpoint item is asked, evidenced, and limited

Start With One Checkpoint and One Plan

Pick a current new hire and set the day-30 checkpoint now. Don't wait for a company-wide survey launch or a polished dashboard. You need agreed outcomes, a manager response, the employee's perspective, and someone accountable for the next action.

Use the same short form at days 30, 60, and 90. Early answers should emphasize clarity and access; later answers should include stronger work evidence and increasing independence.

Copyable manager checkpoint questionnaire

Record the employee, role, manager, checkpoint, and review date. Use the response formats below consistently, with not-yet-observed available where appropriate.

1. Role clarity: The hire can explain their agreed 90-day outcomes without prompting. Rate agreement from 1–5.

1. Remaining ambiguity: What outcome, priority, or success criterion still needs clarification?

1. Resources: Does the hire have working access to the resources needed for the next deliverable? Answer yes, partly, no, or not yet tested.

1. Planned coaching: How much coaching time did you plan during this review period?

1. Delivered coaching: How much happened, and what did it cover?

1. Work evidence: What completed artifact or observed task can you reference?

1. Acceptance standard: Did that work meet the agreed standard, partly meet it, or need further work? Explain.

1. Open support need: What is the priority unresolved need, named owner, and review date?

1. Team norms: Which observable norm is the hire practicing, and which needs explanation?

1. Manager confidence: How confident are you that the agreed outcomes will be met? Record a rating and evidence-based reason.

1. Calibration: Where does your view differ from the employee's feedback, and what evidence would change your assessment?

Ask the new hire to answer the matching feedback items independently. Keep their original wording alongside your observations rather than rewriting both into a single agreed account. Record any unresolved disagreement without treating it as resistance.

Choose a specific action from the response-to-action framework. For HR, repeated access failures across hires justify reviewing provisioning; repeated coaching gaps justify reviewing manager capacity. For recruitment agencies, distinguish a mismatch in role expectations from an onboarding problem before recommending a placement intervention.

Your next step is to use the 30-60-90-Day Plan Generator to create a customized onboarding plan, then confirm the written outcomes and day-30 review criteria with the new hire.

MyCulture.ai offers culture assessments and manager tools for making team expectations more explicit. Visit MyCulture.ai and start with the onboarding plan generator so your first checkpoint has agreed outcomes and work to review.