Checklist Flows

Last Updated 05.09.03

General Description

The Checklist Flow is a flow used for linear or nonlinear processes with a long list of tasks/steps. The flow varies depending on the type of process or task. This guideline contains the different flow examples for the checklist.

Guideline Attributes

Spec Version # - 3.1
Spec Contributors - Raymond Wong, Lisa Serface
UI Models - all models
Example Products - all products
Related Guidelines - Introduction to Page Templates, Messaging (including Confirmation) Page Template, Object List Templates, 2 Step Processes Template, Step by Step (3[+] Steps) Template, Step by Step Page Flows, Introduction to Page Flows, Checklist Templates, Object Templates

Interaction and Usage Specifications

A Checklist Flow generally consists of four types of templates. For details regarding these templates, refer to the guidelines as listed below:

Also, there are two general types of Checklist Flows:

Multiple Discrete Steps Checklist

Linear
The Multiple Discrete Steps Checklist (linear) is for an ordered list of tasks. This option is recommended when the user must perform tasks with multiple, discrete steps in a specific order. It does not allow users to jump forward from task to task. Rather, the user must complete the first task in order to proceed to the next one on the list.
Nonlinear
The Multiple Discrete Steps Checklist (nonlinear) is for an unordered list of tasks. This option is recommended when the user can perform tasks in any order. It does allow users to skip to different tasks (i.e., jumping forward and backwards) from task to task.
Hierarchical (Linear)
The Hierarchical Checklist (linear) is for an ordered list of grouped tasks. This option is recommended when the many tasks can be clearly organized into high-level groups, and that the user must perform the groups of tasks in a specific order. The hierarchical version of the checklist is represented via an HGrid.
Hierarchical (Nonlinear)
The Hierarchical Checklist (nonlinear) is for an unordered list of grouped tasks. This option is recommended when the many tasks can be clearly organized into high-level groups, and that the user can perform any group of tasks in any order. It does allow users to skip to different tasks (i.e., jumping forward and backwards) from group to group. The hierarchical version of the checklist is represented via an HGrid.

Single Related Steps (linear)
A Single Related Steps Checklist (linear) is for an ordered set of tasks. It can also be described as a "super train". This option is recommended when users must perform a single, large, linear process. Users may jump only back to previously visited tasks or to the next immediate task on the list.

Checklist Page Flow Options
Below are flow options for Multiple Discrete Steps Checklist and the Single Related Steps Checklist:

Multiple Discrete Steps Checklist Flow

Single Related Steps Checklist Flow

Visual Specifications

See the Checklist Templates Guideline for details about the individual page templates. From that guideline, see the individual components for detailed visual specifications.

Open Issues

none

Closed Issues

none