Tally: let the last answer decide the next question

Make a fillable form by writing a document

Tally is an online form builder for registrations, customer requirements, feedback and orders. Write questions, add blocks such as choices and text inputs, then publish a link or embed the form on a website. It connects writing questions with making a submittable page, so people can organize information collection without writing code.

Consider a pottery workshop: in-person participants choose a session, while online participants need to provide a delivery address for a materials kit. Showing both groups of questions makes people decide what they can skip. Requiring every field can block someone who needs no delivery.

Write the whole task before deciding which answers change the path

Take a pottery-workshop registration form. In-person participants choose a session; online participants provide a materials-delivery address. Start with document-style editing to write the participation question and both sets of information. Then decide which answers control visibility, required answers and page navigation.

Type /logic to add conditional rules. Hide blocks intended for conditional display before configuring when they appear. Visibility and whether an answer is required are separate settings: hiding a block does not establish that the entire path works.

Let answers explain why the next question appears

1. Ask how the person will participate. It is an understandable question that genuinely changes what follows.
2. Show relevant questions. Display sessions for in-person attendance and the delivery address for online attendance. People need not decide which half of two simultaneous question sets to ignore.
3. Arrange page progression. Same-page visibility can respond to answer changes; page jumps occur on Next or Submit, with rules placed on the relevant page.
4. Keep final submission explicit. Under form settings, supported single-question pages can advance after an answer, but the final submission remains manual. Fewer navigation clicks do not remove confirmation before sending the information.

Each conditional field has a reason to appear. The main benefit is less work deciding “does this question apply to me?”, rather than merely a shorter-looking page.

Go back and change answers to check the whole form

Complete both the online and in-person routes, then try choosing online, entering an address and returning to select in-person. Check visibility, required answers and the received record. A hidden field alone does not prove that its earlier answer has been removed from the record.

After publishing, check a submission through the actual form instead of inspecting only the editor layout. More conditions mean more combinations to check; one smooth route cannot represent every return path. The intended result is a record matching the person's current registration choice, rather than a collection of apparently flexible hiding rules.

Ask for information when it becomes relevant

The workshop starts with participation mode, something the person can answer easily. An address is not permanently removed; it appears when the person chooses a mailed kit. The field now has an understandable reason to appear: the previous choice explains the next question.

Visibility and whether an answer is required need separate decisions. A relevant question is not necessarily mandatory; a previously mandatory field should not confuse people after its entire path stops applying. Conditional logic exposes these relationships to the editor, trading flexibility for the responsibility to define combinations clearly.

Removing irrelevant questions is more useful than squeezing the same questions onto a smaller page.

Separate changing an answer from advancing a page

Content on the same page can react to an answer, while cross-page jumps follow an explicit progression action. One changes what needs filling in now; the other determines where to go next. Editors need to check the latter on the rule’s own page rather than assume a condition placed anywhere changes the entire flow.

This distinction allows both immediate feedback and an understandable pace. Seeing relevant fields after choosing participation mode explains the choice’s consequences. Clicking Next or submitting deliberately advances the process. Check for unexpected jumps, unexplained disappearing content and premature submission.