Describe your venue, campus, or property and how drone flights should be reviewed. Makeform turns your requirements into a structured request for operator details, the aircraft, flight window, operating area, insurance evidence, safety planning, and an approval decision.
Route drone requests to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a complete prompt, tailor the site rules, or send it to the Makeform builder. Each structure is an example you can edit before publishing.
Audience
Production crews and drone operators filming at an event venue
Format
Pre-event request with map, insurance, and review fields
Prompt size
525 chars
Example form structure
Pre-event request with map, insurance, and review fields
Operator and production company
Aircraft and pilot credential details
Requested flight window and backup date
Marked operating-area map
Insurance certificate and site-rule acknowledgment
Suggested routing tags
Needs review
More information
Decision recorded
Ask for a marked flight-area image and exact takeoff point. A venue name alone rarely tells a reviewer where the aircraft will operate.
Step 1
Request
operator, aircraft, purpose, and flight window
Step 2
Screen
map, insurance, site conflicts, and missing details
Step 3
Decide
conditions, reviewer, status, and response
Step 4
Record
one submission trail for the planned operation
Why structure the request
Reviewers need to see where, when, why, and how an operator plans to fly. A drone permission form puts those facts beside insurance evidence and site-specific concerns before anyone responds.
Structured dates, locations, operating boundaries, aircraft details, and purpose make requests comparable and expose gaps that would disappear in an email thread.
Operators can upload insurance documents, maps, and supporting materials with the submission, while reviewers can ask for updates before recording a decision.
Send each request to the right venue, school, or property contact and keep conditions, follow-up questions, and the final status tied to one response.
Adapt it to the site
Start with the closest use case, then replace the sample boundaries, contacts, restricted areas, and review steps with the rules used at your location.
Coordinate production schedules, guest arrival, rigging, outdoor spaces, and a designated launch area before doors open.
Ask about class hours, athletics, parking, student areas, neighboring property, and the campus contact supervising site access.
Capture inspection scope, tenants, rooftops, pedestrian areas, loading zones, and the work order behind a contractor flight.
Map temporary structures, vendors, queues, roads, performance times, and crowd-sensitive areas in the proposed operation.
Permission workflow
Generate the intake form, tune it to the property, and route each submission through the people responsible for access, scheduling, and operations.
Tell Makeform who requests flights, which areas need special attention, what files operators submit, and which internal contact reviews each request.
Add your real restricted areas, available flight windows, insurance requirements, site contacts, and conditional questions for crowds, roads, or night operations.
Notify the appropriate property or event lead, send incomplete submissions back for clarification, and keep requested changes attached to the original response.
Track who reviewed the request, when they responded, any site conditions they added, and whether the operator must provide revised details before the planned date.
Form vs email vs generic document
A decision is easier to revisit when the operator's details, attachments, reviewer questions, and site conditions stay together instead of being scattered across messages.
Field guide
The useful fields identify the people and aircraft, define the proposed operation precisely, surface site impacts, and give reviewers enough context to request changes or record their response.
Operator and client
Separate the person flying from the company, organizer, contractor, or media client commissioning the work. Reviewers then know who can revise the plan and who will be present on site.
Aircraft
Aircraft information helps distinguish a small inspection setup from a larger production operation. Use separate fields so reviewers can compare the submitted equipment with any revised plan.
Flight plan
A precise window and annotated map prevent the phrase over the property from becoming the entire plan. Collect both the primary operation and a weather backup where scheduling is tight.
Insurance and documents
Make uploads required when your internal process calls for them. Ask for the details your reviewer actually checks rather than accepting a filename with no coverage or expiry context.
Site and safety plan
Conditional fields can expand when an operator selects crowds, roads, neighboring property, restricted areas, or low-light operations. That keeps simple requests short without hiding complex impacts.
Review and decision
Use internal fields for ownership and status rather than editing the operator's answers. A recorded property decision does not replace any separate authorization or rule that may apply to the operation.
Related tools
Connect the drone request to contractor access, site inspection, insurance review, event-vendor intake, and incident follow-up using live Makeform tools.
Collect vendor contacts, setup needs, insurance files, and event-day operating details.
Open toolCoordinate who needs site access, which areas they need, and when they will arrive.
Open toolDocument roofs, grounds, assets, and follow-up items after an inspection.
Open toolGather policy references, effective dates, supporting files, and review notes.
Open toolCapture people, time, location, evidence, and follow-up if an issue occurs.
Open toolBuild repeatable checks for aircraft, batteries, cases, and support equipment.
Open toolFAQ
Practical answers for venue teams, school administrators, property managers, and operators setting up a consistent request process.
A drone permission form is an intake form an operator submits to a venue, school, land manager, or property owner before a proposed flight. It records who will operate, the aircraft, purpose, location, date and time, operating boundary, insurance evidence, site impacts, and supporting plans. The receiving organization can then request clarification, add site conditions, or record its decision.
Ask for the requested date, start and end time, backup weather window, takeoff and landing point, marked operating area, maximum planned altitude, route or activity, expected number of flights, and purpose. An annotated map is especially useful on large campuses or event sites. Add conditional questions for roads, crowds, temporary structures, neighboring property, restricted areas, or low-light operation.
Yes. Add file-upload fields for the insurance certificate, site map, client brief, credential evidence, or other materials your process asks reviewers to inspect. Pair uploads with structured fields such as policy reference, effective dates, and expiry so important details are visible without relying only on a filename. Reviewers can request a replacement when a document is incomplete or out of date.
Yes. Use conditional logic to show questions based on site type, flight purpose, or selected operating area. A school version might ask about class and athletics schedules; a venue version can ask about guest arrival and production activity; a managed-property version can cover tenants, rooftops, loading zones, and work orders. Keep common operator and aircraft fields shared across every branch.
No. A property or venue response records that organization's decision about its site and the flight plan it reviewed. It does not replace separate airspace authorization, operating requirements, permits, or other approvals that may apply. State that distinction in the form and ask operators to identify relevant supporting materials without presenting the form itself as an official authorization.
Include internal fields for review owner, status, missing information, requested revision, and response deadline. Keep the operator's original answers intact and collect a revised map or flight window as a follow-up version. That makes it clear which plan was reviewed. Common statuses include received, needs information, under review, decision recorded, and withdrawn.
Yes. Route by property, campus zone, event, flight date, or request type. A filming request might notify event production, while a roof inspection goes to property management. Responses can also be sent to email, Slack, Google Sheets, or connected workflows through Zapier. Keep one person responsible for the decision so the operator receives a clear response.
Yes. Makeform is unlimited free for creating, editing, publishing, and collecting responses with your drone permission form. A paid tier is available only to remove the Makeform badge. You can start with a sample prompt, replace it with your own property requirements, and publish the finished intake form when the fields and routing match your review process.
Replace scattered flight emails with one reviewable request.
