Action-oriented writing · nuanced · v4.6.1

ACT-04

Make the next step obvious. Every screen should have a clear primary action.

Pass example

Your account is ready. Go to your dashboard to get started.

Fail example

Your account has been successfully created.

Relevant content types

Weighted in these moments

This standard behaves differently depending on the reader's moment. Moment-aware evaluation picks one of these adjustments when the moment matches.

  • error_recovery — emphasize
    Errors need actionable next steps, not just a description of what went wrong.
  • empty_state — emphasize
    Empty states need concrete next steps — don't leave the user stranded.

Version history

  1. v4.6.1 · 2026-04-23

    Per-standard version tracking introduced. Every standard starts at the library version current at introduction; bump per-standard when the rule text, examples, or content_type_notes change.

Related standards

Other standards in the Action-oriented writing category.

  • ACT-01 — Start button and CTA text with a verb. Tell the user what will happen. Navigation labels, tabs, section headings, and confirmation or status messages are not CTAs — patterns like 'Project created' or 'Payment sent' are valid confirmation copy and should not be flagged.
  • ACT-02 — Use specific verbs over vague ones. Prefer 'save,' 'send,' 'export' over 'submit' or 'process.'
  • ACT-03 — When communicating a limitation, lead with what the user can do or offer an alternative path. Don't leave users at a dead end. Stating a restriction is acceptable when it's paired with a next step or workaround.

← The content model