Describe the system and what your crew needs before arrival. Makeform creates a pre installation questionnaire for site conditions, access, technical requirements, contacts, scheduling, and photos.
Route responses to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a scenario, customize its prompt, or send it into the builder. The fields are examples, not a live result.
Audience
IT teams preparing switches, access points, or cabling
Format
Technical site survey with conditional network fields
Prompt size
395 chars
Example questionnaire structure
Technical site survey with conditional network fields
Site, contacts, and access window
Rack space, power, and UPS details
ISP handoff, firewall, switches, and VLANs
Upload rack, pathway, and installation-area photos
Is the site ready for technical review?
Suggested routing tags
Ready to schedule
Details missing
Technical review
Ask for clearances, connection locations, and access constraints instead of one readiness question.
Step 1
Scope
system, quantities, rooms, and expected outcome
Step 2
Survey
access, measurements, utilities, and photos
Step 3
Review
installer identifies missing details and prerequisites
Step 4
Schedule
contacts, work window, and delivery plan confirmed
Arrive prepared
Ask for measurements, evidence, and ownership decisions that affect equipment and timing before a technician travels.
Collect clearances, utilities, connection locations, device counts, and photos instead of a general readiness statement.
Show rack, door, gas, or drainage questions only when the selected installation requires them.
Keep answers, files, contacts, and open issues together for estimators, managers, and technicians.
Installer scenarios
Start with one pattern, then add the measurements, utilities, and dependencies your crew checks.
Document ISP handoffs, rack space, power, switching, cable routes, and change windows.
Map doors, cameras, mounting surfaces, restricted areas, escorts, and location photos.
Capture dimensions, wall and ceiling conditions, platforms, lighting, and table connectivity.
Check delivery clearances, placement, utilities, trade prerequisites, storage, and commissioning contacts.
Build the intake
Define the scope, refine questions around site risks, and route responses to the project team.
Name the system, site, rooms, equipment, and decisions the crew must make.
Ask for dimensions, utility locations, models, owners, dates, and specified photos.
Branch by installation, room, utility, or access condition for relevant follow-ups.
Notify the owner, route answers, and follow up on missing details or files.
Questionnaire vs generic checklist
An online questionnaire collects structured answers and files for a specific customer site.
Field guide
Start with these six sections, then add product-specific tolerances, connections, and dependencies.
People and ownership
Capture separate project, technical, facilities, security, and after-hours contacts for installation day.
Site and access
Ask for arrival, check-in, delivery route, work hours, restricted zones, and escort requirements.
Existing environment
Request existing equipment, available capacity, connection points, mounting surfaces, obstructions, and planned removals.
Technical requirements
Use structured fields with units for power, network, utilities, cable distances, environment, and integrations.
Prerequisites and dependencies
List required trade work, network changes, coordination, migration, or removal with an owner and date.
Schedule and attachments
Collect work windows, interruptions, delivery appointments, staging space, acceptance contacts, and review files.
Related tools
Use related tools for onboarding, access, equipment checks, changes, and service follow-up.
Collect account, stakeholder, communication, and project-start details before technical discovery.
Open toolStandardize internal IT requests that lead to deployment, configuration, or installation work.
Open toolDocument equipment identity and condition before deployment or after commissioning.
Open toolGather visitor, timing, escort, and access details for technicians entering controlled sites.
Open toolRecord scope, schedule, cost-input, and approval impacts when site findings change the plan.
Open toolCapture technical symptoms, affected assets, and follow-up details after installation.
Open toolFAQ
Practical answers for installers, IT vendors, integrators, and project coordinators preparing a site visit.
It is an intake sent before equipment or technicians arrive. It collects scope, contacts, access, existing conditions, technical requirements, measurements, prerequisites, schedule, and files for planning.
Ask who owns the project, where work occurs, what exists, which utilities are available, what affects delivery or mounting, which tasks come first, when work is allowed, and which files verify the answers.
Request observable details: doorway width with units, outlet voltage and location, rack capacity, cable distance, or specified photos. Require an explanation for no or unknown.
Yes. Use conditional paths for network, AV, security, electrical, or equipment questions, then branch by area, utility, delivery method, or reuse.
Yes. Add uploads for plans, elevations, inventories, diagrams, exports, and photos. Label each field with the exact view or context required.
Use the person closest to each answer: the owner for scope, facilities for access and utilities, and IT for network details. Capture each contact in one response.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses. The paid tier removes the Makeform badge, so you can begin and continue using the questionnaire without a response or form limit on the free tier.
Route the response for technical review. Check fields and files, list unresolved items, assign prerequisite owners, and confirm scope and timing before scheduling.
Scope site before arrival.
