A nav badge signals unfinished work inside that destination

What it is

A badge on a navigation item is not decoration. It states that this destination contains unfinished work. Unread messages, approvals waiting, items in a cart not yet checked out. It moves “should I go in” from after opening to while still on the navigation. It is not a vague “there is a new feature here”, and not a page-level notice. Scope is pinned to this station.

Why it happens

Navigation is a choice field; a badge is a pending-work cue on one option. Sweeping a row of destinations, the badge raises expected payoff for that one: going in will clear something. Without it, unfinished work waits until someone happens to walk in, and handling is postponed. The cue must map back to objects inside the destination (which unread rows, which pending approvals), or it is only a red-dot anxiety source: go in, find nothing that corresponds, and the cue turns from a navigation signal into noise.

Because it sits on navigation, the badge also steers which path is taken. It should not appear on an entry that cannot handle those items (a read-only About). It should not mean “something somewhere in the system” — that is a global notice’s job. If scope leaks, every badged item looks equally urgent, the choice field is painted uniformly, and the cue dies.

Where it stops holding

A destination with no handleable objects inside (a pure content page) should not wear a badge to pull revisits. A marketing “New” is not unfinished work and should not use the same visual. For assistive tech, the badge must enter the item’s name (“Messages, three unread”), or visual and assistive users receive different choice fields. When unfinished work lives in a child and the badge sits only on the parent, people know this branch has work and still have to look one level down — that can be fine, provided the parent badge clears when the children do.

Applying it

• Badge only destinations where going in can handle the work, and let the inner list explain where the number or dot came from.
• Put the badge in the navigation item’s accessible name; do not rely on colour alone.
• Do not use the same badge for product updates or recommendations, or they will fight unfinished work for the signal.
• How to check: see a badge, go in, and point at the corresponding unfinished objects. If they cannot be pointed at, the cue is false. Then “which station is this dot about”; an answer of “the system is calling me” means scope leaked.

Related

• Within the group: E5.17.2 Large counts on badges need a compacted display · E5.17.3 A badge that never clears dulls sensitivity to new items · E5.17.4 Badge logic must match the actual state exactly
• Adjacent: E6.11 Badges and Dots · E5.02 Bottom Tab Bars
• Search terms: navigation badge · unread count · wayfinding cue