Action-oriented writing · nuanced · v4.6.1

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.

Pass example

You can upload files up to 25 MB. For larger files, use our desktop app.

Fail example

You cannot upload files larger than 25 MB.

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
    Negative framing compounds anxiety in error states.

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-04 — Make the next step obvious. Every screen should have a clear primary action.

← The content model