Why the check is sage, and never red.

The first tracking indicator we drew was a red dot. Of course it was. Red is where every prototype starts, because red is the lazy way to say this is important — and a status indicator feels important while you are drawing it.

Then you put it on screen next to somebody's name, all day, and read what it actually says.

Red is not a colour, it is a mood

Red doesn't mean "the tracker is off". It means explain yourself. It puts the sentence in the imperative: resume, justify, respond. That is a fine mood for a smoke alarm and an unbearable one for a colleague's status while they are in a one-to-one they deliberately paused for.

This is not a subtle effect you need research to detect. An entire generation of remote workers has been trained by a decade of surveillance software to read a red status as an accusation, and they read ours the same way, because ours looked the same. The design was working exactly as built. The build was wrong.

The tracker was reporting a fact. The colour was making an allegation. Only one of those was in the spec.

The replacement is a sage check. It confirms rather than demands: you are here, this is counted, nothing is required of you. A receipt, not a verdict — which is the same distinction that governs how approvals work everywhere else in the product, arriving here as a colour.

The harder case is not "tracking". It is "not tracking", because that is where a monitoring tool usually starts shouting.

When a machine wakes from sleep and the heartbeat sees a gap it refuses to credit, the member gets a line of plain text:

Tracking paused while your computer slept.

Read what is missing. No red. No exclamation mark. No resume now pulsing in the corner. It states the cause, because the cause is exonerating — your laptop was shut, and we know it, and we are not asking you to account for the hours you spent asleep.

The uncounted time is uncounted. That is the whole event. Anything more than a sentence about it is the product editorialising on somebody's evening.

Refusing alarm everywhere would just be a different reflex. There is one place in the desktop app where we deliberately made something noisier than it needed to be — a small local badge in the footer, undimmed, when the app is talking to a development backend instead of the real workspace.

It looks out of place. It is meant to.

The two builds are deliberately signed with the same identity so a macOS permission grant survives switching between them, which means nothing else on screen distinguishes them. Get it wrong in one direction and a member's genuinely tracked work is stranded in a database only an engineer can read. Get it wrong in the other and development noise lands in a real workspace as somebody's evidence.

That is the test we ended up with, and it is narrower than "is this important":

Interface colour in this category of software is not decoration and it is not branding. It is the tone of voice in which a machine talks about somebody's working day to their employer, several hundred times, without ever being asked to justify itself.

So the question we ask of every state we draw is not is this the right colour. It is: read this aloud as a sentence about a person. Would you say it to them?

"You're here, and it's counted" — yes, easily, all day.

"Your tracker has been red for forty minutes" — that is not a status. That is a manager standing behind somebody's chair, rendered in CSS, and shipped to every screen on the team.

Questions, corrections, or a war story of your own? Write to hello@worktrackhq.com — a person reads every message.