An HR business partner who asks “who is leaving this quarter?” sometimes needs a sentence and sometimes needs a wall of names, dates, and open seats. The shape of the answer picks the tool. Kiweely Bridge (coming next) is the chat connection for a question. Kiweely Leaf (coming next) is the screen. Both run as the signed-in person against live Workday data and keep no copy of the rows.
What a board is for
Span of control, attrition, and open roles are spatial. You compare teams, you scan a quarter, you notice the seat that has been open since March. Leaf’s manager views are described as headcount, open roles, and who is out, for managers who rarely open Workday. An HRBP board is that idea aimed at the organizations where the HR Partner role is assigned.
Workday constrains a role-based HR Partner to the organizations on the role assignment. The board is only as wide as that constraint. A partner for one division who sees another division’s names is a security defect, the same class of defect as a manager seeing peer pay. The empty region is a correct result.
Numbers on the board should be numbers that person can already get from Workday: a supervisory organization they support, a turnover or termination report they can run, internal job postings they can see through Job Postings: Internal and Browse Jobs. This article does not name a universal attrition formula. Tenants define termination categories, and a board that invents a rate will not match the report HR already trusts. Point each tile at the report or query that HRBP can run, and label the time window the report uses.
Open roles on the board are requisitions and internal postings, not a private spreadsheet. Evergreen requisitions can be posted and still cannot be hired until someone links a job requisition. If the board shows “ready to hire” on an evergreen posting, it is ahead of Workday.
What chat is for
Chat fits when the partner needs one fact or a short explanation: how many people report to this manager, whether this requisition is posted internally, what Workday returned for a headcount question. Bridge (coming next) is built for that conversation in Claude, ChatGPT, and Gemini, with each person signed in as themselves. The answer disappears with the request. It is a poor place to scan forty teams for a pattern, because the partner cannot see the pattern and the exception in one glance, and the next question starts over.
| Need | Use |
|---|---|
| NeedOne number or a why | UseChat, Bridge (coming next) |
| NeedSpan, leavers, and open seats side by side | UseA Leaf board (coming next) |
| NeedWho the rows include | UseThe HR Partner’s constrained organizations |
| NeedWhere the figure is defined | UseThe Workday report that person can already run |
| NeedWhat gets stored | UseThe screen layout only. Not the headcount extract. |
A board that emails a CSV to a shared mailbox has left the pass-through. So has a chat session where someone pastes that CSV. The point of both products is to read live and drop the payload.
Publish it like any other screen
Leaf’s public page says an HRIS admin describes the screen, tests it, and publishes it, and nothing reaches employees until you say so. An HRBP board is a screen with a small audience. Test it as the partner and as a partner for a different organization before you publish. Tell us the board you want first. Bridge interest sits on the Bridge page if the same team also wants the question path.