This is not a score and it is not a rating. And it is thin — and the thinness is the finding. The machine will not pad this page with plausible-sounding wins to make Marcus look busier than the record says. If you're writing his review, the honest first move is to notice how little you wrote down, and why.
Only what's actually on file. There are two things, and inventing a third is exactly what this machine does not do.
Delivered
In progress
Praise heard · Feedback you gave
A month with nothing on file renders as a month with nothing on file. This is the quiet stretch, shown plainly.
| Feb | Mar | Apr | May | Jun | Jul | |
|---|---|---|---|---|---|---|
| Marcus | 2 meetings |
1 meeting |
April: nothing on file |
May: nothing on file |
1 meeting 1 note |
July: nothing on file |
A steady February, then a three-month gap — nothing written down in April or May, one meeting at the end of June, and nothing yet in July. Marcus is the easy one to under-manage, and the record shows exactly that.
Plain counts of what got written down — not a rating.
| One-on-ones logged | Notes on file | Notes carrying evidence | Feedback given |
|---|---|---|---|
| 4 this cycle | 1 | 0 of 1 | none this cycle |
Every meeting this cycle, newest first — each links its own record.
Open and closed, who owed what. Nothing is ever deleted.
| Commitment | Who | Raised | Due | Status |
|---|---|---|---|---|
| decide whether payments gets a second on-call engineer | you | Jun 30 | — | open · undated · 23 days |
| write the incident post-mortem | him | Mar 10 | Mar 17 | done Mar 16 |