When should I use an ordered list instead of an unordered list?
Quick answer
Use an ordered list when the sequence of items matters—for example, when steps must be followed in a particular order. Use an unordered list when the items are a collection and rearranging them would not change their meaning. For a nested list, put the inner list within the list item it explains, and choose its type according to whether order matters there.
The question, the details, the next step.
I’m writing instructions and notes for a small project. How can I tell whether each list should be numbered or use bullets?
Ask yourself: if I rearranged these items, would their meaning or the intended task change? If yes, use an ordered list. If no, use an unordered list. This is about the relationship between the items, not which marker looks tidier. An ordered list suits steps in a process; an unordered list suits a collection with no meaningful sequence. [S1] [S2]
For example, “open the file, check the heading, then send it” describes a sequence. A list of items to bring to a meeting is usually just a collection. If you find yourself numbering items only to create visual indentation, reconsider the structure: use the list type that matches the content’s meaning. [S2]
What if the items are in a preferred order, but readers could still do them in another order?
Distinguish a meaningful sequence from a convenient presentation order. Number the items when their position communicates something readers need, such as what to do first and what follows. Use bullets when you are merely grouping related choices or notes and their positions do not change the message.
A useful test is to swap two items. If the swap would make the instructions misleading or change what a reader is expected to do, keep the ordered list. If the same items still communicate the same collection, use bullets. This is a practical way to apply the sequence-based guidance; not every list needs to suggest a required sequence.
How should I handle a list inside another list? I don’t want to use numbering just to make the page look indented.
Nest a list only when its items belong under a particular item in the main list. The inner list should sit within that parent list item, rather than being attached to the outer list without a clear connection. Then choose ordered or unordered markers separately for the inner list, based on whether its items have a meaningful sequence. Nested lists can alternate between ordered and unordered types. [S1] [S2]
For example, suppose your outer list is a set of project stages and one stage has several related materials. The stages might need numbers if their order matters, while the materials under one stage might be bullets if they are simply a collection. If the inner entries are the next steps in that stage, numbering them may be clearer. Don’t add a nested list just to produce extra indentation.
Can you show me a quick worked example and a check I can reuse before publishing?
Assume this is a short project handoff note. The first list describes a process; the second is a set of items to gather:
- Open the draft.
- Check the title and date.
- Send the reviewed draft to the project lead.
Materials to gather:
- Current draft
- Review notes
- Updated schedule
The numbered sequence tells readers what to do in order. The materials are grouped together without implying that one must come before another. If a stage in the process had its own sequence of steps, you could nest an ordered list under that stage; if it had a set of related materials, you could nest an unordered list instead. Keep each nested list attached to the item it explains. [S1] [S2]
Before publishing, try the swap test: if changing the order would change the instructions or meaning, use numbers. If not, use bullets. Then check that any nested list clearly belongs to one parent item.
A practical checklist
Ask whether rearranging the items would change their meaning or the task.
Use an ordered list when the sequence communicates necessary steps or progression.
Use an unordered list when the items form a collection without meaningful numerical order.
Nest a list only when its entries belong under a specific parent list item.
Choose the nested list’s type by the meaning of its own items, not by the outer list’s type.
Remove numbering or nesting that serves only to create visual indentation.
A few more useful answers
Should a list of options be numbered?
Use bullets if the options are simply a collection and their order does not matter. Use numbers only if the positions communicate a meaningful order.
Can an ordered list contain an unordered list?
Is indentation alone a reason to make a nested list?
No. Nest a list when the inner items are related to a particular outer item, and choose the list type for their meaning rather than using list markup just to create indentation. [S2]
Sources
References used for this guide.
- [S1] MDN: HTML ordered list element developer.mozilla.org · Checked
- [S2] MDN: HTML unordered list element developer.mozilla.org · Checked