Forms whose answers are features. Build a survey, publish it, and every submission lands as a row in a live feature layer — the location answer is the point geometry.

The survey builder — nine question types, live preview, location on a map
Surveys is a form builder that ends in GIS data instead of a spreadsheet. You assemble questions from a palette — text, paragraph, number, choice, yes/no, date, date & time, star rating, and a location picked on a map — while a live preview shows the form exactly as respondents will see it, in your org theme. Publishing creates a real feature service: one column per question, named after your labels, with the location answer stored as point geometry in WGS 84.
Collecting is a link. Anyone in your org can fill the form at its fill URL — no sharing dance first. Publish it to the web and it runs anonymously on your org subdomain, validated hard on the server: required fields, choice membership, number ranges, rating scales, text length caps. Bad submissions bounce. Nothing writes to your table that the form didn't ask for.
Responses are ordinary feature layers, so there is no export step and no sync job. The Results tab shows a live count, a paged response table and a mini-map of the latest points — and refreshes itself the moment someone submits. The same layer opens in the map viewer, joins dashboards, and redraws its tiles live. A field crew logs a fallen tree; the operations map has the point before they've pocketed the phone.
Text, paragraph, number, single or multiple choice, yes/no, date, date & time, star rating (2–10 stars), and a location question with a click-to-set map picker and a use-my-location button.
Publish creates a real "— Responses" feature service in your content: one column per question, the location answer as point geometry. It renders on maps as vector tiles, opens in the feature table, and feeds dashboards like any other layer.
Publish to web and the form runs on your org subdomain — no account needed to respond. Every answer is validated server-side against the question list; the whole thing is gated so only published surveys accept anything at all.
Live response count, paged table with your question labels as column headers, mini-map of the latest points. Each submission pushes a refresh over Realtime — leave the tab open and watch the rows arrive.
Question palette on the left, inspector on the right, and the actual form in the middle — the same component respondents get, rendered in your org theme. Edits autosave after one second.
Draft → published → closed. Question structure locks at publish so the table schema never drifts under your data; labels stay editable. Close a survey to stop accepting responses, reopen it later. Deleting the form keeps the data.
Add questions from the palette, mark them required, set number ranges, choice options and rating scales. The live preview shows exactly what respondents will see, themed.
One click creates the response feature layer — column names derived from your question labels, point geometry if there's a location question, a plain table if not.
Copy the fill link for anyone in your org, or publish to web for anonymous responses on your org subdomain.
The Results tab counts, tables and maps submissions as they happen. No refresh button required — though there is one.
It's a normal feature layer. Put it on a map, filter it, chart it in a dashboard, open it in QGIS. The answers were GIS data from the first submit.
No demo call. No sales funnel. Just sign up and start mapping.