Set up Tally conditional logic: visibility, required answers and changing choices

State the reason for each branch

A brochure request needs a brochure choice, while a quotation enquiry needs a service and desired timing. Branch around information required for a useful reply, not simply around minimizing question count. Keep the shared reply address outside the branches so respondents enter it once. Write the two intended journeys before implementing the conditions.

Prepare questions before adding logic

Create the common enquiry-type choice and the follow-up questions for both branches. Start the conditional follow-ups hidden and reveal them when the relevant answer is selected. Stabilize labels and options before configuring the rules. Renaming a question later should prompt a review of every condition and downstream destination that depends on it.

Match conditions to actions

Add a logic block with /logic. Show the brochure question for a brochure request, or the service and timing questions for a quotation enquiry. With multiple conditions, all means every condition must match and any means at least one. A company AND quotation test differs from company OR quotation; rewrite the condition as a plain sentence and check representative respondents.

Check required answers together with visibility

When visible follow-ups must be answered, configure and verify the appropriate required-answer behavior. Test that a hidden required field does not block submission and that a visible mandatory question cannot be skipped. If jumping between pages, confirm every intended route is reachable and has a clear way to revise earlier choices. Do not infer submission behavior from visibility alone.

Inspect answers after a branch change

Fill the brochure branch and then change the enquiry to a quotation before submitting. Inspect whether hidden answers remain in the stored response. Downstream processing should use the currently selected enquiry type to determine which fields are relevant. A question disappearing on screen is not proof that its previous data was erased or excluded from the exported response.

Test all routes and an unselected condition

Compare the brochure path, quotation path, missing enquiry type and a mid-form choice change. Check display, validation and stored results in preview and at the published URL. Try the backtracking experience at mobile width. Whenever an option is added, confirm it does not bypass all branches and produce a response missing the information the team needs.

Connect routing to intake operations

Read the category and its applicable fields together in the submission list. When exporting to Sheets, do not treat the intentionally empty fields of another branch as failures. Owner assignment is a separate downstream rule from question visibility. Review both when form questions change. The article defines proposed branch checks rather than a verified form deployment or a guarantee about an untested account's settings.

• Build a Tally contact form: questions, publishing and checking submissions
• Send Tally responses to Google Sheets: native integration and reconciliation
• Assign Airtable form responses: category rules and an unassigned queue