Describe your schools and purchasing questions. Makeform creates a survey that shows where devices, software, connectivity, training, and support fall short.
Send responses to Google Sheets, Slack, and Zapier.
Sample prompts for the survey builder
Choose a prompt, adapt it to your district, or send it to the builder. These structures are examples, not live AI results.
Audience
Teachers and instructional staff across multiple schools
Format
Branching survey with school and role filters
Prompt size
327 chars
Example survey structure
Branching survey with school and role filters
School, grade band, subject, and role
Rate access, reliability, and support
Which teaching tasks are being blocked?
Rank your top three needs
What context should decision-makers know?
Suggested analysis tags
Access gap
Training need
Purchase priority
Ask respondents to separate access problems from confidence problems: a missing device requires a different purchase than unfamiliar software.
Step 1
Segment
school, role, grade band, and subject
Step 2
Measure
access, reliability, confidence, and impact
Step 3
Prioritize
rank hardware, software, support, and training
Step 4
Plan
compare needs before budgets and purchases
From opinions to purchasing signals
Distinguish a broken device from a missing capability, a training issue from a license gap, and a frequent obstacle from a rare inconvenience.
Show relevant questions to teachers, librarians, counselors, aides, and office staff while keeping shared measures for comparison.
Pair how often a problem occurs with what it disrupts: planning, instruction, assessment, communication, accessibility, or administration.
Rankings help respondents separate urgent needs from a long wish list that cannot guide purchasing.
Four lenses
Use actionable categories so administrators can route findings to instruction, IT, professional learning, and purchasing teams.
Inventory availability, condition, sharing, peripherals, charging, and tasks current equipment cannot support.
Capture usage, reliability, duplication, missing capabilities, integrations, and keep-or-replace recommendations.
Locate weak coverage, sign-in friction, downtime, support confusion, and unresolved issues.
Measure confidence by workflow, then collect preferred formats, schedules, and coaching needs.
Survey workflow
Start with a decision, collect comparable evidence, and retain context for each priority.
Specify the budget, refresh, license review, support redesign, or learning plan so every question supports a choice.
Add your platforms, schools, roles, and reporting period; remove topics you will not analyze.
Route respondents to device, software, or role-specific follow-ups without lengthening every response.
Compare schools and roles, read comments beside ratings, and separate broad patterns from isolated requests.
Question design
Structured measures explain the blocked work, affected people, and response worth investigating.
Field guide
Use these sections to connect staff experience to a specific equipment, platform, support, or training decision.
Respondent context
Collect only dimensions you will analyze. Avoid names unless follow-up requires them.
Access & condition
Ask what is available, whether it is available when needed, and how condition affects work.
Software fit
Measure workflow fit, overlap, and missing capabilities. Ask for outcomes before vendor recommendations.
Infrastructure & help
Capture where connectivity or access fails and how staff seek help. Add urgency and instructional impact.
Confidence & learning
Rate confidence for specific workflows, then ask how and when staff prefer to learn.
Priority & evidence
Rank a short list and explain the first choice. Capture affected users, frequency, impact, and workarounds.
Related tools
Pair staff needs with student experience, software review, training assessment, and broad survey tools already available in Makeform.
Ask students about device access, connectivity, and barriers from their perspective.
Open toolReview software usage, fit, reliability, and missing capabilities across a defined audience.
Open toolIdentify confidence gaps and preferred learning formats for a focused training plan.
Open toolCreate a separate observation or evaluation workflow when the goal is teacher practice, not technology purchasing.
Open toolCollect student feedback on learning experiences using structured ratings and comments.
Open toolStart a general-purpose survey when your research question extends beyond school technology.
Open toolFAQ
Practical answers for administrators planning a staff needs assessment.
It asks teachers and staff about technology access, blocked tasks, infrastructure, support, and training. Administrators can use responses when investigating purchases and planning professional learning.
Ask about role, device availability, software gaps, connectivity, support, workflow confidence, and ranked priorities. Pair ratings with frequency and impact for useful context.
Anonymous responses can encourage candid feedback, while school and role still support segmentation. Make contact optional for follow-up, and avoid student names or unrelated personal information.
Focus on decisions you expect to make, branch by role, and remove questions you will not analyze. Use a shared core with targeted follow-ups.
Compare ranked needs with frequency, impact, affected roles, and workarounds. Group requests by needed outcome rather than product name, then create a shortlist for technical, instructional, accessibility, security, cost, and procurement review.
Yes. Use consistent school, role, grade-band, subject, and rating fields. Consider group sizes when sharing results so reports do not identify individuals.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge; it does not unlock additional response capacity.
Run it when the answers can influence a decision, such as before annual planning, a device refresh, a major license renewal, or a professional-learning cycle. Keep a few core measures consistent if you want to compare changes, and update tool-specific questions as the environment changes.
Turn staff experience into clearer priorities.
