About Forms
Forms lets you create structured questionnaires, collect responses, and analyze results — all with built-in version control.
Whether you're collecting feedback, running surveys, or managing event signups, Twynes Forms helps you create flexible forms that adapt to your users.
Key Idea: Every published form is versioned. Responses always stay tied to the exact version users saw.
Form Lifecycle
- Draft: Work in progress, not visible to respondents.
- Active: Live and accepting responses.
- Closed: Automatically stops based on limits or time.
- Trashed: Soft-deleted and recoverable.
Versioning (Core Concept)
Forms use a strict versioning system to ensure data consistency.
- Each publish creates a stable version.
- Editing after publish creates a new draft version.
- Responses are always linked to the version they were submitted against.
Why this matters: Even if you change questions later, old responses remain accurate and usable.
Editing & Publishing
- Edit your form (creates or updates a draft).
- Preview the form before publishing to check question flow and respondent experience.
- Publish to make it live.
- Future edits do not affect already collected responses.
Note: Drafts are overwritten until published — new versions are only created when needed.
Collecting Responses
- Share a single form link — it always points to the latest active version.
- Responses are recorded only after successful submission.
- Respondents may be offered a saved draft if they return before submitting.
- Optional settings include response limits, duplicate handling, email collection, progress display, and confirmation message text.
Response Settings
Use settings to control how responses are collected, identified, and limited.
- Multiple responses: Allow each submission to be recorded separately, or require sign-in to limit respondents to one response.
- Duplicate handling: When one response per person is enabled, returning respondents can be blocked or allowed to update their previous response.
- Email collection: Choose not to collect email, collect verified email via login, or ask respondents to enter an email address.
- Limits: Close a form automatically after a maximum number of responses or after a specific date and time.
- Presentation: Show a progress bar and customize the confirmation message shown after successful submission.
Note: Some settings, such as verified email or one response per person, require respondents to sign in.
Analytics & Insights
View response data with strict alignment to your form structure.
- See summaries for the current version or across all versions.
- Visualize ratings, distributions, and counts.
- Export data based on your selected view.
Important: When viewing “All Versions”, results are aggregated carefully to avoid inconsistencies.
Version History & Rollback
- Preview any previous version.
- Restore an older version instantly.
- Continue editing from that restored version.
Warning: Reverting may remove newer responses tied to discarded versions.
Supported Question Types
Twynes Forms supports a wide range of question types, most of which behave similarly to standard form tools from popular providers.
- Short Answer – Single-line text input.
- Paragraph – Long-form responses.
- Multiple Choice – Select one option.
- Checkboxes – Select multiple options.
- Dropdown – Compact single-select list.
- Star Rating – Visual rating (e.g., 1–5 stars).
- Linear Scale – Numeric scale (e.g., 1–10).
- Multiple Choice Grid – One selection per row.
- Checkbox Grid – Multiple selections per row.
- Date – Calendar-based date input.
- Date & Time – Combined date and time picker.
Location (Advanced)
The Location question type captures precise geographic data (latitude, longitude, and accuracy).
- GPS Share: Quickly capture the user's current location after they choose to share it.
- Map Pin: Select a precise location using an interactive map. Users can drag the pin or move it to their current location.
Privacy Note: Browser location permission is requested only when a user chooses a current-location action. Accuracy depends on device and network conditions.
Use Cases: Check-ins, delivery points, event tracking, and location-based analytics.
Conditional Logic (Dynamic Forms)
Forms can adapt dynamically by showing or hiding questions based on previous answers. Use conditional logic to keep the form focused and avoid asking questions that are not relevant to a respondent.
- Equal / Not equal – Match specific answers
- Less than / Greater than – Numeric conditions
- Answered – Trigger based on response presence
Authoring Rules
- Use only previous questions. A conditional question can only depend on an answer that appears earlier in the form.
- The first question cannot be conditional. It has no previous answer to depend on.
- Do not create loops. Avoid circular dependencies such as Question 2 depending on Question 3 while Question 3 depends on Question 2.
- Keep chains simple. Chained logic is supported, such as Question 3 depending on Question 2, and Question 2 depending on Question 1. Make sure the chain flows forward through the form.
- Prefer stable trigger questions. Multiple choice, dropdown, checkbox, rating, and linear scale questions usually make clearer triggers than long free-text answers.
Response Behavior
- If a trigger answer changes, dependent questions may appear or disappear immediately.
- Hidden questions are skipped during required-question validation.
- Only answers to currently visible questions are submitted. Drafts may remember hidden answers so they can reappear if the respondent changes an earlier answer back.
Use Case: Create shorter, more relevant forms by only showing questions that matter to each respondent.
Best Practice: Design conditional logic as a one-way flow from earlier questions to later questions. This keeps the respondent experience predictable and prevents confusing show/hide behavior.