The status meeting writes itself.
Free to use · No credit card required
Most status meetings are a memory test
Go around the room, everyone recalls what they can, and the loudest update wins the attention. The work that quietly stopped moving three weeks ago never comes up, because nobody remembers to mention the thing they have not been doing. That is precisely the item the meeting existed to catch.
Four buckets, in the order they matter
- Completed since last sync — closes the loop and gives credit
- Blocked — the only bucket where the meeting can unblock something
- No movement in the window — the quiet items that usually slip
- In progress — a quick confirmation, not a discussion
Tie the week back to the quarter
- Objective progress alongside the task groups
- See which objectives have no active work against them
- Key results with real targets, not a percentage someone typed in
- Works for a single team or the whole company
What Meeting Mode gives you
Grouped by what needs saying
Tasks are bucketed into completed, blocked, stale, and in progress — the four things a status meeting is actually about.
Blockers surfaced first
Anything marked blocked leads the agenda, because a blocked task is the only category where the meeting itself can help.
A time window you choose
Look at the last day, week, or fortnight. Match the window to your cadence and the agenda matches the gap since you last spoke.
Objectives in the room
Current objective progress sits alongside the task groups, so the sync connects to the quarter rather than floating free of it.
Live, not a snapshot
Updates made during the meeting are immediately real. No transcribing decisions from a doc into the tool afterwards.
Presentable as-is
Turn it on and share your screen. There is no separate deck to build, which means there is no deck to skip building.
The best outcome is a shorter meeting
We would rather your weekly sync shrink than become a better-run hour. If everyone clears their stack each morning, most of what a status meeting covers has already happened asynchronously, and the meeting can be reduced to the blocked items and the decisions. Several teams using TIBLR have cut a weekly hour to twenty minutes on that basis. That is the goal — not a more elaborate ritual.