
An AI usage survey is a ten-minute anonymous questionnaire that measures how often your people use AI, how deeply, how safely, and what's stopping them. Scored properly, it gives you two readings: where the business sits, which tells you what to fix first, and where each person sits, which tells you what training they need. Run it before you design any AI training, not after.
Everything you need is below: the seventeen questions, the points for each answer, the scoring, and the tools to run it in.
Why does AI training miss when you skip the survey?
Because it's pitched at an average employee who doesn't exist. In most rooms, a few people have used ChatGPT or Claude every day for a year, often on a personal account, and a few have never opened either. Teach the middle and you lose both ends.
Leaders usually can't see the spread. McKinsey asked executives what share of their staff used generative AI for at least 30% of their daily work: they guessed 4%, and 13% of employees said they did (McKinsey, January 2025). In the global study by KPMG and the University of Melbourne, 57% of employees said they hide their use of AI and present AI-generated work as their own (Melbourne Business School, April 2025).
The same study found 47% of employees had received any AI training, and 40% said their workplace had a policy or guidance on generative AI. So people are using AI without guidance, and often without telling anyone. Training designed without knowing that is a guess.
You can't design AI training for a team you haven't measured.
When we start AI training with a business, this survey comes first. It answers two different questions, and the training needs both.
Team by team, how widely and how safely AI is used. It decides the order of work: rules and tools first, or training first.
A level from Starter to Power user, plus a flag for anyone using AI unsafely. It decides which training track each person joins.
What should an AI usage survey measure?
Four things, which we call Intersect's Four Rs: Reach, Routine, Risk and Readiness. Most AI surveys stop at the first one and ask who uses AI and how often. That measures adoption. It doesn't tell you what to teach.
Intersect's Four Rs of AI usage
Who uses AI, how often, and which tools.
Tells you: how far AI has spread, and where it hasn't.
How deeply it's built into real work, and the time it saves.
Tells you: who's dabbling and who depends on it.
Which accounts people use, what data goes in, whether they check the output, and whether they'd admit to using it.
Tells you: whether to fix rules and tools before you push adoption.
Confidence, blockers, how people want to learn, and the task they'd hand over first.
Tells you: what the training covers and how to run it.
Reach and Routine add up to a Usage score. Risk becomes a Safety score. Readiness isn't scored at all, because it's the brief for your training.
What questions should an AI usage survey ask?
Seventeen, which takes about ten minutes. Two are about the person's team and role, so you can compare groups. The rest map to the Four Rs, and every scored answer carries between 0 and 4 points.
Copy the bank into whichever tool you use and keep the wording. It's written so nobody has to confess to anything to answer honestly.
- 1
Which team do you work in?
[Your list of teams]Only list teams of five or more people. Merge the smaller ones.
- 2
Which best describes your role?
Individual contributorManagerSenior leader
- 3
How often do you use AI tools (such as ChatGPT, Claude, Copilot or Gemini) for work?
Never 0A few times a year 1A few times a month 2A few times a week 3Daily 4If someone answers Never, skip them to question 12.
- 4
Which AI tools have you used for work in the past month? Tick all that apply.
ChatGPTClaudeMicrosoft CopilotGoogle GeminiAI built into tools we already useOtherNot scored. Compare the answers with the tools you actually provide.
- 5
Which sentence best fits how you use AI at work?
I ask it the odd question instead of searching 1I use it to draft or summarise, then rework the result 2It's part of how I do specific tasks every week 3I've set up reusable prompts, projects, custom assistants or automations 4 - 6
What do you use AI for? Tick all that apply.
Finding informationWriting or editing emails and messagesSummarising documents or meetingsDrafting reports, proposals or slidesAnalysing data or spreadsheetsResearchBrainstorming and planningImages or designCode or formulasAutomating a repeated taskScore by count: 1–2 ticks = 1, 3–4 = 2, 5–6 = 3, 7 or more = 4.
- 7
Roughly how much time does AI save you in a typical week?
None 0Under 30 minutes 130–60 minutes 21–3 hours 3More than 3 hours 4
- 8
Which accounts do you use AI on for work?
Only accounts the company provides 4A mix of company and personal accounts 2Not sure 1Only my own personal accounts 0 - 9
In the past three months, have you put any of these into an AI tool the company doesn't provide? Tick all that apply.
Customer or client personal detailsConfidential financial figuresContracts or legal documentsStaff or HR informationPasswords, code or system detailsNone of theseScore: None of these = 4, one type = 2, two or more = 0.
- 10
When AI gives you something you'll use in your work, how often do you check it?
Always 4Usually 3Sometimes 1Rarely or never 0 - 11
If you used AI on a piece of work, would you tell your manager?
Yes 4Depends on the work 2Probably not 0 - 12
Does the company have rules on using AI at work?
Yes, and I've read them 4Yes, but I haven't read them 2I don't think we have any 1Not sure 0Everyone answers this one, including people who skipped from question 3.
- 13
How confident are you using AI for your work?
1 Not at all2345 Very - 14
What stops you using AI more? Tick all that apply.
I don't know what it's good for in my jobI'm not sure what I'm allowed to doI don't have access to a good toolNo time to learnI don't trust the answersWorried about what it means for my jobOur systems and data aren't connected to itNothing, I use it as much as I want - 15
How would you like to learn? Pick up to two.
Hands-on session with my teamOne-to-one helpShort videosWritten guides and prompt librariesLearning from a colleague who's good at it - 16
Which task in your week would you most like AI to take off your hands?
Open answer - 17
Have you found or built anything with AI that colleagues should know about?
Open answer
How do you score an AI usage survey?
Each person gets two scores out of 100, one for usage and one for safety. Export the responses to a spreadsheet, convert each answer to its points, and apply two formulas.
The scoring
(Q3 + Q5 + Q6 + Q7) ÷ 16 × 100Reach and Routine. Anyone who answered Never to question 3 scores 0.(Q8 + Q9 + Q10 + Q11 + Q12) ÷ 20 × 100Risk. Only for people who use AI; non-users have no Safety score.Here's an illustrative example. Someone in finance uses ChatGPT a few times a week (3), drafts with it and then reworks the result (2), ticks four tasks (2) and saves 30 to 60 minutes a week (2). That's 9 out of 16, a Usage score of 56: a Regular.
They use a personal account only (0), have pasted confidential figures in once (2), usually check the output (3), would tell their manager depending on the work (2) and haven't read the rules (2). That's 9 out of 20, a Safety score of 45. A Regular with a safety flag gets the safe-use session before anything else.
The business reading: Intersect's AI Usage Map
For the business view, take the median Usage and Safety score for each team and place it on a simple two-by-two. Where a team lands tells you what to do first.
Intersect's AI Usage Map: what to do first
Safe because almost nobody uses it. Start with foundations and a tool people can actually reach.
Move from personal tips to team workflows, and make your power users champions.
Few users, and the ones there take risks. Fix accounts and rules before you push adoption.
People are ahead of the company. Give them an approved tool and clear rules, with an amnesty, then train.
Each team plotted at its median Usage / Safety score, with 50 as the line on both. Teams and scores are illustrative, not client data.
How do the scores shape AI training for employees?
Levels decide who goes into which track. The map decides the order. The Readiness answers decide what goes into each session.
From survey levels to AI training tracks
| Level | Track | What it covers | Format |
|---|---|---|---|
| Any levelSafety under 50 | Safe use, first | Approved accounts, what data never goes in, how to check output, and the rules in plain words | Short session, before anything else |
| Starter0–24 | Foundations | What AI is good and bad at, the approved tool, and five uses in their own job | Hands-on, small groups, their own work on screen |
| Explorer25–49 | Everyday use | Prompting properly, tasks for their role, checking output before it's used | Team workshops built on question 16 answers |
| Regular50–74 | Workflows | Projects, reusable prompts, connecting AI to the tools they use, turning a repeat task into a process | Short sessions plus a shared prompt library |
| Power user75–100 | Builders and champions | Custom assistants and automations, the rules for building them, coaching colleagues | Small cohort, real builds |
Order the tracks by the map: rules and tools first in Shadow AI and Quiet risk teams, foundations first in Sitting out teams, workflows first in Ready to build teams.
The blockers in question 14 tell you whether training is even the fix. If "I'm not sure what I'm allowed to do" comes top, you need rules before a course, and our one-page AI policy template is a place to start. If it's "I don't have access to a good tool", training will stall until you pick one: here's how to set up a shared AI workspace in an afternoon.
If it's "I don't know what it's good for in my job", build the sessions around the answers to question 16. Those are tasks people already want gone, so the examples land.
Your power users are your cheapest trainers, and question 17 finds them. Put managers through early too. Gallup found that employees in AI-adopting organisations who strongly agree their manager supports their team's use of AI are 1.7 times as likely to use it a few times a week or more (Gallup, US data, May 2026).
How do you run the survey so people tell the truth?
Promise an amnesty, make it genuinely anonymous, and show people what happened next. Without all three, the people using AI on personal accounts will answer the way they think you want.
How to run it: six steps
- Week 0Decide what you'll do with the results
Agree who sees them, what you're prepared to change and the date you'll share them back. If you can't answer that, don't send it.
- Week 0Send it from the top, with an amnesty
The CEO or MD explains why, says it's anonymous, and says plainly that nobody gets in trouble for anything they've done with AI so far.
- Days 1–10Keep it open for two working weeks
Remind people on day 3 and day 7. Better still, give teams ten minutes in a meeting to fill it in.
- Week 3Share the results back
Company numbers, the map and what happens next. Never show a group of fewer than five.
- Week 4Start the training
Safe use first for anyone flagged, then the tracks by level.
- Month 6Run it again
Same questions, so the change in scores shows whether the training worked.
Anonymous comes down to settings and one habit. Don't collect names or emails, don't ask anything that would identify someone in a small team, and never report a group smaller than five. Microsoft's own guidance warns that a form sent to a few specific people can be matched to its answers even with names switched off (Microsoft).
If you already pay for business accounts on ChatGPT, Claude or Copilot, set the survey's Reach answers against what your admin usage data shows. A big gap between the two is your shadow AI.
Which survey tool should you use?
The one your people already sign in to. That's Microsoft Forms if you run on Microsoft 365, or Google Forms if you run on Google Workspace. Both come with what you already pay for, and both can be set so they don't record who answered.
Six tools for running an AI usage survey
| Tool | Best for | Keeping it anonymous | Cost |
|---|---|---|---|
| Companies on Microsoft 365 | Choose "Only people in my organization can respond" and untick "Record name" | Included in Microsoft 365 | |
| Companies on Google Workspace | Leave "Collect email addresses" off. People may sign in, but names aren't recorded unless you collect emails | Included in Workspace | |
| A cleaner-looking form for free | No sign-in needed. Don't add name or email fields | Free plan: unlimited forms and responses, fair use | |
| Teams that want built-in charts and analysis | Check the collector settings before sending, and don't ask for names | Free plan stops at 10 questions, so this survey needs a paid plan | |
| One question at a time, polished look | Don't ask for names or emails | Free plan caps at 10 responses a month | |
| Companies already running engagement surveys on it | Built-in minimum group size hides results for small groups | Paid platform |
Checked against each vendor's own pages on 9 November 2026. Whichever you use, export the answers to a spreadsheet to score them.
Pay for something else only if you need what it adds. Culture Amp, for example, hides results for any group below a minimum size you set, so nobody can filter their way to one person's answers (Culture Amp). With the free tools, you enforce that rule yourself when you cut the data.
Where does this break?
- Self-reporting flatters. Even anonymously, people overstate time saved and understate risky use. Treat question 7 as a direction, not a number for a business case.
- Small companies can't stay anonymous. If most teams have fewer than five people, team results identify individuals. Report company-level numbers only, or swap the survey for short conversations.
- The scores are ours, not a benchmark. The weights are our judgement. Use them to compare your own teams and track change, not to compare with another company. Question 3 uses frequency bands that line up with Gallup's, so that one answer can sit beside Gallup's US figures: 15% of employees use AI daily and 30% a few times a week or more (Gallup, May 2026).
- A survey finds people, not value. It tells you who uses AI and how. It won't tell you which processes are worth automating; that's the job of an AI readiness assessment.
- One broken promise ends it. If anyone is disciplined for something they admitted in the survey, nobody will answer honestly again.
What to do next
Pick your tool, copy the seventeen questions, and agree what you'll do with the answers before you send anything. Then put a date in the diary six months out to run it again. The second survey is the one that tells you whether the training worked.
Want us to run it and build the training around it?
We'll run the survey, score it, map your teams and build training tracks from the results, starting with anyone who needs the safe-use basics first.
FAQs
How long should an AI usage survey be?
About ten minutes, which is seventeen questions. That's short enough to fill in during a team meeting, which is the easiest way to get a good response rate. If you have to cut, keep questions 3, 5, 8, 9, 14 and 16.
Should an AI usage survey be anonymous?
Yes. Questions 8, 9 and 11 ask people to admit things. Without anonymity and a clear amnesty, you'll measure what people think you want to hear, which is the opposite of the point.
Should leaders take the survey too?
Yes, and ask them one extra question first: what share of their team they think uses AI weekly. Put the guess next to the real answer when you share results. If the guess is low, that's your case for training made for you.
Can we use AI to analyse the open-text answers?
Yes, if it's a tool the company provides and the answers contain no names. Ask it to group the answers to question 16 into themes and count them. Those themes are your first training examples and your first candidates for automation.
How often should we run it?
Every six months, with the same questions, so the change in scores shows whether training and tools are working. Add new questions at the end rather than rewording old ones.
Related reading
- The One-Page AI Policy: A Template You Can Adopt This Week
- How to Prompt ChatGPT and Claude: An AI 101 for Your Team
- What an AI Readiness Assessment Should Actually Cover
Sources
- McKinsey: Leaders underestimate employees’ AI use, from Superagency in the Workplace, January 2025
- Melbourne Business School: Trust, attitudes and use of AI, a global study 2025 (University of Melbourne and KPMG), April 2025
- Gallup: AI indicator, US employees, data to May 2026, accessed 9 November 2026
- Microsoft Support: Set up your survey so names aren’t recorded, accessed 9 November 2026
- Microsoft Support: Adjust your form or quiz settings in Microsoft Forms, accessed 9 November 2026
- Google Docs Editors Help: Publish and share your form with responders, accessed 9 November 2026
- Google Help: Collect respondents’ email addresses using Google Forms, accessed 9 November 2026
- Tally: free plan, unlimited forms and submissions under fair use, accessed 9 November 2026
- SurveyMonkey: plans and pricing, accessed 9 November 2026
- Typeform Help Center: Free plan, accessed 9 November 2026
- Culture Amp: Confidentiality protections in reporting, accessed 9 November 2026



