Survey Collection
Create a survey, share one link, and watch responses land in the admin as they are submitted. Structured feedback without a spreadsheet, a form tool subscription, or a consolidation afternoon.
Four steps, one link
How each step works
Questions are defined once in the survey builder, which opens as a draft the moment an admin clicks new. Publishing freezes the link; closing it stops responses. Because surveys live where the rest of the operation lives, there is no separate form tool, no export step, and no account to manage.
The survey has a public link that works anywhere: a chat, an email, a QR code in a room. It is kept out of search engines, and one link per survey means one pipe for all responses.
Each submission is validated against the question set on the server and becomes a structured record the moment it arrives, tagged as team, client or external, or stored without a name when the survey is anonymous. The ops Lark chat gets one line per response. Nobody consolidates, nobody retypes, and the tenth response is stored exactly like the first.
Responses are readable on the survey's results page in the admin from the first submission, each time it is opened. If turnout is low or a question is being misread, you find out while there is still time to fix it, not after the survey closes.
The seven elements
Every workflow we document has the same anatomy: seven elements, each assigned to a human, a machine, or both. This is the Centaur Map from our workflow design method.
Someone needs an answer from a group: a cohort, a client team, an audience.
The questions. The hardest part of a survey is deciding what you actually need to know.
What the responses mean and what to do about them. Data collection is automated; interpretation is not.
Every response is validated against the question set and stored the moment it is submitted; the ops Lark chat gets one line per response.
A structured response set, one record per person (or anonymous, if the survey says so), no copy-paste consolidation.
Responses are readable on the survey’s results page in the admin from the first submission.
Response counts, visible while the survey is still open, so low turnout gets chased early.
The standing rules
- One link per survey, one pipe for responses
- Responses are records, never spreadsheet rows to reconcile
- Results stay in the same system as the rest of the operation
- Interpretation is a human job, always
Why it works
- Zero consolidation means results are ready the moment the survey closes
- Visibility from the first response catches low turnout while it is fixable
- Structured records make every survey comparable to the last one
- No extra tool means no extra place for data to go stale