Why a green status report tells you nothing

Picture two phases on the same project, both marked green.

In the first, someone worked through every item, tested what needed testing, and a named person signed it off on a Tuesday afternoon. In the second, nobody has looked at it since it was planned. There was no problem to report because nobody went looking for one.

On the status report, those two phases are indistinguishable. Same colour, same row, same reassuring absence of commentary. And that, rather than any individual's optimism, is the real weakness of the green status report: it records the absence of bad news, and we read it as the presence of good news.

What the question actually asks

A status report is a question, and the question is is there a problem?

That sounds like a neutral thing to ask. It isn't. It puts the burden of proof on the problem: unless someone actively raises a concern, the answer defaults to fine. Green is what you get when nobody says anything.

Now consider who answers it. Mostly, it's people in the middle of the work. They're a little behind — most people on most projects are a little behind — and they expect to catch up, because historically they usually have. Reporting amber feels like an overreaction to a busy week. It invites a meeting, and the meeting takes time away from the catching up. So the rational answer, honestly given, is green.

Nobody in that chain is being dishonest. Each answer is a fair reading of the question as asked. The trouble is that the question isn't the one the reader of the report thinks was asked. The sponsor reading the report wants to know has this been verified? The people filling it in were asked have you hit a problem you can't handle? Those are different questions, and the report quietly substitutes one for the other.

A green that nobody examined

The phase nobody looked at is the important case, and it's more common than it should be.

It's usually a phase that isn't due yet, or one owned by someone who's been pulled onto something more urgent, or one that depends on input from the client side that hasn't arrived. That last one is worth slowing down on, because it's where reporting tends to turn into blame. When the data hasn't been cleansed or the process decisions haven't come back, it's easy to narrate it as the client falling behind. But what we've asked of them is substantial: make careful decisions about how their business will run in the new system, review data they've never had to look at this closely, and do it alongside the job they were hired for. That work is a second job done in the gaps of the first. Of course it moves at the pace of those gaps. The reporting problem isn't that it's slow — it's that a phase waiting on that work can sit at green, because nobody on our side has anything to report about it yet.

So the colour stays the same, and the phase looks identical to one that passed. Months later, when it turns out there was a problem all along, the conversation goes badly not because the problem was hidden but because the report implied something it never actually established.

Three states, not one

The honest alternative isn't a more pessimistic report. It's a more precise one. Instead of a single green, distinguish three states.

Confirmed. A named person signed it off, on a date. Not "the team", not "done" — a person who can be asked about it, and a date that tells you how old the confirmation is. This is the only state that means what most readers assume green means.

Claimed. Someone has said it's done, and the claim hasn't been checked yet. This isn't an accusation. Most claims turn out to be right. But a claim and a confirmation carry different weight, and when a phase is all claims and no confirmations, a reader deserves to know that.

Unexamined. Nobody has looked. Not "fine", not "on track" — simply not yet examined. This is the state that green currently hides, and it's the one that matters most, because it's where surprises live.

None of this requires anyone to work harder or report more often. It requires the report to stop collapsing three different situations into one colour.

Say it in words

The last piece is small and easy to skip, and it's what makes the difference six months later.

When there's no evidence for a phase, write no evidence recorded. In words, on the record, exactly where a reader would look for the sign-off.

The reason is that blank space is ambiguous. An empty cell next to a phase could mean it was checked and found fine, so nobody bothered to note it. Or it could mean nobody looked. At the time, everyone in the room knows which. Six months later — after a handover, a new sponsor, or an audit — nobody does. The reader is left reconstructing history from silence, and silence almost always gets read charitably.

"No evidence recorded" is uncomfortable to write. It looks like an admission. But it's the most useful sentence a report can contain, because it lets someone later tell the difference between we checked and it was fine and we never looked. Those lead to completely different conversations, and only one of them should be reassuring.

Why this is worth the discomfort

The objection is predictable: a report full of "claimed" and "unexamined" looks worse than a report full of green. Sponsors will worry.

They should — about the right things. A green report that turns red overnight is a far bigger shock than a report that honestly said "unexamined" for six weeks and then "confirmed". The first destroys trust in every future report. The second builds it, because readers learn that when it says confirmed, it means it.

And the people filling in the report benefit too. "Claimed" lets someone say they believe it's done without staking their reputation on a verification they haven't done. That's a more honest thing to ask of them, and a more honest answer to receive.

Green, as we use it, is a statement about silence. The fix is to stop letting silence stand in for evidence.

---

ProjectPlanOS has a Readiness view built on this distinction. Items move from claimed to confirmed when a named person signs them off, a claim is never shown as done, and where a phase has no evidence the view says "No evidence recorded" in words rather than leaving a gap.

If you're reading green reports you can't quite trust, asking which of those three states each line is in is the place to start, with or without us.