Badge

A short label on a thing. One shape, three roles, and each role has one look: a status says where something is in its life, a tag says what it is, a flag asks to be noticed.

Playground

Ongoing
Role
Status
Size
<Badge status="active">Ongoing</Badge>

Roles

Pick the role from what the badge says, then the look follows. Never style a badge by hand to stand out: if it should, it's a flag.

Scheduled Ongoing Completed Failed

Status

Where a record is in its life: a mission, an upload, a lab order. Outline with a status icon; the icon carries the colour, the text stays plain. At most one per row.

CTD Water samples Private Generator

Tag

What a thing is or has: a method, a category, a property. Outline and neutral. A dot gives a category its own colour, which means nothing else.

Expired Hidden from customer New

Flag

The one thing on a row that should be noticed: expired, hidden, new. The only filled badge, so keep it rare. Not for lifecycle status.

Members 12 Inbox 3 Logs 99+

Count

How many are in there, next to a tab, a filter or a heading. Use Count, not a Badge. Primary only when they ask for action.

Status icons

Eleven shapes, one family. The ring fills as the work does: dashed, dotted, a pie, full. Everything still moving is one blue, so colour is left for the outcomes. The shape says the state, so it reads without colour.

draft Exists, nothing has started.
waiting Waiting on someone else: a customer, a lab, a queue.
scheduled Has its day and time, and waits for it.
progress Partly there. The pie fills as it goes, and full turns into done.
running The system is working on it now. Will settle by itself.
active Under way out in the world.
done Finished, as it should.
attention Stuck until someone here acts.
failed Ended badly. Someone should look.
cancelled Stopped on purpose before the end.
inactive Out of play: archived, replaced, expired, skipped.
Sampled 0/8 Sampled 2/8 Sampled 4/8 Sampled 6/8 Sampled 8/8

Directions

The sets we compared. Fill is the component; the others stay here for reference.

Setdraftwaitingscheduledprogressrunningactivedoneattentionfailedcancelledinactive
Fill (the component)

The ring fills with the work. One blue for everything moving, a squarer clock; outcomes are full circles.

Before

A clock in a second blue, and a live dot that read as a radio button.

Line

Every state an open ring with a glyph. Quietest, but done and failed lose their weight.

Fill (the component)

DraftPending quoteScheduledOngoingCompletedReschedule requestFailedCancelled

Before

DraftPending quoteScheduledOngoingCompletedReschedule requestFailedCancelled

Line

DraftPending quoteScheduledOngoingCompletedReschedule requestFailedCancelled

Every status, mapped

Each status in Kystdata picks one of the eleven states. Same state, same look, whichever record it's on.

Mission
Draft Pending quote Quote provided Quote rejected Scheduled Reschedule request Pending method changes Ongoing Paused Completed Cancelled
Project
Draft Pending quote Quote provided Scheduled Ongoing Completed Cancelled Archived
Data upload
Queued Processing Needs confirmation Completed Failed Cancelled Replaced Cleared
Lab order
Pending Ordered Sent Completed Cancelled Archived
Plan
Draft Published Active Completed Archived
Export
Queued Building Ready Failed Expired

In a list

Statuses in their own column read as a calm stripe, so the one that needs someone stands out by shape and colour. Tags stay grey. One flag, where it matters.

MissionDateStatusMethods
Starefoss ledning 12 Nov Ongoing
CTD Water samples
Hardangerfjorden 2026 Hidden 14 Nov Planning 2/5
CTD
Byfjorden resipient 18 Nov Scheduled
Visual range Water samples
Osterfjorden 3 Nov Completed
CTD
Sotra vest 1 Nov Reschedule request
CTD buoy

Rules

  • A status is always status= on an outline badge. Never a coloured fill, never a hand-drawn dot: the state lives in the icon, so it reads without colour too.
  • Map a new status to the closest of the eleven states before adding a shape. If two statuses look the same, they should mean the same thing to the person reading.
  • Override a state's tone only to make it quieter: a queued upload waits, but nobody needs to worry, so it's neutral.
  • Flags are rare: one per row at most, and never on every row of a list. If every row has it, it is a column.
  • Never a solid-filled badge. The only solid fill is a Count that asks for action.
  • Labels are one to three words, sentence case: "Needs confirmation", not "NEEDS CONFIRMATION" or "Needs Confirmation".
  • A badge isn't a button. If it opens something (a hover card, a link), it gets the hover and a tooltip or href, and the thing it opens explains itself.
  • sm in dense rows and next to text, md everywhere else. Don't mix sizes in one row.