AI-Enabled Internal Mobility Survey Questions 2026: Employee & Manager Question Bank

By Jürgen Ulbrich

These AI-enabled internal mobility survey questions measure what mobility KPIs won't show: whether employees trust AI matching, feel treated fairly, understand what data is used, and feel safe enough to explore internal moves. This template provides segmented question blocks for employees and managers, a scoring framework with thresholds, and a DACH governance checklist for works councils and data protection.

When do you need this survey?

AI matching tools for internal mobility change how employees experience career opportunities inside an organization. According to the Career Optimism Index® 2026 by the University of Phoenix Career Institute® (5,000 workers, 1,000 employers), 50% of employees say AI increases their confidence in transitioning to a new role — while 62% of employers report that employees develop AI skills faster than the organization can adapt.

The critical lever is trust: the EY Mobility Reimagined Survey 2026 finds that 95% of employees identify trust as a key driver for accepting mobility opportunities. High-trust mobility functions are 1.9x more likely to develop employees into new areas faster than their low-trust counterparts.

This survey is the right tool when you:

  • are piloting or scaling an AI matching tool for roles, projects, or gigs,
  • want to measure whether transparency, fairness, and psychological safety are sufficient,
  • need to involve works councils and data protection teams with evidence, or
  • want early warning signals before a trust breakdown shows up in KPIs.

If you already run a general internal mobility survey, use these questions as an AI-specific extension for your pilot group. A solid baseline is the internal mobility survey template, which covers seven foundational dimensions.

Question bank: AI-enabled internal mobility

Use a Likert scale of 1–5 for all closed statements: 1 = Strongly disagree, 5 = Strongly agree. Add a "Not applicable" option for items that don't apply to every role. Survey employees and managers/HRBPs separately — the perspective gap is one of the most valuable diagnostic signals you can collect.

Block 1: Awareness and understanding of AI matching (Employees)

  • Q1. I know that AI is used to suggest internal roles, projects, or gigs to employees.
  • Q2. I understand what the AI matching tool is meant to do — and what it is not meant to do.
  • Q3. I know where to find guidance on how AI-supported internal mobility works at our company.
  • Q4. I can tell in the process what is an AI suggestion and what is a human decision.
  • Q5. I know which steps in internal mobility are fully human-led versus AI-assisted.
  • Q6. I feel comfortable asking questions about how AI matching influences internal moves.

Block 2: Transparency and control (Employees)

  • Q7. I can see which skills or experiences the AI system used to suggest a role or project.
  • Q8. I can correct or update my skills profile without unnecessary friction.
  • Q9. I can influence what opportunities the AI shows me (e.g., interests, location, workload).
  • Q10. I understand how to improve future AI suggestions (e.g., profile updates, preferences).
  • Q11. There is a clear option to exclude certain data from AI matching.
  • Q12. I have enough control over my data to trust AI-supported matching.

Block 3: Quality and relevance of suggestions (Employees)

  • Q13. AI-suggested roles or projects match my skills and realistic next steps.
  • Q14. AI suggestions help me discover opportunities I would not have found on my own.
  • Q15. The explanation "why was this suggested to me?" is clear enough to act on.
  • Q16. AI suggestions reflect my stated preferences (e.g., function, team type, remote/hybrid).
  • Q17. I can tell whether a suggestion is a stretch opportunity or a close match.
  • Q18. The AI matching tool saves me time compared to searching manually.

Block 4: Fairness and bias perceptions (Employees)

  • Q19. AI-supported internal mobility feels fair across teams and departments.
  • Q20. AI suggestions do not favor employees who are already well-connected internally.
  • Q21. I believe AI matching does not disadvantage employees on part-time or flexible schedules.
  • Q22. I believe AI matching does not disadvantage remote employees compared to office employees.
  • Q23. When AI suggestions seem off, there is a fair way to correct the process.
  • Q24. I trust that human reviewers challenge AI outputs when they are not right.

Block 5: Psychological safety and manager behavior (Employees)

  • Q25. I feel safe exploring internal opportunities without risking negative consequences in my current team.
  • Q26. My manager supports internal moves even when that creates short-term resourcing gaps.
  • Q27. I can discuss AI-suggested opportunities openly in my 1:1s.
  • Q28. I don't worry that AI matching signals (e.g., "mobility interest") could harm my reputation.
  • Q29. If I decline AI-suggested opportunities, I feel no hidden pressure.
  • Q30. I trust that decisions about internal moves are explained respectfully and consistently.

Block 6: Data and privacy (Employees)

  • Q31. I know which employee data is used for AI matching (skills, career history, learning data, etc.).
  • Q32. I know who can see my AI-related mobility signals (manager, HR, talent team).
  • Q33. I trust that access rights prevent unnecessary visibility of sensitive information.
  • Q34. I trust that data for AI matching is retained only for as long as necessary.
  • Q35. I know how to request correction or deletion of data used for AI-supported matching.
  • Q36. I believe our works council / Betriebsrat expectations about AI-supported mobility are respected.

Block 7: Overall impact (Employees)

  • Q37. AI support makes internal mobility more transparent than before.
  • Q38. AI support makes internal mobility more accessible to a broader group of employees.
  • Q39. AI support motivates me to develop skills specifically for future internal opportunities.
  • Q40. AI support helps me understand which skills to build next.
  • Q41. AI support reduces "behind-the-scenes" staffing decisions that employees can't see.
  • Q42. Overall, AI-supported internal mobility improves my employee experience.

Block 8: Onboarding and tool competency (Managers/HRBPs)

  • Q43. I understand how AI matching works well enough to explain it to employees.
  • Q44. I know which data sources feed the AI matching tool (HRIS, skills profiles, learning history, projects).
  • Q45. I have received practical training for using AI matching responsibly in mobility decisions.
  • Q46. I know what I must not do with AI outputs (e.g., treat them as final decisions).
  • Q47. I know where to find policies and escalation paths for AI matching questions.
  • Q48. I feel confident handling employee concerns about AI and internal mobility.

Block 9: Process efficiency (Managers/HRBPs)

  • Q49. AI-supported matching reduces the time I spend on staffing and internal role searches.
  • Q50. AI suggestions integrate smoothly into our talent review or staffing workflow.
  • Q51. AI suggestions reduce the number of applications that are not a good fit.
  • Q52. AI matching helps us identify internal candidates earlier in the staffing process.
  • Q53. The tool supports succession planning by making pipelines and potential candidates more visible.
  • Q54. The admin effort to maintain skills data is reasonable for managers and teams.

Block 10: Match quality (Managers/HRBPs)

  • Q55. AI matching surfaces "hidden" talent beyond the usual internal networks.
  • Q56. AI suggestions align with role requirements and realistic performance expectations.
  • Q57. The AI explanations ("why was this person suggested?") are clear enough for follow-up conversations.
  • Q58. AI suggestions support lateral moves and development moves, not only promotions.
  • Q59. AI matching works for project staffing and short-term gigs, not only permanent roles.
  • Q60. I have seen cases where AI matching improved a mobility outcome for the business.

Block 11: Governance and guardrails (Managers/HRBPs)

  • Q61. We have clear rules for which decisions can use AI support and which cannot.
  • Q62. We have a clear process to challenge AI outputs that seem biased or incorrect.
  • Q63. We document when AI was used and what human judgment was applied.
  • Q64. Accountability is clear: there is always a human owner responsible for the final decision.
  • Q65. Data access and permissions for AI matching are clear and consistently applied.
  • Q66. Our works agreement / internal policy covers AI-supported mobility in a practical way.

Overall ratings (0–10, NPS-style)

  • R1 (Employees). How much do you trust AI-supported matching to treat you fairly in internal mobility? (0–10)
  • R2 (Employees). How useful are AI-based suggestions for your career planning? (0–10)
  • R3 (Employees). How clear is it to you why you received specific AI suggestions? (0–10)
  • R4 (Managers/HRBPs). How much do you trust AI-supported matching to be fair across employee groups? (0–10)
  • R5 (Managers/HRBPs). How useful is AI matching for staffing, talent reviews, and succession discussions? (0–10)
  • R6 (Managers/HRBPs). How confident are you explaining AI-supported mobility to employees and the works council? (0–10)

Open-ended questions

  • O1 (all). Describe one situation where AI-based suggestions improved an internal mobility outcome.
  • O2 (all). Where does AI currently make internal mobility harder, slower, or more confusing?
  • O3 (employees only). What information would help you trust AI suggestions more?
  • O4 (employees only). What worries you most about AI in internal mobility — fairness, privacy, manager reactions, or something else?
  • O5 (employees only). Which data should never be used for AI matching at our company, and why?
  • O6 (managers/HRBPs only). What guardrails or policies are missing for responsible AI-supported mobility?
  • O7 (managers/HRBPs only). What training would help you use AI matching better in staffing and talent reviews?

How to run AI-enabled internal mobility survey questions: timing and sampling

Launch the survey after employees have had their first real experience with the AI tool — not after the launch email. A good trigger: "Employees received suggestions and had at least two weeks to act on them," or "A talent review used AI suggestions at least once." In DACH contexts, involve the works council and data protection officer early, because trust issues surface faster when employees suspect hidden performance evaluation.

  1. Define pilot population and minimum reporting groups (n ≥ 10 per slice).
  2. Send survey 10–14 days after first AI suggestions; keep open for 7 days.
  3. Analyze within ≤ 10 days; publish top findings and next steps within ≤ 21 days.
  4. Implement fixes within ≤ 45 days; run a short pulse (12–15 items).
  5. Make the scale-up decision only after Wave 2 shows stable or improving trust.

Keep your first pilot tight: 1–3 business units, one region, one clear use case (roles, projects, gigs, or mentoring). Then run the survey in two waves: Wave 1 after the first matching experience; Wave 2 after you have shipped at least one or two visible changes. That second wave is where you see whether trust and perceived fairness can actually move. If participation drops below 60% in a pilot, treat that as a signal too — people may not feel safe, or don't believe feedback will change anything.

Scoring and interpretation: what "good" looks like by dimension

Score by dimension, not by individual item. You want to know whether you have a transparency problem, a fairness problem, or a safety problem. Pair that with the overall impact items (Q37–Q42) to avoid local optimization: transparency can rise while relevance stays low, and employees still won't use the tool.

DimensionQuestionsHealthy signalWatch-out signal
Awareness & understandingQ1–Q6, Q43–Q48Avg ≥ 4.0; low variance across teamsAvg < 3.5 or managers score ≥ 0.4 higher than employees
Transparency & controlQ7–Q12Avg ≥ 3.9 and R3 ≥ 7.0Q7 or Q11 < 3.2, or R3 < 6.5
Quality & relevanceQ13–Q18, Q55–Q60Avg ≥ 3.8 and R2/R5 ≥ 7.0Q15 < 3.3 (weak explanations) or Q13 < 3.3 (weak fit)
Fairness & biasQ19–Q24Avg ≥ 3.9; group gaps < 0.3Avg < 3.4 or any group gap ≥ 0.5
Psychological safetyQ25–Q30, Q61–Q66Avg ≥ 4.0 and Q26 ≥ 3.8Q25 or Q28 < 3.5, or manager optimism gap ≥ 0.4
Data & privacy trustQ31–Q36, Q65–Q66Avg ≥ 4.0 and Q32 ≥ 3.8Q32 < 3.3 (visibility unclear) or Q34 < 3.5 (retention worries)
Overall impactQ37–Q42Avg ≥ 3.9; improving by ≥ 0.2 between wavesFlat or declining after fixes

A group gap of ≥ 0.5 between part-time and full-time, remote and office, or different locations should be treated like a product defect — until proven otherwise. Don't debate intent; investigate root cause.

Interventions: what to do when scores are low

Avoid the reflex to turn off AI. Employees and managers typically ask for clearer boundaries — not less technology. The most effective fixes are operational: better explanations, better data hygiene, and better manager conversations. The following logic maps each signal to the right intervention:

  1. If transparency is low (Q7–Q12): fix explanations and user controls first.
  2. If relevance is low (Q13–Q18): fix role requirements and skills data quality.
  3. If fairness is low (Q19–Q24): run group-gap audits and adjust matching rules.
  4. If safety is low (Q25–Q30): coach managers and protect mobility exploration signals.
  5. If privacy trust is low (Q31–Q36): clarify permissions, retention, and access logs.

Managers need scripts: how to talk about AI suggestions, what to say when suggestions are wrong, and how to encourage internal moves without penalizing curiosity. The AI training for managers playbook is a practical reference for what managers need to do differently in 1:1s, reviews, and decisions when AI is present.

Survey blueprints for different phases

You don't need all items every time. Use the full bank once, then move to a short pulse that tracks the same dimensions. This also simplifies works council alignment: fewer questions, clearer purpose, faster action.

BlueprintWhen to useAudienceRecommended itemsTarget length
(a) Employees after first pilot wave10–14 days after first AI suggestionsEmployees in pilotQ1–Q6, Q7–Q12, Q13–Q18, Q19–Q24, Q25–Q30, Q37–Q42 + R1–R3 + O3–O518–22 items
(b) Managers/HRBPs after talent review3–10 days after AI-assisted talent reviewManagers + HRBPsQ43–Q48, Q49–Q54, Q55–Q60, Q61–Q66 + R4–R6 + O6–O718–22 items
(c) Short combined pulse in pilotEvery 6–8 weeks during pilotAllEmployees: Q7, Q13, Q19, Q25, Q32, Q37 + R1/R2; Managers: Q43, Q55, Q62 + R4/R512–15 items
(d) Follow-up after rollout6–12 months after scalingAllCore of all dimensions: Q1–Q42 + manager blocks Q43–Q66 + R1–R620–28 items

DACH governance: works council and data protection in practice

In DACH, perceived legitimacy matters as much as model quality. Employees will ask: "Who sees this?" "Can this hurt me?" "Is this a hidden performance signal?" Answer those questions in writing before the survey goes out.

Co-determination under German labor law

AI matching systems that influence internal staffing decisions are subject to the works council's co-determination rights under § 87 para. 1 no. 6 BetrVG if the system is objectively capable of monitoring employee behavior or performance — regardless of whether the employer intends to use it for that purpose. Under the consistent case law of the Federal Labor Court (BAG), objective capability to monitor is sufficient to trigger co-determination. A works agreement (Dienstvereinbarung) should define purpose, data sources, access rights, human decision authority, and escalation routes.

EU AI Act: high-risk classification from August 2026

AI systems that influence employment decisions — including internal role matching and skills-based staffing — are classified as high-risk under Annex III of the EU AI Act. Core deployer obligations apply from August 2, 2026: risk assessments, documentation, human oversight, and — under Article 86 EU AI Act — the right of employees to request an explanation for decisions influenced by a high-risk AI system. Inform employees and works councils before deploying the system.

GDPR checklist for the survey

  • No results sliced below n ≥ 10 per group; no team view for groups with ≤ 3 people.
  • Review and redact open-text comments for identifiers before sharing with any manager.
  • Include the AI matching system in your data processing records (GDPR Art. 30 documentation).
  • Define an escalation path for fairness concerns: HRBP, DPO, or a joint HR–works council channel; first response within ≤ 7 days.
  • Involve the works council before the pilot survey — share purpose, exact items, anonymity rules, and who sees results.

If you already run structured employee listening programs, reuse your existing governance patterns. The employee survey templates guide includes a works council and GDPR checklist that can be adapted directly for AI mobility feedback.

Responsibilities and follow-up

Treat follow-up like an operations process. Route signals by topic: managers own psychological safety and mobility support at team level; HR owns process clarity, communication, and capability building; IT/HRIS owns tool changes; DPO and works council partners own privacy and co-determination topics.

Signal / item areaThresholdRecommended actionOwnerTimeline
Awareness & understanding (Q1–Q6, Q43–Q48)Avg < 3.5Publish a 1-page "AI matching explained" FAQ + 30-min briefing per teamHR (People Ops)Draft ≤ 14 days; briefings ≤ 30 days
Transparency & control (Q7–Q12)Avg < 3.2 or R3 < 6.5Add "why suggested" explanations + workflow for profile correctionsHR (Talent) + IT/HRISBacklog ≤ 21 days; first release ≤ 60 days
Quality & relevance (Q13–Q18)Avg < 3.3 or R2/R5 < 6.5Audit role requirements + refresh skills taxonomy for top 10 pilot rolesRole owners + HR (Skills)Audit ≤ 14 days; updated profiles ≤ 45 days
Fairness (Q19–Q24)Avg < 3.4 or group gap ≥ 0.5Group-gap audit + adjust matching rules and human review stepsHR (People Analytics) + DPOAnalysis ≤ 21 days; mitigations agreed ≤ 45 days
Psychological safety (Q25–Q30)Avg < 3.5 or Q26 < 3.2Manager enablement: mobility conversation scripts + "no retaliation" commitmentBusiness leaders + HRBPsScripts ≤ 14 days; manager sessions ≤ 30 days
Privacy trust (Q31–Q36, Q65–Q66)Avg < 3.6 or Q32 < 3.3Clarify permissions, retention, and access logs; update works agreement if neededDPO + HR (Compliance) + works councilClarifications ≤ 30 days; policy update ≤ 90 days

Response time standards: ≤ 24 hours for any comment signaling retaliation or data misuse; ≤ 7 days to acknowledge fairness concerns and outline next steps; ≤ 30 days to publish a concrete action plan with owners and deadlines.

For fair evaluation of mobility decisions, structured calibration processes matter. The talent calibration guide provides a practical model for role standards, evidence requirements, and decision documentation that pairs well with AI-assisted suggestions.

Conclusion

AI-supported internal mobility can speed up matching and surface hidden talent — but only if employees and managers trust the process. These AI-enabled internal mobility survey questions give you three actionable signals: early warnings when transparency or psychological safety breaks down, clearer foundations for conversations between employees and managers about growth moves, and priorities for improving data quality, governance, and workflows.

Start small and concrete: one pilot group, blueprint (a) and (b) in your survey tool, owners for follow-up agreed before you send the first invitation. Commit to publishing results and changes within ≤ 30 days. When employees see that feedback leads to better explanations, clearer permissions, and different manager behavior, adoption follows as a byproduct of trust.

FAQ

How often should you run this survey?

For pilots: Wave 1 about 10–14 days after employees first receive AI suggestions, then a short pulse after you ship fixes (usually 6–8 weeks later). After rollout, run a combined pulse every 6–8 weeks for the first six months, then annually or after material changes to the matching system.

What should you do when scores are very low (e.g., avg below 3.0)?

Treat avg below 3.0 as a stop-and-fix signal. Pause scaling, identify the failing dimension (transparency, fairness, safety, or privacy), and implement one visible change within ≤ 45 days. Publish what changed. Then re-run only the core pulse items for that dimension. If scores stay low after two waves, revisit the use case or governance approach.

How do you handle critical comments about bias or retaliation?

Separate two paths: (1) aggregated learning for process improvement and (2) individual risk handling. For any comment suggesting retaliation, discrimination, or data misuse, respond within ≤ 24 hours through your established employee relations channel. For bias concerns, acknowledge within ≤ 7 days, explain the review steps, and share the mitigation plan. Keep anonymity intact and redact identifiers before sharing open-text responses.

How do you align with works council and GDPR requirements?

Bring the works council in before the pilot survey — not after complaints. Share the survey purpose, exact items, anonymity rules (n ≥ 10), and who can see results. Explain data flows, retention, and access rights for both AI matching and survey data, and document them in a works agreement. For the legal framework, the General Data Protection Regulation (GDPR) governs data handling, and — from August 2026 — the EU AI Act adds transparency and explanation obligations for high-risk systems in employment contexts.

Which questions work best for a short pulse between full surveys?

For a 10–12 item pulse: one item from each core dimension — Q7 (transparency), Q13 (relevance), Q19 (fairness), Q25 (safety), Q32 (privacy), Q37 (overall impact) — plus R1 and R2 for employees and Q43 and Q55 for managers. Add O1 and O2 as open-ended questions. This preserves trend comparability while keeping the effort low.

What is the difference between this and a general internal mobility survey?

A general internal mobility survey measures visibility, fairness, manager and HR support, skills readiness, and move experience. This AI-specific extension adds: understanding of the AI matching process, data and algorithm transparency, governance quality, and the specific trust people place in algorithmic decision support. Both instruments complement each other — the general survey as a baseline, this one as an AI-specific layer for pilot groups.

Jürgen Ulbrich

CEO & Co-Founder of Sprad

Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.

Free Templates &Downloads

Become part of the community in just 26 seconds and get free access to over 100 resources, templates, and guides.

Mitarbeiterengagement-Umfrage zur Identifizierung der Motivation und Zufriedenheit
Video
Employee Engagement & Retention
Mitarbeiterengagement-Umfrage zur Identifizierung der Motivation und Zufriedenheit
Free IDP Template Excel with SMART Goals & Skills Assessment | Individual Development Plan
Video
Performance Management
Free IDP Template Excel with SMART Goals & Skills Assessment | Individual Development Plan

The People Powered HR Community is for HR professionals who put people at the center of their HR and recruiting work. Together, let’s turn our shared conviction into a movement that transforms the world of HR.