Online form glossary: logic, embeds, exports and data terms explained
Plain-English definitions of form-building terms: conditional logic, skip logic, required fields, embeds, iframes, CSV export, response limits and more.
Short, practical definitions of the terms you meet when you build, share and analyse online forms. Where a term works a particular way in Branchform, we say so.
Building forms
Form. A set of questions with a share link. In Branchform a form is a draft until you publish it; only published forms accept responses.
Question types. The kind of answer a question takes: short text, long text, email, number, rating, single choice, multiple choice and so on. Pick the narrowest type that fits; an email field checks the format, a free-text field doesn't.
Required question. A question that must be answered before the form can be submitted. Use as few as possible: each one is a reason to give up. In Branchform, a required question that is hidden by logic is never required.
Template. A ready-made form you start from. Branchform includes a contact form, a customer feedback survey, an event RSVP and a quote request; the first three have logic already set. See the feedback survey template.
AI drafting. Describing a form in words and getting a first draft of its questions. In Branchform this is optional, uses your own AI provider key (no markup), and drafts are always created unpublished so you review them first.
Logic
Conditional logic. Showing a question only when an earlier answer matches a condition. The conditional logic guide has examples.
Branching / skip logic. Other names for conditional logic. "Branching" describes the path a respondent takes; "skip logic" describes the questions they skip.
Show-if rule. A rule attached to a question: "show this only if question X is Y". Branchform supports one rule per question with the conditions is, is not, contains, is answered, is not answered, greater than and less than.
Chained rules. A rule that depends on a question which itself has a rule. Hiding the first question also hides the questions that depend on it.
Hidden question. A question whose rule is not met for this respondent. Its answer is discarded and its required setting is ignored.
Sharing
Share link. The public address of a published form. Send it by email, chat or social media.
Embed. Placing a form inside another web page. Branchform offers a script embed and a plain iframe.
Iframe. An HTML element that shows one web page inside another. The plain iframe embed works on sites that block scripts but has a fixed height.
Auto-resizing embed. A script that adjusts the iframe's height to the form's content, so there is no scrollbar inside your page. This is what the Branchform script embed does.
Publish / unpublish. Publishing makes a form accept responses; unpublishing stops it without deleting anything. Publishing in Branchform requires a verified email address.
Responses and data
Response. One submitted form. Response limits count submissions per calendar month (UTC).
Response limit. The number of responses a plan accepts per month: 100 on Free, 5,000 on Pro. When the limit is reached, forms show "not accepting responses" until the next month or an upgrade; there are no overage charges.
Response digest. An email summarising new responses, so you don't have to check the dashboard.
CSV export. A comma-separated file with one row per response and one column per question, readable by any spreadsheet.
CSV injection. A trick where an answer starting with characters such as = or + runs as a formula when the CSV is opened in a spreadsheet. Branchform prefixes such values with an apostrophe so they are shown as text.
Workspace export. A JSON file with everything in a workspace: forms, responses, members, billing records and the audit log.
Data minimisation. Collecting only what you need. It reduces risk and makes forms shorter, which usually improves completion.
Drop-off. Respondents who start a form and don't submit it. Shorter forms with fewer required questions generally lose fewer people; logic helps by hiding questions that don't apply.
Accounts and plans
Workspace. Your team's space: forms, responses and members. Each workspace has its own plan.
Roles. Owner, admin and member. Members create and edit forms; admins also manage the team and settings; owners also manage billing and can delete the workspace.
Branchform footer. The small "made with Branchform" line on forms in the Free plan. Pro removes it.
Plan period. The month a paid plan covers. If you cancel, you keep paid limits until the period ends, then move to Free without losing data.
Try Branchform free
Forms that adapt to every answer. Build with conditional logic, embed anywhere, export responses. The Free plan needs no card; you can export or delete your data any time.