How to Set Up a Sequence Flow Section (Full vs. Partial Ranking)¶

You've got twelve candidate onboarding steps, or a list of fifteen possible features, and you need to know the order a typical user would actually want them in - not just which one wins in isolation. A single "rate each item's importance" question won't get you there: everything clusters near the top of the scale, and you're left with no real sense of sequence at all. A plain drag-and-drop ranking question technically produces an order, but ask it to hold twelve or fifteen items at once and you're asking respondents to plan the whole list in their head before they can move anything - which is exactly the kind of task people abandon halfway through, or finish carelessly just to get it over with.

Sequence Flow solves this by breaking the task into one placement at a time: a respondent taps a slot, picks an item, watches it land, and moves on - free to work in whatever order makes sense to them, right up until every slot they need to fill is filled. This guide covers how to build one, the choices that actually matter when setting it up, and the patterns that produce a result worth reading.

Table of Contents¶

• What a Sequence Flow Section Actually Is
• The Anatomy: Items, Messages, and Ranking Rules
• Step-by-Step: Building Your First Sequence Flow Section
• Full Sequence vs. Just the Top Few: Choosing Correctly
• Design Patterns That Produce a Clear Sequence
• What You Get Back: Analytics and Exports
• Best Practices
• Sequence Flow vs. Ranking vs. Card Sorting
• Illustrative Walkthrough: Ordering a Product Onboarding Flow
• FAQ

What a Sequence Flow Section Actually Is¶

Sequence Flow is one of the section types available inside an Advanced Survey (alongside the Stimulus Section and Pairwise Comparison, each covered in their own guide). Unlike those two, it isn't built around an uploaded image or video - it's built around a pool of plain text items and a fixed set of slots representing positions in the final sequence. Every slot is visible from the moment the task begins; a respondent fills them in whatever order they like, by tapping a slot and choosing an item from what's left in the pool.

Placement is fully reversible while the task is in progress: an already-placed item can be cleared back to the pool, or swapped with its immediate neighbor, without touching anything else in the sequence. Nothing about filling one slot ever reshuffles another.

The Anatomy: Items, Messages, and Ranking Rules¶

It helps to think of a Sequence Flow section as a handful of independently-set pieces, each controlled at a different point in the builder:

A few details worth knowing before you build:

• The intro message and the on-screen reminder are different fields, on purpose. The intro message is shown once, in the moment before a respondent taps Begin - it sets up the task. The on-screen reminder stays visible throughout, which matters for a longer sequence a respondent might otherwise forget the point of halfway through.
• Items are just options underneath, the same underlying structure a plain Ranking question's option list already uses - which is why Batch Input (paste a list, one item per line) works exactly the way it does for Ranking questions elsewhere in the builder.
• The buffer can be skipped entirely. Setting it to 0 removes the "Get ready" beat and drops respondents straight into the interactive builder - worth doing for a Sequence Flow section embedded partway through a longer survey, where a repeated countdown starts to feel like friction rather than orientation.

Step-by-Step: Building Your First Sequence Flow Section¶

1. Add a Sequence Flow section. From inside an Advanced Survey, add a new section and choose Sequence Flow.
2. Add your items. Type them one at a time, or click Batch Input to paste a full list at once (one item per line, up to 20 items, 300 characters each - anything over the limit gets truncated with a warning so you can fix it before publishing).
3. Write your intro message. This is the one thing every respondent sees before they start building - make it specific about what they're ordering and why, not just "please rank the following."
4. Decide full sequence or partial, and set your limits. Leave it unset for a full sequence (every item must be placed), or set a maximum - and optionally a minimum - to let respondents stop once they've placed their top few. See the section below on choosing correctly.
5. Add an on-screen reminder if the sequence is long enough to need one. Short lists usually don't; a ten-or-more-item sequence often benefits from a persistent one-line reminder of what's being asked.
6. Set your buffer, or leave the default. Three seconds is the default "Get ready" beat; drop it to 0 if the section sits inside a longer flow where a countdown would feel repetitive.
7. Preview before publishing. Step through the section yourself to confirm the intro message, reminder, and item pool all read the way you intended, then publish and share the link.

Full Sequence vs. Just the Top Few: Choosing Correctly¶

This is the single most consequential setting in a Sequence Flow section, and it's worth getting right rather than defaulting to whichever option sounds safer.

Choose full sequence when the order itself is the real workflow - an onboarding flow, a checkout process, a set of steps with genuine dependencies between them. If you need to know the whole path, asking for a partial one doesn't answer your question.

Choose "just the top few" when what you actually care about is which handful rises to the top, not a fully ranked opinion on every item. Asking respondents to fully rank fifteen candidate features when your real decision only involves picking the top three adds real fatigue - and fatigue late in a long ranking task tends to show up as careless placement of the items nobody was paying attention to anymore, which quietly degrades the quality of the very items you cared least about even having ranked at all.

A useful test: if you'd be equally happy learning "these are the top four, in order" as you would learning the full ranked list down to the last item, you almost certainly want the partial option.

Design Patterns That Produce a Clear Sequence¶

Onboarding and workflow ordering. List the steps of a proposed flow and ask respondents to arrange them in the order they'd actually want to encounter them. Full sequence is almost always the right call here - a workflow with a step missing from the ranking is a workflow you don't actually understand yet.

Feature or benefit prioritization. List candidate features or benefits, cap it to a top few with the partial ranking option, and use the intro message to be explicit about the tradeoff ("your team can only build three of these this year - which three, in order?"). This produces a genuinely different, more decisive signal than a straight importance-rating question, for the same reason MaxDiff beats a rating scale for a similar kind of decision (see our MaxDiff and TURF guide for the related logic).

Information architecture and navigation testing. Offer the candidate items in a proposed menu or nav structure and ask respondents to arrange them the way they'd expect to find them. Full sequence if you're testing a specific proposed order end to end; partial if you're really only trying to find out which handful of items belong "above the fold."

Customer-journey step preference. For a multi-touch process (a signup flow, a support process), ask respondents to sequence the steps the way they'd want to move through them, then compare that against the order you actually built - a mismatch here is often the fastest way to find friction you didn't know you'd designed in.

What You Get Back: Analytics and Exports¶

Results flow through the same tools you already use elsewhere on the platform - no separate dashboard or export format to learn:

• Route Flow and Route Network views. A completed Sequence Flow submits as an ordinary ranking-style answer, and it's read using item-to-item transition analysis rather than an averaged position per item - covered in full in our Reading Sequence Flow Results guide.
• DOCX export. Each Sequence Flow section exports as a clean, numbered list of its steps alongside your intro message and on-screen reminder - readable in a shared document without needing anyone to open the live survey.
• CSV export and standard analytics. Like every other question type on the platform, results are available for filtering, cross-tabbing, and export in the same place you already work.

Best Practices¶

• Write items the way a respondent would say them, not the way an internal doc labels them. "Set up your profile" reads faster and clearer than "Step 3: Profile Config."
• Decide full vs. partial before you write your items, not after. The two options shape how many items make sense to include in the first place - a full-sequence task with twenty items is a very different respondent experience than a partial one capped to a top five out of the same twenty.
• Use the on-screen reminder for anything past roughly eight to ten items. A short list rarely needs it; a longer one benefits from not making respondents scroll back up to re-read a one-time intro message.
• Avoid near-duplicate items. Two items that mean almost the same thing to a respondent split their own placement across a handful of near-identical options, muddying the transition data the Route Flow and Route Network views depend on - the same failure mode a near-duplicate causes in a MaxDiff study.
• Keep the buffer for a standalone task, drop it for an embedded one. A brief "Get ready" beat helps orient a respondent facing a full-screen builder for the first time in a survey; it adds friction with little benefit if Sequence Flow is one of several similar sections in a row.

Sequence Flow vs. Ranking vs. Card Sorting¶

Worth being precise about, since all three sound like they're doing roughly the same thing:

A plain Ranking question is a single drag-and-drop list, arranged in one continuous motion - the right, lighter-weight tool for a short list a respondent can reasonably hold in their head at once.

Sequence Flow builds toward the same kind of ordered result, but one placement at a time rather than one drag operation - built for longer lists, or lists where the order genuinely matters enough that a considered, slot-by-slot approach beats a quick drag.

Card sorting, a separate and established information-architecture research method, isn't currently a section type on Opionate. Card sorting typically asks respondents to group items into named categories they define themselves (open card sorting) or you provide (closed card sorting) - a categorization task, not a sequencing one. If what you need is "which bucket does this belong in," rather than "what order do these go in," that's a different research method than what Sequence Flow answers today.

Illustrative Walkthrough: Ordering a Product Onboarding Flow¶

Picture a product team that's redesigned a mobile app's onboarding and wants to know if the proposed step order actually matches what new users expect, before shipping it. The five candidate steps are: setting up a profile, connecting a payment method, inviting a teammate, importing existing data, and enabling notifications.

They build one Sequence Flow section, add all five as items, and set it to a full sequence - the whole point is the end-to-end order, not just which step matters most. The intro message reads: "If you were setting this app up for the first time, what order would you want to do these five things in?" They skip the on-screen reminder (five items is short enough not to need one) and leave the buffer at its 3-second default, since this is the only section in a short, standalone test.

Results come back into the Route Flow view showing a clear consensus: profile setup first, then payment connection, then data import, then notifications, with teammate invites last - and a strong per-step agreement reading on every transition except one, where the group is nearly split on whether data import should come before or after connecting a payment method. That single weak link, visible right in the Route Flow diagram, becomes the one open question the team actually needs to resolve - not "did we get the order right," which the strong agreement everywhere else already answers.

FAQ¶

Can I add or remove items after respondents have already started answering?
Removing an item that's already been placed by earlier respondents doesn't retroactively change their answers - but changing the item pool mid-flight makes results harder to compare across respondents who saw different versions of the task, so it's best treated the same way you'd treat editing any other live question: avoid it once real responses are coming in.

What happens if a respondent stops before placing the required number of items?
The Finish action inside the section only becomes available once the minimum required number of slots is filled (every slot, for a full sequence). A respondent who leaves before reaching that floor simply hasn't completed the section, the same as leaving any other required question blank.

Can respondents reorder items after placing them?
Yes - a filled slot can be moved up or down, or cleared back to the pool, at any point before the respondent finishes the section.

Does Sequence Flow support images or video, like the Stimulus Section does?
No - items are plain text. If what you need feedback on is a visual, the Stimulus Section or Pairwise Comparison are the right section types for that.