SPECIFICATION BOOK

Full specifications.

A form system should make its important constraints visible. These sections describe the builder, workflow logic, distribution layer, and analysis surface without hiding operating details.

§1 / BUILDER

Draw the respondent path before publishing it.

The builder is organized around fields, ordering, and a visible public structure. Text inputs, choices, ratings, uploads, dates, payments, and signatures can be arranged into a form that is readable before it is shared.

The working surface favors explicit components over hidden behavior. When a form needs a new field, the change is visible on the drawing, and when a field limit exists it is part of the selected plan.

Parameter	Specification
Field library	Text, choice, matrix, rating, file, date, payment, signature
Editor	Browser-based visual workspace
Draft behavior	Autosaved draft state

§2 / LOGIC

Routes and calculations stay explicit.

Logic jumps let a question determine which section follows, while calculated fields can derive values from existing answers. The comparison table identifies the plans that include these controls rather than assuming every tier has the same workflow power.

This makes a complex questionnaire easier to inspect: the path can be tested before respondents arrive, and the calculation is part of the form definition rather than a separate spreadsheet routine.

Parameter	Specification
Conditional routes	Plan-dependent logic jumps
Calculated values	Blueprint and above
Matrix controls	Surveyor and Architect

§3 / DISTRIBUTION

Publish one drawing through the right channel.

A form can be shared as a link or embedded into an existing surface, so the owner can choose a distribution method without duplicating the underlying questions. Branding controls are shown by plan, rather than quietly changing after publication.

Respondents do not need a FormGrid account for the normal public submission flow. Integrations expand with the subscription level, giving a team options for where submission events should go next.

Parameter	Specification
Share modes	Link and embed
Integration set	3 on Blueprint; 12 plus webhook on Surveyor
Custom domain	Architect

§4 / ANALYSIS

Responses remain traceable after collection.

The results view keeps submitted values linked to the original field names so the form owner can inspect answers before deciding what analysis should happen outside the builder. Response allowances are listed on every plan.

Export is treated as a continuation of the form workflow rather than an exit from it. The owner can move response data into downstream analysis or record-keeping tools while retaining the meaning of the original questions.

Parameter	Specification
Response allowances	100 to unlimited by plan
Export orientation	Preserve form-field structure
Ownership	Response data belongs to the form owner