Insight's job is to say what is worth worrying about this week, drawn from what the other tools already know.
This topic includes:
What the reading is
The project's headline figures, with the risk reading drawn from them.
The reading compares how much of the programme has been used against how much of the work has been finished, and flags where the two disagree. "58% of the programme is elapsed while 20% of the snags are closed" is the kind of sentence it produces — one that a project meeting can act on.
Where each number comes from
| Figure | Read from |
|---|---|
| Time elapsed | The project's start and target completion dates |
| Issues open and closed | The issues register |
| Overdue RFIs | RFIs past their due date and not answered |
| Outstanding submittals | Items not yet closed |
| Cost position | The budget against the forecast |
Nothing here is entered twice. If a figure looks wrong, it is wrong in the tool it comes from — usually a date that was never set.
Reading it honestly
Two habits make the reading useless: leaving issues open after the work is done, and never setting due dates. The first makes the project look worse than it is; the second makes overdue counts meaningless. Both are cheap to fix and neither is fixable here — they are fixed in the register.