A team status report that's verified, not guessed.

01 · The problem

It's due tomorrow and the answers aren't in.

You asked the team on Thursday evening. Two of five answered, one of those said "basically done", and at eleven o'clock three lines are still missing. So you write them from what you remember being true — and hope Tuesday agrees.

2 of 5answered before you started writing “basically”doing a great deal of work in that sentence

02 · What you need

Verified, or flagged — never quietly guessed.

Where a line points at a ticket and your tracker is connected, it's confirmed before it's written up as done — a claim the ticket doesn't back gets held, not pasted. Where she can't confirm, she doesn't hide it: that line is marked reported-only, right next to itself, so you send knowing which parts are checked.

1 of 2claims here didn't survive the check labellednot buried — you know what you're signing

03 · How it runs

The chasing stops being your evening.

Set where the asking happens and what a line gets checked against. Every step rewrites itself to match — she asks each owner individually so nobody anchors off someone else's answer, and the gap is visible before the deadline instead of at it.

04 · What it's worth

The template was never the hard part.

You came for a structure, so take one — five lines, fits a screen. But notice what it costs to fill in honestly: every line needs an answer from someone, and half of them need checking. Collecting the truth behind it is the part that eats your Thursday.