Procedure Step Formatting
Use a numbered procedure when order matters. Write each step as a clear action, normally with an imperative verb and a complete sentence, and keep the sequence concise.
For a true sequence, use numbered steps and write each step as a clear action in the order the reader should perform it.
Key details
Further guidance
Numbering
Use numbered steps for multi-step procedures where sequence matters.
Practical Application
Use numbered steps when sequence matters. Write each step as a clear action in the order the reader should perform it, normally starting with an imperative verb and keeping one main action per step where practical.
Reader Check
Check whether changing the order would change the result. If yes, use a numbered procedure; if no, a bulleted list may be better. Also verify that each step tells the reader what to do, not merely what exists.
Scope
Keep the procedure focused on the task and include enough location/context for the user to know where to act.
Sentence Style
Write each step as a complete, action-oriented sentence, commonly beginning with an imperative verb.
Worked Example
1. Open the project settings. 2. Select “Access.” 3. Add the reviewer’s email address. 4. Select “Save.” The numbering communicates the required order.
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.
- Procedures and instructions — Microsoft Style Guide (opens in a new tab)Microsoft Style Guide · Microsoft guidance for clear procedures, including numbered steps, input-neutral UI verbs, and documentation of supported interaction methods.