MCP Use Cases - Part 2: Two and a Half Beards, Episode 2 has landed 

Thanks for the insightful episode. Does the MCP also connect with Copilot? Haven’t seen it mentioned.

Hi ​@Simona Busuioc - this is a WIP, not live yet

Hi ​@Josh Rod  do you mind sharing the prompt you’ve used to create the PTO mapping? with all of the details?  (+ yes, its not legal advice) 

hi ​@Zach Jones 

for the secession planning app, which data do we need Bob to have in order to present that visual? 

also, can you please share the prompt you’ve used? I would like to try it also for us :) 

Hi Reut, sure thing!

Before you run it

• Connect the HiBob connector in Claude and make sure your account can read employee time-off policies.
• Set the sample size in Step 1. More employees per site gives better coverage but takes longer.
• Treat the output as a starting point for a conversation with your legal or payroll team, not a compliance ruling.

Build me a "Time Off Atlas": an interactive page that maps every site in our HiBob tenant, shows the time-off policies actually running there, and checks them against each country's statutory minimum.

## Step 1. Pull the data from HiBob (use the HiBob connector)
- List every site in the company, with its country, headcount and holiday calendar.
- HiBob exposes time-off policies per employee, not per site. So for each site, take a sample of employees (up to [3] per site, and different departments where possible) and read the time-off policies assigned to each one.
- For every policy you find, record: policy ID, name, unit (days/hours), allowance type (unlimited or allowance-based) and amount, cycle, minimum request, carryover rules, approval flow, and anything unusual (zero allowances, seniority tiers, attachment rules).
- Treat a site's coverage as the union of the policies across the employees you sampled. Sites with no employees are "greenfield".
- Before you build anything, tell me how many employees you sampled per site. I need that to know how far to trust the results.

## Step 2. Analyse
- Sort every policy into a leave category: annual, sick, maternity, paternity, parental, bereavement, carer's, jury/public duty, reserve/military, marriage, family and domestic violence, short-term disability, long service, time off in lieu, work-location tracking.
- For each site's jurisdiction, list the statutory leave requirements. For each one give the category, whether it's mandatory or only common practice, the minimum entitlement in plain words, and the law it comes from. Use state or province rules where they matter (New York, Ontario, and so on).
- Flag a gap when a mandatory category isn't covered by any sampled policy.
- Flag configuration drift. That means allowances below the statutory floor, templates from one country applied in another, the wrong holiday calendar for a site, employees at the same site on different policy sets, policies with zero allowances, and "unlimited" policies used where the law requires a balance you can prove.
- Quote the figures behind each drift flag (for example: "15 days granted vs 28 required, 13 short").

## Step 3. Build the page (single self-contained HTML artifact)
Tabs:
1. Atlas: a world map with a pin per site. Pin colour shows status (red = mandatory gap, blue = advisory gap only, green = covered, dashed ring = greenfield) and pin size shows headcount. Hover a pin to see a summary. Click it to lock the pin and open the site in the inspector. The header shows totals for sites, policies, statutory gaps and drift flags.
2. Coverage: a matrix with sites as rows and leave categories as columns. Each cell is covered, missing, or not mandated locally. Include a toggle for mandatory-only vs all categories.
3. Deep dive per site: the sampled employees and their policy IDs, the live configuration of each policy, the drift flags, and a statutory checklist (what's outstanding vs what's covered).
4. Templates: a build sheet for each gap, with suggested unit, allowance type, grant timing, cycle, minimum request, carryover and approval flow, plus a short "why" and a "watch out" note.
5. Build and import: tick the gaps you want to close, then generate a CSV or JSON of draft policies with a copy-to-clipboard button. Label the output as a draft spec to review and then build in Settings > Time off. Don't imply it can be bulk-imported.
6. Method: data source and date, sample sizes per site, limitations, and how HiBob models a time-off policy.

Design: clean and data-dense, with light and dark mode, and it has to work on a laptop screen. Add a legend for the map.

## Guardrails
- Show employees by role only, never by name. This page may get shared.
- Statutory figures come from your general knowledge and can be out of date. Mark any you're unsure of, say so on the Method tab, and put "Not legal advice. Confirm with local counsel before changing policies" on the Templates and Build tabs.
- A red cell means "not found in the sample". That's weaker than "not configured". Say this clearly on the Coverage tab.
- Keep the artifact private until I've reviewed it.

What to expect

• Sampling is the main limit. HiBob assigns policies per employee, so a site can hold policies that none of the sampled employees are on. Raise the sample size if a result looks wrong.
• Check the statutory figures. Claude's legal floors come from general knowledge. Entitlements that changed recently are the most likely to be out of date.
• The build output is a spec. You still create the policies in Settings > Time off. The CSV or JSON gives you the configuration to follow.
   

Feel free to share feedback on how it goes!

​@Zach Jones  any chance you’ve seen my comment above? 
:
 

for the secession planning app, which data do we need Bob to have in order to present that visual? 

also, can you please share the prompt you’ve used? I would like to try it also for us :)