Bulleted vs. Numbered Lists
Bulleted and numbered lists serve different information structures. Microsoft recommends bullets for related items that do not need a particular order, and numbers for sequential steps or prioritized items.
Use bullets when order is not meaningful; use numbers when sequence, priority, or explicit item references matter.
Key details
Important caveats
Bullet Boundary
Use bullets for items that share a relationship but do not need to appear in a particular order.
Number Boundary
Use numbers for sequential procedures, ranked/prioritized items, or contexts where item numbers are referenced.
Further guidance
Practical Application
Use bullets for unordered related items. Use numbers when sequence, ranking, priority, or later references to “step 2” or “item 3” matter.
Reader Check
Would changing the order change the task or meaning? If yes, use numbering; if no, bullets are usually clearer.
Worked Example
Requirements can be bulleted when order is irrelevant. Installation steps should be numbered because readers need to follow them in sequence.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Lists (opens in a new tab)Microsoft Style Guide · Bulleted lists for unordered related items and numbered lists for sequences or priorities