RedHub AI
How the roll-up gate works
How the Meeting-to-Action Handoff gate works
This tool grades whether a meeting's action items actually got handed off. It reads 4 items and rolls them into one verdict — the worst, never the average — then a gate that can only make it worse.
The 4 items
An action item with no named owner is DROPPED no matter how many of the other four checks - due date, acceptance, system of record, definition of done - are set; 'the team' owns nothing. An owned item with zero of those four checks is dropped too. One dropped item is enough to roll the whole meeting up to HANDOFF BROKEN - never averaged away by the items that are fine.
Why: One item is fully tracked and one is a normal chase - just missing a due date and a definition of done. But two items are DROPPED: one has no named owner at all, and the other has an owner but none of the four support checks set. One dropped item breaks the handoff for the whole meeting, not just that item, so this reads HANDOFF BROKEN even though half the list is in good shape.
No single item is the crisis — the clustering is. The roll-up takes the worst, the gate escalates when trouble compounds, and it names the one thing to fix first. Grades the handoff, not people - your marks, not a benchmark, and not a record of anyone's performance.