Describe your audience and planning decision. Makeform builds a technology usage survey covering access, frequency, confidence, barriers, and support needs.
Send survey responses to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose an example, adapt it, or send it into the Makeform builder. The structure shown is not a live AI result.
Audience
Students using technology at school and home
Format
Mobile-friendly survey with conditional access questions
Prompt size
346 chars
Example survey structure
Mobile-friendly survey with conditional access questions
Which devices can you use for schoolwork?
How dependable is your internet outside school?
How often do you use each learning tool?
What gets in the way of completing digital work?
What technology support would help most?
Suggested analysis tags
Access gaps
Training needs
Tool requests
Ask what task people need to complete, not only which device they own.
Step 1
Define
audience, decision, and survey window
Step 2
Measure
access, use, confidence, and barriers
Step 3
Segment
compare roles, locations, or grade bands
Step 4
Plan
turn patterns into prioritized actions
Planning evidence
An inventory says what exists. A survey shows how technology fits real work or learning and where access, reliability, or confidence blocks progress.
Use one frequency scale, then connect tool use to teaching, collaboration, reporting, or remote work.
Branch by location, role, or grade band to find group-specific problems and skip irrelevant questions.
Structured questions reveal patterns; open responses preserve explanations the choices missed.
Designed for two settings
Use language, segments, and examples that match what respondents actually do.
Cover learning devices, home internet, shared access, platform use, and support.
Connect classroom tools to teaching, accessibility, reliability, and professional learning.
Map approved software to tasks, workarounds, confidence, and training.
Segment priorities while avoiding unnecessary personal details.
Survey workflow
Define the decision, generate questions, pilot them, and review meaningful groups.
Choose device replacement, software renewal, training, connectivity, classroom practice, or broader planning.
Describe the audience and tools, remove jargon, add local choices, and ask one idea at a time.
Test confusing terms, missing choices, mobile layout, length, and branching with a small mixed group.
Compare planned groups, then read comments for explanations before choosing actions.
Choose useful evidence
Surveys provide comparable input; records and conversations add context.
Field guide
Keep fields tied to your decision and explain how responses will be used.
Access
Separate availability from dependable access. A device may be shared, lack needed permissions, or lose connectivity.
Frequency
Ask about a defined period, such as a typical week. Let nonusers choose not applicable.
Experience
Confidence, satisfaction, and reliability are different ideas. Ask each about specific tasks.
Barriers
Offer specific barriers such as connectivity, condition, permissions, integration, accessibility, time, or instructions.
Support
Connect needed skills to tasks and ask about usable formats, timing, language, and channels.
Priorities
Ask respondents to rank feasible priorities, then add one optional field for context.
Related tools
Broaden the survey or focus on student, software, and connectivity needs.
FAQ
Answers for school leaders, IT teams, and operations staff.
It asks a defined group how they access and use devices, software, connectivity, and support. Schools and companies measure frequency, confidence, reliability, barriers, and priorities to inform planning.
Ask about available devices and internet, tools used during a typical period, tasks, confidence, reliability, barriers, support preferences, and ranked priorities. Add grade band, role, department, location, or work setting only when those comparisons affect action.
Use the shortest survey that supports the decision. A software pulse may be brief; a baseline may cover access, use, experience, barriers, and priorities. Pilot it on a phone and remove repeated or unused questions.
Not for a group-level baseline. Avoid names when grade band, program, or campus is enough. If follow-up is needed, explain why and use a separate optional contact field.
Use neutral wording and ask one idea at a time. Do not assume more technology is better. Offer not applicable and other choices, and let respondents report improvement, no change, or decline.
Yes. Branch after a role, grade band, department, device, or application choice. Each person sees a common baseline and relevant follow-ups. Keep shared measures identical when comparing groups.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and reuse your survey without a response cap. The paid tier removes the Makeform badge.
Review access, frequency, confidence, barriers, and priorities separately. Compare planned groups, note small response groups, and read comments. Check patterns against inventories, support records, or interviews before documenting actions.
Plan from how people actually use technology.
