Conversational form vs standard form

Use a conversational form, one question per screen, when the form is short and every question stands alone: surveys, RSVPs and lead capture. Use a standard (classic) form when the form is long, gets reviewed before it is sent, is printed or exported as a PDF, or needs a second person to e-sign it.

The two formats are not competing versions of the same thing. They make opposite trades, and the rest of this post sets out which one fits which job.

What each format changes for the respondent

A classic form is a page. Everything is visible, so somebody can read the whole ask before answering any of it, skip to the hard question, scroll back to check what they wrote, and see how much is left without being told.

A conversational form is a sequence. One question fills the screen, the next arrives when the current one is answered, and nothing else competes for attention. Each individual answer is cheaper, because there is only one thing to look at, and the total number of interactions is higher, because every answer costs a tap to advance.

That is the whole trade. Attention per question against control over the whole. Nielsen Norman Group describes the general version of this as progressive disclosure, and their caution is the relevant one here: staging works when the split matches what people actually need, and starts to hurt as soon as somebody has to move between levels to find something.

It has also been measured. A 2006 experiment published in Public Opinion Quarterly fielded the same instrument, up to 268 possible questions, to a sample of over 21,000 undergraduates, with about 10,000 responding and roughly a tenth randomly assigned a scrolling version rather than a paged one. The researchers compared break-offs, item missing data and the time spent in each section. It is worth knowing the question has been studied properly at that scale, and worth being sceptical of any vendor who answers it in one sentence.

Decision rule: length, field kinds, review need

Three questions, in this order.

How long is it? Under about ten questions, conversational reads well and feels lighter. Past twenty, it becomes a corridor, and people want the map that a classic page gives them. The finished forms published on this site fall out along exactly that line. Counted on 13 September 2026 across 140 examples, the conversational ones have a median of 10 fields and the classic ones a median of 16.

What kinds of field does it need? This is the one that ends the argument early. If the form needs an e-signature from a second person, or any of the twelve design blocks, it is classic, because neither exists in the conversational toolkit. If it needs an audio or video recording, it is conversational, for the opposite reason. A drawn signature, a photo and a file upload work in both.

Does anyone need to review it before submitting? A job application, a grant submission or an expense claim gets read back before the button is pressed. A classic page supports that. A sequence does not, without walking backwards through every screen.

Field support table

The table at the foot of this post lists what each format supports on the published form, not only what the builder offers.

The conversational toolkit offers 25 components and the classic one 36. Every conversational entry has its own renderer: the photo field shows the same single photo upload as the classic page, and the inline signature shows the same pad, drawn or typed. The e-signature field, which sends the finished response to someone else to sign, is not in the conversational toolkit at all, and neither are the twelve design blocks.

The reverse gap is smaller but real. Recording, audio or video, up to 120 seconds by default, exists only in the conversational toolkit, as does the profile block that puts name, email, phone and address on one screen. Neither is offered for a classic form.

Two smaller differences catch people out. On a classic form, a field’s description is only rendered for file upload and photo; every other field drops it, so explanatory text has to be a paragraph block above the field. On a conversational form, a number field’s minimum and maximum are not passed to the input, so the range is only checked on submit, after every question has been answered.

Cases for conversational: surveys, RSVPs, lead capture

Conversational is the right call when the form is short, every question stands alone, and the respondent has no reason to review.

A satisfaction survey qualifies. So does an RSVP, where the questions are are you coming, for how many, and what will you eat. So does most lead capture, where the point is to make the first answer feel small. The shortest form in the example set here, a six-field newsletter signup, is conversational for exactly that reason, and only one of its six questions is required.

Ratings are the strongest case. A rating question answered against a page of twenty other ratings gets anchored to its neighbours. Given its own screen, it gets considered on its own terms.

Cases for classic: applications with uploads, anything printed, anything signed

Classic is the right call when any of these are true.

Something has to be countersigned by a second person through the e-signature field. The form will be printed, exported to a fillable PDF, or read back as a document, because the design blocks that make a form look like a document only exist in the classic toolkit. Or the form is simply long, and its sections are separate jobs, in which case the paginated classic layout gives you steps without giving up the page.

Applications sit squarely here. So does anything with a consent paragraph the respondent is expected to read before ticking, because a consent clause on its own screen with a single tick underneath is easier to click past than one sitting above the signature it authorises.

Themes and welcome screens

Both formats support a welcome screen and a thank-you screen, and both can carry an estimated time. The theme sets are separate: 12 classic themes and 25 conversational ones, and they do not overlap, because a theme for a full-screen single question is doing a different job to a theme for a page of fields.

The practical consequence is that the format and the look are chosen together. A form cannot be switched to the other format later, so moving it means rebuilding it with a theme from the other set.

The pair of examples

Two forms on this site ask about the same subject in opposite formats.

The 360 feedback form is conversational and ten questions long. Three of those are rating grids, and giving each grid its own screen is the entire argument for the format: a rater considers one dimension at a time instead of pattern-matching down a page.

The performance review form is classic and nineteen questions long. It uses the same rating matrix component, but it also carries two table inputs, a signature at the end, and a structure that a manager and an employee read together in a meeting. It works better as classic because the whole document has to be visible at once, and a meeting reads it top to bottom rather than one screen at a time.

If the underlying problem is that the form is too long rather than the wrong shape, start with the field count data across 140 examples instead. And if you want the plain definition of the term rather than the decision, that lives on the conversational form question page.