The agenda is the coverage specification. Every line names the dimension it evidences, so a question the meeting never reached becomes a gap against that dimension rather than a silence nobody notices.
The weekly a delivery team already holds, written down as a specification rather than a habit. At a seven-day cadence the room accumulates its own history faster than any report written about it, so the comparison that matters — committed against landed — is between two consecutive meetings rather than between a meeting and somebody's memory of it.
Also called: Weekly stand-up · Sprint review · Team weekly · Delivery check-in · Planning session
6 lines, run every 7 days. The order is the running order, and it closes where it opened — on Accountability, a 7-day round trip.
Each carries a weight in the roll-up. A dimension with no evidence behind it is not scored at a middle value — it renders as unknown, and below the coverage floor the row reads never covered rather than green.
What the team committed to, against what actually shipped.
Commitments made in the room, and whether they land.
Whether the team leaves with the same understanding of what matters.
Impediments raised, owned and cleared.
How long a decision takes from raised to made.
Whether the whole room contributes, or three people do.
Deliberately. These are read from how the room behaved, not from what it worked through — you cannot schedule participation, so it can never be "never covered". Any dimension without a line can be thin, but it can never be a missed question.
Because each line names a dimension, the gap scanner can say which one went uncovered and for how long. These are the four states it raises, and each one is a different problem with a different fix.
The line has never been reached in this room. The dimension has no evidence at all.
It was raised and the room moved on without landing an answer.
It was covered, but not within the 7-day cadence this room type expects.
There is an answer and an action, and nobody's name is against it.
Team Rooms is one of eleven configurations of the same engine. The demo runs on fictitious teams and sample data — every number traces back to something somebody said in the room.