Reading a project report that is hiding something

Project reporting almost never lies outright. It goes amber, it uses the passive voice, it reports activity where it used to report progress, and it moves the date without mentioning that it has moved.

The skill worth having is not detecting dishonesty. It is noticing the specific ways a report changes when the person writing it has stopped believing their own plan.

Activity replaces progress

A healthy report says what is finished. A struggling one says what is underway. The moment a status report starts describing effort rather than completion, something has stopped completing, and the writer is filling the space with the truest thing they can say.

The percentage stalls at a plausible number

Ninety per cent complete for three consecutive reporting periods is not ninety per cent complete. It is the number somebody picked when they still thought it was nearly done, held because revising it downwards requires a conversation nobody wants.

Risks become issues without anybody deciding

Watch for a risk that quietly moves from the risk register into the narrative as a fact of life. That transition usually happens without a decision, and it is the moment the project accepted something it had previously planned to prevent.

What to ask

Ask what would have to be true for the current date to hold, and listen for whether the answer is a plan or a hope. Ask who else has to do something, and whether they know. Ask what the writer would do with two more weeks, because the answer reveals what they actually think is blocking them.

None of this is about catching somebody out. A project manager reporting amber for the third time is usually the person most aware of the problem and least able to say it plainly in a room full of sponsors. The questions above give them a way to.