BadgeOS stores each badge, step, and rank as a post in the achievement-type hierarchy, and every award is recorded as user meta under _badgeos_achievements on the member. Each row carries a state that goes from pending, to awarded, to occasionally revoked, but the default admin only shows a flat list per member, which makes it slow to see how many submissions are waiting across the whole program.

SleekView Kanban points at the awarded achievements records, lets you pick the column that holds the state (the literal status entry inside the awarded achievement, or the related post_status on the achievement post for manual review badges), and renders one card per award. Each card shows the member, the badge title, the points value, and how long the submission has been waiting.

When a reviewer drags a card from Pending into Awarded or Revoked, SleekView writes the new value back through the BadgeOS award functions, fires the usual badgeos_award_achievement hooks so notifications and point totals update, and drops the card from the queue. Bulk grants still work the old way, but day-to-day program review finally feels like a queue.

A recognition program only works if it feels timely. The BadgeOS product is doing the right thing by tracking every award, but the admin experience makes review feel like archaeology, which means manual badges tend to bunch up at the end of the month. By that point the members who earned them have lost the thread and the reward feels detached from the work.

A kanban view changes the shape of that work. Instead of asking a program lead to remember who submitted a nomination, the Pending column is the work, and it stays in view until it is empty. The Banked column holds long-running peer awards without losing them, and the Revoked column makes audit decisions visible to the next reviewer.

Moving cards keeps the same hooks BadgeOS already fires, so point totals, related ranks, and member notifications stay correct, and the program team can answer questions about why a badge moved without digging through user meta. The work feels small because each card is small, and that is the difference between a reward program that hums and one that quietly slips.